Scope of Work Template for Scan to BIM Projects

A field-tested scope framework that keeps Scan to BIM on track

If you’ve ever watched a Scan to BIM engagement drift, you know the culprits: vague deliverables, fuzzy tolerances, and no acceptance test at the end. The fix isn’t complicated, but it has to be precise. Below is the scope structure we use at ZEALOT on projects from Columbus hospitals to Mansfield warehouses. It’s practical, numbers-forward, and tuned to how people actually work.

You can adapt this for your next RFP or as an internal checklist. Pair it with our deeper dives on LOD selection, file formats, and the VLX3 capture workflow.

First principle: lock the “what,” “how accurate,” and “how you’ll say yes”

• What: Deliverables, formats, element list, model uses.
• How accurate: Point density, modeling tolerances, coordinate control.
• How you’ll say yes: QC process and a pass/fail acceptance checklist.

Everything else—schedule, price, and risk—follows from those three.

“Once we wrote the element matrix and tolerances in plain English, RFIs dropped by half. Everyone modeled what mattered—and ignored the noise.”

— PM, Columbus adaptive-reuse team

Deliverables and formats you can actually use

Spell this out so nobody is guessing in month two.

• Point cloud formats: E57 primary; RCP/RCS for Autodesk users; LAS on request. Typical building E57 size: 0.6–1.2 GB per 1,000 sq ft for interior-heavy scans.
• Model: Revit 2021+ at LOD 200/300/400 per element (see matrix below). IFC export if needed.
• 2D outputs: Floor plans, RCPs, sections, and elevations in AutoCAD (DWG) via Scan to CAD and Floor Plans.
• Documentation: Scope sheet, element matrix, model usage notes, assumptions, and a QC report with screenshots and point-to-model residuals.

If you need help picking, our team can align deliverables to your downstream workflows in architecture, construction, or adaptive reuse.

Coordinate system, control, and registration

Don’t leave this to chance. Put it in the scope.

• Coordinate basis: Project North and shared coordinates pinned to survey control. If provided, we’ll use State Plane Ohio North/South (NAD83, US survey feet) or your civil file. If not, we’ll establish a stable local system with a single transform to your survey later.
• Control: Checkerboard and sphere targets plus survey control shots in larger or multi-level buildings. Control check shots every 100–150 ft and at vertical transitions (stairs/shafts).
• Registration: SLAM trajectory from NavVis VLX3 with cloud-to-cloud refinement and survey control constraints. Terrestrial tie-ins with Leica RTC360 or Faro Focus where line-of-sight matters (atriums, shafts, exterior tie-ins).
• Expected accuracy: Registered point cloud ±6 mm RMS in controlled interiors; ±10 mm in complex multi-story tie-ins. Point density 5–10 mm at 10 m for key areas unless otherwise stated.

More background on our capture stack lives here: Building 3D Laser Scanning and Technology.

Mobile vs. terrestrial: when we switch tools

We use both. Your scope should allow for the right tool in the right place.

Element matrix and LOD

Define the model to support your decisions—not to decorate your sheets.

• Levels and grids: LOD 300. Levels at finished floor, roof, and mezzanines. Grids per structure if visible.
• Structure:
• Columns and beams: LOD 300 (centerline with section), LOD 400 only where connections are part of scope.
• Slabs: LOD 300 with true thickness where observable; floor flatness/levelness by surface (no analytical FF/FL unless added).
• Architectural:
• Walls, openings, shafts: LOD 300 to finished faces. Unique wall types captured as families if recurring.
• Doors/windows: LOD 300 geometry with overall sizes; LOD 400 for historic units only when flagged.
• Stairs/rails: LOD 300 footprint and riser count; LOD 400 shop-level not included unless added.
• MEP/F:
• Ducts/pipes > 1.5 in: Centerline + OD at LOD 300; valves at LOD 200 (locations only) unless called out.
• Major equipment (RTUs, AHUs, boilers): LOD 300 bounding geometry; LOD 400 by manufacturer if submittals provided.
• Site:
• Adjacent grade within 10 ft of façade; curbs/ramps at LOD 200 unless otherwise specified.

Tie this back to model use (demo, coordination, as-builts). For help calibrating, see LOD 200 vs 300 vs 400.

Modeling tolerances and acceptance criteria

Put numbers in the contract so everyone stops arguing on Teams.

• Point cloud tolerance (registered): ±6 mm interiors; ±10 mm exteriors/multi-building.
• Modeling tolerance: Model faces and centerlines within ±10 mm of the registered cloud for LOD 300 elements; ±6 mm for LOD 400 elements modeled from terrestrial anchors.
• Completeness: 95% of visible surfaces modeled within the scan scope. Hidden or inaccessible areas documented with photos and flagged on the “Assumptions” sheet.
• Acceptance test (owner/AE review within 10 business days):
• 30 random dimension checks across structure, arch, and MEP: pass if ≥ 90% within tolerance and no systematic bias.
• Three cross-sections: overlay of model and point cloud with maximum residual annotated.
• File open test: Model opens in Revit within 2 minutes on a 32 GB workstation; point cloud links resolve.
• Deliverable inventory: Revit model, E57, RCP/RCS, DWGs, QC report, and coordinate transform notes.

If you need a deeper spec, start here: How to Write a 3D Scan Deliverable Spec.

Schedule that reflects the real work

• Site prep by owner/GC: Clear access, unlock spaces, notify security. Here’s a checklist: How to Prepare Your Site for a 3D Laser Scan.
• Capture: 40,000–80,000 sq ft/day interior with VLX3; exteriors add 0.5–1 day for terrestrial tie-ins.
• Registration and QC: 2–5 business days per building, depending on size/complexity.
• Modeling:
• LOD 200: 15,000–25,000 sq ft/week per modeler
• LOD 300: 8,000–12,000 sq ft/week per modeler
• LOD 400: 3,000–6,000 sq ft/week per modeler
• Typical delivery: 50,000 sq ft at LOD 300 in 15–20 business days from mobilization. 200,000 sq ft across multiple levels: 4–6 weeks.

A quick Ohio example

We scanned a 118,000 sq ft brick warehouse in Mansfield for adaptive reuse into 90 lofts. Two days on site with the NavVis VLX3, plus one afternoon of RTC360 setups to anchor a three-story atrium and the north façade. Registration landed at ±6.4 mm RMS. The consolidated E57 was 84 GB; the RCP/RCS set was 96 GB.

Model scope was LOD 300 for structure and architecture; MEP at LOD 200 except 14 key risers and the boiler room at LOD 300. We delivered a Revit 2023 model, 12 DWG floor plans/sections for the GC, and a QC packet. Turnaround: 17 business days. The architect logged three RFIs total—down from 18 on their previous project without scanning. Estimated savings: ~$42,000 in avoided rework and one less site visit for each discipline.

For similar context, see our Mansfield warehouse adaptive reuse and the Downtown Mansfield case study.

Preservation note

For historic work, scanning supports traditional methods; it doesn’t replace them. We pair the point cloud with measured hand sketches, targeted manual profiles (moldings, stair nosings), and archival review. Models stay truthful to what the cloud shows, while the preservation team decides what requires hand verification. More here: How 3D Scanning Supports Historic Preservation Documentation.

QC and change management that avoid scope creep

• RFI window: 10 business days after initial deliverables. RFIs consolidated into a single log with priority labels.
• Minor edits: Up to 8 hours of modeling corrections included if items were in scope and failed acceptance. Past that, we issue a change order.
• Out-of-scope triggers (price by rate card):
• Spaces locked or added after mobilization
• Above-ceiling obstructions requiring tile removal
• Specialty modeling (ornate plaster, timber joinery) not in the element matrix
• New control from civil not provided at kickoff
• Rescans: Additional mobilization if building conditions change after capture.

Example scope language you can copy

• Purpose and uses
• The model will support schematic design, early coordination, and quantity takeoffs for selective demolition.
• Deliverables
• Revit 2023 model at LOD 300 per element matrix; E57 + RCP; four DWG floor plans and two sections.
• Coordinate system
• Shared coordinates aligned to survey control (NAD83 Ohio North, US ft). Control by GC; ZEALOT to verify with check shots.
• Capture method
• NavVis VLX3 SLAM with terrestrial tie-ins (RTC360) at atrium and exterior faces; control density 1/100 ft.
• Tolerances
• Registered cloud ±6 mm interior; model ±10 mm to cloud for LOD 300.
• Acceptance
• 30 random checks; three section overlays; two-week review window.
• Schedule
• Mobilize MM/DD; capture 2 days; registration 3 days; modeling 10 business days; review 10 days; final package within 5 days of comments.
• Assumptions
• Above-ceiling access limited; model only visible infrastructure >1.5 in.
• Exclusions
• Design, engineering, or code interpretation; clash detection; LOD 400 fabrication unless added.

Workflow: how we’ll execute

1) Pre-mobilization

• Review drawings, finalize element matrix, and confirm coordinate basis. Issue a site readiness checklist.

2) Field capture

• Walk the building at a steady pace with the VLX3, logging 45–60 minutes per pass; place targets at long corridors and floor transitions. Terrestrial setups for long lines of sight and exteriors.

3) Registration and control

• Process SLAM trajectories, run cloud-to-cloud refinements, fix residuals >8 mm, and lock to survey control. Document transforms.

4) Modeling

• Build levels/grids, then structure, then walls/openings, and finally MEP. Use Autodesk Revit with families labeled by LOA/LOD.

5) QC and delivery

• Run section checks, export the QC report, and deliver the model plus point cloud and 2D drawings via secure link.

If you want to understand why we lean on mobile capture for large interiors, read Why Mobile LiDAR Beats Traditional Surveying for Large Buildings. And for teams starting from estimates, see Preconstruction Estimating with Point Cloud Data.

What ZEALOT brings

• NavVis VLX3 for speed; Leica RTC360/Faro Focus for anchors and exteriors.
• SLAM registration plus survey control for reliability at scale.
• Clean deliverables in Revit, DWG, E57, RCP/RCS that plug into your workflows.
• Modeling capacity sized to schedule—multiple modelers when the clock is tight.
• Straight answers on what matters and what doesn’t.

For Scan to BIM on active facilities—hospitals, campuses, plants—see our case studies in the portfolio and related work across engineering and industrial. If you need full documentation packages, we also handle As-Built Documentation and end-to-end Scan to BIM.