Coordinators, managers and assigned engineers
Recurring maintenance and checklists
Define your own maintenance intervals, generate due work and retain versioned inspection results.
What to do
- Open Maintenance. Under Checklist templates, create a name and up to 50 clearly written steps. Mark the steps that must have a result before a report can be prepared. Give a reason for the new template.
- Create a maintenance plan. Select equipment, its assigned technician, first due date, interval, days/weeks/months and the plan time zone. Select a checklist version when required. The software does not supply manufacturer or statutory intervals.
- Choose automatic generation only if your organization has automatic processing enabled. Otherwise use Generate this due occurrence on or after the due date. A due occurrence creates one case and one unscheduled work order; repeated requests for that occurrence return the same order.
- Review the generated work-order link, then use the normal appointment and visit workflow. The due date is a maintenance deadline, not a booked appointment. Older missed occurrences are retained individually rather than skipped.
- The engineer opens the visit report. A maintenance checklist is attached automatically with the version chosen by the plan. For other report drafts, choose Attach checklist. Once attached, its template version stays fixed.
- For each step choose Pass, Fail or Not applicable. Explain failed or not-applicable results. Save checklist results. Required unanswered steps prevent report preparation; a documented failure remains visible and does not mean that equipment is safe.
- Review the checklist in the prepared report and PDF before confirmation. To correct a confirmed report, use the existing amendment process; earlier report versions retain their original results.
- Pause a plan with a reason to stop new occurrences. Resume it to continue from its outstanding due date. For a different interval, equipment, technician or checklist, pause the old plan and create a reviewed replacement. Generated orders are preserved.
- Record measurements with the saved unit and equipment-approved inclusive limits. With no configured limit, select a reviewed result yourself; the system makes no automatic pass assumption.
- Follow-up questions appear only when the earlier result matches their condition. Explain failed or unavailable checks. Save and reload before preparing the report; inactive answers are cleared. Signed report snapshots preserve the original checklist version and values.
Before you continue
Monthly recurrence is anchored to the first due day. A plan starting on 31 January is due on the last day of February, then 31 March. Dates use the plan time zone and are not shifted by daylight-saving clock changes.
Automatic processing works only for explicitly enabled organizations and plans. Each pass processes one due occurrence per plan. Paused plans, moved equipment and unavailable technicians require review. No emails, invoices or traffic requests are generated.
Editing a checklist template creates a new version. Existing plans and attached reports keep their chosen version. A recorded pass is a service result, not a certification.
Questions and troubleshooting
Why can I not generate an occurrence?
Check whether the plan is paused, its due date is still in the future, its equipment moved to another customer or its technician is inactive. Reload after another user has generated an occurrence.
Can I replace a required maintenance checklist on the report?
No. The plan pins a specific version so that its required checks cannot be silently changed. Correct the results through the draft or amendment workflow. Use a replacement plan for future template changes.
Why is an old due date still shown?
The system preserves each missed occurrence. Review the backlog with the responsible coordinator; it does not silently declare old maintenance complete.