TL;DR
A clear 3D laser scanning Scope of Work (SOW) defines project purpose, areas, accuracy, deliverables, and logistics. It prevents scope creep and ensures the final data meets the design team's needs for renovation and as-built documentation.
A comprehensive Scope of Work (SOW) for 3D laser scanning services is the foundation for a successful reality capture project. It clearly defines the project's purpose, the physical areas to be captured, the required accuracy, the final deliverables, and the criteria for acceptance. A well-written SOW prevents miscommunication, manages expectations, and ensures the data delivered is precisely what the architectural or engineering team needs for design, analysis, or documentation.
This guide provides a step-by-step framework for architects, engineers, and BIM managers to develop a clear and effective SOW for any 3D laser scanning project.
How to Write a Comprehensive 3D Scanning SOW
A thorough SOW acts as a detailed checklist, compelling all stakeholders to consider the project from start to finish before work begins. This process mitigates risks and aligns expectations between the client and the scanning provider.
1. Define the Purpose and End Use
Begin with the "why." The intended application of the scan data dictates every subsequent decision. Is the scan for preliminary as-built documentation, a complex renovation design, structural analysis, historic preservation, or MEP coordination?
Be specific. A point cloud intended for schematic design has vastly different resolution and accuracy requirements than one used to generate fabrication-level MEP models. Clearly stating the purpose allows the scanning provider to recommend the most appropriate technology and workflow.
2. Set Scan Areas, Levels, and Exclusions
Never use ambiguous descriptions like "scan the whole building." Provide the scanning firm with floor plans, site plans, or satellite images with the required scan areas clearly marked. This "scan polygon" should define the precise boundaries.
Specify all required areas: interior rooms, exterior facades, roof surfaces, structural bays, and above-ceiling MEP spaces. Just as importantly, explicitly list all areas to be excluded from the scope, such as occupied tenant spaces, secure rooms, or inaccessible crawl spaces. This clarity is the best way to prevent scope creep and ensure accurate pricing.
3. Specify Accuracy and Level of Development (LOD)
This is the most technical—and most critical—part of the SOW. It's essential to distinguish between point cloud accuracy and BIM model Level of Development.
- Point Cloud Accuracy: This refers to the measurement precision of the raw data itself, after registration. A typical specification for high-quality work is a registered field accuracy of ±5 mm.
- Level of Development (LOD): This applies only to Scan-to-BIM deliverables and defines how detailed the modeled elements will be. Projects commonly fall within LOD 200 to LOD 350.
- Model Tolerance: This defines the required accuracy of the BIM model relative to the point cloud. ZEALOT Reality Capture, for example, models to a tolerance of ±10 mm between model faces and the registered cloud for a typical LOD 300 project.
4. Detail Deliverables and Formats
List every file and format the design team requires. Ambiguity here can lead to receiving data in unusable formats. For a detailed breakdown, review a complete guide to point cloud deliverables for BIM managers.
Common deliverables include:
- Registered Point Cloud: Specify the format (e.g., Autodesk ReCap .RCP, .E57) and whether it should be colored, structured, or unified.
- 360° Imagery: Note if a hosted web viewer (virtual tour) is needed or just the raw panoramic image files.
- Revit Model: Specify the Revit version (e.g., 2023, 2024) to ensure compatibility.
- 2D CAD Drawings: If needed, specify formats (.DWG, .DXF) and what plans, elevations, or sections are required.
5. Establish Coordinate System and Control
The SOW must define how the scan data will be spatially oriented. Will it be aligned with an existing site survey, a local project grid, or can it exist in its own relative coordinate system? If the scan must tie into known coordinates, the provider will need to work with a surveyor to place and locate survey control targets on site.
6. Clarify Site Logistics and Access
Provide the full site address, a primary point of contact, and a detailed description of any access requirements or restrictions. This includes working hours, security check-in procedures, occupied areas, and any required personal protective equipment (PPE) or site-specific safety training. This information is crucial for the scanning team to plan for safe and efficient field operations.
7. Set the Schedule and Milestones
Define the key project dates and durations. A typical SOW should include deadlines for:
- Field capture completion
- Delivery of the registered point cloud
- Client review period for the point cloud
- Delivery of the final Revit model or other specified deliverables
- Final client review and acceptance
For reference, ZEALOT can often complete field capture in 1-3 days for typical commercial buildings, deliver the registered point cloud in 3-5 business days, and provide a complete LOD 300 Revit model in 3-5 weeks.
8. Define QA and Acceptance Criteria
How will the final deliverables be evaluated and approved? This section should tie directly back to the accuracy, LOD, and deliverable specifications. Define a specific review period (e.g., 5-10 business days) for the client team to inspect the deliverables and confirm they meet the SOW requirements. Objective acceptance criteria protect both parties by setting a clear definition of "done." A project can avoid many common Scan-to-BIM QA failures with a clear SOW.
9. Address Data Ownership and Retention
The SOW should state who owns the final deliverables. In most cases, the client who commissions the scan owns the registered point cloud and any derivative models or drawings. The SOW should also specify how long the scanning provider is contractually obligated to retain a backup of the project data.
10. Confirm the Pricing Basis
Finally, the SOW should reference the formal quote and confirm the pricing structure. Most 3D scanning projects are quoted on a fixed lump-sum basis when the scope is well-defined. If the scope is uncertain, the work might be done on a time-and-materials basis with a stated not-to-exceed amount. Detailing how much 3D laser scanning costs is complex, but the SOW ensures the agreed-upon price is tied to a specific set of tasks and deliverables.
SOW Template for 3D Laser Scanning Services
Use the following clauses as a starting point for your next project's Request for Proposal (RFP) or SOW.
1.0 Project Overview & Purpose
[Briefly describe the project (e.g., renovation of a 50,000 sq ft historic warehouse) and the primary use for the scan data (e.g., to support architectural design and MEP coordination for an adaptive reuse project).]
2.0 Scope of Work Area
[Reference attached, marked-up drawings (e.g., A-101, A-102) showing the full extent of the required scan area. List all areas to be included, such as: All interior spaces on floors 1-3; all exterior facades; main roof surfaces.]
3.0 Exclusions from Scope
[List all areas explicitly excluded from the scan scope, such as: Tenant-occupied suite 210; basement crawl space; inaccessible ceiling plenums.]
4.0 Field Capture Requirements
4.1 Required Field Accuracy: The registered point cloud shall have a global accuracy of [e.g., ±5 mm] as verified by a network of control targets.
5.0 Project Deliverables
5.1 Registered Point Cloud: One (1) registered point cloud in Autodesk ReCap (.RCP) format, structured, and in full color.
5.2 360° Imagery: A hosted web link to immersive 360° panoramic imagery of all scanned areas.
5.3 Revit Model: One (1) Revit [e.g., 2024] model at Level of Development (LOD) [e.g., LOD 300].
5.4 Modeled Elements: The model shall include the following elements: [e.g., Structural columns and framing; floors; roof; interior and exterior walls; doors and windows; major MEP mains >4" in diameter.] A full breakdown of what to include can be found in a [3D scan deliverable specification](/blog/how-to-write-3d-scan-deliverable-spec).
5.5 Model Tolerance: All modeled geometry shall be located within [e.g., ±10 mm] of the corresponding surfaces in the registered point cloud.
6.0 Project Schedule
[List key milestone dates for field capture, point cloud delivery, and final model delivery.]
7.0 Acceptance Criteria
[The client will have ten (10) business days from receipt to review each deliverable against the requirements of this SOW. Provider will address any noted deficiencies within five (5) business days.]Common SOW Mistakes to Avoid
- Vague Area Definitions: "Scan the second floor" is an invitation for disputes. Always provide marked-up plans.
- Ignoring LOD: Not specifying a Level of Development for a Revit model is the single most common cause of mismatched expectations in Scan-to-BIM.
- Forgetting Exclusions: Assuming the provider knows what *not* to scan can lead to costly change orders or wasted time capturing unnecessary areas.
- No Acceptance Criteria: Without objective criteria for how success will be measured, a project is open to endless revisions and subjective feedback.
Next step
A well-defined SOW is the first step toward a successful reality capture project. If you're ready to discuss your project requirements, the team at ZEALOT Reality Capture can provide a detailed quote and SOW tailored to your specific needs. Contact the team at 614-210-3679 or request a quote online.
Next step
Scope review and a written quote come back within 24 hours. Call 614-210-3679 or send project details through the contact page.