How to prepare maintenance work orders for due service
Learn how to prepare maintenance work orders from approved plans, calendar and meter triggers, and evidence from a machine's last accepted service.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What maintenance work orders are
To prepare maintenance work orders, turn evidence that a specific asset is due for service into work a supervisor can review. Start with the asset's preventive maintenance plan, the approved schedule and task references for recurring service. Establish the last service the organization accepted, compare current dates or readings with the plan, and check whether an order already covers that same service cycle.
The result pairs a due-maintenance register with work order drafts for new cycles that need them. The register records why work is due, what evidence is missing, and who should handle it. A draft gives the next person the asset, approved task, and preparation requirements. The supervisor can then decide when and how to release the work based on staffing, parts, access, and the site's approval process.
What it does for the business
- Give production a useful view of upcoming workA dated list of work and its triggers gives production and maintenance a basis for discussing access around planned activity. They can coordinate around the asset's actual needs and raise schedule conflicts before a crew is booked.
- Keep the maintenance backlog accurateMatching findings to open orders lets planners route follow-up to the person already handling the cycle. Planners can focus on aging work and genuinely new orders without sorting through duplicate requests.
- Find preparation gaps before the work windowA draft that points to missing parts evidence or an outdated task reference gives the supervisor something specific to resolve. The team can check availability before committing people and setting aside production time.
- Improve records for the next service cycleClear completion requirements tell the crew what to record and the supervisor what to approve. An accepted completion with the right date and meter value gives planners a defensible starting point for the next cycle.
Maintenance work orders, step by step
Identify the asset, plan, and last accepted service
Each service decision starts with the asset and its approved baseline.
What to do
- Set the site, evaluation time and time zone, and planning horizon. Confirm which assets and plan versions are in scope, and record stable identifiers alongside the names people use on the floor.
- Read the approved plan and record which time and usage triggers apply. Retain the governing task reference and the rule for combining the triggers, and distinguish a disabled trigger from a configured one with missing data.
- Find the record of the last accepted completion and capture the date, meter value, and completion reference where applicable. Keep a planned date, canceled order, and recent reading in their own fields.
- Ask for an approved starting baseline when an asset enters service without prior completion. Carry any out-of-service or safety hold into the register and route it to the responsible person.
Why
A display name can refer to more than one machine, and a maintenance plan can change while the asset ID stays the same. The accepted baseline identifies the cycle you are evaluating and protects the due date from moving when an old order is edited or canceled.
Check calendar and meter triggers
A due decision should show the baseline, threshold, and observation behind it.
What to do
- For calendar-based service, apply the interval exactly as the plan defines it, then compare the resulting due date or time with the cutoff. Use the governing calendar convention if the plan specifies months or business days.
- For usage-based service, add the configured interval to the accepted completion meter in the same unit. Check that the latest reading belongs to the asset, falls within the allowed age, and was observed by the evaluation time.
- Investigate a reading below the baseline or prior accepted reading. For a reset or replacement, ask for the approved record that explains how cumulative usage carries forward before you use the new reading.
- Apply the approved rule for combining triggers. Under a whichever-comes-first rule, either satisfied trigger makes the cycle due. If neither is satisfied and one cannot be evaluated, keep the status unresolved.
Why
Calendar and usage triggers can turn due at different times. A machine that sees little use can still reach a time limit, and a heavily used machine can reach a usage threshold early. Showing each trigger separately lets the planner act on supported due work while asking for the missing reading.
Match existing work and prepare new drafts
A new observation can change the due status while the service cycle stays the same.
What to do
- Match open orders to the asset, plan, revision, and last accepted completion. Check whether an inspection referral already points to that cycle, and route follow-up to the open order's owner when you find a match.
- Hold a new draft when the cycle identity is unclear. Resolve older completion-looking or canceled records against the accepted service evidence before recalculating from a different baseline.
- For a new due cycle, write the asset and site, governing task reference, trigger, required skill, responsible owner, proposed timing, parts evidence, and dependencies. Give unknown items a named follow-up or ask for an owner.
- State which completion record the supervisor will need. Refer safety-critical repair findings to the authorized person with the observed evidence and keep any work holds visible.
Why
Duplicate orders can pull parts and people toward the same work while leaving the real backlog hard to read. A draft linked to a cycle gives the supervisor a clear review item, and the evidence it requests at completion supports a clean start to the next cycle.
Review the evidence and the ability to release work
Due status tells you when the plan calls for service, and release requires its own checks.
What to do
- Recompute a due threshold and check the equality case where the observation reaches that threshold. Verify dates, units, observation times, and any continuity record used to interpret meter history.
- Trace a draft to the current approved plan and confirm it does not duplicate an open order. Review the draft and the source record together when identifiers, aliases, or plan versions are similar.
- Check that the draft names the task reference, required skill, parts status, and any site dependency. Have the authorized supervisor confirm the people, materials, and instructions before releasing work.
- Specify the evidence the supervisor will accept after the job. Make the asset, service date, cycle, and meter reading traceable to the completed task where they apply.
Why
A sound due calculation can coexist with missing parts or unresolved site access. Reviewing release requirements gives the supervisor time to handle those gaps. Checking the completion evidence now also helps prevent a later update from starting the next cycle on the wrong date.
Hand over due work and evidence gaps
A useful maintenance handoff tells each owner what to act on and what to verify.
What to do
- Lead with due work that can move into preparation. Give each cycle a distinct row with the trigger, evidence, proposed action, and responsible person, and link existing orders where relevant.
- Bring unresolved baselines, stale readings, and missing plan references into the same handoff as specific evidence requests. Show which assets or cycles the review actually covers.
- Ask the responsible planner or supervisor to confirm draft details and release work through the site's process. Route held work directly to the person who can resolve the condition.
- Keep accepted service records with the asset and plan. Carry remaining gaps into the next review and update the baseline only from accepted completion evidence.
Why
The supervisor needs to know which orders require action and which questions can wait for a reading or record. Coverage helps distinguish a site with no due work from a review that had too little evidence to decide.
Common mistakes
- Starting the clock from a canceled orderUse accepted service evidence or an approved starting baseline for the cycle.
- Using a reading from the wrong unit or assetMatch the asset ID and unit before comparing the reading with the threshold.
- Ignoring a configured trigger with missing evidenceKeep the trigger visible and ask for the missing baseline or reading.
- Drafting again after each new readingMatch the cycle against existing work before creating another draft.
- Treating due work as ready for releaseHave the responsible supervisor confirm the required people, instructions, and parts.
What a good result looks like
- One row per asset, plan revision, and service cycle with a clear evaluation cutoff.
- A traceable baseline, interval, observed value, and status for each configured trigger.
- Existing order references or new drafts that explain the action and ownership.
- Visible holds with specific evidence requests and people who can resolve them.
- Completion requirements that connect accepted service back to the correct cycle.
And then what? Using the result
- Take due items to the next production and maintenance planning discussion to agree on access and staffing.
- Have parts owners confirm availability for the orders the supervisor wants to release.
- Send uncertain readings, missing baselines, and duplicate records to the people who maintain asset or service history.
- Capture the supervisor's accepted service record so the next calculation starts with the right baseline.
When to run it
- Before setting the maintenance scheduleUse a fresh cutoff to identify work that needs an owner, parts check, or site access decision.
- After a meter replacement or handoverReview the approved continuity and baseline records before relying on the new readings.
- When the same service appears on several listsReconcile the inspection referral, preventive plan, and open orders against the same service cycle.
Questions people ask
How do you prepare maintenance work orders?
Confirm the asset, approved plan, and last accepted service, then test the plan's due criteria and match open orders. Draft work for new due cycles with the evidence a supervisor needs to review and release it.
How do you decide when preventive maintenance is due?
Compare the evidence with the applicable calendar or usage thresholds in the approved plan. For a whichever-comes-first rule, either supported threshold can make the work due.
What if a meter reading is missing or stale?
Mark the usage trigger unknown and ask for a usable reading. A valid calendar trigger may still establish that service is due, depending on the plan's rules.
How do you avoid duplicate maintenance work orders?
Check existing work against the asset, plan revision, and cycle baseline before writing a draft. Route a matching open order to its owner and link any inspection referral.
What should a maintenance work order include?
Include the asset and location, approved task reference, due evidence, required skill, owner, proposed timing, parts and dependencies, and completion requirements. Identify gaps so the supervisor knows what to resolve before release.
Does a closed order reset the maintenance interval?
Use a closed order as the new baseline only when it supplies accepted completion evidence for that asset and plan. Check the date and meter value the next cycle requires.
More jobs in Ops
Prepare maintenance work orders, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac