Buildability review: the questions we ask before a drawing is issued

A drawing can look finished and still not be ready to build from.

It can have clean linework, a tidy title block, a revision cloud, a drawing number and a professional layout. But that does not automatically mean the information is coordinated, complete or practical on site.

The real question is not only:

Does the drawing look correct?

The better question is:

Can someone actually build from this without guessing?

That is where buildability review matters.

A buildability review looks at drawings from the point of view of construction, coordination and site use. It checks whether the information is clear enough, whether key junctions are resolved, whether related drawings agree, and whether the package raises obvious risks before it is issued.

At Krain Studio, buildability review sits alongside technical CAD production, drawing audits, schedule checks and construction detailing. The aim is not to replace the architect, engineer, contractor, warranty provider or Building Control body. The aim is to identify missing information, unclear details and coordination risks before they become site questions.

This article explains the questions we ask before a drawing is issued.

1. Can the drawing be understood by someone who has not been in the meetings?

This is one of the most important tests.

Many drawings make sense to the person who produced them because they know the project history. They remember the design meetings, email decisions, client comments and consultant discussions.

The site team may not.

A contractor or subcontractor may only receive the drawings, schedules and specifications. They may not know which assumptions sit behind the drawing. They may not know which decisions are still unresolved. They may not know that a note was copied from an older revision and no longer applies.

So the first buildability question is:

Can this drawing stand on its own?

We look for:

• —Clear drawing title
• —Correct revision information
• —Readable notes
• —Clear dimensions
• —Relevant section and detail references
• —Obvious drawing status
• —Clear relationship to other drawings
• —Unresolved items identified rather than hidden
• —No reliance on private project knowledge

If a drawing only makes sense to the person who drew it, it is not ready enough for wider issue.

2. Are the plans, sections and details coordinated?

A buildable package needs joined-up information.

A plan may show one condition. A section may show another. A detail may show a third. Each drawing may look acceptable on its own, but the project team needs to know which information applies.

We check whether the drawings agree with each other.

Typical questions include:

• —Does the section match the plan?
• —Does the detail match the section?
• —Does the wall build-up match the notes?
• —Does the roof detail match the roof plan?
• —Does the window head detail match the elevation?
• —Does the threshold detail match the external levels?
• —Does the drainage route match the floor plan?
• —Does the door schedule match the plan?

Many site questions begin with drawing disagreement.

If a contractor has to decide between the plan and the detail, the package is creating unnecessary risk.

3. Are the key junctions resolved?

Buildings often succeed or fail at junctions.

The difficult parts are not usually the large open areas of wall or floor. The difficult parts are where things meet.

We look closely at junctions such as:

• —Wall to floor
• —Wall to roof
• —Roof to parapet
• —Eaves and verge
• —Door thresholds
• —Window heads, cills and jambs
• —Cavity closers
• —DPC and DPM continuity
• —Insulation continuity
• —Balcony or terrace interfaces
• —External wall to internal partition
• —New construction meeting existing construction
• —Service penetrations through fire or acoustic lines

A general arrangement drawing may show the arrangement in principle, but the junction detail explains how it works.

If the package has no detail for a critical junction, or if the detail is generic and does not match the project, the risk should be flagged before issue.

4. Is there enough space for structure?

Architectural drawings need to allow for structure.

That sounds obvious, but it is a common source of problems.

A ceiling zone may look fine until a steel beam is allowed for. A drainage route may look simple until joist directions are checked. A roof detail may look neat until rafter depths, truss zones or insulation requirements are added.

We ask:

• —Has the structural zone been allowed for?
• —Do openings align with structural logic?
• —Are lintels, beams or padstones likely to clash with other information?
• —Is there enough ceiling depth for structure and services?
• —Does the roof build-up allow for actual structural depth?
• —Do drainage routes pass through structural elements?
• —Do sections reflect the likely structural arrangement?
• —Is structural engineer input required before issue?

This is not about doing the engineer’s job. It is about identifying where the architectural information may not have allowed for the structural reality.

If a drawing relies on a beam being impossibly shallow or a pipe passing through a steel without coordination, the issue needs to be raised.

5. Is drainage actually workable?

Drainage often looks easy on a plan.

A line is drawn from one point to another. The route appears clear. The drawing moves on.

But on site, drainage needs falls, space, access, coordination with structure, coordination with fire and acoustic requirements, and a realistic route to a connection point.

We check:

• —Is the drainage route clear?
• —Is there enough fall?
• —Is the pipe run too long or too shallow?
• —Are SVPs sensibly located?
• —Does drainage clash with joists, steels or foundations?
• —Are boxing and service voids allowed for?
• —Are access points shown where needed?
• —Are penetrations through walls/floors considered?
• —Does drainage affect fire or acoustic separation?
• —Does the route depend on assumptions that need confirming?

A buildability review does not replace a drainage designer or contractor, but it can flag obvious risks before the drawing is issued.

If drainage cannot physically fit through the zone shown, it is better to find that before site starts.

6. Are levels and thresholds clear?

Levels are one of the most expensive things to get wrong.

A threshold detail might look fine in principle, but it needs to work with external ground levels, drainage, door system requirements, DPCs, insulation, accessibility and weathering.

We check:

• —Are finished floor levels clear?
• —Are external levels clear?
• —Are steps, ramps or falls shown?
• —Are level-access requirements identified where relevant?
• —Does the threshold detail manage water properly?
• —Does the DPC/DPM arrangement make sense?
• —Does the door frame fit the build-up?
• —Are balcony or terrace levels coordinated?
• —Are drainage channels or falls required?
• —Is there enough information for site setting out?

Unclear levels create site risk because they affect structure, drainage, access, waterproofing and finishes.

A drawing package should not leave threshold logic to be solved on site unless that is clearly intended and controlled.

7. Do the schedules match the drawings?

Schedules are often where buildability problems hide.

A window or door schedule may appear complete, but it still needs to match the plans, elevations and details.

We check:

• —Are all doors and windows scheduled?
• —Do schedule references match the plans?
• —Do window marks match the elevations?
• —Are fire ratings coordinated?
• —Are security notes clear?
• —Are external and internal doors separated properly?
• —Do scheduled sizes match the drawn openings?
• —Are threshold requirements identified?
• —Has supplier information been incorporated?
• —Are old references still present?

Schedules are used for pricing, ordering and installation. If the schedule is wrong, the wrong item can be ordered.

That is why schedule review is part of buildability review, not just document control.

8. Has supplier information been properly coordinated?

Supplier information can improve a package, but only if it is properly fed back into the drawings.

A supplier may confirm sizes, frame depths, cill profiles, installation requirements, ventilation requirements, fire certification, security certification or system constraints.

The question is:

Has that information changed the drawings?

We look for signs that supplier information is floating outside the package:

• —Supplier dimensions not reflected in the schedule
• —Frame details not updated
• —Cill or threshold requirements missing
• —Product assumptions not noted
• —Fire or security certificates not coordinated
• —Specialist drawings referenced but not included
• —Supplier comments not carried into revisions
• —Installation requirements not reflected in details

An email from a supplier is not the same as coordinated construction information.

If the drawing package is going to be used for construction or procurement, important supplier information should be visible where the project team needs it.

9. Are fire, acoustic and thermal lines understood?

A buildability review should look for the important performance lines in the building.

Fire, acoustic and thermal requirements are not just notes. They affect junctions, penetrations, doors, walls, floors, ceilings, service routes and details.

We check whether the drawings make these issues clear enough.

Questions include:

• —Where are the fire lines?
• —Where are the acoustic separations?
• —Where is insulation continuity required?
• —Do service penetrations affect fire or acoustic performance?
• —Do doors and walls align with fire strategy requirements?
• —Are cavity barriers or fire stopping zones considered?
• —Do details show the intended thermal line?
• —Are cold bridges or awkward junctions likely?
• —Do notes match the drawings?

This is not about replacing specialist input. It is about asking whether the architectural drawings communicate the intent clearly enough and whether obvious coordination gaps exist.

If a pipe route cuts through a compartment line, someone needs to know before it becomes a site issue.

10. Are copied notes and standard details still valid?

Copied information is one of the quiet risks in technical drawing packages.

Standard details and notes are useful. They save time and promote consistency. But they become dangerous when they are copied without being checked against the current project.

We look for:

• —Notes that refer to the wrong wall type
• —Old project references
• —Outdated specification notes
• —Generic details that do not match the plan
• —Details showing materials not used on the project
• —Incorrect fire, acoustic or insulation notes
• —Planning-stage wording left in technical drawings
• —Revision clouds left from previous issues
• —Standard details used for non-standard conditions

A copied detail is not automatically wrong. But every standard detail needs to earn its place in the package.

The test is simple:

Does this detail match the actual condition being built?

11. Is the drawing clear about what still needs confirming?

Not every drawing can answer every question.

Sometimes a drawing is issued while waiting for structural input, supplier confirmation, client decisions, site information or Building Control comments.

That is normal, but the drawing should be honest about it.

We look for unresolved items that are hidden rather than identified.

Examples include:

• —“Subject to structural engineer confirmation”
• —“Supplier to confirm”
• —“Site dimension to be checked”
• —“Existing drainage route to be confirmed”
• —“Fire strategy to confirm”
• —“Manufacturer’s details to be incorporated”
• —“Opening size subject to survey”
• —“Final specification TBC”

These notes should not be used to avoid coordination, but they can be useful when something genuinely remains unresolved.

The important thing is that unresolved items are visible, tracked and actioned.

Hidden assumptions create problems. Clear assumptions can be managed.

12. What would the contractor ask first?

This is a useful final test.

Before a drawing is issued, we look at it from the point of view of the person who has to use it.

What would they ask?

If the likely questions are obvious, the drawing package should try to answer them before issue.

A buildability review does not remove every future query, but it should reduce the avoidable ones.

Final thoughts

A buildability review is not about criticising a drawing package.

It is about asking whether the information is clear, coordinated and practical enough for the next use.

A drawing can be visually tidy and still contain missing information, broken references, unresolved junctions, schedule mismatches or coordination risks. Those issues are much easier to deal with before the drawings are issued than after they become site questions.

At Krain Studio, buildability reviews form part of wider freelance architectural technology support, including drawing audits, AutoCAD 2D technical production, construction detailing, schedule checks, Building Control drawing support and Stage 4/5 package support.