Scan-to-BIM Deliverables
| Deliverable | Format | Use | | --- | --- | --- | | Point cloud | E57, PTS | Primary data | | Floor plans | DWG + PDF | Design reference | | Revit model | RVT | BIM coordination |
2025 Scan-to-BIM Costs (ex VAT)
| Property | LOD 200 | LOD 300 | LOD 350 | | --- | --- | --- | --- | | 2–3 bed | £800–£1,200 | £1,200–£1,800 | £1,800–£2,500 | | 4+ bed | £1,200–£1,800 | £1,800–£2,500 | £2,500–£3,500 |
BIM Execution Plan Template for Scan-to-BIM Projects
A BIM Execution Plan (BEP) defines how BIM will be used on a project. For scan-to-BIM projects, the BEP specifies scanning requirements, deliverables, and coordination procedures.
This template helps contractors, architects, and BIM managers define scan-to-BIM requirements for their projects.
1. Project Information
- Project name and address
- Client name and contact
- Main contractor name and contact
- Architect name and contact
- BIM manager name and contact
- Scan-to-BIM surveyor name and contact
2. Project Scope and Objectives
Define why scan-to-BIM is being used:
- Capture existing conditions for design development
- Produce as-built BIM model for FM
- Support structural assessment and analysis
- Enable clash detection and coordination
- Provide historical record
3. Survey Scope
Define what will be scanned:
Buildings: All existing structures within the project scope.
Areas: Define specific floors, wings, or zones to be scanned.
Exclusions: Note any areas excluded from scanning and reason.
Access restrictions: Note any areas with limited access and how this is handled.
4. Scanning Specifications
Define technical scanning requirements:
Scanner type: Specified scanner model or performance standard.
Point density: Minimum points per square metre.
Accuracy standard: Target accuracy in millimetres.
Coverage: Minimum scan positions and overlap requirements.
Registration method: How scans will be registered into a single point cloud.
5. Deliverables
Define BIM deliverables:
Point cloud data: Format — LAS or PTS. Coordinate system and datum.
BIM model: Software — Revit version. LOD — 200, 300, 350, or 400.
Drawings: Format — DWG or PDF. Drawing types and scales.
Other: Additional deliverables as required.
6. Level of Development (LOD) Specification
Define LOD for each element:
Structural elements: Walls, floors, columns, beams — LOD target.
Architectural elements: Doors, windows, stairs — LOD target.
MEP elements: If included — LOD target.
Site elements: If site is included — LOD target.
7. File Format and Software Requirements
Define software and format requirements:
BIM software: Revit version and discipline.
CAD software: AutoCAD version.
Point cloud software: Compatible formats.
Coordinate system: National grid or site-established.
Units: Metres or millimetres.
8. Coordination Procedures
Define how scan data is shared and coordinated:
File sharing platform: Common Data Environment or equivalent.
Version control: How model versions are tracked and named.
Review procedures: How model reviews are conducted and documented.
Issue management: How clashes and issues are identified and resolved.
9. Quality Assurance
Define QA procedures:
Scan coverage verification: How complete scanning is verified.
Model accuracy verification: How LOD compliance is checked.
Revisions management: How revision requests are handled.
Sign-off procedures: How deliverables are approved.
10. Programme and Milestones
Define key dates:
- Scanning dates and duration
- Point cloud delivery date
- BIM model delivery dates by phase
- Review and sign-off dates
11. Roles and Responsibilities
Define who does what:
Client: Provides access, approves deliverables, funds works.
Main contractor: Coordinates scanning, manages programme.
Architect: Defines requirements, reviews deliverables, approves design.
BIM manager: Manages BIM process, coordinates team, maintains standards.
Scan-to-BIM surveyor: Conducts scan, delivers point cloud and BIM model.
12. Data Ownership and Usage
Define data rights:
Ownership: Who owns the scan data and BIM model.
Usage rights: Who can use the data and for what purposes.
Intellectual property: IP rights in the data.
Retention: How long data is retained and archived.
Why a BIM Execution Plan Matters
A BIM Execution Plan ensures all parties understand what scan-to-BIM will deliver, how data will be used, and who is responsible for what. Without a clear BEP, scan-to-BIM projects encounter problems:
Scope ambiguity: Unclear deliverables lead to disputes about what was included. The surveyor delivers one thing; the architect expects another.
Format incompatibility: BIM models delivered in incompatible software versions cannot be opened by the design team.
LOD disputes: BIM models delivered at lower LOD than required. Design team cannot use the data for intended purposes.
Programme delays: Scanning and modelling timelines are not integrated with the design programme. Data arrives too late for effective use.
A clear BEP avoids these problems. All parties agree requirements before work begins.
Completing the Template
Complete each section of the template with reference to your specific project. Key decisions to make:
LOD selection: Choose LOD appropriate for the intended use. LOD 300 is typical for design development. LOD 350 is needed for construction documentation.
Scanner specification: Specify scanner performance standards rather than specific models. This allows the surveyor to use appropriate equipment while ensuring quality.
File format: Choose formats compatible with your design software. Revit format is standard for BIM. DWG for CAD workflows.
Programme integration: Align scan-to-BIM programme with design programme. Scanning must be completed before design development begins.
Review and Approval
The BEP should be reviewed and approved by all parties before scan-to-BIM work begins:
- Client approves the scope and deliverables
- Architect approves the technical requirements
- Main contractor confirms programme integration
- Scan-to-BIM surveyor confirms the specification is achievable
Formal approval protects all parties. It confirms that everyone understands what will be delivered and when.
Fixed-Fee Scan-to-BIM from icelabz
icelabz works with clients to develop BIM Execution Plans for scan-to-BIM projects. We review the BEP, confirm specifications, and deliver scan-to-BIM services according to the plan.
All scan-to-BIM work is fixed-fee with no hidden charges. Contact icelabz with your project requirements for a fixed-fee quote.
Common BEP Mistakes to Avoid
Unclear LOD: Vague LOD requirements lead to disputes. Be specific about what LOD means for each element type.
Over-specified scanning: Requiring excessive point density or coverage increases cost without proportionate benefit. Specify what is genuinely needed.
Ignoring hidden areas: Not addressing hidden areas in the BEP means they may not be captured or modelled. Specify how hidden areas will be handled.
No revision limitations: Unlimited revisions drive up cost. Specify revision rounds and additional charges for extra revisions.
Programme misalignment: Scanning schedule that does not integrate with design programme is ineffective. Align scanning with design milestones.
Using the BEP During the Project
The BEP is a live document. Reference it during the project to:
- Verify deliverables meet specifications
- Track programme milestones
- Manage revision requests
- Resolve disputes about scope or quality
Regular reviews against the BEP ensure the scan-to-BIM project stays on track.
Fixed-Fee Scan-to-BIM Projects
icelabz delivers scan-to-BIM projects according to agreed BIM Execution Plans. All deliverables are defined in the BEP. Fixed-fee pricing applies.
Contact icelabz with your project requirements for a fixed-fee quote.