Ordering a scan-to-BIM deliverable that comes back usable starts with four things specified up front: LOD per building system, file format, coordinate system or shared origin, and the QA acceptance criteria. Leaving any of these unspecified is the most common reason a delivered model needs rework.
This post is for architects who already understand what scan-to-BIM is and need a practical checklist for what to include in the order so the deliverable comes back ready to design against.
What should be in a scan-to-BIM request before the scan happens?
Four things, at minimum:
- LOD per system. Not one number for the whole building — specify architecture, structure, and MEP separately, based on how each will actually be used.
- File format. Revit (RVT) is standard; specify the Revit version if the project team is on an older release, since backward compatibility isn’t guaranteed.
- Coordinate system or shared origin. If the model needs to align with an existing site survey, civil drawing, or another consultant’s model, that shared origin point needs to be established before modeling — not reconciled afterward, consistent with the National BIM Standard-United States.
- QA acceptance criteria. What dimensional tolerance is acceptable, and who signs off before the model is considered final. Architects who specify this up front get fewer surprises at delivery.
What deliverables come out of a scan-to-BIM order?
Standard deliverables are the Revit model itself, the source point cloud (E57 format) so the firm retains the raw measured data independently of the model, and a brief QA summary noting any areas the scan couldn’t reach or verify. CAD (DWG) floor plans and sections are available as an add-on if the project needs 2D documentation alongside the model.
What’s the architect’s role once the model is delivered?
Reviewing it before design work builds on top of it. Even with QA on P3D’s end, the architect of record should spot-check the model against the acceptance criteria set at order time — particularly at LOD transitions, where architecture might be LOD 300 but adjacent MEP is LOD 200. A five-minute review at delivery catches mismatched expectations before they become design-phase rework.
How does specifying scope up front change the timeline?
It shortens it. Projects that arrive with LOD, format, and coordinate system already decided move straight to modeling after the scan. Projects that leave these decisions open usually need a scoping call after the scan but before modeling starts, which adds time without adding value — the same conversation, just later in the process. Specifying scope before the scan, not after, is the single biggest lever architects have over how fast a scan-to-BIM deliverable comes back.
What does this look like on an actual order?
A Grand Rapids architecture firm ordering a scan-to-BIM deliverable for a historic building adaptive-reuse project specified LOD 300 for architecture and structure (needed for construction documents), LOD 200 for existing MEP (being replaced entirely, so dimensional precision on the old system wasn’t worth paying for), and requested the model share an origin point with the firm’s existing site survey so both files would align without manual repositioning. That level of specification meant the model went from scan to usable Revit file with a single delivery review, not a back-and-forth.
Where does this process still require judgment calls that a spec sheet can’t cover?
Unusual existing conditions — a structural element that doesn’t match any standard Revit family, a renovation that layered three different eras of construction on top of each other — still require a modeler’s judgment about how to represent them, even with LOD and format fully specified. That’s a conversation worth having directly with the modeling team rather than trying to write every edge case into the initial order.
These four specification items matter most on renovation and adaptive-reuse projects, where the existing building has more variability than new construction. A ground-up building typically has a simpler existing-conditions story — fewer surprises, more consistent construction methods throughout. A building that has been added onto, renovated, or repurposed across multiple decades tends to have inconsistent structural systems, mismatched floor-to-floor heights, or mechanical systems that were never fully documented, which is exactly the kind of variability that makes LOD and QA criteria worth deciding deliberately rather than defaulting to a standard package.
Coordinate systems matter more than architects sometimes expect. A model that isn’t aligned to an existing site survey or a structural engineer’s model looks fine on its own, but creates real coordination problems the moment two consultants’ files need to be overlaid — clashes that aren’t real clashes, dimensions that don’t reconcile, hours spent figuring out why two supposedly aligned files don’t actually align. Establishing a shared origin point before modeling starts avoids that entirely.
Do I need to know LOD terminology to place a scan-to-BIM order?
No. P3D will walk through what LOD each system needs based on how the model will be used — the checklist here is what to have decided by the time modeling starts, not something the architect has to specify unaided.
Can P3D match an existing Revit model’s naming conventions and family types?
Within reason — provide the existing project’s Revit standards or family library at order time, and the modeling team will match naming conventions and family usage where the existing point cloud data supports it.
What if the delivered model doesn’t meet the QA acceptance criteria we specified?
Flag the specific discrepancy against the criteria set at order time. Because those criteria are defined up front, revisions against them are scoped as a correction, not a new request.
How far in advance should LOD and format be decided before the scan date?
Ideally before scheduling — it doesn’t change the capture itself, but knowing the target LOD and format lets P3D confirm turnaround and pricing accurately before the site visit rather than after.
Related reading: Matterport to BIM: How Reality Capture Feeds Construction Documentation · Understanding LOD: What Level of Detail Means in BIM from Reality Capture · Scan-to-BIM for Architects: Workflow, Deliverables, and What to Specify (companion piece — general workflow)
Planning a scan-to-BIM order? Call 616-312-3947 or visit perspective3-d.com/get-in-touch.