Scan to BIM: Complete Guide from Laser Scan and Point Cloud to Revit Model
Scan to BIM turns laser scans and point clouds into usable Revit models for renovation, as-built records and coordination. This guide covers capture, registration, modeling rules, Level of Development, quality checks and hiring specialists.
Scan to BIM is the workflow that turns measured existing conditions — typically a laser scan and its point cloud — into a model that architecture, engineering and construction teams can use. The scan is a dense set of points in space. The model is a set of typed elements with levels, categories and parameters. Those are different objects. Tracing every point into a mesh is not BIM. Interpreting a building from a cloud, with stated tolerances and a Level of Development, is Scan to BIM.
A terrestrial laser scanner measures distances and angles from stations. Photogrammetry and some mobile systems also produce point clouds, with different error behaviours. The raw product is stations or chunks. Registration aligns them into one cloud in a coordinate system. Control (targets, survey points, known grids) determines whether that cloud sits on the project grid or floats in scanner space.
If Scan to BIM will later federate with a new design, registration must be on the same shared coordinates the BIM Execution Plan names. A beautiful cloud in the wrong place is a coordination hazard. Ask who owns survey control. A BIM modeller is not automatically a registered surveyor. Do not blur those professions.
Cloud density and accuracy are not the same. A dense interior scan of a plant room can still be noisy around shiny pipes. A sparse facade scan can still be accurate at corners if control is good. Write the required use: floor flatness study, architectural envelope, MEP as-built, heritage fabric, clash against a new insert. The use drives resolution, not a slogan of “high definition.”
Safety and access constrain capture: live hospitals, occupied offices, roads, roofs. Scanning cannot invent the back of a beam that was never seen. Occlusion is a scope fact. The model should mark unseen zones, not guess them.
What the modeller actually does
The modeller interprets. A wall in a cloud is a cluster of points that the specialist fits to a wall type with a thickness, a height, and a location line. If the wall is out of plumb, the brief must say whether to model it true, to model it plumb with a deviation note, or to model it as a mass for record only. Those three models look different and cost different amounts.
Revit Scan to BIM commonly uses the cloud as an underlay (Revit, Recap, or a coordination tool) while the specialist places walls, floors, roofs, columns, ducts and equipment families. Some teams mesh first; a mesh is still not BIM. Prefer categories that schedule. Model-in-place should be reserved for truly irregular heritage geometry, with a note.
MEP Scan to BIM is slower than architectural Scan to BIM. Pipes occlude each other. Insulation hides diameter. Valves need families. Ask whether you need centreline systems with assumed sizes, or measured outside diameters, or fabrication-level spools. Do not order fabrication LOD from a walkthrough scan.
Structural Scan to BIM must distinguish a beam’s painted fire protection from steel size. If you cannot see steel, you cannot honestly model steel size. You can model an envelope. Write that.
Level of Development for existing buildings
LOD language from AIA and BIMForum is widely used for new design. For existing buildings it is often stretched. Be explicit. “LOD 300 architectural envelope” might mean walls, floors, roofs, openings located to a stated tolerance, without interior fit-out. “LOD 350 plant room MEP” might mean main equipment and large bore pipes with clearances, not every 15 mm tube.
Level of Detail (how much geometry is shown) is not Level of Development (how much you may rely on the element). A highly meshed irregular cornice can still be unreliable as a quantity. A simple wall with a surveyed location can be highly reliable for area. Do not pay for decorative meshes if you need reliable walls. See the LOD article.
Tolerances should be numeric: for example, walls located so that a check measurement on a sample set of corners falls within an agreed band. This article does not invent a universal millimetre law. Agree the band with the surveyor and the use. Fit-out against a heritage wall needs a tighter conversation than a warehouse racking layout.
Quality checks that belong in the contract
Overlay the model on the cloud in section. If walls float 40 mm off the points, the model is a sketch. Check levels against a survey datum, not against “that looks like Level 2.” Check that openings exist where the cloud shows openings. Check that unseen areas are marked, not filled with typical design walls.
For MEP, section a congested rack. If pipes are pretty but ignore the cloud, reject the milestone. For structure, pick a connection: does the model claim a size the cloud cannot support?
Deliverables: native Revit, indexed cloud or a Recap file with a stated coordinate system, a deviation report (even a sampled one), a list of assumptions, and photographs of occluded zones if captured. IFC if exchange is required. Do not skip the assumption list; it is the honesty of Scan to BIM.
Uses: renovation, as-built, facilities, disputes
Renovation design uses Scan to BIM so new work fits old work. Clash detection then includes the existing cloud or the modelled existing as a trade. See clash detection.
As-built records use Scan to BIM at handover or after variations. That model should not keep design-phase generic families if the installed equipment is known; see as-built BIM.
Facilities teams use models for wayfinding, asset location and future works. They need parameters that match their asset list, not only geometry. That is a data brief.
Dispute and insurance uses need a chain of custody for the cloud and a conservative modelling rule: do not “clean up” a deformed slab if the deformation is the point. Tell the specialist the use. A pretty renovation model can be a bad evidence model.
Scan to BIM versus CAD to BIM
If you have both a cloud and old drawings, the drawings are hypotheses; the cloud is measurement (within its errors). Do not force the cloud to match a 1990s CAD plan that was never true. Use CAD for system intent (a schematic) and the cloud for location. The CAD to BIM guide is the drawing-led path; this article is the measurement-led path. Many jobs need both, in that order of trust.
Briefing and hiring
A Scan to BIM brief includes: building type, access constraints, who supplies the cloud, coordinate system, software versions, disciplines, LOD/tolerance table, unseen-area rule, sample zone as milestone one, and whether registration is in scope. If the client only has unregistered scans, say so; registration is a skill.
Samples to request: a section overlay of model versus cloud, a plant room, a facade bay, a deviation table for a sample. Renders of a mesh are not samples.
Hire on BIMProSG with a sample room first. Packaged services may list Scan to BIM of a stated area. Project postings suit whole buildings. Protected milestones should release on overlay quality, not on a 3D screenshot.
Limitations you should write down
Occlusion: above ceilings not scanned, inside shafts, behind insulation
Specular surfaces and glass
Moving people and fit-out that changed after the scan date
Legal survey versus BIM interpretation
MEP size assumptions
Cost of modelling clutter (chairs, temporary works) that you should usually exclude
A specialist who lists these unprompted is more trustworthy than one who promises a “perfect twin.” Digital twin language is optional and often inflated; an as-built BIM model with a date stamp is enough for most construction uses.
Quality checklist
Cloud registered to project coordinates
Sample overlay in plan and section
Unseen zones marked
Categories correct
MEP systems only as scoped
Assumption log
Scan date recorded
File hygiene (no meshed furniture unless requested)
Native file opens in agreed Revit version
Interior fit-out, heritage fabric and industrial plant — three modelling temperaments
An office fit-out Scan to BIM job is mostly partitions, ceilings, and a few services above a tile. The temptation is to model every chair. Resist unless the use is a furniture relocation study. Partitions that stop at the ceiling tile are not full-height walls; the cloud will show that if you look. Modelling them as full-height will break the next tenant’s services coordination.
Heritage fabric is the opposite temperament. Irregular vaults, out-of-plumb walls, and carved stone may need masses or adaptive families, plus a stated decision about whether the model is a measured record or a simplified coordination envelope. Mixing those two in one file without notes will mislead a structural engineer who thinks a wall is plumb and load-bearing in the way a new wall would be.
Industrial plant and data halls are closer to MEP Scan to BIM at high intensity. Equipment skids, cable ladders, and pipe racks occlude. The brief must name the diameter cut-off, whether skids are one family or many, and whether the cloud date matches a shutdown. A scan during operation will miss what was behind a running unit. A specialist should say so in the assumption log rather than inventing the hidden face.
Colour, classification and the cloud as a coordination object
Some teams keep the registered cloud in Navisworks as a clash partner: new design versus existing points. That can catch a beam that hits an existing duct you did not model. It can also generate thousands of hits against clutter. Isolate the cloud by region. Do not clash a whole building cloud against a new typical floor without a section box.
Classification of modelled existing elements matters if the model will feed quantities or assets. An existing wall that is plastered masonry should not inherit a new drywall type because that type was in the template. Create existing types. Phase them as existing. Future demolition will then be a phase filter, not a detective story.
Photographs taken at scan time are underrated deliverables. A pipe that looks like 100 mm in a noisy cloud may be labelled 80 mm in a photo of a stencil. Ask for photo linking if the scanner system provides it. It is cheaper than modelling the wrong diameter into a fabrication conversation.
File sizes, worksharing and handing the cloud to a design team
Point clouds are large. The modelling team needs a strategy: central Recap, regioned RCS files, or a coordination-only decimated cloud. Revit does not need the survey-grade dense cloud on every modeller’s disk if a regioned file covers the floor they are working on. Write the strategy so a freelancer in another office is not waiting on a 200 GB upload without a regioning plan.
When the model returns to an architect, they need to know what they may edit. Existing walls should be pinned or workset-protected if the architect’s job is new partitions only. A design team that “tidies” existing walls to the grid will destroy the point of Scan to BIM. The BEP should say: existing is measured; new is designed; conflicts are RFIs.
Capture planning with the modeller in the room (or on the call)
A scan that misses the soffit above a congested corridor cannot be modelled into truth. The modeller should help plan stations: look-up shots into ceilings during a controlled tile lift, night access to plant rooms, and extra stations at riser doors. That is not the modeller pretending to be a surveyor. It is the modeller saying which surfaces the LOD table needs to see. If access cannot be granted, the assumption log should list those surfaces as unseen before modelling starts, not after a pretty but fictional soffit is delivered.
Control points should be coordinated with the project grid. If the surveyor’s system is a national grid and the building BIM is an internal origin, the BEP must show the transform. A freelancer who “moves the cloud until it looks right” is creating a unique coordinate planet. Federation with new design will then be an accident.
Colourised clouds are useful for material interpretation; they are not a substitute for a type decision. A red pipe in a photo is not automatically a fire service. Confirm with labels, schematics, or a site person.
Modelling order that reduces rework
Do datum and envelope first: levels, grids if they can be inferred, floors, major walls, structure you can see. Then major openings. Then MEP mains. Then equipment. Then small bore if in scope. Teams that start with furniture and feature lights waste the first week and still have a floating slab. Milestone reviews should follow this order so you can reject an envelope that does not overlay before you pay for valves.
For architecture, stacked walls and curtain systems should be decided early. For structure, do not guess steel sizes inside fire protection. For MEP, do not guess insulation thickness if the cloud shows a lagged diameter; write the assumption.
Deviation reporting without fake millimetre guarantees
A sample of corners, a sample of pipe invert-like measurements where possible, and a note on noise around glass and stainless plant. Present deviations as a table of checks, not as a single “accuracy” marketing number. If a check fails, either remodel or reopen the unseen/assumption log. Do not average the cloud into a straight wall if the wall is bent and the use is a fit-out against that wall.
Heritage and industrial uses will want different reporting. A warehouse racking job may care about floor flatness more than ornate cornices. Ask the use before you model the cornice.
Living with the cloud after the model exists
Keep the cloud. The model is an interpretation with a date. Future disputes, future fit-outs, and future QTO arguments will want the points. Region the files so the next team can load one floor. Write the path in the handover note. A Scan to BIM service that deletes the cloud because the model “is done” has destroyed the evidence of its own work.
When new design is inserted, clash against both the model and, where useful, the cloud in a section box. The model may have omitted a bracket the cloud still shows. That is a feature of Scan to BIM, not a failure, if the brief allowed omissions below a size.
Indoor mobile scanning and mixed methods
Mobile scanners and photogrammetry can fill gaps, with different error profiles. The brief should name the mix. A mobile pass down a corridor plus terrestrial stations in a plant room is a common honest mix. A mobile-only plant room may miss tops of racks. Do not pretend all scanners are equal. Ask the capture team for their method statement and align it to the LOD table.
Modelling MEP from a cloud when labels exist
Stencil labels and valve tags in photos save hours of diameter guessing. Request that capture includes photos of labels. The modeller should record the label in a parameter when they can read it. When they cannot, they should not invent a diameter from a noisy cluster alone without an assumption tag.
Safety, permits and occupied buildings
Capture may need permits, after-hours access, and infection-control rules in healthcare. Those are not BIM software issues, but they delay clouds and therefore models. Put access constraints in the brief so a freelancer does not promise a date that access cannot support. Confidentiality of clouds of homes and secure plants belongs in the order.
Delivering a Scan to BIM model into a live design team
The design team will want to start new work before the as-existing model is finished. Issue the envelope first. Then the plant rooms. Tell them what is still unseen. If they model new ducts through an unseen void, that is a known risk. The assumption log protects both sides.
Quality failure modes worth failing a milestone for
Envelope that does not overlay in section. Levels that ignore survey datums. MEP as generic models. Unseen zones filled with typical design. Cloud not on project coordinates. No assumption log. Any of these is a fail. Pretty meshes of chairs are not a pass.
Who should capture the scan? A survey-capable team. BIM modellers may attend to specify density. Do not assume one person is both unless they can prove both.
Can we model from photographs only? Photogrammetry can help facades and some interiors. For plant rooms, laser is usually more reliable. Scope the method.
Do we model every conduit? Usually no. Agree a diameter cut-off.
How do we handle out-of-plumb walls? State the rule: true, plumb-with-note, or mass.
Is Recap required? Use whatever pipeline keeps coordinates. Recap is common in Autodesk stacks, not a law.
Can AI auto-extract walls? It can propose. A person still checks openings, types and occlusions. See AI and BIM in 2026.
What about Singapore submissions? An existing-conditions model is not automatically a CORENET X BIM submission. Submission rules are official and project-specific; see the Singapore guide.
Sources and reference notes
Scanner manufacturers publish accuracy statements for instruments; those are not the accuracy of a finished BIM element. RICS and similar professional bodies publish measured survey guidance in some markets; use the document that applies to your appointment. Autodesk documents Recap and Revit point-cloud linking. BIMForum LOD is industry usage, not a statute. This article does not cite invented millimetre guarantees.
Image brief
A split view: point cloud on the left, typed Revit walls and ducts on the right, same section cut. A second image: registration targets on a grid. No glowing “digital twin” cityscapes.
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.