How to Scope Laser Scanning for a Building

A laser scan can capture millions of measured points, but it cannot correct a brief that leaves key decisions unresolved. Knowing how to scope laser scanning properly means defining what the design team needs to rely on, not simply arranging a scanner visit. The difference shows up later: in whether a section aligns with site conditions, whether a Revit model supports coordination, and whether the project team can design without repeated return visits.

For existing buildings, especially listed properties, irregular structures and complex refurbishment sites, the scope is the first control on quality. It establishes the required accuracy, the areas to be captured, the outputs to be produced and the practical conditions that could affect the survey.

Start with the decisions the documentation must support

The most useful question is not, “What can be scanned?” It is, “What will the team use the information for?” A planning-stage feasibility study needs a different level of detail from a technical design package, a heritage record or a model intended for services coordination.

Set out the intended use at the outset. For example, the output may support existing floor plans and elevations for planning, a coordinated Revit base model for design development, or detailed measured sections through an irregular roof structure. This determines the capture strategy and how much interpretation is needed after site work.

It also avoids two common problems. The first is commissioning more model detail than the project can use. The second is receiving a visually convincing point cloud or model that does not contain the geometry, annotation or accuracy needed for the next design decision.

Where several consultants will use the information, agree the primary workflow early. A point cloud may be sufficient for a specialist consultant, while the architect may require clean 2D CAD drawings and a Revit model. These are related deliverables, but they are not interchangeable.

Define the survey extent before defining the deliverables

A drawing package is only as dependable as its coverage. Survey extents should be described in practical, unambiguous terms: which buildings, storeys, rooms, roof areas, basements, external elevations and surrounding features are included.

For refurbishment work, identify the interfaces that matter. This may include party walls, adjacent structures, service risers, roof junctions, stair cores, plant rooms or floor level changes between old and new construction. If an extension is planned, capture enough of the existing building and relevant external context to establish levels, openings, roof geometry and connection points.

Do not assume that “the whole building” is precise enough. A warehouse may have a main volume, offices, mezzanines, loading areas and inaccessible roof zones, each requiring a different approach. A listed house may contain cellar vaults, concealed roof spaces and distorted walls that affect the accuracy and usefulness of the final record.

The brief should also state what is excluded. Restricted tenant areas, unsafe spaces, loose furniture, ceiling voids and inaccessible elevations can all affect completeness. Clear exclusions are not a limitation of the survey. They are an honest record of what the documentation can and cannot represent.

Set accuracy around risk, not habit

Laser scanning supports high-accuracy measured documentation, but a project does not automatically require the same tolerance everywhere. The appropriate accuracy depends on the decisions being made and the consequences of getting them wrong.

An existing-condition plan used to test broad layouts can tolerate a different level of interpretation from one used to fabricate joinery, coordinate steelwork or position new services in a constrained historic interior. Similarly, the geometry of a regular commercial shell is generally more straightforward than a timber-framed building with uneven floors, leaning walls and non-orthogonal rooms.

Discuss accuracy alongside the required representation. Is the requirement for measured floor plans with wall thicknesses, or is every beam, opening reveal and sloping ceiling required? Are floor levels needed at key thresholds, throughout each room, or only where they affect accessibility and drainage? Does the project need true geometry, or a simplified model suitable for design coordination?

For heritage and complex-geometry projects, it is often sensible to retain the point cloud as the measured reference while producing a model that has been deliberately rationalised for its intended use. A Revit model is not automatically a forensic record of every surface deviation. It should be clear where geometry is modelled to actual conditions and where it is simplified to maintain an effective design workflow.

Scope laser scanning around access and site conditions

The site visit is not an isolated operation. Access arrangements have a direct effect on capture coverage, programme and cost. A well-prepared scope records working hours, keyholders, security procedures, induction requirements, occupied areas, parking, loading restrictions and any requirement for permits or escorts.

Consider the building as it will be on the survey day. Occupied offices, retail spaces, schools and healthcare environments may need scanning outside normal hours or in planned phases. Active construction sites may require coordination with the principal contractor. Heritage sites may have restrictions around fragile finishes, public access or limited opportunities to enter roof spaces.

Visibility is equally important. Laser scanning records visible surfaces, so items obscured by stored materials, suspended displays, dense furniture or closed service cupboards may not be captured. This does not always justify clearing every space. It does mean deciding which obstructions are acceptable and which need to be removed or opened before the survey.

External work should be considered separately. Trees, parked vehicles, temporary scaffolding and poor access can obscure elevations. If aerial imagery, roof capture or external context is required, make that explicit and account for weather, airspace considerations and safe access in the programme.

Specify outputs that people can use immediately

A useful scope names the outputs, their format and their purpose. “Scan to BIM” alone does not explain the required model content, level of development or drawing deliverables.

For 2D documentation, confirm the drawing types required. These may include floor plans, roof plans, reflected ceiling plans, elevations, sections and site context drawings. State whether dimensions, room names, levels, door and window tags, materials or heritage features are required. It is more efficient to agree drawing conventions before production than to revise a complete set after delivery.

For BIM, define the software version, coordinate system, model origin and expected level of development. A model at LOD100 may be suitable for massing and initial feasibility. LOD300 may support coordinated design information. LOD400 requires a more specific conversation because fabrication-level content must be tied to clearly defined scope and responsibility.

Ask how the model will be hosted and used. If the design team works from Revit, native RVT delivery may be appropriate alongside exports. If several disciplines use different platforms, agreed exchange formats and coordinate conventions reduce avoidable alignment issues. The point cloud format, registration approach and any requirement for sectional or orthographic imagery should be confirmed too.

A practical scope should cover at least these five points:

• Required drawings, models and point-cloud files

• Software versions, file formats and naming conventions

• Model detail, classification and information requirements

• Coordinate system, datum and survey control requirements

• Review stages, delivery dates and responsibility for approvals

Allow for registration, control and verification

Scanning is only one part of the documentation process. Individual scan positions must be registered into a single coordinated dataset, then checked against control and site measurements. The required approach varies with project scale, external coordination needs and the consequences of accumulated error.

For a self-contained building survey, a local coordinate system may be appropriate. For a project that must align with topographical information, structural grids, neighbouring surveys or civil engineering data, establish the required control and datum before capture starts. Retrofitting this decision later can create unnecessary conversion work and uncertainty.

Verification should be part of the agreed workflow, not an assumed extra. Quality checks may include registration reports, measured spot checks, drawing review against point-cloud data and model audits against the stated brief. The goal is dependable geometry, not a large volume of data with no clear basis for use.

Build a realistic programme for the full service

A one-day survey does not necessarily mean one-day delivery. Programme planning should include site preparation, scanning, registration, processing, CAD or BIM production, internal quality assurance, client review and any agreed revisions.

Turnaround depends on building size, access, output complexity and the condition of the source information. A clean shell captured for floor plans can move quickly. A multi-storey listed building with intricate roof geometry, multiple sections and a detailed Revit model requires more production time because the value lies in careful interpretation, not only data capture.

Give the documentation team any existing plans, models, photographs, grid information and project requirements before the visit. Existing information should never replace measurement, but it can help identify discrepancies, plan coverage and focus attention on critical areas.

A clear brief makes laser scanning more than a site activity. It creates a dependable starting point for design, coordination and conservation decisions. If the building is unusual, the programme is tight or the intended outputs carry significant design risk, involve the documentation specialist before the brief is fixed. The best scope is one that gives every downstream user confidence in what has been measured, modelled and delivered.