How to write a repair ticket from a photo or message
A repair ticket is the written record that turns "the machine is making a noise" into work someone owns. This guide shows how to write a useful ticket from nothing more than a photo or a short message sent by an operator. It matters because a vague report costs a second phone call, and a second phone call can cost an hour of downtime.
Why this matters
In a garment unit in Tiruppur with sixty sewing machines, an operator sends the supervisor a photo of a needle bar that has bent and a line saying "machine not working". The supervisor knows which machine, but the mechanic does not. He walks the floor, asks questions and comes back for a tool. A ticket written from that same photo, with the asset number, the symptom and the risk, would have saved him the walk and told the supervisor whether the line could move to another machine.
Before you start
- A tag or number on every machine, matching the asset register.
- An asset register with location, model, last service date and the engineer responsible.
- A simple ticket form with fixed fields: asset ID, reporter, time, symptom, risk and photo.
- A phone with a camera at each section, and a rule that photos include the asset tag.
- A short list of what counts as unsafe, such as exposed wires, smoke, leaks and broken guards.
Step by step
- The operator takes the photo with the asset tag in the frame, and a second close-up of the problem area. If a photo is not possible, the operator sends one line stating the machine number, what happened and when. No ticket should start without the asset ID.
- The person receiving the photo or message, usually the supervisor, copies the facts into a fault ticket: asset ID, time, reporter, symptom in plain words and the attached photo. The symptom is written as what was seen or heard, such as "needle bar bent, needle strikes plate", and not as a guess like "motor issue".
- The maintenance engineer reads the ticket, checks the asset register for the machine's history, and sets the risk: unsafe, line stopped, or running with a problem. If it is unsafe, the engineer asks the operator to switch off and tag the machine before anything else.
- The engineer calls the responsible person and records the name and time. The plant head sees the ticket if a part must be bought or a vendor is needed, and adds the decision and estimated cost to the repair note.
- After repair, the operator tests the machine on real work, such as stitching a sample piece, and writes the result in the test record. The photo of the repaired part can be added to the same ticket.
- The maintenance engineer logs the time lost in the downtime log, from the moment the ticket was opened to the moment the machine was released.
- The engineer adds one line on prevention: a part to keep in stock, a check to add to the weekly round, or a training point for operators. This line is what stops the same photo arriving again next month.
Who does what
| Role | What they do | Record they own |
|---|---|---|
| Operator | Takes the photo, reports the fault, tests after repair | Fault ticket and test record |
| Maintenance engineer | Reads and risk-rates the ticket, calls the responsible person, logs downtime | Asset register and downtime log |
| Plant head | Approves vendor or parts spend | Repair note |
Common mistakes
- Sending a photo with no asset tag, which makes it a guess about which machine it is.
- Writing a diagnosis in the symptom line instead of what was actually seen.
- Opening a new ticket for every message about the same fault, so the history is scattered.
- Skipping the risk rating, which means a safety issue waits in the same queue as a cosmetic one.
- Closing the ticket when the part is replaced and before anyone has run the machine on real work.
How to tell it is working
- Repeat failures. Count the tickets in the last quarter where the same machine had the same symptom as an earlier ticket. Divide by all tickets. A falling figure shows that the prevention lines are being acted on.
- Mean repair time. For all tickets closed in the month, add the hours from opening to tested release and divide by the number of tickets. A good ticket should shorten this, because the engineer arrives knowing what to bring.
- Unresolved faults. Count the tickets still open at month end. List any that are older than a week. These need a reason on the ticket and a date for the next step.
Questions people ask
Who owns fault to fix?
The maintenance engineer owns the ticket through to closure, and the plant head owns approvals for spend. The operator who reported owns the first facts and the test after repair. One name should always appear against an open ticket.
What is the minimum record for fault to fix?
A ticket with the asset ID, time, symptom and photo, a repair note, a test record and a downtime entry. These four records let anyone trace what went wrong and how long it took.
When should a case stop?
A ticket stops when the machine passes its test and the downtime is logged. If the repair is a temporary fix, keep the ticket open with the permanent repair as a dated action rather than closing it.
Can a spreadsheet support this stream?
Yes. One row per ticket, with columns matching the form, and a folder for photos named by ticket number, is enough for a small unit. Keep the asset IDs identical in every sheet so the history of a machine can be filtered quickly.
What should the owner review?
The owner should look at tickets that stayed open longest, machines with repeated tickets and the cost of vendor repairs. Reading five or six photos and notes from the month often shows more than the totals do.