Servicing the systems nobody sees

A building is full of systems that do their work where nobody looks. Smoke is cleared by ventilation in a shaft most occupants never see. Water reaches the upper floors because a pump runs in a plant room. A fire damper closes inside a duct to stop fire spreading through the ductwork. Emergency lighting waits, charged and dark, for the day the power fails. These systems share a quality that makes them dangerous to manage: when they are working, there is nothing to notice, and when they have failed, there may still be nothing to notice, right up until the moment they are needed and are not there.

That is the heart of the problem with hidden systems. The feedback loop that keeps visible things maintained, you see the damage, you fix it, does not operate. A cracked window gets reported. A fire damper seized shut inside a duct does not report itself. The only thing standing between "working" and "failed unnoticed" is a servicing regime that goes and checks deliberately.

Why invisibility breeds neglect

Most maintenance is reactive in practice even when the policy says otherwise, because human attention follows visible problems. The lift that stops gets fixed quickly, because everyone knows about it within an hour. The systems with no everyday symptoms slide to the back of the queue, not through negligence exactly, but because nothing is pushing them forward. They make no noise, generate no complaints and cost nothing to ignore, until they cost everything.

The systems most prone to this quiet neglect tend to be the ones that matter most in an emergency:

• Smoke control and mechanical ventilation, which only run in a fire or a test.
• Fire and smoke dampers concealed within ductwork, which must close on demand.
• Sprinkler and dry or wet riser systems, charged and waiting.
• Emergency and escape lighting, invisible until the mains fail.
• Pumps, boosters and generators that sit idle between the moments they are essential.

Each of these is a life-safety system. Each is also, by design, out of sight. The combination is exactly the one a servicing regime exists to manage, because nothing else will.

Some hidden systems carry a legal cadence

For a subset of these systems, the law removes the discretion and sets the rhythm for you. That is helpful, because a fixed cadence is far easier to defend and to schedule than a vague intention to check "regularly".

Lifts are the clearest example. Under LOLER, lifting equipment that carries people must have a thorough examination at least every 6 months, while load-only lifting equipment is examined at least every 12 months, or in accordance with a written scheme, according to the HSE. In high-rise residential buildings, the cadence goes further: the Fire Safety (England) Regulations 2022, in force 23 January 2023, require responsible persons to carry out monthly checks of firefighters' lifts and key firefighting equipment, according to the NFCC. These are not aspirations. They are intervals, and a missed interval is a finding waiting to be made.

Where the law sets a cadence, the management task is simply to never miss it. Where it does not, the task is to set a sensible cadence yourself and hold to it with the same discipline, because the absence of a statutory interval does not mean the system can be left.

A regime, not a memory

The thing that keeps hidden systems serviced is not effort or good intentions; it is structure. A service due on a date that lives only in someone's head will eventually slip, because heads are busy and people move on. A service tied to a schedule that surfaces the date, assigns it, and records the result against the asset is one that survives staff changes and quiet quarters.

The table is less important than the principle behind it: every hidden system needs a named cadence, an owner and a record. The record is what turns a service from an event nobody can later confirm into evidence that the duty was met. This is the same argument we make for planned maintenance beating reactive every time, and hidden systems are where the case is strongest, because reactive maintenance cannot react to a failure it cannot see.

The record is the proof

For hidden systems in particular, the servicing record does double duty. It is the operational tool that tells you the system was checked and works, and it is the evidence that you discharged your obligation. After an incident, the question is never "did you mean to maintain it"; it is "show me when it was last serviced and what was found". A system serviced on a rhythm, with each service logged against the asset, answers that question on its own. A system serviced when someone remembered cannot.

Holding those records against the asset rather than in a separate folder is what keeps the history legible over years and across managers. It lets a pattern, a damper that keeps failing its drop test, a pump that needs ever more frequent attention, become visible before it becomes a failure. Pulling the schedule and the records together against a compliance calendar is what stops the invisible work from slipping out of view along with the systems themselves.

A short, practical close

The systems nobody sees are precisely the ones most likely to go unserviced, because nothing in the everyday running of a building reminds you they are there. The defence is unexciting and reliable: give every hidden system a named cadence, honour the statutory intervals where they exist, assign each service to someone, and record the result against the asset so the proof exists when it is asked for. SAMRISK ties those schedules and records together in one place, so the work that protects people on the worst day does not quietly lapse on all the ordinary ones. This is general information rather than engineering advice, and each system should be serviced to the standard set by a competent person.