Preventive maintenance that opens its own work orders.

From plan to work order without relying on anyone's memory

A preventive plan starts in the same wizard that opens any work order: pick the type, priority, customer, asset, assignee and checklist, then switch the scheduling from one-off to recurring. From then on the plan runs by itself.

A server routine checks every plan once an hour. When an occurrence falls due, the work order is created with its own code, the plan's checklist copied item by item, the technician already assigned and the origin “schedule” written to its history — so nobody mistakes a plan-generated job for one opened by hand.

• One work order per occurrence — each visit keeps its own record, photos, parts and report, instead of one form overwritten every month.
• Checklist inherited from the plan — the technician gets the right inspection list without anyone attaching it.
• Traceable origin — the creation event says the job came from the plan, not from a person.

Nine frequencies and three ways to end

Plans accept the intervals real maintenance programs use: daily, weekly, biweekly, monthly, bimonthly, quarterly, every four months, semiannual and annual.

You also decide how long the plan runs. Once its end condition is met the plan deactivates itself and stops generating work orders — nobody has to remember to switch it off.

• Never — for equipment that stays in your care indefinitely.
• On a date — aligned with the end of a contract term or a warranty.
• After a number of occurrences — twelve monthly visits, four quarterly ones — and not one more than was sold.

Your team's schedule by month, week and day

The agenda in the technician's pocket, even with no signal

In the app, every technician has a monthly agenda with their work orders and upcoming maintenance, filterable by orders, upcoming or everything. Overdue items are flagged, and each entry shows the estimated hours for the job.

The agenda is part of the app's offline cache: technicians check their schedule inside a cold room or a basement, and plan-generated work orders run through the same offline flow as any other job.

Adjust the plan without rewriting the past

Everything on a plan can be changed later: title, description, type, priority, customer, asset, assignee, estimated hours, initial notes, checklist, frequency, start date and end condition.

A plan can also be paused without being deleted — the crew is on holiday, the machine is down for a refit, the contract is being renegotiated. Work orders already generated keep what was recorded on them; the change applies from now on.

Planned work kept apart from firefighting

Every Atus work order is classified as preventive, corrective, inspection or calibration. The classification travels with the job through the list, the filters, the report and the billing close, and it is what shows how much of the week was planned and how much was firefighting.

If you sell maintenance, each customer can carry a default price for preventive, corrective, inspection and calibration work. And a preventive visit that fails in the field is not lost: when the technician cannot do the job, the work order becomes “unrealized” with the reason recorded, and an optional automation reopens it with a fresh deadline.