Digital work orders, from request to invoice.

Four work order types and a status cycle that matches the field

Every work order is classified as preventive, corrective, inspection or calibration — the classification that feeds your maintenance KPIs and separates planned work from firefighting.

The status cycle runs from open to billed, through in progress and on hold. Beyond it sit two outcomes most systems ignore: cancelled and, above all, unrealized.

• Four priority levels — critical, high, medium and low, visible in the list, the calendar and the technician's app.
• Unique code per company — generated automatically on creation, so you can reference the work order in an email, a contract or an invoice.
• Controlled reopening — a cancelled, completed or unrealized work order can return to open; a billed one cannot — that is an accounting decision, not an operational one.

Four entry points, one flow

Execution captured as it happens

Records written afterwards are records invented afterwards. In Atus the technician documents the job while doing it, and every event carries the real time it occurred.

• Checklists with evidence — checkbox, free-text or single-choice items, grouped into sections; an item can require a photo before it can be completed.
• Before and after photos — stored by type, rendered as a gallery in the report — and mandatory if your company configures it that way.
• Time logging — start and end entries produce the actual hours, compared against the estimate in the report.
• GPS checkpoints — coordinates stamped at key moments as proof of attendance.
• Technician and customer signatures — captured on screen, or sent as a link so the customer signs on their own phone.

“Unrealized”: the status that rescues a wasted visit

The technician drove out and could not do the job: the gate was locked, the machine was running, nobody had the key. Marking that completed corrupts your KPIs; marking it cancelled erases a trip you already paid for.

In Atus that outcome has its own status, with a mandatory free-text reason and a timestamp. The visit still counts, the reason stays in the history, and the demand is not lost.

An optional automation returns an unrealized work order to open on its own — at the turn of the day or after a number of hours you choose — with a fresh execution deadline so it does not come back already overdue.

Finding the right work order among thousands

The work order list is the most used screen in the system, so it was built to filter fast and to be shared: every filter you apply goes into the URL, and the view you assembled can be sent to a colleague or bookmarked.

• Combinable filters — free text, customer, asset, technician, status, priority, date range, overdue, and with or without a contract.
• Your own tags — a colour-coded vocabulary your company defines — area, shift, billing bucket — filtered with AND logic.
• Sort by any column — with stable pagination that never repeats or skips a row as you page through.
• Archived kept separate — deleted work orders move to an archive view; nothing ever leaves the database.

Services, fees and parts on the work order itself

A work order carries what was charged, not only what was done. Three independent collections — services, fees and parts — each with quantity, unit of measure and unit price.

Amounts are stored as whole cents, so no rounding error accumulates through the monthly close. Parts can come from the catalog or be typed in the field when the item was not registered yet, inheriting the correct unit from the catalog — so a part sold by the litre is never counted in pieces.

Every move is recorded

Each status transition stores the previous state, the new one, the reason, the author and the timestamp. Alongside it, an event log keeps the other meaningful changes to the work order.

That history is what answers the hard questions months later: who reopened this work order, why the deadline moved, when the part was added, who approved the extra cost.

The report your customer receives