As-Built Packages Engineers Actually Use

# As-Built Packages Engineers Actually Use: Plans, Overlays, and Model-Ready Extracts

Existing condition documentation fails most refurbishment projects not because the data is absent, but because it is delivered in a format that cannot be acted upon. A PDF scan of a 1970s drawing set, a point cloud with no registered coordinate system, or a Revit model built from assumed dimensions rather than measured geometry all create the same downstream problem: engineers cannot trust what they are working from, so they either over-engineer to compensate or they miss critical conflicts during design. The result is variation orders, programme delays, and in some cases, structural interventions that were entirely avoidable.

The gap between raw survey data and a usable as-built package is where most investigation programmes fall short. Capturing data is a solved problem. Lidar scanning, GPR scanning, and photogrammetry can document a building to sub-millimetre accuracy. The question is whether that data is processed, structured, and delivered in a way that integrates directly into a structural engineer's workflow, an architect's design model, or a project manager's coordination environment. For most asset owners, the answer is still no.

This article addresses what a properly constructed as-built package contains, how each component is produced, where legacy drawing reconciliation fits into the process, and what the output looks like when it is genuinely model-ready rather than nominally so.

What Engineers Actually Need From As-Built Documentation

The standard deliverable from a building survey is a point cloud and a set of 2D drawings. For straightforward projects, that may be sufficient. For refurbishment work involving structural modifications, facade replacement, services coordination, or heritage compliance, it is rarely enough.

Structural engineers working on refurbishment need dimensionally accurate floor plans with confirmed slab thicknesses, column grid coordinates tied to a known datum, beam depths, and connection geometry. Architects need wall face positions, ceiling heights, and opening dimensions that reflect what is actually built, not what was permitted. Project managers need a coordination model that can be interrogated for clash detection before trades are mobilised on site.

A usable as-built package for a refurbishment project typically contains:

• Registered point cloud: in a coordinate system compatible with the project datum, formatted for import into Revit, AutoCAD, Navisworks, or Rhino
• 2D CAD drawings: extracted from scan data, showing existing conditions at each level with confirmed dimensions
• Structural overlay drawings: that reconcile scan geometry against original structural drawings, flagging discrepancies
• Model-ready BIM elements: built to LOD 300 or LOD 350, depending on project requirements, with embedded attribute data
• Condition annotations: where NDT findings such as delamination, carbonation depth, or reinforcement position are referenced directly on the model geometry

Legacy Drawing Reconciliation: Why It Cannot Be Skipped

Most buildings constructed before the mid-1990s have incomplete or inaccurate documentation. Drawings may reflect design intent rather than what was built. Structural members may have been relocated during construction. Slabs may have been poured at different thicknesses than specified. Penetrations may have been cut post-construction without documentation.

Legacy drawing reconciliation is the process of overlaying scan-derived geometry against original drawings to identify and quantify discrepancies. This is not a quality check on the original drawings. It is a systematic comparison that produces a reconciled set of documents showing what was designed, what was built, and where the two diverge.

In a commercial office tower investigation in Sydney's CBD, Lidar scanning of 22 floors revealed column grid offsets of up to 47mm from the original structural drawings, with cumulative drift across the building height that had not been documented in any subsequent survey. The reconciliation process identified three floors where the offset was sufficient to affect the design of a proposed facade replacement system. Without that reconciliation, the facade engineer would have been detailing to a grid that did not exist.

The reconciliation output is typically a set of overlay drawings in CAD, with a discrepancy schedule that logs each identified variance by location, magnitude, and structural significance. Engineers use this schedule to determine which variances require further investigation and which can be absorbed into design tolerances.

Point Cloud to CAD and BIM: The Processing Workflow

Raw point cloud data from a Lidar scan is not a deliverable. It is a dataset that requires registration, cleaning, and structured extraction before it has engineering value. The processing workflow determines the accuracy and usability of everything that follows.

Registration and Coordination

Individual scan positions are registered together using target-based or cloud-to-cloud methods to produce a unified point cloud. The registered cloud is then coordinated to the project datum, typically using survey control points established by a licensed surveyor. This step is critical for multi-storey buildings where floor-to-floor coordination must be maintained across the full height of the structure.

Extraction and Modelling

2D drawings are extracted by slicing the point cloud at nominated cut planes, typically 1200mm above finished floor level for plan views, and at mid-span for section views. Extracted geometry is traced in CAD and dimensioned from the point cloud, not from legacy drawings. This distinction matters: dimensions must reflect measured reality, not assumed positions.

BIM elements are built from the extracted geometry using the point cloud as a reference. For structural elements, this means modelling beams, columns, and slabs at their actual positions and dimensions, not at nominal sizes. A 250UC89 column that has been encased in concrete may measure 380mm x 380mm in the scan. The BIM element should reflect the encased dimension, with the steel section noted as an attribute.

Level of Development

The appropriate Level of Development (LOD) for as-built BIM varies by project phase and intended use. LOD 200 is adequate for early feasibility. LOD 300 is the minimum for design coordination. LOD 350 is required where interface conditions between structural, architectural, and services elements must be resolved in the model before construction. Asset owners retaining the model for ongoing facilities management typically require LOD 400 with embedded asset data.

Integrating NDT Findings Into the As-Built Package

As-built documentation for refurbishment projects should not be limited to geometric data. Where structural condition is relevant to the design, NDT findings must be integrated into the as-built package so that engineers can assess condition in the context of geometry.

GPR scanning produces reinforcement position data, cover depth measurements, and void detection results that are directly relevant to structural assessment. Half-cell potential surveys produce corrosion probability maps. Carbonation depth testing, conducted in accordance with AS 1012.20, establishes the depth of carbonation front relative to reinforcement cover. These results are most useful when they are georeferenced and overlaid on the as-built geometry, not delivered as standalone reports.

A practical integration approach maps NDT results onto the as-built floor plans and sections using a consistent referencing system. Reinforcement positions from GPR are shown on structural overlays. Corrosion probability zones from half-cell surveys are colour-coded on plan. Carbonation depth results are tabulated by grid reference and linked to the relevant drawing. This allows the structural engineer to assess condition and geometry simultaneously, which is the basis for any rational remediation design.

For further context on why this integration matters before refurbishment work begins, refer to our earlier article on as-built documentation and its role in renovation planning.

When the As-Built Package Is Not Enough

There are conditions where as-built documentation, regardless of quality, cannot substitute for further structural investigation. These include:

• Suspected structural modification: where scan geometry suggests members have been removed, relocated, or altered without documentation
• Concealed construction: where finishes, cladding, or services prevent scan access to structural elements
• Material uncertainty: where the as-built drawings do not confirm concrete grade, reinforcement specification, or connection type
• Condition-critical assessments: where the structural adequacy of existing elements must be confirmed before new loads are applied

In these situations, the as-built package defines the investigation scope rather than replacing it. Engineers should treat discrepancies identified during legacy drawing reconciliation as triggers for targeted investigation, not as documentation anomalies to be noted and set aside.

Concrete core extraction for compressive strength testing in accordance with AS 1012.14, combined with reinforcement sampling and tensile testing, may be required to confirm material properties. Where connection geometry cannot be confirmed from scan data, localised opening up works may be necessary. The as-built package should be structured to accommodate these findings as they are produced, with the model updated to reflect confirmed conditions.

Delivering a Package That Gets Used

The test of an as-built package is whether it gets used. Packages that are too large to open, formatted for software the project team does not have, or structured around the surveyor's workflow rather than the engineer's are routinely set aside in favour of site measurements and assumptions.

Practical delivery considerations include file size management for point clouds, with tiled or decimated versions provided alongside the full-resolution dataset. CAD drawings should be delivered in the project's nominated version of AutoCAD or MicroStation, not in the latest release. BIM models should be delivered in IFC format in addition to the native Revit or ArchiCAD format, to ensure compatibility across the project team. Coordinate systems should be documented explicitly, with transformation parameters provided for projects using a local datum.

Attribute data embedded in BIM elements should follow a consistent naming convention agreed with the project team before modelling begins. Retrofitting attribute structures after delivery is time-consuming and frequently incomplete.

Conclusion

As-built documentation for refurbishment projects is an engineering product, not a survey deliverable. The distinction matters because it determines what gets captured, how it is processed, and what format it is delivered in. A point cloud and a set of PDFs is a starting point. A registered, coordinated, NDT-integrated, model-ready package that has been reconciled against legacy drawings is what engineers, architects, and project managers can actually build from.

The investment in producing that package at the outset of a refurbishment project is consistently recovered in reduced design uncertainty, fewer site variations, and more defensible structural decisions. For asset owners managing buildings with incomplete or unreliable documentation, it is the foundation on which every subsequent design and maintenance decision rests.