When to use it
Use this when a fault needs a clear history or will pass to another technician. Start with the effect on the school day, rather than a guessed technical cause.
The blank template: what to record
- Reference, time and owner
- Use the approved ticket reference, the time the fault was reported and the role responsible for the next action.
- Impact and scope
- State which rooms, services and tasks are affected, and which checked examples still work.
- Observed evidence
- Copy the exact error and record relevant timestamps. Link to restricted evidence in the approved system.
- Checks and changes
- Record each check, its result and any authorised change. Separate observation from interpretation.
- Next action and update
- Give the next check, its owner and a specific update time. Keep unresolved work open.
- Outcome, verification and learning
- Record the recovery test, confirmation from the affected user and one practical improvement.
Download the TXT version to edit these headings, or print the PDF pack for a paper draft.
Fictional training example
A completed example
- Reference, time and owner
- DEMO-104, 08:35. Classroom support technician.
- Impact and scope
- One teaching-room display reports No signal. The laptop screen works. The next lesson starts at 08:50.
- Observed evidence
- Display is on HDMI 2; the labelled laptop cable is connected to HDMI 1. No wider outage has been established.
- Checks and changes
- With the teacher's agreement, selected HDMI 1. No settings on the laptop or network changed.
- Next action and update
- Technician to verify the lesson display and audio before 08:45.
- Outcome, verification and learning
- Teacher confirmed the intended slide and audio played. Technician to update the input label and review the classroom quick card this week.
Check the finished record
- Could another technician continue without repeating your checks?
- Does every open action have an owner and update time?
- Does the recorded outcome describe a real verification test?
Use an explicit “unresolved” or “workaround” outcome when a service has not been fully restored. A neatly completed form is useful only when it represents the evidence accurately.
Put it into practice
Choose one recent, non-sensitive example with your team. Ask another person to read the draft and explain the next action. Revise any field that leaves them guessing, then transfer the agreed structure into your approved record system.