From the makers of Equipment Maintenance Log — a maintenance log you keep by voice
Equipment Repair Request Form
An equipment repair request form should capture five things: which machine, what is wrong, how urgent it is, who reported it, and the current hour or mileage reading. Add a photo and a status that stays open until the repair is logged. Below is a ready form you can copy into a document, a spreadsheet or a chat.
The form
| Field | Fill in |
|---|---|
| Request date and time | |
| Reported by (name, phone) | |
| Machine / unit number | |
| Location (job site) | |
| Hour meter or odometer | |
| What is wrong? (symptom, not guess) | |
| When did it start? Constant or intermittent? | |
| Safe to operate? | Yes / Yes with limits / No |
| Priority | Critical / This week / When convenient |
| Photo or video attached | Yes / No |
| Assigned to | |
| Date repaired and hour reading | |
| Work done and parts used | |
| Status | Open / In progress / Waiting on parts / Closed |
Priority levels people can use
- Critical: machine is unsafe or stopped and blocking work. Mechanic called now.
- This week: machine runs, but the problem will get worse or limits production.
- When convenient: cosmetic or minor; fold it into the next scheduled service.
Defining these in writing prevents the daily argument about what "urgent" means.
How operators should describe a problem
Symptoms beat diagnoses. Compare:
- Weak: "Hydraulics shot."
- Useful: "Boom lifts slow when hot, after about an hour of work. Noise from pump side. No leaks seen. 3,410 hours."
Ask operators to add three things: when it happens, what they were doing, and what they already checked. A 20-second voice message with a photo beats a text that says "it's broken."
Why requests get lost
- Requests are made verbally on site and forgotten by the time anyone reaches the shop.
- The note has no unit number or hours, so the mechanic cannot tell which machine or how it has changed.
- No one owns the request, so it is not clear whether it is assigned.
- The repair is done but never written back, so the same request is made again.
Fix the first by making it easy to report from the field, and the last by requiring that every closed request records the work and the hours. These records also feed maintenance planning, because repeating problems show up in the history.
Handling it in the app
In Equipment Maintenance Log, an operator can simply post in the machine's chat: "Skid steer 2, left track slipping when turning, 1,905 hours" with a photo. The AI assistant records it as a defect with the date and hours, and the whole team sees it in that machine's history. The mechanic replies with the repair, for example "Adjusted track tension, replaced idler, 1,908 hours," and both entries sit together in the service history. Entries can be reviewed and corrected, since AI can make mistakes. See logging by voice.
FAQ
Do I need a paper form?
No. The format matters less than capturing the same fields every time. A spreadsheet, a shared document or a machine chat all work.
Who should approve repair requests?
Small fleets usually let the mechanic or owner decide. Set a dollar limit above which the owner approves, and write it on the form.
Should every small issue go on the form?
Yes, if it is cheap to report. Small issues recorded with hours are how you spot patterns before a breakdown.
How long should closed requests be kept?
As long as you own the machine. The record is part of its service history and helps at resale.
