TL;DR
TL;DR: A complete Scan to BIM handover for a renovation project includes a discipline-appropriate LOD model, a linked and registered point cloud, shared coordinates with fixed levels and grids, disciplined worksets and naming, model-derived 2D sheets, a deviation report, and a defined file format package (RVT, E57, RCP, IFC, DWG). Missing any one of these turns coordination problems into field problems.
Table of contents
- Why deliverables need to be specified, not assumed
- Deliverable 1: the Revit model, LOD by discipline
- Deliverable 2: the linked, registered point cloud
- Deliverable 3: shared coordinates, levels, and grids
- Deliverable 4: worksets and naming standards
- Deliverable 5: 2D sheets derived from the model
- Deliverable 6: clash and deviation reporting
- Deliverable 7: the handover package and file formats
- A receiving workflow for the architect's project team
- FAQ
Why deliverables need to be specified, not assumed
Renovation architects who treat Scan to BIM as a single line item — "provide a Revit model of existing conditions" — routinely receive a file that is technically a model but is unusable for coordination. It may lack shared coordinates, bury geometry in a single workset, or omit the point cloud link entirely. None of that is visible from a rendered screenshot in a proposal.
The fix is to specify deliverables the way a structural engineer specifies a steel connection: as a list of discrete, verifiable items, each with an acceptance criterion. This is the same discipline that governs a 3D laser scanning scope of work, and it should carry through into the Scan to BIM services contract, not stop at the field capture phase. The seven deliverables below cover what a renovation team actually opens, links, and works from once the model arrives.
Deliverable 1: the Revit model, LOD by discipline
What it is. The native RVT file, built from registered scan data, with geometry developed to a specified Level of Development per element category and discipline — not a single blanket LOD for the whole building.
How to specify it. Assign LOD by category: walls and structure at LOD 300, MEP main runs at LOD 200-300, and any elements slated for direct tie-in (existing duct stubs, structural connections) at LOD 400. Reference LOD 200 vs 300 vs 400 in a Revit model from scan in the contract language so both sides are working from the same definitions. For renovation work specifically, request the Revit scan to BIM renovation workflow, which is built around tie-in and phasing needs rather than new-construction modeling.
How to verify it. Open the model with the point cloud visible and spot-check element faces against the cloud at a sample of locations per floor — corners, openings, and any area flagged for renovation work. Confirm the LOD matrix delivered matches what was contracted, category by category.
Failure mode when missing. A model built to a single undocumented LOD either over-delivers on areas nobody needs (wasted fee) or under-delivers on the areas where the renovation actually touches the building, forcing the design team to re-verify dimensions in the field mid-project.
Deliverable 2: the linked, registered point cloud
What it is. The scan data, registered into a single coordinate system and linked into the Revit file as an RCP/RCS reference — not deleted after modeling, but retained as a living reference plane.
How to specify it. Require that the point cloud remain linked in the delivered RVT, positioned by shared coordinates (see Deliverable 3), and that registration accuracy be documented against the field-recorded tolerance, typically within 5mm.
How to verify it. Toggle the point cloud link visibility in a 3D view and section through several locations to confirm alignment with modeled geometry. Check the registration report for control point residuals rather than accepting a verbal assurance.
Failure mode when missing. Without the linked cloud, the architect has no independent way to check the model against actual field conditions later in design or during construction administration — every discrepancy that surfaces in the field becomes a dispute over whose data is wrong. Point cloud organization practices from organize point cloud data for Scan to BIM apply directly here.
Deliverable 3: shared coordinates, levels, and grids
What it is. A Revit project set up on shared coordinates tied to a fixed survey or site reference, with levels matching actual floor-to-floor conditions and grids (where applicable) matching structural bay lines rather than arbitrary Revit defaults.
How to specify it. Require that shared coordinates be established at project origin and documented, not left at "internal origin." Levels should reflect verified finish-floor elevations from the scan, not assumed uniform story heights.
How to verify it. Acquire coordinates for a handful of known site benchmarks and confirm they resolve correctly in the model. Check level elevations against a few field-measured floor-to-floor heights.
Failure mode when missing. Every downstream discipline that links the model — structural, MEP, civil — inherits a coordinate mismatch. Consultants end up manually shifting linked files against each other project by project, and small errors compound into the kind of coordination gap covered in as-built accuracy and design coordination.
Deliverable 4: worksets and naming standards
What it is. A model organized into worksets by discipline or system (architectural shell, existing MEP, structure, site), with a documented naming convention for views, sheets, and families.
How to specify it. Provide or request a project-specific BIM execution plan that defines workset breakdown and naming before modeling starts, not after.
How to verify it. Open the Worksets dialog and confirm the breakdown matches what was agreed. Spot-check family and view names against the naming standard document.
Failure mode when missing. A model with everything in Workset1 cannot be selectively opened, closed, or worked in by different team members without loading the entire dataset, which slows every session and makes large renovation models unworkable on typical office hardware.
| Deliverable | Verification method | Typical failure if skipped |
|---|---|---|
| LOD model by discipline | Compare geometry to point cloud, category by category | Under- or over-modeled areas |
| Linked point cloud | Toggle visibility, section through key areas | No independent field check later |
| Shared coordinates/levels/grids | Test against known benchmarks | Coordination mismatch across disciplines |
| Worksets and naming | Open Worksets dialog, check naming doc | Unworkable, slow-loading model |
Deliverable 5: 2D sheets derived from the model
What it is. Existing-conditions plans, sections, and elevations generated directly from the Revit model — not drafted separately in 2D and delivered alongside it as an unrelated file.
How to specify it. State explicitly that sheets must be view-based outputs of the model, tagged to model elements, so that any future model revision updates the sheet automatically. Coordinate this with floor plans deliverable expectations if plans are also required as a standalone product for permitting or leasing.
How to verify it. Change a wall or door in the model in a test session and confirm the corresponding sheet view updates. If it does not, the sheets were drafted independently and will drift from the model over time.
Failure mode when missing. Hand-drafted sheets diverge from the 3D model silently. A contractor working from the sheet set and a designer working from the 3D model end up coordinating against two different versions of "existing conditions" without realizing it.
Deliverable 6: clash and deviation reporting
What it is. A documented comparison between the as-scanned point cloud and either the modeled geometry or an existing set of legacy drawings, flagging areas where they diverge beyond the specified tolerance.
How to specify it. Set a tolerance threshold in advance — commonly around 10mm at LOD 300 — and require that any deviation beyond it be reported with location and magnitude, not just flagged as "differences noted." This is the same discipline covered in Scan to BIM tolerance analysis for engineers and point cloud QA in Scan to BIM.
How to verify it. Review the deviation report against a sample of flagged locations in the model, and confirm the tolerance basis matches the contract language rather than an unstated internal default.
Failure mode when missing. Without a deviation report, legacy drawings and field reality are assumed to agree until a wall opening lands in the wrong spot during construction. Renovation and adaptive reuse projects, which lean on incomplete or outdated original drawings, are the most exposed to this failure.
Deliverable 7: the handover package and file formats
What it is. The full set of files needed for every consultant and contractor to work with the deliverable in their own software, not just the native Revit file.
How to specify it. Require the native RVT model, the registered point cloud in E57 and RCP/RCS, an IFC export for non-Revit users, and DWG exports of key sheets. Confirm the format list against point cloud file formats: E57, RCP, LAS, PTS so nothing is assumed.
How to verify it. Open each file type independently — not just the RVT — before the field team demobilizes or the contract closes out. An IFC that fails to open in a structural engineer's software is a problem discovered too late if it surfaces after handoff is complete.
Failure mode when missing. A single-format handover locks out any consultant not running the same Revit version, forcing a re-export cycle that delays coordination meetings and, on multi-discipline renovation teams, becomes a recurring bottleneck every time a new file is needed.
A receiving workflow for the architect's project team
- Confirm the LOD matrix and tolerance basis against the original scope of work before opening the model.
- Open the RVT with the linked point cloud visible and spot-check geometry at a sample of locations per floor.
- Verify shared coordinates, levels, and grids against known site benchmarks.
- Check workset breakdown and naming against the BIM execution plan.
- Test that 2D sheets update when model elements change.
- Review the deviation report for any flagged areas exceeding the agreed tolerance.
- Open every file in the handover package in its intended software before sign-off.
FAQ
What LOD should a renovation Revit model be delivered at?
Most renovation work is specified at LOD 200-300 for existing conditions, with LOD 400 reserved for specific elements like MEP tie-ins or historic assemblies that need fabrication-level detail. The LOD should be assigned by element category and discipline, not applied uniformly across the whole model.
Should the point cloud stay linked in the Revit file after modeling is complete?
Yes. The registered point cloud (RCP/RCS) should remain linked in the model as a permanent reference, not deleted after modeling. It is the only way to verify the model against reality later in design or during construction administration.
What accuracy should a renovation architect expect from a scan-to-BIM model?
Field-registered scan data is typically accurate to within 5mm, and the resulting Revit model should hold a typical tolerance of about 10mm at LOD 300. Tolerance should be stated in the deliverable specification, not assumed.
Why do model-derived 2D sheets matter if the 3D model is accurate?
Sheets generated directly from the model stay synchronized with any model updates and prevent the common failure mode where a hand-drafted plan silently diverges from the as-built geometry used for design decisions.
What file formats should be included in a Scan to BIM handover package?
A complete package typically includes the native RVT model, the registered point cloud in E57 and RCP/RCS, an IFC export for non-Revit consultants, and DWG exports of key sheets, so every downstream user can open the deliverable in their own software.