# Equipment repair log template that stays searchable

An equipment repair log lasts only if the columns stay fixed. This post lists the fields that make an old row findable later, shows three illustrative Excel examples, and ties weak machine-history recording in a Cebu MSMI study to why US plants need a searchable repair log. Template included.

**Short answer:** An equipment repair log you can still search in two years needs fixed fields, not free text alone: asset ID and serial, fault code as displayed, symptom, cause, fix, parts with numbers, captioned photos, date and technician. The columns below, with a filled example you can copy into Excel, are built so a later search can find the row.

**Applies to:** maintenance and service teams that keep an equipment repair log, work orders or downtime log in Excel or on paper, especially US plants that use "repair log" / "downtime" vocabulary. Worked examples use fault codes already covered on this blog (for example Fanuc SV0401 and Yaskawa oC). **Last verified:** 6 Nov 2026. **Author:** Muhammed Fahiz

*US-vocabulary sibling of our India [breakdown register format (Excel)](https://hangersearch.com/blog/breakdown-register-format-excel) post. Same field logic; different plant words and date format.*

## What should an equipment repair log include?

A usable equipment repair log is a single place where each downtime event gets one row, with the same columns every time. It is not a free-text notebook and it is not a scrap of paper that says "running now".

At minimum it should capture:

- Which machine it was (asset ID, model, serial)
- What the machine showed (fault code as displayed)
- What the engineer saw (symptom in plain words)
- What was found and what was done (cause, fix)
- What parts went on (with part numbers)
- When, who, and optionally how long it was down
- Photos kept with the row, with a short caption

Without those fields, a later search for the same machine and the same code has nothing solid to match. Nick Nickolovski put the failure mode in one sentence in a comment on a public LinkedIn post by Delin S. in October 2026: "Same machine, five different descriptions, so it never adds up to one problem." We wrote that problem up in [same machine, five descriptions](https://hangersearch.com/blog/repeat-breakdown-same-machine).

The rest of this post is the field list, why each field helps a search two years later, a filled example, and when Excel is enough.

![Wall-mounted clipboard rack of blank work-order cards beside a packaging-line drive panel](/blog/media/equipment-repair-log-template-mw4hq6rv.png)

## Which fields make an old report findable later?

Each column below exists so a later engineer can find the row by machine, by code, or by symptom words, and then trust what it says.

| Field | What goes in it | Why it makes the row findable later |
|---|---|---|
| Date (MM/DD/YYYY) and time | When the downtime started or when the work order closed | Lets you sort a machine's history and see repeats |
| Asset ID | Your plant tag for that machine (CNC-12, PKG-04) | Groups every visit to one machine even when the description changes |
| Model | OEM model as on the nameplate | Lets you search across sister machines of the same type |
| Serial number | Nameplate serial | Distinguishes two identical models on the same line |
| Fault code as displayed | Exact code on the HMI or drive (SV0401, oC, GF) | The most precise search term you have; variants hide repeats |
| Symptom in plain words | What was seen before the reset ("servo won't ready after E-stop") | Catches visits where no code was shown, and supports a word search |
| Cause found | What the check showed, not a guess | A found row is useless if it only says "checked OK" |
| Fix done | What was actually done | Tells the next engineer whether to repeat the same step |
| Parts replaced (with part numbers) | Part name and OEM or store part number | Lets you search by part and reorder the right item |
| Photo / caption | Link or file name, plus a caption naming machine and part | An uncaptioned photo can't be found or trusted later |
| Technician | Who closed the work order | Useful for follow-up; not a substitute for the fields above |
| Downtime hours (optional) | Hours from stop to running again | Useful for MTTR tallies; leave blank rather than invent a number |

*Our recommended columns for a searchable equipment repair log, not a published standard.*

Two fields do most of the search work: a firm machine identity (asset ID plus serial) and the fault code exactly as displayed. Without them, five different write-ups of the same fault stay five rows, which is the Nickolovski problem in [same machine, five descriptions](https://hangersearch.com/blog/repeat-breakdown-same-machine). Symptom, cause and fix are what make a found row usable. Parts and captioned photos stop the next visit from starting from zero. Our post on [what to write before closing a downtime job](https://hangersearch.com/blog/its-running-now-is-not-a-fix) covers the write-up itself; this page is the repair log those write-ups feed.

## What does a filled example look like?

The three rows below are illustrative examples invented for this template. They are not real plant data. The machines and codes are the kind of US CNC and packaging work this blog already covers (Fanuc SV0401 and Yaskawa VFD fault codes).

| Date | Time | Asset ID | Model | Serial | Fault code | Symptom | Cause found | Fix done | Parts replaced | Photo / caption | Technician | Downtime hrs |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 03/12/2025 | 14:40 | CNC-12 | Haas VF-2 / Fanuc | HS-44821 | SV0401 | X-axis servo will not ready after E-stop; "improper V ready off" | Contactor chatter on V-ready circuit; loose terminal on servo amp | Tightened V-ready terminals; replaced contactor; axis ready OK | Contactor CR-24V-40A | CNC-12_20250312_vready-term.jpg - V-ready terminal before tighten | J. Martinez | 2.5 |
| 07/03/2025 | 09:15 | PKG-04 | Packaging line, Yaskawa GA500 | YK-22018 | oC | Infeed belt trips on accel after product changeover | Motor cable insulation low at junction box; accel time too short for new load | Dried and reseated terminals; lengthened accel; IR check OK | None | PKG-04_20250703_jbox.jpg - junction box before reseat | A. Chen | 1.5 |
| 09/28/2025 | 22:10 | CNC-07 | Doosan Lynx 220 | DN-11903 | SV0401 | Turret axis alarm after night washdown; will not home | Coolant in servo connector; wet pins on amp side | Dried connector; replaced amp-side plug; megger cable OK | Connector kit CK-SV-04 | CNC-07_20250928_amp-plug.jpg - wet amp connector | Night shift / M. Brooks | 3.0 |

*Illustrative examples only. Invented for the template. Not claimed as real plant records.*

Notice what a later search can do with these rows. Filter Asset ID = CNC-12 and you get that machine's history. Search fault code = SV0401 and you get both servo-ready trips, on two different assets. Search "junction box" or the part number CK-SV-04 and you land on the wet-connector fix. A one-line note that said only "reset, running" would match none of those.

Copy the header row from the example table into a new sheet to start. Keep one file as the repair log, freeze the header, and add rows the same way every time. Dates in the US examples use MM/DD/YYYY.

## Excel or paper?

Either can work. What fails is a format that changes every shift.

**Excel (or a shared sheet)** is usually enough when:

- One file is the repair log, not a new workbook per month with different headers
- Headers are frozen and nobody renames columns
- Dates use one format (in the US, MM/DD/YYYY) so sorts work
- Photos live in a shared folder and the Photo / caption cell holds the file name or link
- Finalized rows are not overwritten; corrections get a new note, not a silent edit

**Paper** still works on the floor for the first write-up. The risk is the transfer step. If the paper work order is the only record, a later search has to open a filing cabinet. If paper is the capture and Excel is the repair log, treat the Excel row as the finalized record and keep the paper only as backup.

A CMMS is fine too, as long as the same fields exist as required fields, not optional free text. The tool matters less than whether the columns stay stable for two years.

![Laptop with a blank spreadsheet grid beside a paper work order and a compact servo drive on a steel desk](/blog/media/equipment-repair-log-template-mw4hqt5v.png)

## Why do weak machine-history records keep costing time?

A 2025 DEMATEL study of Micro, Small and Medium-Scale Machine Shop Industries (MSMIs) in Cebu City, Philippines - not India and not a US plant sample - measured how those shops were recording machine history. Van Gaitano N. Vergara surveyed preventive-maintenance practice and reported medium-level performance in recording machine history cards (1.83) and in machine safety (2.46). The same abstract flags frequent machine breakdowns, inadequate documentation and ineffective scheduling of maintenance activities.

The abstract also reports mean time between failures and mean time to repair for three problem machines in that sample: lathe MTBF 486 hrs / MTTR 144 hrs; welding MTBF 541 hrs / MTTR 59 hrs; portable grinder MTBF 311.63 hrs / MTTR 13.5 hrs. We are citing the published abstract only; the full PDF is closed access.

The geography is Cebu, Philippines. The vocabulary of this post is US ("equipment repair log", "downtime", "work order") because that is how many US plants name the log. The useful takeaway for any small machine shop is the same: if machine history cards are the weak row in the scorecard, a repair log you cannot search later will not fix the pattern of frequent downtime. Filling the columns above is the low-cost version of a machine history card that a later engineer can actually find.

## How does this tie to searching old service reports?

An equipment repair log is only half the job. The rows have to stay findable when the person who wrote them has left, and when the next visit is at 2 a.m.

- Group by machine first, then by code: [same machine, five descriptions](https://hangersearch.com/blog/repeat-breakdown-same-machine)
- Write cause and fix before you close: ["It's running now" is not a fix](https://hangersearch.com/blog/its-running-now-is-not-a-fix)
- Treat messy text, scans and uncaptioned photos as a data problem: [searching old service reports is a data problem](https://hangersearch.com/blog/searching-service-reports-data-problem)
- Look for a prior fix on the same alarm: [alarm already solved three years ago](https://hangersearch.com/blog/alarm-already-solved-three-years-ago) and [find a past service fix for a repeat machine fault](https://hangersearch.com/blog/find-past-service-fix-repeat-machine-fault)

None of those steps need a new tool on day one. They need the fields in the repair log to exist and to be filled the same way every time.

## What this doesn't tell you

The Vergara / DEMATEL paper is a study of MSMIs in Cebu City. Its Likert scores and MTBF/MTTR figures describe that sample. They are not US plant benchmarks and they are not a measured test of Excel repair logs. The field list and the three example rows are ours, built so a later search has something to match. We found no study that measures how much a fixed-column equipment repair log improves search hit rate two years later.

## How would you find this in your own archive?

If your team already writes repair-log rows and service reports, the next problem is finding the right prior case when the machine is down. HangerSearch is private, retrieval-only search over your team's own finalized service reports, searched where they already sit. You search by fault code, model or symptom. It shows the prior reports that match and why each matched, and opens the cited page. Nothing is generated, and if there is no similar report, it says so. It cannot invent an asset ID or a cause that was never written down, which is why the repair-log columns come first. See [how we handle your reports](https://hangersearch.com/trust).

Book a 20-minute demo: hangersearch.com

## FAQ

### What should an equipment repair log template include?

An equipment repair log template in Excel is one sheet where each downtime event is one row and the columns stay fixed: date, asset ID, model, serial, fault code as displayed, symptom, cause, fix, parts with part numbers, photo caption, technician and optional downtime hours. Freeze the header row, use MM/DD/YYYY in the US, and keep photos in a shared folder linked from the Photo cell.

### Which fields make an old repair report searchable later?

Asset ID plus serial, and the fault code exactly as displayed, do most of the find work. Symptom, cause and fix make a found row usable. Part numbers and captioned photos stop the next visit from starting from zero. Free text alone, with no machine identity and no code, is what produces five descriptions of the same fault.

### Is Excel enough, or do we need a CMMS?

Excel is enough if one file is the repair log, headers never change, dates use one format, and finalized rows are not silently edited. A CMMS is fine when the same fields are required. Paper is fine for capture if the finalized record still lands in the repair log. The format that fails is a new layout every month.

### How is this different from a breakdown register?

It is the same field logic under US plant vocabulary. Indian plants usually say "breakdown register" and use DD/MM/YYYY; many US plants say "equipment repair log" or "downtime log", talk about work orders, and use MM/DD/YYYY. See the India sibling: [breakdown register format (Excel)](https://hangersearch.com/blog/breakdown-register-format-excel).

### Why cite a Cebu study in a US repair-log post?

Because the published abstract is one of the few recent open measurements of weak machine-history-card recording in small machine shops, and the documentation gap it reports is the same gap a US equipment repair log is meant to close. The plants studied were MSMIs in Cebu City, Philippines - not a US sample. The MTBF/MTTR figures are from that sample only.

## Sources

1. Van Gaitano N. Vergara, "Assessing Preventive Maintenance Program for Micro, Small, and Medium Scale Machine Shop Industries Using DEMATEL", 2025 4th International Conference on Computational Modelling, Simulation and Optimization (ICCMSO), published 20 Jun 2025, DOI 10.1109/iccmso67468.2025.00041. Cited from the published abstract only (full PDF closed access). Read 5 Nov 2026 (reused for this US sibling 6 Nov 2026). Supports: Cebu City MSMIs geography; medium-level performance for machine history cards (1.83) and machine safety (2.46); lathe MTBF 486 hrs / MTTR 144 hrs; welding MTBF 541 hrs / MTTR 59 hrs; portable grinder MTBF 311.63 hrs / MTTR 13.5 hrs; findings of frequent breakdowns, inadequate documentation and ineffective scheduling.
2. Nick Nickolovski, comment on Delin S., public LinkedIn post "Maintenance keeps fixing, but the same machine keeps breaking." (11 Oct 2026); comment dated 12 Oct 2026: https://www.linkedin.com/posts/delinsirkov_maintenance-cmms-reliability-activity-7514852511011463168-0mhw. Previously read for [our repeat-breakdown post](https://hangersearch.com/blog/repeat-breakdown-same-machine) (31 Oct 2026). Supports: "Same machine, five different descriptions, so it never adds up to one problem."
3. Fanuc SV0401 and Yaskawa oC used only as context for the invented example codes; see our earlier post [Yaskawa VFD fault codes](https://hangersearch.com/blog/yaskawa-vfd-fault-codes) for the oC example. Fanuc SV0401 appears as a code already discussed on this blog; its dedicated page is not linked here because it is not live. The example rows in this article are invented illustrations, not field reports.

## Related

- [Breakdown register format (Excel) that you can still search in two years](https://hangersearch.com/blog/breakdown-register-format-excel) (India sibling)
- [Same machine, five descriptions: why repeat faults never add up](https://hangersearch.com/blog/repeat-breakdown-same-machine)
- ["It's running now" is not a fix](https://hangersearch.com/blog/its-running-now-is-not-a-fix)
- [Searching old service reports is a data problem, not a model problem](https://hangersearch.com/blog/searching-service-reports-data-problem)
- [The alarm was already solved three years ago](https://hangersearch.com/blog/alarm-already-solved-three-years-ago)
- [Find a past service fix for a repeat machine fault](https://hangersearch.com/blog/find-past-service-fix-repeat-machine-fault)
- [How HangerSearch handles your data](https://hangersearch.com/trust)