Equipment maintenance log template
A free Excel log for equipment inspections, faults, repairs and service. Each entry records what happened, how long the equipment was down, what was done, by whom, the parts cost and when to check it next. A Total row adds up downtime and parts cost, and the Open status shows which fixes are not finished.
What's in the sheet
Sample rows. Replace them with your own.
| Logged | Equipment | Location | Type | What happened | Downtime (min) | Action taken | Done by | Parts cost | Next check | Status | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-09-14 07:40 | Sealer, packing line 2 | Plant 1 | Fault | Seal bar not reaching temperature, bags opening | 45 | Replaced the thermocouple | Luis | $38.50 | 2026-09-21 | Fixed | |
| 2026-09-14 09:00 | Cold room 3 compressor | Plant 1 | Inspection | Weekly check, pressure normal | 0 | None needed | Priya | $0.00 | 2026-09-21 | Fixed | |
| 2026-09-15 13:20 | Forklift 2 | Warehouse | Fault | Battery drains in about 3 hours | 0 | Ordered a new battery | Sam | $0.00 | 2026-09-18 | Open | Use forklift 1 until Thursday |
| 2026-09-15 16:00 | Produce washer | Plant 1 | Service | Quarterly service | 120 | Belts and spray nozzles replaced | Vendor, CleanTech | $410.00 | 2026-12-10 | Fixed | |
| 2026-09-16 06:50 | Label printer, line 1 | Plant 1 | Fault | Labels printing faint | 10 | Cleaned the print head | Chris | $0.00 | 2026-09-23 | Fixed | Third time this month. Consider a new head. |
What each column is for
- Logged
- Date and time it was logged.
- Equipment
- The machine, with the line or number.
- Location
- Plant, room or site.
- Type
- Inspection, Fault, Repair or Service.
- What happened
- What happened, as the operator saw it.
- Downtime (min)
- Minutes the equipment could not run.
- Action taken
- What was done about it.
- Done by
- The person or vendor who did it.
- Parts cost
- Parts only, not labor.
- Next check
- When to look at it again.
- Status
- Open or Fixed.
- Notes
- Patterns, warranty, anything for next time.
How to use it
- 1Log every fault when it happens, even when the fix takes a minute.
- 2Record downtime in minutes. It is the number that justifies a new part or a new machine.
- 3Set a next check date for every entry, including routine inspections.
- 4Filter Status to Open at the start of each week, and sort by Equipment to spot repeat faults.
Where the spreadsheet stops helping
- Small faults get fixed on the spot and never written down, so repeat problems stay invisible.
- The repair history lives in one technician’s head.
- Nobody adds up downtime, so the case for replacing a machine is never made.
In Markhub
Let a fault become a to-do with an owner
- 1Report the fault in the equipment hub, by call, in chat or with a photo.
- 2Live Context drafts a to-do from what was said, with the equipment and the symptom. You confirm it and choose who fixes it.
- 3The Task Manager agent follows up on repairs that stall, and the history stays in the hub for the next time it breaks.
Start free, then add the Task Manager from the agent library in your workspace.
Questions
What should an equipment maintenance log include?
The equipment, what happened, the downtime, what was done and by whom, parts cost and the next check date. Downtime and repeat faults are what turn a log into a decision.
Should routine inspections go in the same log?
Yes. An inspection that found nothing still proves the check was done, and it keeps the next check date in one place.
How do I spot a machine that keeps failing?
Sort by Equipment and look at the Fault rows. Three faults on the same machine in a month is usually worth a closer look.
Does it work in Google Sheets?
Yes. Upload the .xlsx file to Google Drive and open it with Google Sheets. The formulas and dropdowns carry over. The CSV has the same sample rows as plain values.
More templates
- Daily sales report templateClose each store and channel, match sales to payments, and catch a short cash drawer the same day.
- Shift handover templateHand over what is open, what is blocked and what the next shift has to do by when.
- Decision log templateRecord what was decided, why, and what happens next, so a month later you can still answer why.