Write the plan per asset as tasks with a frequency and an owner, put due work where technicians look every day, record every completion, and move repeat breakdowns into the plan.
Why maintenance plans fail
Almost every plant has a maintenance plan. It lives in a binder, a wall chart, or the head of the senior technician. It fails for predictable reasons: nobody is reminded when a task is due, production pressure pushes it back a week and then another, and nothing records whether it was done. The first sign of a problem is a breakdown, which is exactly what the plan was meant to prevent.
Preventive maintenance is not hard to understand. It is hard to keep doing. The system's job is to make the next task obvious, put it in front of the right person, and make skipping it visible.
Write the plan per asset
In Sundial's Assets & Maintenance module, each asset that needs upkeep gets an asset maintenance record listing its tasks. Each task has a description, a type (preventive or calibration, for example), a frequency (daily, weekly, monthly, quarterly, half-yearly, yearly and longer), a start date, and the person it is assigned to. The next due date is calculated from the frequency and the last completion.
Write tasks so that someone new could do them. "Service compressor" is a reminder for an expert. "Check oil level, replace intake filter, drain condensate, record discharge pressure" is a task anyone qualified can complete and anyone else can verify. Attach the manufacturer's checklist where you have it.
Start with the assets whose failure stops production or creates a safety risk. A complete plan for every chair in the office can wait.
Put due work where people look
A maintenance team does not open a planning report each morning. They look at their own list. Sundial assigns maintenance tasks to people, so each technician sees what is due and overdue for them, on a phone on the shop floor as well as on a desktop.
For the maintenance manager, the useful view is overdue tasks by asset and by person. An overdue list that grows week after week is not a discipline problem to lecture about; it is a capacity signal. Either the plan is too ambitious for the team, or production is not releasing machines for planned work. Both are conversations to have with evidence.
Coordinate with production planning. A task that needs a machine stopped for four hours should be scheduled into a window the planner knows about, not discovered at the start of a shift.
Log every completion
When a task is done, the technician records it in the maintenance log: the date, what was done, any readings, and notes on anything found. The next due date moves forward from the actual completion. If the task was skipped or only partly done, that is recorded too.
The log is what makes the plan trustworthy. An auditor, an insurer or a customer asking for calibration records gets a list, not a promise. More usefully, when a machine does break down, the first question, when was it last serviced and what was found, has an answer in seconds.
Repairs, costs and feedback into the plan
Breakdowns still happen. Record each one as an asset repair: the failure, the dates the asset was out of service, the work done, spare parts consumed from stock and any external service cost. Parts used are issued from inventory against the repair, so stock levels and repair cost stay right without a separate entry. Repairs that extend the asset's life can be capitalized into its value.
Over time, repair history per asset becomes the most useful input to the plan. A machine that keeps failing in the same way needs a new preventive task or a shorter interval. A machine whose repair cost keeps climbing is a replacement decision, and the asset register already holds its book value for that conversation.
Downtime entries from production complete the picture: how long the asset was unavailable, not just what the repair cost. We are building Sundial so an agent can draft a monthly maintenance review per asset, combining tasks done, tasks missed, repairs and downtime, and suggest plan changes for the maintenance manager to accept or reject.





