Knowledge / AEC-native data

As-built drawings and handover packs

The record set describing the building as constructed, together with the health and safety file and the information required for the golden thread.

At practical completion the contractor hands over the record of what was built: the as-built or record drawings, the health and safety file required under CDM 2015, the asset information, and for a higher-risk building the golden thread information. It arrives as thousands of files in folders named by several subcontractors, and the client's FM team inherits it and searches it for years. The record drawings are usually the last construction issue with a stamp, and the changes made on site live in instructions and RFIs the pack does not contain. As-built drawings AI is worth having only if it can tell a record from a superseded issue and read the pack against the instructions that changed the building, with every answer traceable to the sheet it came from.

What teams need to ask of it

  • Which drawing is the record for this area, and which earlier issues are superseded even though they also carry an as-built stamp?

  • Does the record drawing show the change made by this instruction, or was it never picked up?

  • On a refurbishment, where is the pre-refurbishment asbestos survey, and which residual risks does the H&S file carry forward?

  • Which drawing shows this valve, this isolator or this access hatch, and what does the O&M manual call it?

  • Is the pack complete against the employer's information requirements, and what is missing?

  • Which record drawings were re-drawn and which are marked-up construction issues?

  • For a higher-risk building, which documents in the pack form part of the golden thread information?

Why generic AI gets it wrong

A handover pack is a folder tree, and a folder tree carries almost no meaning. The relationship between a record drawing, the instruction that altered what it shows, the commissioning certificate for the plant on it and the residual risk in the H&S file exists only in the heads of the people who compiled it. Read the files as text and a general-purpose tool sees a drawing titled as-built and treats the title as the fact. It cannot tell that two sheets with the same number and the same stamp differ by one riser position, or which of them the site team actually built from.

The record is also incomplete by its nature. The last change to the level 3 riser was an instruction, the reason for it was an RFI, and the day it was built is in a site diary. None of those documents are in the handover pack, so a tool reading the pack alone has no way of knowing that the drawing it is quoting was overtaken. Its answer will name a drawing, a revision and a location, and will read as if a competent document controller wrote it. An FM engineer will send someone to open the wrong ceiling. The confidence of the answer is the problem, because a hesitant one would have been checked.

One question, answered

QUESTION

ANSWER

SOURCES

See it on your data.

See it on your data.

We onboard a focused slice of your project data, configure the ingestion paths, extract a structured context graph, and build a workflow against the resulting structured knowledge layer.

Related to

The handover pack is where the O&M manuals, the record drawings and the asset information meet, and it inherits everything the construction drawings and the IFC and BIM models carried through the project. Handover pack structuring is the workflow that turns it into a register the FM team can use, and lessons learned capture reads it for the changes that were made late and why.

Frequently asked questions

Frequently asked questions

Does it read marked-up construction issues as well as re-drawn as-built sets?

Can it check the pack against our information requirements?

How do we see it on a handover pack we have already received?

Related pages