Practical working guide
A recurring service visit plan with an exception log
Plan recurring service work with a repeatable visit checklist and a separate record for each occurrence. Record skipped tasks and changed conditions as exceptions. Marking the overall customer account “complete” cannot show which visit happened or which work remains outstanding.
Separate the service plan from each visit
| Plan information | Occurrence information |
|---|---|
| Agreed scope and frequency | Visit date, assigned person and actual attendance |
| Standard checklist version | Checks performed and evidence |
| Access and escalation route | Access achieved or exception raised |
| Permitted consumables or methods | Actual use and items requiring review |
A missed task is an exception, not completion
Fictional example: a maintenance visit includes three checks. Two pass; the third cannot be performed because a room is locked. Record “visit attended, one check blocked”, identify the access owner and agree a next step. Do not copy last month’s pass result. Link the exception to this visit, so the next person sees whether it was resolved before another scheduled occurrence.
Review recurrence without concealing history
For each exception, retain reason, affected task, customer notification, owner and closure evidence. Update the standard plan only after reviewing repeated exceptions; preserve the checklist version used for past visits. Keep proposed extra work separate from the recurring scope. This template organises delivery records and does not imply automatic recurring billing, scheduling or equipment certification.
Check exceptions from the previous occurrence at the next briefing, while keeping each visit’s completion evidence separate.