8 Structural Deliverables to Confirm Before You Hire a Scan to BIM Service

# 8 Structural Deliverables to Confirm Before You Hire a Scan to BIM Service

TL;DR

• A structural BIM contract should name eight specific deliverables — not just "a Revit model" — each with its own format, tolerance, and acceptance criterion.
• LOD (BIMForum Level of Development) describes how complete a model element is; LOA (USIBD Level of Accuracy) describes how closely it matches reality. They answer different questions and neither substitutes for the other.
• Zealot's registered point clouds hold ±5 mm registered accuracy; model faces produced from those clouds hold ±10 mm to the registered cloud at LOD 300.
• The single most common source of structural BIM rework is an unstated modelling convention — most often whether primary members were modelled to centreline or to face.
• A one-page deliverable spec, filled in before a contract is signed, closes most of the gaps that show up later as RFIs and change orders.

By the ZEALOT Reality Capture technical team. Published 2026. Last updated 2026.

Structural engineers and BIM managers who buy scan to BIM services are frequently handed a scope of work that lists "point clouds, BIM model, as-built drawings" and nothing else. That phrase is not a specification — it names a category of file, not the tolerance, format, or convention that determines whether the deliverable is usable for structural analysis or coordination. Every unresolved item below has, in practice, turned into an RFI, a re-model, or a coordination clash discovered after fabrication drawings were already underway.

This page functions as a checklist: eight deliverables, what to specify for each, the tolerance that applies, the expected file format, and the failure mode that results when the item is left vague. A pasteable one-page spec block and a consolidated tolerance table follow the checklist so the items can go directly into a scope of work or RFP.

Why "a Revit model" is not a deliverable specification

"A Revit model" specifies a file extension, not an outcome. It says nothing about which Level of Development (LOD) applies to which discipline, whether the model's geometry was measured directly from the registered point cloud or represented from record drawings, or which tolerance the model is held to. BIMForum's LOD Specification (cite by edition year in the contract) defines LOD 100 through 500 as a statement of how much geometric and non-geometric detail a model element contains at a given phase. USIBD's Level of Accuracy (LOA) Specification C120 and Guide C220 define a separate, unrelated concept: how closely the modeled or captured geometry corresponds to the physical condition, expressed as Measured Accuracy or Represented Accuracy.

LOD and LOA are frequently conflated in scopes of work, and the confusion is expensive: a model element can be LOD 350 (fully detailed, connections modeled) while still being "represented" rather than "measured" — meaning the geometry was drawn to match record documents, not verified against the scan. A structural deliverable spec must state both: the LOD target per discipline, and whether that geometry is measured or represented, with the tolerance that applies to measured elements. Discipline separation also matters — a structural model modeled to LOD 300 does not imply the architectural or MEP models share that same LOD, and a scope that states one blanket LOD number for "the model" leaves that ambiguity unresolved.

The 8 deliverables

1. The registered point cloud itself

What to specify: file format (E57 master plus RCP/RCS working files, or the formats the receiving software requires), who retains ownership of the source files after delivery, and whether a residual report is included documenting registration quality.

Applicable tolerance: ±5 mm registered accuracy, tied to surveyed control, with loop closures verified and residuals reported rather than withheld.

Format: E57 (open, vendor-neutral master format per ASTM E2807) plus RCP/RCS for Autodesk workflows; LAS or PTS where required by other software.

Failure mode if unspecified: the structural team receives only a finished model with no way to independently verify it, and has no cloud to check against when a discrepancy surfaces during coordination or fabrication.

2. Verified structural grid

What to specify: whether the grid delivered is the as-measured grid (surveyed from the physical structure) or the record grid (from original drawings), and — if the two differ — a reconciliation document showing the offset between them, column line by column line.

Applicable tolerance: grid deviations should be reported against the same ±5 mm registered accuracy baseline used for the point cloud.

Format: RVT grid object plus a PDF or spreadsheet reconciliation table.

Failure mode if unspecified: the model is built on an assumed grid that does not match the as-built structure, and every downstream dimension inherits the error silently.

3. Primary members modelled to centreline or to face

What to specify: explicitly state whether beams, columns, and other primary structural members are modeled to their centreline or to their outer face. This single convention decision affects every clearance check, connection detail, and clash report that follows.

Applicable tolerance: ±10 mm to the registered cloud at LOD 300, applied consistently once the convention is fixed.

Format: RVT structural framing and column families, with the convention stated in the model's project information or a delivered modeling standards document.

Failure mode if unspecified: this single ambiguity causes more downstream rework than any other item on this list — clash detection between structural and MEP models becomes unreliable when one discipline assumes centreline and the other assumes face, producing false clashes or missed ones.

4. Column plumbness and out-of-plumb reporting

What to specify: the reporting format for column plumbness — per-column deviation values, a summary table, or a color-coded plan — and the tolerance threshold against which "out of plumb" is flagged.

Applicable tolerance: deviation figures reported against the ±5 mm registered point cloud accuracy; the acceptance threshold itself should be set by the structural engineer of record, not assumed by the scanning provider.

Format: a tabular report (PDF or spreadsheet) cross-referenced to column marks in the model.

Failure mode if unspecified: existing lean or displacement in columns goes undocumented and is discovered mid-retrofit, when it is far more disruptive to address.

5. Floor-plate deviation / levelness

What to specify: whether floor flatness is reported using FF-FL (F-numbers) methodology or as a deviation heat map against a reference plane, and the threshold that triggers a flag.

Applicable tolerance: deviation values are measured against the registered cloud's ±5 mm accuracy; the pass/fail threshold is a project-specific decision that should be stated in the scope, not left to the modeler.

Format: a heat-map image plus the underlying deviation dataset, or an FF-FL report where that standard applies.

Failure mode if unspecified: slab irregularities that affect equipment placement, flooring systems, or structural loading assumptions are missed until construction.

6. Connection and detail capture level

What to specify: exactly what is included at LOD 350 for connections — bolt patterns, gusset plates, weld symbols, or simplified representative geometry — since "LOD 350" alone does not answer that question.

Applicable tolerance: ±10 mm to the registered cloud at LOD 300; connection-level detail at LOD 350 should state its own tolerance and modeling convention rather than inheriting LOD 300's by default.

Format: RVT structural connection objects or detail components, with a written note in the model narrative describing what was captured versus schematically represented.

Failure mode if unspecified: fabricators and detailers assume connection geometry is field-verified when it is schematic, and shop drawings are built on assumptions the model never actually confirmed.

7. Deviation analysis: model vs cloud

What to specify: the tolerance threshold the analysis checks against, the percentile pass criterion (for example, what percentage of measured points must fall within tolerance), and the deliverable format.

Applicable tolerance: ±10 mm at LOD 300, measured as the model's deviation from the registered point cloud, not from record drawings.

Format: a color-coded deviation heat map plus a summary statistics table (mean, standard deviation, percentile pass rate).

Failure mode if unspecified: there is no documented evidence that the model actually matches the cloud within tolerance, and any dispute over model accuracy has nothing to reference.

8. Coordination file for clash

What to specify: file format, discipline separation (structural, MEP, architectural delivered as distinct linked models rather than merged), and what the structural engineer needs to receive from MEP and architectural teams to run a meaningful clash check.

Applicable tolerance: inherits the tolerance of the source models feeding the coordination file; a clash report is only as reliable as the least-accurate model linked into it.

Format: NWC/NWD for Navisworks-based coordination workflows, with each discipline's model delivered as a separate linked file.

Failure mode if unspecified: disciplines are merged into a single file with no separation, making it impossible to isolate which model is responsible for a given clash, or one discipline's model is missing entirely and the "coordination" file coordinates nothing.

A one-page deliverable spec you can paste into a scope

The block below can be copied directly into a scope of work or RFP. Fill in the bracketed items with the values that apply to the project; leave the tolerance columns as shown unless the project requires a tighter standard.

STRUCTURAL SCAN TO BIM — DELIVERABLE SPECIFICATION

1. Registered point cloud
   Format: E57 (master) + [RCP/RCS / LAS / PTS]
   Ownership of source files: [client retains / vendor retains]
   Residual report included: [yes/no]
   Tolerance: ±5 mm registered accuracy, tied to surveyed control

2. Structural grid
   Source: [as-measured / record / both with reconciliation]
   Reconciliation document required: [yes/no]

3. Member modeling convention
   Primary members modeled to: [centreline / face]
   Applies to: [columns / beams / braces / all]

4. Column plumbness
   Reporting format: [per-column table / plan heat map]
   Flag threshold: [project-specific value]

5. Floor-plate deviation
   Method: [FF-FL / deviation heat map]
   Flag threshold: [project-specific value]

6. Connection detail capture
   LOD target: [LOD 200 / 300 / 350]
   Connections captured as: [field-verified geometry / schematic representation]

7. Deviation analysis (model vs cloud)
   Tolerance threshold: ±10 mm at LOD 300
   Pass criterion: [percentile, e.g. 95% of checked points within tolerance]
   Deliverable: heat map + summary statistics table

8. Coordination file
   Format: NWC/NWD
   Discipline separation: structural, MEP, architectural as separate linked files
   Disciplines required from others: [list]

Delivery format for drawings (if applicable): RVT, DWG, PDF
Software targets: [Revit / AutoCAD / Navisworks / ArchiCAD / SolidWorks]

Cross-reference this block against the complete scan to BIM scope of work guide before sending it to a provider — the guide covers the full scope template beyond structural-specific items.

The tolerances that apply to each

Model faces held to ±10 mm at LOD 300 is a Zealot-published figure, not a universal industry constant — any provider's committed tolerance should be stated in writing before the contract is signed, not assumed from a marketing page.

Frequently asked questions

Should structural members be modeled to centreline or face?

Either convention is acceptable, but it must be stated explicitly and applied consistently across the model. Centreline modeling is common for early-stage structural analysis; face modeling is often preferred for clash detection against MEP systems because it reflects actual clearance. The convention should be fixed in the scope of work before modeling begins, since switching conventions mid-project effectively requires re-modeling every primary member.

What is a deviation heat map?

A deviation heat map is a color-coded visualization showing, point by point or area by area, how far the finished model's geometry departs from the registered point cloud it was built from. Green typically indicates values within the stated tolerance (for example, ±10 mm at LOD 300); red or orange indicates areas that exceed it. It is delivered alongside a summary statistics table showing the mean deviation and the percentage of the model that passes the stated tolerance.

Do I get the point cloud with the model?

Whether the point cloud is delivered alongside the finished model, and who retains ownership of it afterward, should be a stated line item in the contract rather than an assumption. Some providers deliver the model only; Zealot's stated commercial terms include the client retaining source files. Confirm this in writing before the project starts, since the registered cloud is the only independent record against which the model can later be checked.

What LOD do I need for a structural retrofit?

The LOD required depends on what the retrofit design requires from the model. Early feasibility and layout work can often proceed on LOD 200 geometry; detailed connection design, fabrication coordination, or clash detection against existing MEP typically requires LOD 300 or LOD 350, with the higher level reserved for connections and details that the retrofit design directly depends on. LOD should be specified per discipline and, ideally, per structural element type, rather than as a single blanket number for the whole model.

What is the difference between LOD and LOA?

LOD (BIMForum Level of Development) describes how complete and detailed a model element is — how much geometric and non-geometric information it carries. LOA (USIBD Level of Accuracy) describes how closely that geometry matches physical reality, expressed separately as Measured Accuracy or Represented Accuracy. A model element can carry a high LOD (fully detailed) while still being drawn to match record documents rather than measured from a scan — LOD says nothing about accuracy on its own, and both should be specified together.

What tolerance applies to the point cloud itself, before any modeling happens?

The registered point cloud, before any BIM modeling is applied to it, carries its own registered accuracy figure — Zealot's published standard is ±5 mm, tied to surveyed control, with loop closures verified and residuals reported rather than withheld. This is distinct from the ±10 mm tolerance that applies to modeled faces at LOD 300, which accounts for the additional step of converting cloud data into finished geometry.

Why does discipline separation matter in the coordination file?

A coordination file that merges structural, MEP, and architectural geometry into a single model makes it difficult to determine which discipline is responsible for a given clash, and makes it impossible for any one discipline's engineer to isolate and review just their own model. Delivering each discipline as a separate, linked NWC/NWD file preserves the ability to run clash detection meaningfully and to trace a flagged conflict back to its source model.

How do I know if a provider's deliverable list is actually a specification or just a category list?

A real specification names, for each deliverable, the file format, the applicable tolerance, and the modeling convention used (such as centreline versus face for structural members). A scope of work that lists only "point clouds, BIM model, as-built drawings" without those details is a category list, not a specification, and leaves the items in this article unresolved until they surface as change orders. The buyer's checklist for choosing a 3D laser scanning provider covers how to evaluate whether a provider's proposal meets this bar.

---

Confirming these eight deliverables before signing a scope of work is the most direct way to prevent the RFIs, re-models, and clash-detection failures that trace back to an unstated convention or an unspecified tolerance. Structural teams evaluating providers should also review the comparison of point clouds versus finished BIM models and the overview of scan to BIM providers for structural teams as companion reading, and can request a project-specific deliverable spec through ZEALOT's scan to BIM services page or by contacting the team directly.