The scope of work document is where most scan-to-BIM project problems originate. Vague descriptions of deliverables, unstated assumptions about LOD, and missing definitions of project boundaries create disputes that consume time and budget long after the scanning is complete.
A well-written scan-to-BIM scope of work protects both the client and the provider by establishing clear expectations before work begins. Every dollar spent on scope definition saves multiples during execution.
The physical scope defines exactly what gets scanned and what gets modeled. Floor plans with highlighted zones, not just area descriptions, eliminate ambiguity about boundaries. Vertical scope from slab to slab, from slab to deck, or from finish floor to a specific elevation above ceiling must be stated explicitly.
Exclusions are as important as inclusions. If certain rooms, floors, or areas are not part of the scope, list them. If exterior scanning is excluded, state it. Assumptions that seem obvious during proposal development become disputes when they are not documented.
Access constraints should be addressed in the scope. Are there areas that require escorts, off-hours access, or special safety training? Will the scanning crew have continuous access or limited time windows? These constraints affect scheduling, pricing, and coverage completeness.
Every deliverable should be described with enough specificity that both parties understand what will be produced. A point cloud deliverable specification should include format, coordinate system, density, and noise tolerance. A BIM model specification should include software version, LOD by discipline, file structure, and naming conventions.
LOD specifications need to go beyond citing a number. Include descriptions of what each LOD level means for each discipline in the project. Structural LOD 300 looks different from mechanical LOD 300 and plumbing LOD 300. Reference images or example models reduce interpretation differences.
Intermediate deliverables and review milestones should be specified if they are expected. Will the client review registration reports? Is there a model review at 50% completion? Are there hold points where approval is required before proceeding? Define these checkpoints in the scope to prevent surprises.
Numeric accuracy requirements remove subjectivity from quality discussions. Registration accuracy, model-to-cloud deviation tolerances, and dimensional accuracy targets should all be stated with specific values. Generic language like high accuracy or tight tolerances invites disagreement.
Quality control procedures should be outlined in the scope. Who performs QC, what metrics are checked, and what happens when deliverables do not meet accuracy requirements should all be defined before work begins. Rework provisions protect the client. Clear acceptance criteria protect the provider.
Realistic timelines account for access scheduling, processing time, modeling effort, and review cycles. A scope that promises a 100,000 square foot scan-to-BIM deliverable in two weeks is setting up both parties for disappointment.
Schedule dependencies should be explicit. The scanning schedule depends on site access. Processing depends on scanning completion. Modeling depends on processed data delivery. Client review periods add time between milestones. Each dependency should be stated with a duration estimate.
The scope should include a change management process for the inevitable adjustments that occur during project execution. Additional areas, LOD upgrades, and schedule changes all require a defined process for requesting, approving, and pricing changes. Without this process, scope creep becomes a source of conflict rather than a managed reality of project work.
Scan-to-BIM pricing is one of the least standardized costs in construction technology. Quotes from different providers for the same project can vary by 300% or more. Some of that variation reflects genuine differences in quality and scope. Much of it reflects inconsistent assumptions about what the deliverable includes.
Building an accurate scan-to-BIM budget requires understanding the cost drivers at each phase and knowing which variables have the biggest impact on total project cost.
Scanning costs are driven by site size, complexity, and access constraints. A straightforward open office floor scans faster than a congested mechanical room of the same square footage. Multi-story buildings with limited elevator access take longer than single-story facilities. Occupied spaces that require off-hours scanning add premium time.
Typical scanning day rates range from $1,500 to $2,500 depending on equipment, operator experience, and geographic market. A skilled operator with a high-speed scanner covers more ground per day than a less experienced operator, making the higher day rate often more cost-effective on a per-square-foot basis.
Drone capture for exteriors and large sites typically runs $2,000 to $3,000 per day including mobilization, flight operations, and initial data processing. RTK-enabled drones reduce the need for ground control points, which can save a half-day of survey work on large sites.
Raw scan data requires processing before modeling can begin. Registration, cleaning, and formatting typically add 1-2 days of processing time per day of field capture. Processing rates range from $1,000 to $1,500 per day depending on the software platform and the level of cleanup required.
Projects with many scan stations or complex multi-floor registration take longer to process. Targets versus targetless registration affects processing time. The quality of field capture directly impacts processing effort. Clean, well-planned scans process quickly. Poorly captured data requires extensive manual intervention.
Modeling is typically 50-70% of total scan-to-BIM project cost, and it is the phase with the most variability. LOD requirements, building system complexity, and modeler skill level all drive significant cost differences.
LOD 200 modeling for basic spatial reference might cost $0.05-0.10 per square foot. LOD 300 for MEP coordination typically runs $0.15-0.35 per square foot. LOD 350 for complex mechanical spaces can reach $0.50 or more per square foot. These ranges vary significantly based on system density and building type.
Offshore modeling resources at $30-40 per hour reduce cost but require strong QC processes to maintain quality. Domestic modelers at $80-120 per hour deliver faster turnaround and easier communication but at higher rates. The best approach depends on project timeline, quality requirements, and available management oversight.
Scope changes are the most common budget buster. Additional areas requested after scanning begins require remobilization. LOD upgrades mid-project require rework. Adding disciplines that were not in the original scope means new modeling passes through existing data.
Rework from quality issues adds cost that should have been prevented. Inaccurate registration discovered during coordination, modeling errors found during field installation, and missing coverage identified after the scanning crew has left all generate unplanned expenses.
Technology costs including scanner maintenance, software licenses, data storage, and computing resources are ongoing operational expenses that should be amortized across projects rather than ignored until they appear as surprise line items.
A well-structured scan-to-BIM budget breaks cost into four components: field capture, processing, modeling, and project management. Add a 5-10% contingency for scope adjustments and unforeseen complexity. Include QC time as a line item, not an afterthought. The projects that budget explicitly for quality control deliver better results than those that treat it as overhead.