Mansard Roof Extensions in Westminster

Use the adopted plan, not an old policy number

Westminster confirms that the City Plan 2019–2040 (2026) replaced its previous plan. The current document contains Policy 45: Townscape and architecture, including provisions for roof extensions. Begin with that adopted text. An older report may still be helpful background, but the existence of a familiar policy number in it is not evidence that the number remains current.

Ask your planning adviser to record the documents used for the assessment and the relevant passages. Keep the adopted plan separate from older guidance, earlier applications and design examples. This small piece of organisation makes it easier to understand why a particular roof form is being explored and which constraints still need a site-specific response.

Read the terrace as a group

The current roof-extension provisions distinguish groups already characterised by roof additions from terraces with an unimpaired roofline. They address the design of additions and, where relevant, a coordinated approach across a terrace. The policy is not a blanket endorsement of an isolated mansard wherever there is room to draw one.

Prepare photographs that show the whole group, not just the property frontage. Note the visible roof forms, parapets, chimneys and changes between buildings. Ask the designer which features appear consistent and which belong to later alterations. The purpose is to understand the composition, not to select the largest nearby addition and assume it establishes a precedent.

Build an evidence set around the roof

Commission or assemble appropriate existing drawings before treating the internal layout as fixed. Ask for the relationship between the existing roof, stair, ceilings and external features to be clear. Photographs and measured information should describe the same condition. Where a feature cannot be inspected, label it as unconfirmed rather than using an assumption without explanation.

A useful design review compares the existing and proposed roof from the same viewpoints. Include the places where the addition could be seen, the silhouette of the group and the relationships at party walls. These are practical recommendations for explaining a proposal; the precise application documents should be agreed with the planning adviser using the council’s current requirements.

Keep architectural details in the discussion

The City Plan’s supporting text on mansards discusses the age and character of buildings and features such as chimneys, parapets and cornices. Ask the designer to explain how those elements are treated rather than presenting a roof volume without its detail. The supporting text also describes circumstances in which further upward extension may be inappropriate.

Consider windows, junctions, drainage and any equipment together. A roof design can change substantially as these details are resolved. Keep a schedule of decisions and show revisions consistently across elevations and sections. If the design relies on hiding an element from a view, ask for evidence of that relationship instead of a broad statement that it will be discreet.

Check the heritage context separately

Use Westminster’s conservation-area information and mapping to identify relevant designations, then consult the material for the particular area. The council’s conservation-area audit directory warns that older audits can refer to policies that predate the current framework. Read the description of character alongside the adopted plan, and ask your adviser how each document informs the proposal.

Keep a distinction between understanding the building’s significance and choosing a construction solution. A technically achievable alteration still needs an appropriate planning and heritage assessment. Do not assume that a roof is unimportant because it is difficult to see from the nearest pavement. Ask what evidence is needed to explain its role in the building and its wider setting.

Test the internal arrangement without fixing the outcome

A sketch layout can help reveal questions about the stair, circulation and usable space, but it should remain provisional while the external approach is assessed. Ask the designer to identify where the accommodation depends on a disputed roof height, an unresolved junction or an assumption about existing structure. Keep alternatives visible so the discussion is about viable options rather than a single drawing that is difficult to revise.

Invite the relevant technical advisers to explain how their requirements interact with the roof design. Their role is to assess the actual proposal, not to certify an example copied from another building. Record any issue that could alter the external appearance so it can be considered before the planning information is finalised.

Read older roof guidance with care

Westminster’s page for older supplementary guidance explains that those documents refer to a superseded policy framework and may remain relevant where consistent with adopted policy. A historic roof guide can illustrate design vocabulary without settling today’s planning decision. Make that distinction explicit in the project brief.

When discussing an earlier approved extension, ask for the application documents, decision and relevant conditions rather than relying on a photograph. A similar appearance does not establish identical circumstances. The useful comparison explains both similarities and differences, including the original roof, surrounding buildings and the particular design that was assessed.

Move from research to a project discussion

Prepare a concise brief explaining the rooms you hope to accommodate and the documents already available. Include the unresolved questions about the roof group, heritage context and structure. Our Westminster loft conversions page is the service destination for a proposed project. For further background on designations and area documents, read conservation areas in Westminster. Keep the policy enquiry separate from any promise of permission.

Frequently asked questions