TL;DR
A clear 3D laser scanning scope of work prevents ambiguity and ensures project success. This document should define the project's purpose, specify the exact areas and quantities for scanning, and state the required accuracy levels based on standards like USIBD. It must also detail capture methods, all deliverables with their formats, the Level of Development (LOD) for each discipline, and any site constraints or access schedules. Finally, the scope should establish clear acceptance criteria and revision processes to manage expectations and ensure the final BIM or CAD files meet project requirements.
# How to Write a 3D Laser Scanning Scope of Work, Step by Step
TL;DR
- Define the project's purpose and specific areas to be scanned with exact square footage.
- Set clear accuracy and tolerance requirements using standards like USIBD LOA.
- Specify capture methods (terrestrial vs. mobile) and coverage needs (e.g., above-ceiling).
- List all required deliverables and their file formats, including the point cloud and BIM model.
- Assign a Level of Development (LOD) for each discipline (Architectural, Structural, MEP).
Jump to:
How to Define the Project Purpose and Objectives? · How to Specify Areas to Be Scanned and Quantities? · How to Set Accuracy and Tolerance Requirements? · How to Detail Capture Methods and Coverage? · How to List Deliverables and Required Formats? · How to Define Level of Development (LOD) by Discipline? · How to Document Site Constraints, Access, and Schedule? · How to Establish Acceptance Criteria and Revision Policies? · Sample 3D Laser Scanning Scope of Work Template · Where to go next
A 3D laser scanning scope of work (SOW) is the single most important document for procuring reality capture services. For architecture, engineering, and BIM teams, a poorly written SOW leads to inaccurate quotes, misaligned expectations, and deliverables that fail to meet project needs. A precise, detailed SOW ensures the scanning provider understands exactly what to capture, model, and deliver, preventing costly change orders and delays.
This article provides a step-by-step framework for drafting each clause of a comprehensive 3D laser scanning SOW. It includes copy-and-paste sample language that can be adapted for your specific renovation, adaptive reuse, or as-built documentation project. Following these eight steps will help you create a document that serves as a clear and enforceable agreement with your scanning partner.
How to Define the Project Purpose and Objectives?
The first clause of the SOW sets the stage for the entire project. It tells the scanning provider why the data is being collected. This context is critical, as the purpose of the scan—whether for an adaptive reuse due diligence guide, MEP coordination, or a structural retrofit—dictates the necessary accuracy, detail, and deliverables. Vague objectives lead to generic proposals; specific objectives lead to tailored solutions.
This section should clearly state the project name, address, and the ultimate goal. Is the deliverable supporting schematic design, construction documentation, or facility management? Is the focus on architectural features, structural elements, or congested above-ceiling spaces? Answering these questions upfront ensures every subsequent decision aligns with the end use of the data.
Sample Clause Language:
>
1.0 Project Overview and Objectives
>
1.1 Project: [Project Name, Project Number]
>
1.2 Location: [Street Address, City, State, ZIP Code]
>
1.3 Objective: The primary objective of this 3D laser scanning scope of work is to capture existing conditions of the specified areas at the project location. The resulting point cloud data and 3D BIM model will be used by the design team to support the [e.g., Construction Documents phase] for a [e.g., multi-floor tenant interior renovation]. The data must be suitable for [e.g., clash detection, design coordination, and as-built verification].
How to Specify Areas to Be Scanned and Quantities?
Ambiguity in the scan area is a common source of conflict. This clause must precisely define the physical boundaries of the work. "Scan the third floor" is not enough. Does that include inside every room, plenums, stairwells, and elevator shafts? Use marked-up floor plans as an exhibit to the SOW, highlighting all required areas.
State the total square footage to be captured. This is a primary factor in pricing, as scanning services are often estimated on a per-square-foot basis, typically ranging from $0.05 to $0.20/sq ft depending on complexity and deliverables. Being specific about the scope of a large facility, such as an 80,000–120,000 sq ft warehouse, prevents misunderstandings about the scale of the effort. Explicitly list any areas that are *out of scope* to further eliminate confusion.
Sample Clause Language:
>
2.0 Areas of Investigation
>
2.1 Scan Area: The scope includes 3D laser scanning of the following areas, totaling approximately [Total Square Footage] sq ft:
- Interior of floors [Floor Numbers], including all accessible rooms, corridors, and common areas.
- Above-ceiling conditions in all main corridors and mechanical rooms.
- Building exterior facades (North and West elevations) from ground level.
- Main mechanical, electrical, and plumbing rooms [Room Numbers].
>
2.2 Boundaries: Refer to the attached drawing set [Drawing Set Name/Number], pages [Page Numbers], for highlighted areas indicating the exact boundaries of the scan area.
>
2.3 Exclusions: The following areas are expressly excluded from this scope: [e.g., Roof, inaccessible crawl spaces, occupied tenant suites not listed above].
How to Set Accuracy and Tolerance Requirements?
Not all projects require the same level of precision. Specifying an unnecessarily high accuracy increases cost and time, while insufficient accuracy renders the data useless. This clause should define the required accuracy using an industry-standard framework, such as the U.S. Institute of Building Documentation (USIBD) Level of Accuracy (LOA) specifications. ASTM E3125-17 provides further standards for data quality.
For most architectural and MEP renovation work, a registered point cloud accuracy of ±5mm is a common and achievable standard. This means the dimensional uncertainty between any two measured points in the final combined point cloud is no greater than 5 millimeters. The SOW should state this numerical tolerance and how it will be verified, for instance, against a set of control points established by a licensed surveyor. This makes accuracy an objective, measurable criterion. You can learn more about what ±5mm accuracy means in practice for design and construction.
Sample Clause Language:
>
3.0 Accuracy and Tolerance
>
3.1 Point Cloud Accuracy: The final registered point cloud shall achieve a relative accuracy of USIBD LOA 20. The maximum statistical error between any two points within the combined point cloud shall not exceed ±5mm.
>
3.2 Control and Verification: The scanning provider shall use a closed-traverse survey method to establish control throughout the project site. The final registration report must be submitted to the Client, demonstrating that accuracy targets have been met. The Client reserves the right to field-verify dimensions between the model and known site conditions.
How to Detail Capture Methods and Coverage?
This section defines *how* the data will be collected. The choice of technology affects speed, detail, and cost. For example, a provider might use tripod-mounted terrestrial scanners for high-precision setups in mechanical rooms and mobile LiDAR systems like the NavVis VLX3 for rapid, walking-pace capture of large, open floors. Specifying the method ensures the right tool is used for the job. Read more about the differences in a comparison of mobile vs. terrestrial laser scanning.
Beyond the hardware, define the required coverage. Is color data (RGB) necessary for material identification and visualization? Is it critical to capture elements above accessible ceiling tiles? Specifying these details ensures the provider allocates the necessary time and equipment to capture all critical project elements, avoiding data gaps that can halt design work later.
Sample Clause Language:
>
4.0 Data Capture and Coverage
>
4.1 Methodology: Data capture shall be performed using a combination of tripod-mounted terrestrial laser scanners for high-detail areas (e.g., MEP rooms, facades) and mobile LiDAR mapping systems for efficient capture of large interior spaces (e.g., open office floors, corridors).
>
4.2 Coverage: The provider shall ensure comprehensive, line-of-sight coverage of all visible surfaces within the defined scan area. Occlusions (shadows) shall be minimized by using a sufficient number of scan setups.
>
4.3 Special Conditions:
- Capture shall include full-color (RGB) photographic overlays for all point cloud data.
- Capture shall include areas above accessible ceiling grids in all corridors and spaces designated as "MEP" on the attached drawings.
How to List Deliverables and Required Formats?
This is a simple but critical section: an exhaustive list of every file and product you expect to receive. Ambiguity here is costly. If you need a Revit model, specify "3D Revit Model." If you only write "3D Model," you might receive a non-editable mesh file. Be specific about file formats and software versions to ensure compatibility with your team's workflow.
A complete deliverables list might include the raw point cloud, a registered point cloud, a 3D BIM model, 2D CAD drawings, and access to a web-based viewer. For a more detailed guide on this specific topic, see the guide on how to write a 3D scan deliverable spec.
Sample Clause Language:
>
5.0 Required Deliverables
>
The Provider shall furnish the following deliverables upon completion of the scope of work:
>
5.1 Registered Point Cloud: One (1) complete, registered point cloud in Autodesk ReCap format (.rcp/.rcs) and one (1) in the non-proprietary E57 format (.e57).
>
5.2 3D BIM Model: One (1) 3D model authored in Revit 2023 (.rvt file). The model shall be built from the point cloud and adhere to the LOD requirements in Section 6.0.
>
5.3 2D CAD Drawings: 2D drawings exported from the Revit model in AutoCAD format (.dwg). This shall include, at a minimum:
- As-built floor plan for each scanned level.
- As-built reflected ceiling plan for each scanned level.
>
5.4 Online Viewer: Link and access credentials to a web-based platform for viewing the point cloud and 360° imagery for a period of 12 months.
How to Define Level of Development (LOD) by Discipline?
Level of Development (LOD) specifies how much detail and geometric information is included in the 3D model for different building systems. A model can be developed to different LODs for architectural, structural, and MEP components. Scan-to-BIM projects typically fall within the LOD 200–350 range. Failing to specify LOD is a guaranteed path to a deliverable that is either underwhelming or needlessly over-detailed and expensive.
Use a table to clearly define the LOD requirements for each discipline. This communicates expectations clearly and helps the provider price the modeling effort accurately. For example, you may require LOD 300 for major structural members but only LOD 200 for architectural partitions. Understanding the differences between LOD 200, 300, and 400 is key to specifying this correctly.
Sample Clause Language:
>
6.0 3D Model Level of Development (LOD)
>
6.1 Specification: The 3D Revit model shall be developed to the Levels of Development defined below, based on the BIMForum LOD Specification. Modeling is limited to elements that are visible and identifiable in the point cloud data. No concealed elements (e.g., in-wall piping, rebar) will be modeled.
>
6.2 LOD by Discipline:
>
| Discipline | LOD | Modeled Elements |
|---|---|---|
| Architectural | LOD 200 | Walls, floors, ceilings, doors, and windows modeled as generic elements with accurate location and size. |
| Structural | LOD 300 | Columns, beams, slabs, and primary bracing modeled with specific size, shape, location, and orientation. |
| MEP (Piping) | LOD 300 | Piping 2" in diameter and larger, modeled with specific size, location, and including valves and fittings. |
| MEP (Duct) | LOD 200 | Main trunk and branch ductwork modeled as generic rectangular or round elements with accurate dimensions and location. |
| Electrical | LOD 200 | Major equipment, cable trays, and conduit runs 2" and larger modeled as generic volumes. |
How to Document Site Constraints, Access, and Schedule?
Logistics are a major component of any fieldwork. This clause must inform the scanning provider of all known site conditions that could affect their work. Is the building occupied? Are there specific hours when work is permitted? Are there security checks, safety orientation requirements, or areas that require special PPE?
Providing this information upfront allows the provider to plan accordingly and build these factors into their schedule and price. A surprise discovery that scanning can only happen between midnight and 4 a.m. will inevitably lead to a change order if not addressed in the SOW. Clearly listing the site contact for scheduling and access is also essential. For projects in active environments, it is important to know if you can scan an occupied building and what protocols are needed.
Sample Clause Language:
>
7.0 Site Conditions, Access, and Schedule
>
7.1 Site Status: The project site is a [e.g., fully operational hospital]. Work must be coordinated to minimize disruption to building occupants and operations.
>
7.2 Access Hours: On-site scanning activities are restricted to [e.g., 7:00 PM to 5:00 AM, Monday through Friday]. No work is permitted on weekends or holidays without prior written approval.
>
7.3 Coordination: The provider must coordinate all site visits a minimum of [e.g., 72 hours] in advance with the designated site contact: [Name, Title, Phone, Email].
>
7.4 Safety: All provider personnel must complete the site's safety orientation prior to commencing work and wear required PPE (hard hat, safety vest, safety glasses) at all times.
How to Establish Acceptance Criteria and Revision Policies?
How will you determine that the work is complete and correct? This final clause defines the terms of acceptance. It ties back to the accuracy and LOD requirements defined earlier. The criteria for acceptance should be objective: does the model align with the point cloud within the specified tolerance?
This section should also outline the process for review and revision. A typical arrangement allows the client a set number of business days (e.g., 10) to review the deliverables and submit a consolidated list of comments. The SOW should state how many rounds of revision are included in the base fee (typically one). This protects both parties from endless revision cycles and unmanaged scope creep.
Sample Clause Language:
>
8.0 Acceptance Criteria and Revisions
>
8.1 Review Period: The Client shall have [e.g., 10 business days] from receipt of the final deliverables to conduct a quality assurance review.
>
8.2 Acceptance Criteria: Deliverables will be considered complete and accepted upon Client verification that:
- The 3D model is dimensionally consistent with the registered point cloud.
- The 3D model meets the LOD requirements detailed in Section 6.0.
- All deliverables listed in Section 5.0 have been provided in the correct format.
>
8.3 Revisions: One (1) round of revisions to correct modeling errors or omissions that deviate from this SOW is included. The Client will provide a single, consolidated list of requested revisions. Revisions requested due to changes in Client requirements or design direction will be considered additional scope and subject to a change order.
Sample 3D Laser Scanning Scope of Work Template
To simplify the process, here is a skeleton template combining all eight clauses. Copy this structure and fill in the bracketed information to create the foundation of your next SOW. For a more comprehensive document, you can find a complete scope of work template for Scan-to-BIM available for download.
**3D LASER SCANNING SCOPE OF WORK**
**Project:** [Project Name]
**Date:** [Date]
**1.0 Project Overview and Objectives**
1.1 Project: [Project Name, Project Number]
1.2 Location: [Street Address, City, State, ZIP Code]
1.3 Objective: [Describe the purpose of the scan and how the data will be used.]
**2.0 Areas of Investigation**
2.1 Scan Area: [List all specific areas, floors, and rooms. State total approximate square footage.]
2.2 Boundaries: [Reference attached drawings with highlighted scan areas.]
2.3 Exclusions: [List all areas explicitly excluded from the scope.]
**3.0 Accuracy and Tolerance**
3.1 Point Cloud Accuracy: [Specify USIBD LOA level and/or numerical tolerance, e.g., ±5mm.]
3.2 Control and Verification: [Describe requirements for survey control and registration reporting.]
**4.0 Data Capture and Coverage**
4.1 Methodology: [Specify required technology, e.g., terrestrial, mobile LiDAR.]
4.2 Coverage: [Describe requirements for minimizing occlusions.]
4.3 Special Conditions: [State requirements for color (RGB) data, above-ceiling scans, etc.]
**5.0 Required Deliverables**
5.1 [Deliverable 1]: [e.g., Registered Point Cloud in .rcp and .e57 format.]
5.2 [Deliverable 2]: [e.g., 3D Revit 2023 Model (.rvt).]
5.3 [Deliverable 3]: [e.g., 2D CAD Drawings (.dwg) of floor plans.]
5.4 ...
**6.0 3D Model Level of Development (LOD)**
6.1 Specification: [Reference BIMForum LOD Specification.]
6.2 LOD by Discipline: [Insert table defining LOD for Architectural, Structural, and MEP systems.]
**7.0 Site Conditions, Access, and Schedule**
7.1 Site Status: [Describe site conditions, e.g., occupied, under construction.]
7.2 Access Hours: [Specify days and times when work is permitted.]
7.3 Coordination: [Provide details for the site contact person.]
7.4 Safety: [List all mandatory safety protocols and PPE requirements.]
**8.0 Acceptance Criteria and Revisions**
8.1 Review Period: [Define the number of days for client review.]
8.2 Acceptance Criteria: [List the objective criteria for approving deliverables.]
8.3 Revisions: [State the number of included revision rounds.]Where to go next
A well-written 3D laser scanning scope of work is not an administrative burden; it is a critical tool for project risk management. By clearly and specifically defining every aspect of the project, from objectives to acceptance, AEC teams can ensure they receive accurate, useful data that supports their design and construction goals on time and within budget.
For firms looking to implement these best practices, ZEALOT provides nationwide Scan-to-BIM services built on clear communication and precisely defined deliverables. The team is equipped to handle complex projects, from industrial plants to historic structures, with a focus on delivering data that integrates seamlessly into BIM workflows.