Process templates
Maintenance Request Process Template
When nobody knows how to report a fault, small issues become downtime. This template shows the flow from report to test and the urgent/planned split.
Free. Lanes, steps and approvers come ready; you can change everything.
Process flow
Each row is a role (swimlane); steps run left to right.
| Reporter | 1 · StartReport the fault | 6 · EndTest and hand back | ||||
|---|---|---|---|---|---|---|
| Maintenance team | 3 · StepRespond immediately | 5 · StepCarry out the repair | ||||
| Maintenance lead | 2 · DecisionSet the priority | 4 · StepSchedule the work |
Step by step
Report the fault
- Location and machine stated
- Photo attached
Set the priority
- Urgent → Step 3: Respond immediately
- Planned → Step 4: Schedule the work
Respond immediately
Schedule the work
Carry out the repair
- Safety measures taken
- Parts replaced logged
Test and hand back
Who does what? (RACI summary)
R: responsible · A: approves
| Step | Reporter | Maintenance team | Maintenance lead |
|---|---|---|---|
| Report the fault | R | ||
| Set the priority | R | ||
| Respond immediately | R | ||
| Schedule the work | R | ||
| Carry out the repair | R | ||
| Test and hand back | R | A |
When to use it
- Faults are reported by phone and get lost
- Maintenance priorities cause disagreement
- Repairs are not tested before handover
Tips
- Stick the request-form QR on the machine so faults open as jobs.
- Make safety measures a required check in the repair step.
- Let the maintenance lead approve the handover.
More process templates
Run the process with your team on one map
Open the template, give each step an owner and a date, and send it to your field team as step-by-step instructions and QR labels.