Keeping plans in step with the building as it changes

A building rarely changes all at once. It changes a wall here, a new partition there, a riser rerouted during a refurbishment, a fire door swapped for one with a different rating. Each change is small enough to feel like it does not warrant updating the drawings, and so it does not. A year later the plan in the file no longer matches the building in the ground, and nobody decided that should happen. It happened by accumulation. Keeping plans in step with the building is mostly about catching those small changes at the moment they occur, because catching them later means a survey.

The drift problem is a habit problem

Out-of-date plans are almost never the result of one big oversight. They are the result of a missing habit: no agreed trigger for updating a drawing, no owner for the job, and no place where the current version is obviously the current version. When those three things are absent, drawings rot quietly. The works get done, the contractor leaves, and the only record of the change is in someone's memory or a closed email thread.

This matters more than it used to. The golden thread under the Building Safety Act 2022 is meant to be an accurate, up-to-date digital record carried through occupation, not just a snapshot taken at handover. For high-rise residential buildings, the Fire Safety (England) Regulations 2022, in force 23 January 2023, require the responsible person to keep floor and building plans available to the fire and rescue service and in the secure information box. A plan that no longer shows the building is not a minor housekeeping issue in that context. It is a record that could mislead the people who rely on it in an emergency.

Decide what counts as a change worth recording

Not every alteration needs a new drawing, and pretending otherwise leads to a process people abandon. The job is to agree, in advance, which changes are significant enough to update the plan. As a rough division of the field:

• Always update: changes to compartmentation, escape routes, fire doors, risers, structural walls, or the external wall build-up.
• Usually update: new partitions that change room layout, relocated alarm panels or call points, changes to access and lockable spaces.
• Rarely update: cosmetic finishes, furniture, signage that does not affect escape.

The line will move with the building, but having a line at all is what keeps the process alive. When everyone knows that a moved fire door always triggers an update and a repainted corridor never does, the updates that matter actually happen.

Tie the update to the work, not to a calendar

The most reliable moment to update a plan is when the work that changed the building is signed off, not at some later review that may never come. If a contractor permit or a works order closes out a job that moved a wall, that closure is the natural trigger to revise the drawing. Waiting for an annual plan review means a year of changes pile up and have to be reconstructed from memory, which is exactly how surveys get commissioned. Linking the update to the work keeps the cost low, because the people who did the change are still available to describe it.

This is one reason it helps to hold plans, permits and the maintenance record in the same place. When a piece of work that affects the layout is logged, the prompt to update the plan can sit right next to it rather than in a separate process that depends on someone remembering. We have written about chaining deadlines this way in a maintenance calendar that chains its own deadlines, and the same logic applies to drawings.

Keep the old versions, not just the new one

Replacing a plan with a newer plan loses something valuable: the ability to say what the building looked like at a given date. For compliance, the history matters. If a fire risk assessment was carried out against the layout as it stood in March, and the layout changed in June, you want to be able to show both states and the date the change happened. That is the difference between version control that holds and a folder of files with confusing names. A drawing should carry its date, its author and what changed, so the sequence reads in order.

Real version control for drawings is not glamorous, but it is what lets a record survive scrutiny. The principles are the same as for any compliance document, which we set out in version control for building documents that actually holds. The plan is just a document with geometry.

A living drawing beats a perfect one

There is a temptation to aim for one immaculate set of drawings and treat updating them as a special event. It is the wrong target. A slightly rougher plan that is updated the week the building changes is worth more than a beautiful set that froze two refurbishments ago. The goal is a living record, kept current by small acts rather than rescued by occasional large ones.

In practice that means deciding who owns the drawings, agreeing what triggers an update, and keeping the versions where the whole team can see which one is live. SAMRISK holds plans alongside the rest of the building record so an alteration logged against the building can prompt the drawing to follow, and the history stays attached rather than overwritten. You can see how plans sit beside the wider record on the building plans page.

The next time a contractor moves something in your building, treat the closing of that job as the moment to update the plan. Catch the change while it is fresh, keep the old version, and the drawings will still be telling the truth long after the work is forgotten.