Preparing a demolition drawing: strip out vs keep

Demolition drawings fail when existing and proposed blur together

The single most common problem I see on demolition drawings is someone reusing the existing conditions layer as the demolition layer without any visual distinction, so a contractor on site genuinely cannot tell at a glance what's coming out and what's staying put. A demolition drawing has exactly one job, to make removal scope unambiguous, and that means the drawing convention matters as much as the accuracy of what's shown.

The standard approach, and the one I'd recommend defaulting to unless your practice has its own convention, is hatching or colouring everything to be demolished in a hot colour, red is the near universal choice, with everything to be retained left in black or a neutral existing colour, and anything new proposed shown in a third colour entirely so there's zero confusion between the three states.

Building the existing conditions base honestly

You can't draft an accurate demolition plan from a design drawing that's been quietly updated over several revisions, because by that point it may no longer reflect exactly what's physically on site. Start from a genuine existing conditions survey, or at minimum a recent site verification, and only then start marking elements for removal, because a demolition drawing built on outdated existing information risks a contractor stripping out something that was actually already replaced or, worse, missing something that needs to come out because it was never accurately shown in the first place.

An existing staircase, for instance, whether it's staying, being replaced with a new configuration, or removed entirely to open up a stairwell, needs to be shown at its actual current dimensions before you mark its fate, not at whatever the original as-designed drawing said it should be.

On a refurbishment where the existing drawings are more than a few years old, it's worth budgeting time for at least a partial resurvey of the areas directly affected by demolition scope, even if a full remeasure of the whole building isn't in budget, since the areas being demolished are exactly the areas where inaccurate existing information causes the most expensive on site surprises.

What typically gets flagged for removal

On a domestic extension or refurbishment, the usual candidates are internal partition walls being opened up, an existing staircase being relocated or replaced, external gates and boundary features being altered for a new access point, and areas of paving or hardstanding being broken out ahead of new foundations or a resurfaced driveway. Each of these needs its own clear demolition note, not just a colour change, because a colour alone doesn't tell a contractor whether to salvage, skip, or carefully remove and store an item for reinstatement.

For anything with potential heritage or reuse value, period ironmongery on a gate for instance, note it explicitly as 'remove and retain for reinstatement' rather than leaving it lumped in with general demolition, because once it's in a skip that instruction can't be undone.

Services routing through elements marked for demolition needs flagging too, even though it's not strictly part of the architectural block set, since a partition wall coming out might be carrying cabling or pipework that needs rerouting before it's safe to strip, and a demolition drawing that's silent on this can send a contractor into a wall without the right isolations done first.

Keeping the block library separate for existing vs new

It helps enormously to maintain distinct block definitions for existing-to-be-demolished items versus their proposed replacements, even when they're visually similar, rather than reusing one block and just changing its layer colour. An existing gate marked for removal and a new gate being proposed in roughly the same position are functionally different objects in the drawing's logic, and keeping them as separate block inserts avoids the classic mistake of a contractor referencing the wrong one during a site visit because both were technically 'the gate block' in the file.

Same goes for paving, if an existing paved area is being broken out and replaced with a different module or pattern, show the existing paving block on the demolition layer and the new paving block on the proposed layer as genuinely separate inserts, not one block with a note saying 'replace.'

This separation also protects you when a demolition scope changes mid project, which happens more often than anyone plans for, because if the existing and proposed blocks were ever merged into one, unpicking a scope change means re-establishing what was originally there, whereas keeping them separate from the start means you can simply toggle a layer back on to recover the original condition instantly.

Sequencing and the drawings that follow

A demolition drawing rarely stands alone, it usually needs to be read alongside the proposed works drawing, and the two need to line up dimensionally so a site team isn't cross referencing two sheets that don't quite agree on where a wall or boundary actually sits. I always overlay the demolition and proposed sheets on screen before issuing, even briefly, just to confirm nothing marked for removal is actually needed to support something shown as retained, which happens more often than you'd expect on drawings assembled by more than one person.

Where the demolition scope affects structural elements, flag it clearly for the structural engineer's review too, since removing what looks like a simple partition can occasionally turn out to be doing more work than the architectural drawing assumed.

Common demolition drawing mistakes worth avoiding

A handful of mistakes show up repeatedly on demolition drawings, and most trace back to rushing the drawing rather than any lack of skill. The most common is marking an element for demolition without checking whether it's actually load bearing or carrying services that need isolating first, a partition that looks purely cosmetic on the existing drawing can occasionally turn out to be doing structural work nobody flagged, and a demolition note that doesn't distinguish 'non structural, remove freely' from 'structural, confirm with engineer before removal' puts that judgement call entirely on whoever's on site that day.

The second is forgetting to note what happens to the void once something's removed, if a staircase comes out to open up a stairwell, does that opening get temporarily guarded, does the floor edge need protection, and a demolition drawing silent on interim safety during the works window is genuinely a gap worth closing before issue, not just an architectural drafting nicety.

I'd also flag scope creep as a recurring issue, a demolition scope that grows during the works, someone on site deciding to take out a bit more than was marked because it seemed sensible at the time, without the drawing ever being updated to reflect it, which then leaves the as-built record wrong for anyone relying on it later.

The habit that prevents site disputes

The catch here is that demolition disputes on site are expensive and slow everything down, so the small extra effort of a genuinely clear colour convention, honest existing conditions, and explicit notes on anything ambiguous pays for itself the first time it prevents a contractor calling to ask 'does this include the gate or not.' A demolition drawing that answers that question before it's asked is doing its job properly.

It's a small discipline in the context of a whole project programme, but I've seen a single ambiguous demolition drawing cost a contractor a full day chasing clarification before proceeding, which on a tight programme is a real, billable delay that a clearer drawing would have avoided entirely.