TL;DR
A Revit model can be within ±10 mm of the registered cloud at LOD 300 and still fail on the project because of coordinate, phasing, or workset problems — accuracy and usability are separate checks. LOD (BIMForum Level of Development) describes how developed a model element is; USIBD LOA (Level of Accuracy) describes how dimensionally faithful it is to reality. Shared coordinates and origin-to-origin linking determine whether the point cloud and model land correctly in an existing project — the most common source of rework after handoff. Phasing set incorrectly on a renovation job is the most common reason a scan-to-BIM model gets rebuilt instead of reused. A sample deliverable, opened and checked against these 8 items before commitment, catches nearly all of these problems for free.
# 8 Revit Checks to Run Before You Hire a Scan to BIM Service
A registered point cloud can be dimensionally correct — ±5 mm survey-grade registered accuracy, tied to control, verified by independent check measurements — and still be unusable the day it lands in your Revit project. The failure isn't in the scan. It's in the handoff: the model links in the wrong place, phasing is wrong, or two people on your team can't work in it at once.
That gap is rarely discussed because most buyer guides stop at accuracy numbers. This page starts where those guides end: inside the Revit file. Every check below is something an architect or BIM manager can verify on a sample deliverable in under five minutes, before signing a contract.
TL;DR
- A Revit model can be within ±10 mm of the registered cloud at LOD 300 and still fail on the project because of coordinate, phasing, or workset problems — accuracy and usability are separate checks.
- LOD (BIMForum Level of Development) describes how developed a model element is; USIBD LOA (Level of Accuracy) describes how dimensionally faithful it is to reality. They answer different questions and both should be stated in writing.
- Shared coordinates and origin-to-origin linking determine whether the point cloud and model land correctly in your existing project — this is the single most common source of rework after handoff.
- Phasing set incorrectly on a renovation job (Existing vs. New Construction vs. Demolition) is the most common reason a scan-to-BIM model gets rebuilt instead of reused.
- A sample deliverable, opened and checked against these 8 items before commitment, catches nearly all of these problems for free.
Why "accurate" and "usable in Revit" are different problems
A model can meet its stated accuracy and still fail your project if it isn't built the way your Revit workflow expects it to be built. Accuracy is measured against the point cloud; usability is measured against how your team links, phases, and edits the file. Both need to be confirmed separately, in writing, before work starts.
The industry conflates two standards that answer different questions. LOD (Level of Development), defined by the BIMForum LOD Specification, describes how developed and reliable a model element's geometry, information, and reliability are — is a wall a generic placeholder or a modeled assembly with correct materials and dimensions. LOA (Level of Accuracy), defined by the USIBD Level of Accuracy Specification (C120) and Guide (C220), describes dimensional fidelity — how closely the modeled geometry matches measured, physical reality, expressed in banded tolerances (LOA 10 through LOA 50). A model can be built to a high LOD with poor LOA, or vice versa. Ask for both, separately, and get both in writing.
| Standard | What it governs | What it does not tell you |
|---|---|---|
| BIMForum LOD 100–500 | Element development: geometry, reliability of information | Dimensional accuracy to the physical building |
| USIBD LOA 10–50 | Dimensional fidelity: Measured vs. Represented Accuracy | Whether the element geometry is fully developed |
There's a second gap that has nothing to do with either standard: file hygiene. A model can carry the right LOD and LOA and still be a liability if it's one monolithic workset, has hundreds of unresolved warnings, or bloats to a file size your hardware can't open on a laptop in the field. That's what the 8 checks below cover.
The 8 Revit checks
1. Shared coordinates and origin-to-origin linking
What to ask: How will the point cloud and the delivered model land in your project's coordinate system — by shared coordinates, or origin-to-origin?
How to verify it in Revit: Link the sample model or point cloud into a blank project using "Auto — Origin to Origin," then check the Project Base Point and Survey Point against your survey control. If the provider has already acquired site control, the link should land correctly without manual repositioning.
Red flag: "We'll set it up on our end" with no explanation of which coordinate system or control network the model is tied to. That answer means the alignment work becomes your problem after delivery, not before.
2. LOD committed per discipline, in writing
What to ask: Is the LOD stated separately for architectural, structural, and MEP elements, or is it a single number for the whole model?
How to verify it in Revit: Open the sample, select a wall, a structural column, and an MEP element if present, and compare their development against the stated LOD for each discipline.
Red flag: A proposal that quotes one LOD figure for "the model" without breaking it out by discipline. Architectural LOD 300 and structural LOD 300 require very different modeling effort and cost.
3. Represented accuracy stated against the registered cloud
What to ask: What is the modeled geometry's tolerance to the registered point cloud, and at what LOD? Zealot's method holds model faces to ±10 mm of the registered cloud at LOD 300.
How to verify it in Revit: Link the RCP/RCS point cloud alongside the model and visually check wall faces and floor slabs against the cloud at several points, or run a deviation/clash check if your QA tooling supports it.
Red flag: A stated accuracy with no reference point — "±5 mm" without saying accurate to what, checked how, or at what LOD.
4. Worksets and model division
What to ask: Is the model divided into worksets by discipline, level, or zone, so more than one person can work in it simultaneously?
How to verify it in Revit: Open Collaborate > Worksets and check the breakdown. A model intended for team use on a renovation project should not load as a single default workset.
Red flag: One monolithic workset with no division — workable for a quick reference model, not for active design coordination.
5. Phasing set correctly for renovation
What to ask: Are elements assigned to Existing, Demolition, and New Construction phases, matching how your team plans to design against them?
How to verify it in Revit: Open a view, check its Phase and Phase Filter properties under View Templates, and confirm existing-condition elements are set to the Existing phase, not New Construction.
Red flag: Everything modeled into a single phase. This is the single most common cause of a scan-to-BIM model being effectively rebuilt from scratch on a renovation job — a model with no phasing can't distinguish what's being kept from what's being demolished.
6. Native families vs. in-place geometry
What to ask: Are walls, doors, and structural elements built as native Revit families and system families, or imported as mesh or DirectShape geometry standing in for real building elements?
How to verify it in Revit: Select a handful of elements and check their category and family in the Properties panel. A wall should report as a Revit Wall, not a generic model or imported solid.
Red flag: Elements that are DirectShape, imported mesh, or linked CAD substituting for modeled building components — they won't schedule, tag, or coordinate the way native families do.
7. The registered point cloud delivered alongside the model, in a format Revit reads
What to ask: Does the deliverable include the registered point cloud itself — RCP/RCS for Revit, plus an open-format E57 master — or only the finished model?
How to verify it in Revit: Confirm the RCP file links directly with Manage Links > Point Clouds, and confirm an E57 master file is included separately for use outside Autodesk software.
Red flag: Model-only delivery, or a proprietary viewer with no exportable point cloud. Without the source cloud, your team has no way to independently verify the model later.
8. Sample deliverable before commitment
What to ask: Can you provide a sample of a comparable project's Revit model, at the LOD you're proposing, before contract signature?
How to verify it in Revit: Open the sample and run checks 1 through 7 on it directly — coordinates, LOD by discipline, tolerance to the cloud, worksets, phasing, family use, and cloud delivery format.
Red flag: A provider unwilling to share a sample, or one that offers only screenshots or a locked viewer instead of an openable file.
A five-minute Revit acceptance test
Once a sample or delivered model is in hand, run this sequence before accepting it:
- Link the file. Use Insert > Link Revit (or open the model directly) and confirm it loads without errors.
- Check coordinates. Compare Project Base Point and Survey Point locations against your survey control or existing site model.
- Check phases. Open View Properties on a floor plan and confirm the Phase is set to Existing, with a Phase Filter that shows existing elements distinctly from any new work.
- Select five elements at random — a wall, a door, a column, a duct or pipe if MEP is included, and a floor — and check their category in the Properties panel. Each should report as a native Revit category, not a generic model or import.
- Run a deviation check against the cloud. Link the RCP alongside the model and spot-check wall faces at three or four locations for visible gaps beyond the stated tolerance (±10 mm at LOD 300).
- Check worksets. Confirm the model is divided by discipline or level under Collaborate > Worksets.
- Check the warnings count and file size. Open the Warnings dialog (Manage > Warnings) — a high, unreviewed warning count is worth asking about directly. Confirm the file size is workable for your hardware and workflow.
A model that passes all seven is one your team can open, link, and design against without rework. A model that fails two or more of these is worth a conversation with the provider before the contract is signed, not after.
What this costs and how long it takes
Scan-to-BIM projects move through five stages — planning, field capture, registration, modeling, and QC — and each has a documented range. Field capture covers 80,000–120,000 sq ft per day; registered point clouds are typically returned in 3–5 business days; LOD 200 modeling for roughly 100,000 sq ft runs 10–15 business days, while LOD 300 for the same area runs 3–5 weeks. Typical end-to-end delivery across smaller renovation projects runs 1–3 weeks.
For a worked example: a 100,000 sq ft renovation would need roughly one field day for capture, 3–5 business days for the registered cloud, and — if LOD 300 architectural modeling is specified — 3–5 weeks for the finished Revit model with the checks above already satisfied. What moves that number is scope per discipline: adding structural or MEP at the same LOD extends the modeling timeline, since each discipline is modeled and checked separately, not bundled into one pass. Quote turnaround itself is typically same-day to 24 hours.
Why this matters more on renovation than new construction
New-construction Revit models are built from a clean design intent; there's no competing "as-is" condition to reconcile. Renovation and adaptive-reuse projects are different: the scan-to-BIM model has to coexist with a design team actively drawing changes against it, often with multiple consultants linking the same file. That's why checks 1, 4, and 5 above — coordinates, worksets, and phasing — matter more on renovation work than the accuracy number alone. A model can be dimensionally perfect and still cost a design team days if the architectural team can't work in it alongside structural and MEP without conflicts.
This is also where LOA does real work that LOD can't. A structural engineer sizing a retrofit steel connection against an existing column needs to know the *represented accuracy* of that column's modeled position — is it LOA 20 (±5 mm, individual points), LOA 30 (±15 mm), or looser — not just that the column exists as a modeled family at some LOD. Ask for the LOA band alongside the LOD figure, in the same line of the proposal, not as a separate document that never surfaces.
Reading a proposal: what "committed in writing" should look like
A scan-to-BIM proposal that has answered all 8 checks above reads differently from one that hasn't. It states LOD per discipline (not one blanket number), it names the coordinate system and control method, it commits to a stated tolerance against the registered cloud, and it lists the deliverable formats by name — RVT, RCP/RCS, E57 — rather than "digital files." If a proposal is vague on any one of these, that's the item to raise before signature, not after the model is delivered and the design schedule is already running.
Frequently Asked Questions
Related reading: Point Cloud QA for Scan to BIM, How Poor Point Clouds Cause BIM Coordination Problems, Evaluating 3D Laser Scanning Services in the US, Benefits of 3D Laser Scanning for As-Builts, LOD 200 vs. 300 vs. 400 in a Revit Model From Scan, and Scan to BIM Pricing: What a Revit Model Costs.
Frequently Asked Questions
Related reading: Point Cloud QA for Scan to BIM, How Poor Point Clouds Cause BIM Coordination Problems, Evaluating 3D Laser Scanning Services in the US, Benefits of 3D Laser Scanning for As-Builts, LOD 200 vs. 300 vs. 400 in a Revit Model From Scan, and Scan to BIM Pricing: What a Revit Model Costs.