Breakdown Maintenance Register Format

Published on 10/18/2026 • Updated on 10/22/2026

A machine stops at 10:40. The technician arrives at 10:55, finds a burnt contactor, replaces it by 11:50 and the line runs again at 12:00. By evening nobody remembers the details. A week later the same contactor burns again. A breakdown register, filled in each time, turns these events into a record you can learn from.

This guide gives a breakdown register format with columns, a short list of cause codes, sample entries, the arithmetic for downtime and a simple method for finding repeat faults. The format is given inline. There is no file download.

What the register is for

The breakdown register is a log of every unplanned stop: when it began, what failed, why, how long it lasted, what was done and what it cost. Used well it answers three questions. Which machines stop most? What fails most? How long do we take to restore?

The register format

Fifteen columns look many, but each is quick to fill when the technician is standing at the machine with the card.

A short cause code list

A short list lets you count causes later. Free text cannot be counted. Keep UNK for the cases where you truly do not know and review them weekly.

Downtime and response arithmetic

Three times give three figures for every breakdown.

• Response time: attended at minus reported at.
• Repair time: restored at minus attended at.
• Downtime: restored at minus reported at, or the full stop time.

For BD-0112 above: reported 10:40, attended 10:55, restored 12:00. Response 15 minutes, repair 65 minutes, downtime 80 minutes. Our guide on MTTR and MTBF explains how these roll up into plant measures.

Sample entries

These entries are made up. Notice that C-4 appears twice with the same cause in a short time. That is a repeat fault, and the register just showed it.

Finding repeat faults

This is a one hour job a month and it often gives the best return of any maintenance meeting.

Writing a useful root cause note

The cause code says what kind of fault it was. The root cause note says why it happened. A simple method is to ask why up to five times.

The example is made up. The point is that the fix lies at the bottom, not at the top. Replacing the contactor again is the answer to the first line only.

Who fills it and when

The technician who attends the breakdown fills the first part at the machine: times, description, action. The supervisor adds the cause code and root cause note at the end of the shift, with the technician. The maintenance lead checks every entry the next morning and chases blanks. Make it a rule that a breakdown without an entry is not closed.

Keep a blank card on the machine itself or in the technician's pocket, so that no one needs to walk to the office. A pencil on a string next to the machine works better than a policy.

Cost and spares

Record the parts used and the cost, even a rough one. A running total of repair cost per machine tells you when repair stops making sense and replacement starts. Compare the cost of the last year of breakdowns with the price of a new unit. When the repairs add up to half or more of the replacement price, it is time to raise the question with management.

Link spares used to the stock register. A part that appears on the card three times in a month is a part that should be in stock at the machine, not in a store across the plant.

Using the register at shift handover

At the start of each shift, the outgoing supervisor reads the open breakdowns aloud, with what has been done and what is pending. The incoming supervisor signs. This takes five minutes and prevents the classic loss of knowledge between shifts, where the day team repairs a machine halfway and the night team starts from nothing.

A worked example

The numbers are illustrative. The method, count then investigate, is the point.

Common mistakes

Another mistake is recording only long stops. Short stops add up and often hide the real pattern.

A third is blaming the operator by default. Code OPR only when you have checked that the machine was used outside its rules.

A fourth is never closing the follow-up. A follow-up with an owner and a date, reviewed monthly, is the part that prevents the next stop. Without it, the register is only a diary.

A two-week start

Get the register running.

Repeat the review monthly, and keep a one-page summary of each month. Put the totals on the notice board for the shift teams: number of stops, hours lost, top machine and top cause. When the team sees the numbers fall after a fix, they see the point of filling the register, and the habit sustains itself. When the numbers do not fall, ask what the register is telling you and act on that in the next meeting.

Five-minute self-check

Check your breakdown records against these points.

Two or more no answers mean this is worth fixing before anything else on your list.

Reader Q&A

Bottom line

A breakdown register works when it is filled at once, uses cause codes and is reviewed monthly for repeat faults.

Start with the format above and share the top three with the team every month. Over a year the register becomes the best training material you have, because every entry is a real failure on a real machine in your own plant.

Author of the Blog Post

Aadeshwar Modi

Technical Content Writer at VisitorFlow

Aadeshwar Modi is a marketing technical content writer who loves writing on technology and AI topics.