9 Top Mistakes in As Built Documentation

A refurbishment scheme is already under pressure when the existing drawings look tidy, but the building does not. That disconnect is where costly decisions start. Many of the top mistakes in as built documentation happen before design even begins, when teams rely on incomplete site information, vague scopes, or outputs that look finished but are not dependable enough to build from.

For architects, technologists and consultants, the issue is rarely documentation for its own sake. It is what poor documentation does downstream. A missing soffit level can affect coordination. An assumed wall thickness can distort net areas. A simplified roof form can create planning, detailing and access problems later. Good as built documentation should reduce uncertainty, not hide it.

Why top mistakes in as built documentation matter

As built documentation sits at the start of many design and coordination workflows, so small errors rarely stay small. They move into planning drawings, measured areas, structural assumptions, MEP coordination and contractor queries. By the time the problem is visible, the team is already spending time correcting something that should have been dependable from day one.

This is especially true on heritage, irregular or geometry-heavy buildings. A conventional approach may appear cheaper at instruction stage, but if the documentation does not reflect actual site conditions, the cost returns later as rework. Precision has a direct value when the building is complex, access is constrained, or the project team needs a model they can use immediately.

1. Treating old drawings as verified information

One of the most common mistakes is starting from legacy plans and assuming they are broadly correct. Existing drawings can be useful reference material, but they are not evidence of current site conditions unless they have been properly checked. Buildings change. Extensions get regularised badly. Partitions move. Ceiling zones are altered. Services routes rarely match archived information.

The problem is not using old drawings at all. The problem is using them without a clear verification process. If a team traces, adapts or models from inherited information that has not been checked against measured reality, they risk embedding guesswork into every later stage.

2. Scoping the survey too narrowly

A project may begin with a request for floor plans, then quickly expand to include reflected ceiling plans, elevations, sections, roof information or a Revit model. If the original capture scope was too narrow, the team may have enough data for one output but not enough for the next. That usually means a return visit, design delay or incomplete modelling.

This is where brief quality matters. A dependable survey scope is shaped by intended use, not just by an initial drawing list. If the building is likely to require coordination around ceiling voids, roof geometry, stair cores, plant zones or facade articulation, that should be captured at the start. The most efficient site visit is usually the one planned with downstream outputs in mind.

3. Ignoring tolerances and expected level of detail

Not every project needs the same degree of detail, and pretending otherwise creates problems. A planning-stage massing model does not require the same granularity as a coordination-ready Revit model. Equally, a listed building with warped geometry cannot be documented to the same assumptions as a regular new-build shell.

One of the top mistakes in as built documentation is failing to define what accuracy and detail actually mean for the project. Teams ask for a BIM model, but not the intended LOD. They request elevations, but not whether they need every moulding, sill offset or façade irregularity represented. When those expectations remain unstated, the delivered output may be technically competent but operationally wrong for the brief.

4. Smoothing out irregular geometry

Many documentation issues come from making buildings more regular than they really are. Walls that taper get drawn straight. Floors that fall are treated as level. Historic timber structures are simplified into symmetrical lines because the true geometry feels inconvenient. It may make the drawings look cleaner, but it makes them less useful.

This matters most in heritage properties, complex refurbishments and architecturally sensitive spaces, where geometry is not an anomaly but part of the project condition. If the documentation removes those irregularities, the design team loses the ability to make informed decisions about fit, clearance, intervention and conservation impact. Clean drawings are not the goal. Dependable geometry is.

5. Missing the hard-to-reach or easy-to-overlook areas

Documentation failures are often found in roof spaces, service risers, ceiling voids, plant rooms, rear elevations, stair undersides and external level changes. These areas can be awkward to access, but they often carry disproportionate design risk. A project may proceed comfortably until somebody needs to route services through a zone that was never properly captured.

The trade-off is practical. Not every hidden area can be accessed on every visit, and some constraints are genuine. But these gaps should be identified early and recorded clearly. Unknowns are manageable when they are explicit. They become expensive when a drawing implies certainty that was never there.

6. Producing outputs that are accurate but not usable

Technical accuracy alone is not enough if the files arrive disorganised, inconsistent or difficult to work with. Layers that are poorly structured, lineweights that obscure information, unclear naming conventions, over-modelled families or heavy Revit files can all slow a design team down. In practice, this is a quality issue just as much as measurement accuracy.

The best documentation supports immediate use. Plans should read clearly. Sections should be placed where they answer real design questions. Models should be built to the agreed purpose, not inflated with unnecessary complexity. Design-ready outputs save time because they reduce interpretation, not because they contain the maximum possible amount of information.

7. Failing to communicate assumptions and exclusions

No survey captures everything. That is normal. What matters is how assumptions, limitations and exclusions are communicated. If a loft was inaccessible, say so. If floor finishes prevented structural build-up verification, record that. If certain dimensions were inferred from adjacent measurable conditions, that should be transparent.

This is one of the clearest markers of a reliable documentation partner. Honest communication protects the design team. It allows architects and consultants to decide where further opening-up, intrusive checks or follow-up investigation may be needed. Silence creates false confidence, and false confidence is far more damaging than a clearly stated limitation.

8. Choosing speed or low cost over dependable capture

Fast turnaround matters, and so does cost control. But when documentation is treated as a commodity purchase, quality becomes inconsistent very quickly. Low-fee, lightly scoped survey work may appear efficient at instruction stage, yet the saving disappears if the team spends days checking dimensions, remodelling geometry or issuing revised packages.

This does not mean every project needs the highest possible level of capture. It means the method should suit the risk profile of the building. On simple assets, a lighter approach may be enough. On irregular, listed or coordination-sensitive projects, precision-first capture usually pays for itself because it prevents avoidable uncertainty.

9. Waiting too long to involve the documentation team

Existing-condition information is often treated as an early procurement task rather than a technical decision. The result is a rushed instruction, limited briefing and avoidable scope gaps. By the time the documentation provider is involved properly, the programme is already tight and key questions about outputs, access and intended use have not been answered.

Early involvement usually improves the result. It allows the survey strategy to be shaped around actual project needs, whether that means targeted sections, façade detail capture, roof modelling, or point cloud-backed Revit outputs. It also helps identify constraints before the site visit rather than after the files are delivered.

How to avoid these mistakes in practice

Most problems are avoidable when the project starts with a clearer brief and a more disciplined capture strategy. The useful questions are straightforward. What decisions will this documentation support? Which outputs are needed now, and which may be needed next? Where is the geometry likely to be irregular, concealed or difficult? What level of detail is appropriate for the stage and procurement route?

It also helps to judge documentation quality by usability, not just by file type. A floor plan is not dependable because it exists in CAD. A model is not useful because it is in Revit. The real test is whether the output reflects site reality closely enough, clearly enough and in the right structure for the design team to work with confidence.

For practices working across England and Scotland, that becomes even more important on remote sites, listed properties and refurbishments with limited tolerance for return visits. In those situations, careful scoping and accurate capture are not premium extras. They are what keep the project moving.

Good as built documentation should feel quiet in use. It should not force constant checking, second-guessing or remedial measurement. When the geometry is dependable, the scope is properly defined and the outputs are built around real design needs, the whole project starts from firmer ground.