A maintenance log that earns its keep

Most maintenance logs fail in the same quiet way. They start as a tidy spreadsheet or a bound book on a shelf, they capture the first few jobs in full, and then the entries thin out. A line here, a date there, a name nobody recognises. By the time anyone needs to rely on the log, to settle a dispute, defend a position or plan the next year's work, it has stopped being a record of what happened and become a record of what someone remembered to write down. A log only earns its keep when it changes a decision later, and that depends almost entirely on how it is built.

What a log is actually for

It helps to be honest about the jobs a maintenance log does, because they are not all the same and they pull in different directions.

The first is evidence. If a component fails, or a tenant complains, or a regulator asks, the log is the contemporaneous account of what was done and when. The second is planning. A complete history tells you which assets are eating your budget, which contractors deliver and which jobs keep recurring because the root cause was never fixed. The third is handover. When a building changes hands, or a managing agent changes, the log is a large part of what the next person inherits.

These three jobs share one requirement: the entry has to be trustworthy at the moment someone reads it, often years after it was written. That is a higher bar than "we wrote something down."

The fields that make an entry usable

A weak log records that work happened. A strong one records enough that someone who was not there can understand it. The difference is a handful of fields, captured consistently.

The last row is the one most often missed and the one that does the most work. An entry that sets its own next due date turns the log from a history into a forward plan. Without it, the log tells you what you did but not what you owe.

Statutory cadences belong in the same place

Some maintenance is discretionary and some is required by law, and a log that mixes them without distinction makes it hard to see what is genuinely overdue. The recurring legal checks are a good anchor because their timing is fixed and well known.

• Rented homes in England need an electrical inspection at least every five years, with the report given to tenants within 28 days and to new tenants before they move in (gov.uk landlord rules). The EICR and its date belong in the log, not in a separate compliance folder.
• Lifting equipment that carries people requires a thorough examination every six months under LOLER, and load-only lifting equipment every 12 months, or in line with a written scheme (HSE). Those examinations are maintenance events with legal force, and the log should treat them that way.
• For high-rise residential buildings, the Fire Safety (England) Regulations 2022, in force 23 January 2023, require monthly checks of firefighters' lifts and key firefighting equipment, with faults reported (NFCC; gov.uk). Twelve entries a year, every year, attributable to a person.

When the statutory checks and the routine servicing sit in one log, the gaps show up on their own. When they are split across systems, the gaps hide.

Why the medium matters

A log on paper or in a personal spreadsheet has two structural problems. It can be edited after the fact without trace, which weakens it as evidence, and it lives with one person, which weakens it at handover. A record that timestamps entries, keeps earlier versions and stays attached to the building rather than to an individual avoids both.

This is the same discipline that sits behind the golden thread for higher-risk buildings, an accurate, up-to-date digital record held through a building's life (ICE, under the Building Safety Act 2022). You do not need to manage a higher-risk building to borrow the principle. A maintenance log that is current, attributable and hard to quietly rewrite is useful in any building.

Keeping it alive

The honest truth is that the best log is the one people will actually keep, which means it has to be quick to add to and obvious where to add to. A field engineer standing in a plant room will not open a thirty-tab spreadsheet. The entry has to take seconds, attach the photo or certificate from the phone in their hand, and set the next due date automatically.

That is the practical case for holding maintenance against the building itself, alongside its compliance calendar and its asset list, rather than in a file that depends on one person's diligence. SAMRISK keeps the log, the cadence and the evidence in the same record, so an entry written today is still legible and trustworthy when someone needs it in three years. For the wider argument about doing the work before it becomes urgent, our piece on planned maintenance beats reactive every time is worth a read.

A maintenance log is a small thing that quietly underwrites a lot of larger ones. Build it so it can be relied on, and it pays for itself the first time someone asks a hard question.