Naming and filing that survives a handover

Records are rarely lost because someone deleted them. They are lost because nobody could find them. A folder called "Final docs", another called "Final docs v2", a scan named after the date it was scanned rather than what it shows, an email attachment that lived only in one person's inbox: the information existed the whole time, but the person who needed it could not lay hands on it when it mattered. A handover is the moment all of that comes due, because the person inheriting the building has none of the context that made the mess navigable to the person who created it.

Naming and filing sound like clerical concerns, beneath the attention of anyone managing safety-critical buildings. They are not. They are the difference between a record that survives a change of manager and one that has to be reconstructed from scratch, at cost, under time pressure, often after something has already gone wrong.

Why a handover is where filing fails

While a building stays with the same manager, a disorganised filing system works well enough. The manager carries the map in their head. They know that the asbestos survey is in the folder marked with the surveyor's name, that the lift records are split between two places for historical reasons, that the most recent fire risk assessment supersedes the one with the more recent file date because of a re-issue. None of this is written down. It does not need to be, until the day that person leaves.

At handover, the head full of context walks out of the door. What remains is the filing system as it actually is, not as the departing manager experienced it. If the names do not describe the contents, and the structure does not follow an obvious logic, the incoming manager faces an archaeology problem rather than a building to manage. This is precisely the situation the golden thread is meant to prevent: under the Building Safety Act 2022, the golden thread is an accurate, up-to-date digital record of building information held through design, construction and occupation, according to the ICE. A record that only one departed person could read is not, in any useful sense, current.

Name the file for the person who has never seen it

The test for a good file name is simple. Could someone who has never met you, who has just inherited this building, tell what the document is from its name alone, without opening it. Most working file names fail that test badly.

A few principles carry most of the weight:

• Describe the content, not the circumstance. "Fire-risk-assessment" beats "FRA final FINAL", and certainly beats "scan_0042".
• Put the date in the name, in a sortable form, so the newest version is obvious and files line up in order rather than scattering alphabetically.
• Name the building or block, even when it feels redundant, because files travel out of their folders into emails, downloads and shared drives where the folder context is gone.
• Avoid initials and in-house shorthand that mean something only to the current team.
• Keep version markers meaningful: a clear "superseded" beats three files that all claim to be final.

None of this is clever. It is the opposite of clever. It is the dull discipline that means a stranger can read your filing.

Structure that mirrors how the building is governed

Names solve the problem of the individual document. Structure solves the problem of where to look. The most durable structures mirror the way a building is actually governed rather than the order in which paperwork happened to arrive.

A structure organised around systems and assets survives staff changes because it does not depend on who did what. It maps onto the questions a new manager, an auditor or a regulator will actually ask: where is the current fire risk assessment, when was the lift last examined, what is outstanding. The folder that answers those questions directly is worth more than the one that faithfully records the order of arrival.

Consistency across buildings beats perfection in one

A naming convention is only as useful as it is repeated. A beautifully ordered folder for one building, sitting beside twenty others organised differently, helps nobody managing the portfolio. The value compounds when the same categories, the same naming pattern and the same idea of "current" apply everywhere, so that a manager moving between buildings already knows where to look before they open anything.

This is the argument for filing inside a system rather than a shared drive. A system can enforce the convention rather than relying on each person to remember it. It can make the current version unmistakable, retire the superseded one without deleting it, and attach a record to the asset it concerns rather than to a folder someone chose in a hurry. The same logic runs through turning a filing cabinet into a searchable record: the point is not tidiness for its own sake, but findability when it counts.

What good filing buys at the moment of handover

When a building changes hands cleanly, the incoming manager can answer the basic questions on day one rather than week six. They are not paying a surveyor to reproduce a document that already exists somewhere unfindable. They inherit not just files but the meaning of the files, because the structure carries the logic that used to live in someone's head. This is the practical face of the golden thread, and it is also what an auditor expects to see: records that are current, complete and legible to someone other than their author. It connects directly to the wider question of records that survive a change of managing agent, which is the same problem viewed from the organisation rather than the file.

A short, practical close

Good naming and filing is unglamorous work that pays off only at the moments you cannot predict: a staff departure, a regulator's request, an incident, a sale. The discipline is modest. Name files so a stranger can read them, structure folders around the building's systems rather than the order paperwork arrived, and apply the same convention everywhere so the pattern is portable. SAMRISK holds records against the building and the asset they belong to, with the current version always clear, which is what lets the next manager pick up where the last one left off. This is general information rather than a records-management standard, and your retention obligations should be checked against the current rules that apply to you.