Fault-to-fix: intake and evidence form
This form captures a fault at the moment it is reported, whether it is a machine stopping, a customer complaint about a delivered item or a failed service visit. The person who receives the report fills it in, and the technician or supervisor who acts on it uses it, so nobody has to ask the reporter the same questions again.
When to use it
Use it for every fault, however small, the first time it is reported by a staff member, customer or visitor. A fault that is only mentioned in passing and never written down is the one that returns, so start the form even before the cause is known. Keep a few printed copies at the front desk, on the shop floor and in the service vehicle, or keep the same fields in a shared sheet, so the form is never more than a moment away.
The template
| Field | What to enter | Source record | Owner |
|---|---|---|---|
| Fault number | Next number in the fault log | Fault log | Person receiving the report |
| Date and time reported | Exact time, not just the date | Call, message or visit note | Person receiving the report |
| Reported by | Name, phone number, role or customer | Call or message | Person receiving the report |
| Asset, product or service | Machine name and tag, batch or invoice number, or service visit reference | Asset list, invoice, job sheet | Person receiving the report |
| Location | Branch, line, room or customer address | Site list | Person receiving the report |
| What happened | Symptom in plain words, when it began, how often | Reporter's account | Reporter, written by receiver |
| Evidence collected | Photo, video, reading, sample kept, error note | Files and sample label | Supervisor |
| Severity | Stops work, slows work, risk to safety, cosmetic | Severity guide | Supervisor |
| Assigned to and by when | Technician name and promised time | Roster | Supervisor |
| Customer or user told | Date, time and what was said | Message or call record | Person receiving the report |
How to fill it
- Fault number: never skip or reuse a number, even for duplicates. Link duplicates to the first one.
- Reported by: a phone number matters, because the technician may need to call back.
- Asset, product or service: use the tag or batch number, not "the big machine".
- What happened: record the reporter's words first. Add your own observations in a separate line.
- Evidence collected: a photo of the fault plus one showing the asset tag is enough. Keep a sample of a defective item and label it with the fault number.
- Severity: use your own written guide, and raise it later if more is learned, but note the change.
- Assigned to and by when: a name and a time, not a department.
Example row
| Field | What to enter |
|---|---|
| Fault number | 0452 |
| Date and time reported | 5 Nov, 10:40 |
| Reported by | Sunita Rao, retailer, 98XXXXXX10 |
| Asset, product or service | Batch 24-118, 40 cartons, invoice 3187 dated 28 Oct, worth ₹86,400 |
| What happened | Seals leaking on about 6 cartons, noticed on opening, not before |
| Evidence collected | 4 photos, 2 leaking packs kept and labelled 0452 |
| Severity | Slows sales, no safety risk |
| Assigned to and by when | Vikram (quality), visit by 6 Nov, 5 pm |
Review and sign-off
- The supervisor checks that each form is complete before work starts, and signs it.
- The operations head scans the week's forms for missing fields and repeat assets.
- Escalate to the owner at once if severity is set to risk to safety, or if the same batch or asset appears in more than one form within the week.
Keeping it up to date
- Add a field when you find yourself asking the same question twice, and remove one that is always blank.
- Keep photos and samples with the form number as the file or label name.
- Keep forms for the period your CA or the law requires, and at least as long as any warranty or complaint period you offer.