As-Built BIM Models: Requirements, Uses and How to Prepare Models for Handover
An as-built BIM model records the constructed condition for handover, facilities use and future works. This guide covers survey inputs, modeling rules, Level of Development, data fields, quality checks and how to prepare models clients can actually use.
An as-built BIM model is a model that records the constructed condition of an asset at a stated date, with a stated method of verification, for a stated use: handover, facilities, future works, or record. It is not a design model with the title block changed to “as-built.” It is not automatically a laser-perfect mesh of every bolt. It is a disciplined update of geometry and information so that the next person can trust it within the limits you wrote down.
Date of record. Method: field measure, laser scan, redlines, or a mix. Which systems are included. Which Level of Development and which tolerances. Who verified. What remains design-intent because it was not seen (above a hard ceiling, inside a wall). Without those sentences, “as-built” is a slogan.
Level of Development 500 in BIMForum/AIA-related usage is often used for field-verified elements. It does not mean maximum visual detail. A verified wall location can be simple geometry. A decorative mesh of an unverified plant can be a lie. See the LOD article.
Inputs: redlines, scans, submittals and the live model
Contractor redlines are fast and incomplete. Scans are measured and occluded. Submittals tell you which equipment was purchased. The live design model tells you the intended connectivity. As-built modelling is the reconciliation. When they disagree, the brief must say which source wins for which system. Default: measurement wins for location; submittal wins for equipment type; unanswered disagreements become a log, not a guess.
Scan to BIM is the right tool when existing or installed geometry is complex. It is not mandatory for every door swing if a room-by-room checklist is enough. Mix methods honestly.
Uses that change the modelling rules
Facilities management wants asset identifiers, maintainable equipment, and spaces that match room numbering. Future renovation wants reliable envelope and structure. Dispute resolution wants conservative modelling and a chain of custody for surveys. Quantity reconciliation wants types that match commercial items. A single file can serve more than one use if you do not fill it with contradictory shortcuts. If uses conflict, split the deliverable: a geometric as-built and a separate asset table.
COBie or similar handover schemas appear in some appointments. They are not universal law. If they are in the appointment, you need a field list and a responsible person. Empty COBie is worse than none.
Preparing the design model for handover
Strip unused options. Remove exploded CAD. Replace design placeholders with installed families where known. Phase correctly. Update grids only if they were actually moved and surveyed. Keep a copy of the design model archive so as-built editing does not destroy history. Export IFC if the client’s environment is not Revit, and test the export. File naming should follow the BIM Execution Plan handover clause.
Do not purge parameters the client needs for assets. Do purge unused materials and leftover groups that were design options. Agree the purge policy; irreversible cleanup on the only copy is a defect.
Quality checks
Overlay scan or measure a sample of rooms. Check equipment tags against a sample of nameplates. Check that unseen zones are marked. Check that the model opens in the named version without mystery plugins. Check space names against the client’s room list. Check that residual design clashes that were never built are not still presented as live issues.
Outsourcing as-built work
Milestone a sample floor overlay. Do not buy a whole campus as-built until the sample passes. Provide the scan, the redlines, the submittals, and the room list. Price will follow occlusion, discipline mix, and data fields, not a fake global rate. See cost.
Singapore handover to an owner is not the same as CORENET X submission. Do not instruct a freelancer to “make it CORENET as-built” without an official requirement. See BIM in Singapore.
Quality checklist
Date and method stated
Source-priority rule
Unseen zones marked
Installed equipment where known
Sample overlay passed
Asset fields only as briefed
Archive of pre-as-built model
Native plus agreed IFC
Room names match client list
Room-by-room close-out versus whole-building slogans
As-built work fails when it is described as a percentage of a campus. It succeeds when it is described as rooms, systems, and a date. A close-out checklist for a typical floor might include: scan date, overlay of envelope, door swings checked against ironmongery list, ceiling services photographed before close-up, equipment nameplates photographed, room names matching the client list, and unseen ceiling voids marked as unseen. That list is boring and it is the job. A freelancer who wants to skip it in favour of a flythrough has misunderstood handover.
Whole-building slogans (“LOD 500 complete”) hide the mechanical penthouse that was never scanned because of access. Keep a register of incomplete zones. Incomplete is allowed. Hidden incomplete is not. The register should be a milestone deliverable alongside the model.
Asset data without pretending every parameter is gold
Owners often want equipment lists: mark, manufacturer, model, serial, install date, warranty, filter size. Some of those fields can be read from a nameplate and a submittal. Some cannot. Do not type “TBC” in fifty required fields and call the COBie complete. Either reduce the required set or fund the survey of the fields. Empty structured data is a hazard because the next software will treat it as known.
Space data is as important as equipment data. If the client’s CAFM system uses a room numbering scheme that differs from the architect’s door schedule, the as-built model must pick a master and map the other. That mapping table is a handover document. Modelling both numbers into competing parameters without a master is how two apps disagree forever.
Do not invent energy performance values, fire ratings, or flow rates that were not on the installed nameplate or the approved submittal. A design-phase parameter left in the as-built file is a common lie. Strip or flag design-only parameters in the method note.
Legal survey versus BIM record — keep the hats separate
A registered surveyor’s plan is a professional product with a legal context. A BIM as-built is usually a project information product. On some appointments they meet; on many they do not. Do not ask a freelance Revit modeller to certify a boundary. Do not assume a laser scan used for MEP as-built meets a cadastral standard. If the client needs both, hire both, and register both to the same stated coordinate system so they can be overlaid without a fight.
When disputes are foreseeable, freeze the cloud and the model with checksums or an equivalent custody note. Pretty cleanup of a deformed slab may be exactly the wrong act. Tell the specialist the use.
Mechanical, Electrical and Plumbing as-built peculiarities
Mechanical: installed equipment often differs from the design family. Replace the family or clearly parameterise the substitution. Duct sizes after site changes should be measured, not copied from the last design issue. Flexible duct that proliferated on site should be modelled only if the use needs it; otherwise record a typical note.
Electrical: switchgear nameplates, tray routes that drifted, and extra-low voltage baskets added late are the usual deltas. Device-by-device as-built of every outlet is expensive; many owners need containment and equipment, not every socket. Write the cut-off.
Plumbing: as-built inverts on buried lines may need survey, not a guess from a slab soffit. If you cannot see it, mark unseen. Do not invent a slope that looks tidy.
Fire protection: as-built sprinkler heads versus ceiling layouts matter for future fit-out. If you include them, coordinate with the ceiling as-built, not with the design reflected ceiling plan.
Handover package structure
A usable package contains: native model, IFC if agreed and tested, cloud or scan index if used, submittal index, room mapping table, incomplete-zone register, method statement with date, and a short “how to open this in two years” note including software version. Put it in the folder the BIM Execution Plan named. A marketplace milestone that dumps a single RVT into chat is not handover.
If the owner’s team has no Revit, the tested IFC and a PDF space/equipment list may be the true handover, with the RVT as archive. Test the IFC on their viewer, not only on yours. Singapore owner handover is still not automatically a CORENET X event; keep those processes distinct unless a contract ties them.
Phasing the as-built update during construction
Waiting until after practical completion to start as-built BIM is how ceilings hide the truth. A better pattern is zone-wise: when a floor’s services are installed and still visible, capture and update that floor. Then the ceiling closes. Then you still have a chance. This pattern needs a programme hook, which is why it sits near 4D thinking even when you do not buy a 4D film. The contractor’s BIM lead should put capture windows on the look-ahead.
Updates should be incremental with versioned models, not a single heroic rewrite. Incremental updates need element IDs that remain stable so that clash issues and asset records do not reset. If you replace every family every week, you are not updating; you are remodelling.
Photographs as a controlled input
A named photo set with room numbers and dates can support as-built where a scan is excessive: door swings, equipment labels, ceiling access panels. Photos are not a point cloud. They do not give reliable millimetre locations. They do prevent the wrong family from being left in a room. Store them with the model package. A freelancer should not rely on unmarked phone photos in a chat thread as the only record.
Owner operators and the first week after handover
If the owner cannot open Revit, spend a milestone on a tested IFC plus a space/equipment list in a format they can filter. Walk them through one floor. If they have a CAFM, do a mapping rehearsal with ten assets before you map ten thousand. Failure at ten is cheap. Failure at ten thousand is a project.
Passwords, licences, and plugin dependencies must be gone or documented. A model that only opens with a specialist’s custom add-in is not handed over. Native files plus a how-to note are the minimum.
Demolition, strip-out and partial records
Partial refurbishments produce partial as-builts. The model should show what was recorded and what is still design-era geometry, with a graphic or parameter distinction. Painting everything as as-built because the project is “finished” will poison the next renovation. Keep an archive of the design model. The as-built file should not be the only copy of history.
Mechanical water treatment plants, data halls and other dense rooms
These rooms justify scans even when the rest of the floor does not. Budget them separately. Occlusion is severe. Shutdowns may be required. The assumption log will be long and that is acceptable. Do not apply a typical-office Scan to BIM unit rate to a live data hall. See cost for why unit rates need exclusions.
What not to model as-built
Temporary protection, packaging, and people. Chairs unless the use is space planning. Every small-bore tube unless the use is a laboratory tie-in. Guessed buried services. Invented serial numbers. Design energy values. Those omissions should be listed so a future reader does not think they were not present on site.
As-built BIM for future demolition permits and alterations
The next team will ask: what is in this wall, what is in this shaft, what is the slab thickness we can trust. If your as-built model used generic walls, they will scan again. That may still happen — scans get better — but a typed as-built reduces the second team’s uncertainty. Write the intended next use if you know it. A model for wayfinding can be lighter than a model for structural alteration. Do not sell the light model as the heavy one.
Naming of record files
Include the record date in the file name. “AsBuilt.rvt” is how three dates overwrite each other. Follow the BEP. Store a read-only copy. If worksharing remains on, save a detached archive as well so a future office without your server can open it.
Residual design clashes in an as-built file
If a design clash was never built that way, it should not remain as a live clash in the record model. Either the geometry was updated to the field or the clash is historical and belongs in an archive log. Mixing historical clashes into a facilities model trains the owner to ignore issues. Clean with a method, not with a hide.
Mechanical nameplates and serials
Serial capture is slow and valuable for warranties. If it is in scope, use a room-by-room photo protocol. If it is not, do not leave “12345” as dummy data. Dummy data is worse than blank because it looks real in a CAFM import.
As-built BIM and warranties
Warranty periods care about what was installed, not what was designed. Equipment families and serials, where captured, support claims. A design family left in place with a marketing name will send a facilities person to the wrong spare part. If you cannot capture serials, capture manufacturer and model from submittals at least, and say serials were not captured.
Partial floors and phased occupation
Phased occupation means part of a floor is as-built and part is still a site. The model should use phases or a parameter so the owner does not trust a live work zone as a record. Date stamps per zone beat a single file-level date when occupation is staggered.
Exporting a record IFC
Test it on the owner's viewer. Rooms, equipment, and unique IDs should survive. If they do not, fix the export or change the handover format. Do not assume a successful native file is a successful owner file.
As-built BIM and hidden services
What you cannot see, you must not invent. Ground-penetrating radar, opening-up works, and specialist surveys are other appointments. The as-built BIM can host their results if provided, with the source named. It should not guess a pipe in a wall because “there is usually one.” Mark unknown. Owners prefer an honest unknown to a confident fiction that later becomes a drill injury.
Record models are dated opinions backed by evidence
An as-built BIM model is a dated opinion of the constructed asset, backed by scans, redlines, submittals, and photos you can still find next year. Keep the evidence with the file. Keep the unseen zones visible. Keep the owner’s room names. If you do those three things, the model is useful. If you do not, no amount of photoreal material will make it a record.
A facilities team that cannot find the record date, the unseen list, and the room mapping in the first five minutes of opening the package will not use the model. Put those three items in a one-page cover note. The cover note is a deliverable. It is not optional decoration.
Handover is a package: native file, tested IFC if agreed, evidence (scan, photos, submittals), unseen list, room map, and a dated cover note. Missing evidence makes a pretty file a rumour. Keep the rumour out of the owner’s archive.
Is a photogrammetry mesh an as-built BIM? It can be a record mesh. It is not a typed BIM model until someone models or classifies it.
Who signs the as-built? Whoever the contract names. A freelancer can prepare; they may not be the certifying surveyor.
How soon after completion should we scan? As soon as the relevant systems are visible and safe. Ceilings close; opportunity closes.
Do we model hangers as-built? Only if the use needs them. Facilities often does not. A future dense renovation might.
Can AI recognise equipment? It may assist tagging. Nameplates and submittals still need people. See AI and BIM 2026.
What if the contractor never modelled? Then as-built is a new modelling job from scan and drawings, not an update.
LOD 500 for the whole building? Rarely honest. Use a table by system.
Sources and reference notes
BIMForum/AIA LOD 500 language is industry usage for verified elements. Measured survey professional standards apply where a legal survey is required; BIM modelling is not automatically that survey. buildingSMART and client BIM libraries describe some handover schemas. Official Singapore processes for building works approvals are separate from owner handover unless a contract ties them.
Image brief
A dated stamp on a model properties view: “Record date, method: laser scan + submittals.” Split section of cloud versus modelled equipment. No “digital twin city” hero shot.
A buyer’s guide to Revit modeling services: architectural, structural and MEP scopes, file hygiene, family work, deliverables, pricing factors, and a hiring checklist for specialist freelancers.