Irregular Building Documentation Workflow

A bay that is not quite square, a roofline altered across several extensions, or a listed stair that twists between uneven floors can make an irregular building documentation workflow the difference between a confident design start and weeks of avoidable checking. Existing drawings often describe an earlier version of the building, while a quick site measure may miss the relationships that matter most once design work begins.

For architects and consultants, the objective is not simply to gather dimensions. It is to establish a dependable record of existing conditions, then translate that record into CAD or BIM outputs that suit the next design decision. That requires a workflow with clear scope, disciplined capture, appropriate modelling, and transparent quality control.

Why irregular buildings need a different approach

Regular buildings allow reasonable assumptions. Parallel walls tend to remain parallel, standard floor-to-floor relationships may repeat, and a limited set of measured checks can support conventional drawings. Irregular buildings do not offer that margin.

Heritage properties, converted industrial spaces, old townhouses and buildings altered in phases commonly contain changes in level, distorted walls, non-orthogonal rooms, uneven roof geometry and concealed structural adjustments. The issue is rarely one unusual feature in isolation. It is the way multiple irregularities interact. A wall that leans slightly may affect room areas, ceiling lines, elevation alignment and the apparent position of a roof junction.

This is why documentation should begin with the intended use of the information. A planning feasibility study needs a different level of certainty from a detailed refurbishment, coordination package or fabrication-sensitive design. Capturing more information than a project needs can add cost and programme time. Capturing too little creates a false economy when the design team must revisit site or work around uncertain geometry.

Set the documentation brief before site capture

A productive workflow starts with a short, specific conversation rather than a generic request for “as-built drawings”. The survey and documentation team should understand what will be designed, which areas are in scope, and where risk sits in the building.

The brief should establish the required outputs: for example, existing floor plans, elevations, sections, reflected ceiling plans, roof plans, a registered point cloud, or a Revit model. It should also define drawing scales, required units, file formats, naming conventions and any client BIM standards. If the design team intends to use a model for coordination, it is worth agreeing the model’s level of development at this point rather than assuming that all Revit models carry the same level of detail.

Access requirements matter just as much. Roof voids, basements, service areas, locked rooms and occupied spaces can all affect completeness. For listed buildings, the team should identify fragile finishes, restricted areas and elements that require particular care before equipment arrives on site.

A good brief does not eliminate every unknown. It makes those unknowns visible early, allowing the capture method and fee to reflect them honestly.

Capture geometry, not just individual measurements

For complex existing buildings, 3D laser scanning provides a strong geometric foundation. A scanner records millions of spatial points from each position, creating point-cloud data that represents walls, floors, ceilings, structure and visible features in their measured location. When scan positions are properly registered, the dataset allows the documentation team to examine relationships across rooms, floors and external elevations without relying on isolated measurements.

That does not mean laser scanning removes professional judgement. Glass, highly reflective surfaces, dense vegetation, tight voids and hidden construction can create gaps or uncertainty. Site notes, photographs and targeted manual checks remain valuable, particularly where materials, construction logic or access constraints affect how the captured information should be interpreted.

For a building with complicated roof forms or large external elevations, the capture plan may also need external control, elevated access or supplementary methods. The right approach depends on the site, the required accuracy and what must be documented. A modest internal refurbishment may not justify the same capture strategy as a heritage conversion with complex roofs and retained façades.

Registration and coverage checks are not optional

The point cloud is only as useful as its registration and coverage. During processing, scan positions must be aligned into a common coordinate system and checked for accuracy. Missing rooms, poorly captured junctions or inaccessible surfaces should be identified before drawing or modelling begins.

This stage is where a responsive documentation partner protects the programme. If information is incomplete, the team should explain what is missing, why it matters and whether a return visit or a documented assumption is the sensible route. Silent omissions are far more damaging than clearly recorded limitations.

Turn point-cloud data into usable design outputs

A point cloud is evidence, not a finished deliverable for every project. Design teams need structured information they can read, issue, coordinate and build from. The documentation phase converts measured data into the agreed format while preserving the logic of the captured building.

For CAD drawings, this means setting reliable floor levels, drawing wall positions from the point cloud, representing openings and features consistently, and placing sections where they reveal critical height changes or complex junctions. On irregular buildings, a single long section may be more valuable than several conventional cuts if it explains the relationship between split levels, roof structure and retained fabric.

For BIM, the modeller must make informed choices about how to represent non-standard conditions. A Revit model may need sloping floors, variable wall profiles, bespoke roof geometry or carefully modelled structural elements. However, model complexity should serve a defined purpose. Creating every visible imperfection as bespoke geometry can make a model slow, difficult to edit and disproportionate to the design stage.

The practical question is not whether the model looks impressively detailed. It is whether it represents the geometry and information needed for dependable decisions. A model at LOD100 may support massing and feasibility; LOD300 may be appropriate for coordinated design; LOD400 should be reserved for cases where fabrication-level definition is genuinely required.

Build checks into the irregular building documentation workflow

Quality assurance should happen throughout the workflow, not solely at final issue. Before delivery, the documentation team should cross-check the agreed scope against completed outputs, verify levels and key dimensions, review plan-to-section consistency, and inspect difficult locations against the underlying point cloud and site imagery.

Particular attention should go to interfaces where errors travel furthest: stair connections, roof-to-wall junctions, changes in floor level, party walls, façade returns and structural openings. These are often the locations where a small misunderstanding can affect several drawings and then become embedded in a developing design.

It is also useful to distinguish measured geometry from reasonable interpretation. In heritage buildings, surfaces may be visibly uneven, while the design team may need a simplified but accurate-enough plane for early work. That simplification can be appropriate if it is controlled and communicated. The problem is not interpretation itself; it is presenting an interpreted element as exact measured fact.

Deliver files that fit the team’s working method

A dependable output is one the recipient can use immediately. CAD files should be cleanly layered, sensibly named and purged of unnecessary clutter. Revit files should open in the agreed version, use a coherent family strategy and avoid needlessly heavy geometry. Drawings should include clear scales, levels, annotation and any necessary notes on scope or areas of limited access.

The delivery conversation matters too. A concise handover should confirm the files supplied, explain any assumptions or exclusions, and identify features that may need verification during later design stages. This is particularly useful where a building remains occupied or where parts of the structure could not be exposed.

For teams working across England and Scotland, a specialist survey partner can also help keep the process predictable across dispersed sites: clear quotation, agreed scope, scheduled capture, controlled production and timely issue. Space Captures applies this precision-first approach to complex and architecturally sensitive buildings, with outputs tailored to the design team’s required format and level of detail.

Use documentation as a decision-making baseline

The strongest existing-condition information does more than support a planning submission or provide a background plan. It gives the project team a shared spatial reference from which to test options, coordinate disciplines, price interventions and identify risk before it reaches site.

An irregular building will always contain some uncertainty. The right documentation workflow does not pretend otherwise. It records what was captured, defines what has been modelled, and makes the remaining questions clear enough for the design team to address them at the right time. That is how complex geometry becomes a dependable starting point rather than a recurring source of design risk.