How to Write a 3D Scan Deliverable Spec That Protects Your Project

Most reality capture jobs don’t fall apart in the field. They fall apart on page two of the RFP. I’ve watched a clean scan, solid registration, and a fast turn all get torpedoed by a vague line that reads, “Provide a 3D scan and a Revit model.” That sentence invites scope creep, misaligned expectations, and do-overs nobody budgeted for.

What follows is the spec I wish crossed my desk every time. It’s practical, it’s measurable, and it keeps everyone honest—from the PM to the BIM lead to the owner who signs the check.

“Bad specs make good scanners look bad. A precise spec makes the whole team look smart.”

What a Protective Deliverable Spec Actually Covers

Four things. Nail these and you’ll avoid 90% of the fights:

• Accuracy in millimeters—not adjectives.
• LOD by system—not “LOD 300 everything.”
• Formats and versions your team can open today.
• Acceptance criteria everyone agrees to before anyone drives to site.

If you’re new to the process, bookmark these deeper dives for later: Scan to BIM (Revit LOD 200/300/400), Point Cloud File Formats Explained, and a straight talk on gear here: Inside the NavVis VLX3.

1) Put Accuracy in Numbers That Drive Methods and Cost

“High accuracy” is a feeling. Your project needs a number.

• Registration tolerance: how tightly the individual scans fit together after registration. Typical AEC target: 2–6 mm RMS.
• Absolute accuracy: how well the dataset ties to survey control or a real-world grid. Typical AEC target: 8–12 mm to state plane or project grid.

Here’s the quick reference I send to PMs:

What this means in practice:

• On a 250,000 sq ft distribution center in Cincinnati, our NavVis VLX3 runs typically register at 3–4 mm RMS when we close loops every 8–12 minutes and seed with six to ten control targets per bay. Tying to state plane with a total station resection keeps absolute at 8–10 mm.
• For tight tolerance needs (machine placement, anchor bolt plans), we supplement with a Leica RTC360 or Faro Focus on critical elements and push registration to 2–3 mm and absolute to 6–8 mm—but it adds time.

If your scope is master planning or existing conditions at schematic level, you can relax to 6–10 mm registration and 15–20 mm absolute and save real money. Spell it out.

Control Isn’t a Footnote—Assign It

Decide who is responsible for:

• Setting survey control (licensed surveyor vs. scanning vendor)
• Providing coordinates (state plane NAD83/Ohio South, NAVD88) or a project grid
• Supplying control drawings and point lists
• Archiving control shots and photos

The control budget for a mid-size building is small (often $1,500–$3,000), but skipping it is how “my model is 0.25’ off” emails start.

2) Set LOD by System So You Don’t Pay for Detail You’ll Never Use

We don’t model door stops to LOD 400 if you’re replacing rooftop units. Tie development to the actual decisions your team needs to make.

Recommended baselines:

• Architecture: LOD 200 walls, doors, windows, slabs, openings. Add soffits, bulkheads, and parapets if they impact MEP routing or facade scope.
• Structure: LOD 300 for primary steel, columns, beams, braces, and bearing walls if your engineers will reuse the model. Connections modeled generically unless called out.
• MEP: LOD 300 for duct and pipe ≥ 2"; LOD 200 for branches; exclude flex and lines < 1". Model equipment at LOD 300 where nameplate data affects coordination.
• Site: LOD 200 surface with spot grades, curbs, ramps, and major utilities as-observed.

Numbers behind the advice:

• On a 180,000 sq ft office-to-residential conversion in Mansfield, LOD 200 architecture and LOD 300 primary MEP (≥ 2") cut modeling hours by 28% versus “LOD 300 everything.” The engineering team still coordinated 500+ penetrations cleanly and issued 0 RFIs on soffit depths. See the full story: Downtown Mansfield: 180K Sq Ft in 3 Weeks and Adaptive Reuse of a 1920s Mansfield Warehouse.

If you’re unsure, specify LOD per sheet set. Example: “LOD 300 for systems shown in M2.x and P2.x; LOD 200 for systems shown in M1.x and P1.x.” It maps directly to your deliverables.

3) Name the Deliverables You Can Actually Open

Don’t assume your team runs the newest software. Call versions in ink.

• Point cloud: RCP/RCS for Autodesk Recap, plus E57 as an open standard. LAS if civil/survey will consume it. Typical size guidance: 1.5–3.0 GB per 10,000 sq ft at 5–10 mm spacing, so a 200,000 sq ft building is 30–60 GB in E57 and 80–140 GB in RCP once indexed.
• Revit: year-specific (e.g., 2024). If you need IFC, name the schema (IFC4).
• 2D CAD: DWG (AutoCAD 2018+), with plotted PDFs for record.
• Coordinates: “Tied to Ohio South State Plane, US Foot, NAVD88” or “Project grid with shared coordinates documented.”

Also state any downstream needs: If you’re doing Scan to CAD for shop drawings, say so. If you want floor plans only, note that and see our guide on right-sizing scope: Accurate As-Built Floor Plans for Renovation Projects and 2D/3D Floor Plans.

4) Define the Acceptance Test Before Anyone Shows Up On Site

This clause is the cheapest insurance you’ll add.

• Check measurements: Provide 10–20 tape-friendly dimensions (column-to-column, slab-to-ceiling, opening widths) distributed across floors. The scan/model must hit within the stated tolerance.
• Sample area review: Name a 5,000–10,000 sq ft zone. The BIM lead and scanning provider review model-to-cloud for completeness and LOD against that zone.
• Clash test: If multiple disciplines are modeled, run a basic clash in Navisworks or Revit (tolerance stated; e.g., 12 mm).
• Turnaround: Require a live deliverable walkthrough within 5 business days of handoff so issues don’t sit.

If it passes, you accept. If it misses, the revision scope is already defined. No drama, no surprises.

5) Don’t Forget the Operational Stuff That Trips Schedules

Put these bullets in the RFP and you’ll save a week of back-and-forth.

• Survey control: who sets it, who pays, record retention.
• Site access: escorts, background checks, badging, PPE, union rules, and hot work permits (for scanners, typically “no spark,” but some plants still require permits).
• Exclusions: tenant spaces, energized substations, confined spaces, ceiling plenums unless tiles are remove-and-replace by others.
• Working hours: “6:00 a.m.–6:00 p.m., no weekends,” or the opposite if you need clear floors.
• Data retention: how long the vendor will keep raw and processed data (standard is 12–24 months).
• Deliverable corrections vs. change orders: Define what’s an in-scope fix (e.g., missed AHU in scanned area) versus an out-of-scope change (e.g., added mezzanine not accessible on scan day).
• Safety plan: If it’s an industrial or healthcare site, this matters. We’ve scanned live OR suites and refineries; both need a pre-task plan. See our industrial and construction notes.

A Quick Columbus Story: How the Spec Saved $22,400

We scanned an active hospital wing in Columbus—seven floors, 142,000 sq ft, nights only. The RFP required:

• 2–4 mm registration; 8–12 mm absolute to project grid
• Revit 2024: LOD 200 arch, LOD 300 MEP ≥ 2"
• E57 + RCP point cloud; DWG floor plans per level
• Acceptance: 12 check measurements and a 7,500 sq ft sample area

Field time: 3 nights with NavVis VLX3 (walking pace), plus 18 RTC360 setups for critical tie-ins. Registration residuals landed at 3.2 mm average; absolute checks were ±9 mm. During the review, the design team flagged a missing transfer duct in the sample area. Because acceptance criteria were in writing, we corrected it in two days—no change order, no noise.

The best part: the GC avoided a second mobilization for an “oh, we forgot the interstitial” scan. The spec had the interstitial included as an access note. That alone saved 2 nights and $22,400.

If you’re working historic or preservation, the same rules apply—but scanning supports, it doesn’t replace, traditional documentation. We pair As-Built Documentation with measured drawings, photos, and notes. See how that balance plays out: How 3D Scanning Supports Historic Preservation Documentation.

Equipment Implications (So You Know What You’re Buying)

When you ask for 2–4 mm registration at typical indoor ranges:

• NavVis VLX3 SLAM excels for interiors and long corridors at walking speed, with loop closures every 8–12 minutes and 5–10 mm point spacing at 10 m. Great for large footprints and tight schedules.
• Leica RTC360 or Faro Focus static scans fill the gaps—exterior facades, roof equipment, tight tolerance tie-ins, and glass-heavy atriums where SLAM can struggle.
• Registration is cloud-to-cloud, tied to control targets shot with a total station. We archive targets, photos, and a registration report.

These choices drive cost and time. That’s why the accuracy numbers matter.

For a deeper look at when mobile LiDAR wins, see: Why Mobile LiDAR Beats Traditional Surveying for Large Buildings.

Sample One-Paragraph Spec You Can Paste Into an RFP

Provide a registered point cloud at 2–4 mm registration RMS and 8–12 mm absolute accuracy, tied to Ohio South State Plane (US Foot), NAVD88. Deliver in RCP/RCS and E57; include LAS for civil. Provide a Revit 2024 model: LOD 200 Architecture and Structure, LOD 300 MEP for duct and pipe ≥ 2", with equipment modeled at LOD 300 where nameplate data informs coordination. Include 2D floor plans per level in DWG (AutoCAD 2018+) and PDF. Acceptance is conditional on a 12-point check measurement set within tolerance, a 7,500 sq ft sample area model-to-cloud review, and a live deliverable walkthrough within 5 business days of handoff.

That short paragraph prevents about 80% of the disputes we see.

Add-Ons Worth Calling Out (Only If You Need Them)

• Floor and ceiling RCPs for interiors teams: 2D/3D Floor Plans.
• Stockpile volumes or tank capacities: Volumetric Scanning.
• Topographic surfaces and hardscape for site upgrades.
• RCP lighting fixtures at LOD 200 for lighting calculations.
• BIM execution plan alignment (naming, shared coordinates).
• Preconstruction quantities from point clouds: Preconstruction Estimating with Point Cloud Data.

Handoff Timeline Reality Check

For planning, here’s what we see on mid-size work:

• Field capture: 50,000–75,000 sq ft per day with VLX3 (occupied), faster if empty.
• Registration and QA: 2–4 business days per 100,000 sq ft.
• Modeling: LOD 200 arch + LOD 300 MEP (≥ 2") runs 1–2 weeks per 100,000 sq ft with a steady team.
• Total turnaround: 2–4 weeks depending on scope and access.

You can compress it, but the quality tax shows up later in coordination. A clear spec lets you set a realistic schedule now.

Where This Fits in Your Process

• Owners: Put this language in your RFPs. It protects budgets.
• Architects/Engineers: Tie LOD to the sheets you’ll stamp.
• GCs: Use acceptance criteria to lock coordination dates.
• Preservation teams: Treat scanning as a supporting layer to drawings and field notes—not a replacement.

If you want a deeper template, grab our longer checklist: Choosing the Right 3D Scanning Provider and our LOD 200 vs 300 vs 400 guide.