Mastering Heritage Impact Assessment in 2026
By Domus
By Domus
A lot of teams meet heritage risk too late. The site looks straightforward, the appraisal works, heads of terms move quickly, and then a planner or conservation officer asks for a heritage impact assessment that exposes a design assumption nobody priced, timed, or stress tested.
That's when a viable scheme starts to wobble. Not because heritage is obscure, but because it was treated as a planning appendix instead of a commercial input.
A good heritage impact assessment does more than satisfy validation. It tells you whether your massing, materials, access strategy, programme, and lender narrative still hold once heritage constraints are on the table. If you want fewer redesign loops, fewer planning surprises, and cleaner underwriting, it needs to sit much earlier in the workflow.
A familiar scenario. A developer secures a site on the edge of a conservation area and assumes the heritage issue is manageable because the building itself isn't listed. The initial appraisal carries a sensible allowance for planning risk, the architect develops a scheme with an extra storey, and the lender gets a clean early pack showing acceptable margin.
Months later, the local authority pushes back. The issue isn't only height. It's roof form, façade rhythm, visibility from a nearby heritage asset, and the effect of new activity on the character of the setting. Suddenly the preferred cladding package looks wrong, window proportions need redesign, and a previously efficient unit mix starts to unravel.
That's how schemes drift from “minor constraint” to “margin problem”. A conservation area can hide serious restrictions on form, materials, and townscape response. On more sensitive sites, even a modest intervention can trigger a much deeper evidence burden than the team expected. If you want a broader view of how these risks show up before planning, this piece on planning constraints that kill deals is worth reading alongside your acquisition checks.
The failure point is rarely the existence of heritage policy. It's the sequencing.
Practical rule: If heritage could influence scale, external appearance, demolition scope, or setting, it belongs in pre acquisition diligence and first pass viability.
Take a conversion and extension near a locally listed building. The first scheme may look compliant on daylight, access, and unit efficiency. But if the authority expects a stronger response to the setting, you may need a lower ridge line, revised materials, and more detailed justification for every visible change. That can mean fewer saleable metres, a slower planning route, and specification changes that hit cost before anyone has updated the model.
At that point, the heritage impact assessment isn't about history. It's about financial certainty, scheme durability, and whether the deal still deserves more time and money.
A heritage impact assessment is the formal evidence pack used to explain the significance of heritage assets affected by a proposal and to assess how the proposed development would change that significance. In the UK, it isn't a nice to have. It's a planning requirement in the right circumstances, and it needs to be prepared with enough rigour to stand up to scrutiny from the local planning authority, consultees, and often lenders.
In the UK, a Heritage Impact Assessment is a mandatory requirement for development proposals affecting listed buildings, World Heritage Sites, conservation areas, and locally listed buildings, as codified under Paragraph 172 of the National Planning Policy Framework. The assessment must follow a five step methodology from Historic England's Good Practice Advice in Planning Note 3 (2017) to systematically evaluate impacts on over 9,000 listed buildings and 1,600 conservation areas according to this UK HIA overview.

The phrase “heritage asset” catches more than many teams expect. It can include listed buildings, conservation areas, World Heritage Sites, and other designated or locally recognised assets. It also includes their setting, which is where many schemes get caught out. Setting isn't just a view. It can include relationships, context, use, and the way a place is experienced.
That matters in practical design terms. If you're working on a refurbishment or extension, details that look secondary in a cost plan can become central in the HIA. Material compatibility is a good example. When a proposal depends on replacing or matching historic finishes, specialist references can help teams understand what a credible contextual response looks like, including resources on selecting historic cement tiles where material character is part of the planning conversation.
A weak HIA leaves too much to interpretation. A strong one helps the project team answer four commercial questions early:
A heritage impact assessment should be treated as evidence for decision making, not just evidence for submission.
An HIA is more than a description of an old building. It's an assessment of significance, the contribution of setting, the impact of change, and the extent to which harm can be avoided, reduced, or justified. That's why it sits right at the junction of planning, design, and commercial appraisal.
If your consultant only writes descriptive history and doesn't link that analysis to the proposed scheme, you don't yet have the report you need.
By the time a scheme reaches formal pre-app, the HIA should already have tested the design against the deal model. If that work starts only after drawings are fixed, the report often becomes a defence document for a scheme that is already too expensive to revise.
A good HIA gives the project team a method for making decisions in the right order. It checks what matters, shows where harm arises, and identifies what can still be changed before planning risk turns into valuation risk or lender concern.
In the UK, the standard reference point is Historic England's Good Practice Advice Note 3, which sets out a five-step approach to assessing settings and impact. The planning conclusion then needs to align with the National Planning Policy Framework categories of no harm, less than substantial harm, or substantial harm. In London, many practitioners also use a more granular scale for judging degrees of less than substantial harm, reflected in this heritage report appendix used in London practice.
Step 1 identifies the heritage assets affected by the proposal and the extent of their setting, a stage where poor scoping starts to cost money. If the team focuses only on the listed building next door and ignores the conservation area, key views, or related assets nearby, the baseline is wrong and the design can head in the wrong direction.
Step 2 assesses significance and the contribution made by setting. A useful report is specific. It should explain which views, spaces, approaches, boundaries, and relationships add heritage value, and which elements make little or no contribution. That distinction matters because it tells the architect where there is room to move and where there is not.
Step 3 tests the effect of the proposal. Height, massing, demolition, extensions, roof plant, materials, openings, access changes, boundary treatment, and changes in use all need to be assessed against the significance identified earlier. This is also the point where the HIA should be read alongside the appraisal model. If preserving significance means losing saleable area, adding specialist materials, or reducing plant capacity, those consequences need pricing, not just noting.
Step 4 sets out avoidance, reduction, and enhancement measures. This step reveals consultant quality. A weak report merely states that harm can be mitigated. A useful one identifies what should change, what that change is likely to do to cost and programme, and whether the revised scheme still holds together commercially.
Step 5 records the planning balance and any ongoing requirements. For the developer, that means understanding likely conditions, reserved details, recording obligations, material approvals, and conservation constraints that can affect procurement and delivery. For the lender, it helps translate heritage advice into underwriteable risk.
The right level of reporting depends on the sensitivity of the site and the scale of change. Proportionality matters, but false economy is common. A short statement can be enough for modest works. On a sensitive or highly geared deal, a thin report often saves a small fee up front and creates a much larger problem later.
| Aspect | Heritage Statement (Proportionate) | Full Heritage Impact Assessment |
|---|---|---|
| Typical use | Minor works and simpler proposals with limited heritage effects | Major schemes, sensitive settings, or proposals with clear potential for heritage harm |
| Scope | Summary of significance and likely effects | Detailed assessment of assets, setting, impact pathways, harm levels, and mitigation |
| Evidence base | Focused and proportionate | Broader documentary research, site analysis, visual review, and scheme testing |
| Commercial use | Helps with early planning sense-checking | Informs viability testing, design revision, lender review, and planning strategy |
| Cost benchmark | Often at the lower end of consultant fee scales for straightforward minor projects, with benchmarks for small heritage statements referenced by the Resi guide to heritage statements and consultant costs | Higher fee input, usually scoped around the number of assets, sensitivity of the setting, and amount of design iteration required |
A credible HIA usually includes the following:
The strongest reports also show their workings. They make clear why one option performs better than another and what the commercial consequence of that choice may be. That matters in credit papers and investment committee discussions. If the heritage consultant concludes that the current design causes a level of harm likely to attract objection, the development appraisal, planning strategy, and lender narrative all need to move together.
For teams already running parallel planning inputs, heritage should sit beside transport, townscape, archaeology, and environmental review rather than arriving as a stand-alone appendix at submission stage. On larger or more sensitive schemes, it helps to understand how the HIA interacts with wider evidence such as an environmental impact assessment process for planning applications, because one workstream can change assumptions in another.
The best HIA reports read like decision documents. They show what the scheme does to significance, what can still be changed, and what that means for consent, cost, and funding.
The recurring failure is vagueness. Statements such as “the proposal respects local character” carry little weight unless the report explains how, where, and to what degree. Long historical descriptions without a clear analysis of change are just as weak.
If the report does not link significance to design impact, planners are unlikely to rely on it. Lenders should be equally cautious, because an unclear HIA leaves too much room for redesign, delay, and revised underwriting assumptions late in the process.
A deal can look clean at appraisal stage, then start slipping once heritage advice arrives and the scheme needs to change. The expensive part is rarely the report fee itself. It is the redraw, the planning delay, the revised cost plan, and the awkward conversation with a lender who underwrote a scheme that no longer exists.
Commission the HIA early enough to influence the scheme and the credit story behind it. For a sensitive site, that usually means pre acquisition, exclusivity, or immediately after heads of terms. If the first proper heritage review starts after the design has settled and the appraisal has been circulated, the team is already paying for late information.
Appoint a heritage consultant who deals regularly with planning applications, significance assessment, and design iteration on live development projects. Accreditation matters, but so does judgement. The right adviser can tell the difference between a genuine consent risk and a point that can be managed through design changes, sequencing, or better evidence.
That commercial judgement is what separates a useful report from a planning appendix. The consultant needs to work with the architect, planning lead, and viability team, because the findings can affect massing, demolition assumptions, façade retention, programme, and lender conditions. If the design team is still being assembled, it helps to understand role boundaries early. Hutter Architects on architect types gives a simple breakdown of who typically leads what.
Bring the consultant in at the same point you test planning policy, access, title constraints, and abnormal costs. Heritage is not a report to bolt on once the drawings look presentable. It is part of deciding whether the scheme you want to buy, fund, or promote is the scheme that can get consent.
Late instruction creates familiar problems:
On funded deals, I treat the HIA as part of risk underwriting. If heritage findings could reduce floorspace, alter phasing, or trigger more negotiation with the local authority, that needs to be visible in the appraisal and explained in lending papers before it becomes a problem.
Budget in proportion to the decision the report needs to support.
A short heritage statement for a modest proposal may cost hundreds rather than thousands. The Planning Portal's guidance on when a heritage statement is needed is a useful starting point for understanding where a lighter document may be appropriate. A full HIA for a more sensitive or higher value scheme will cost more because it requires detailed assessment of significance, setting, impact, and mitigation, often with several rounds of design input.
The wrong question is “what is the cheapest report we can buy?” The right question is “what level of analysis will stop us from underwriting the wrong scheme?”
A cheap report is expensive when it arrives too late to influence design, fails to answer officer concerns, or leaves the lender uncertain about planning risk. On marginal deals, that uncertainty can do more damage than the consultant fee ever will.
Before appointing, ask four questions:
If the answer to the last two questions is yes, scope the HIA as a commercial risk document as well as a planning one. That usually means paying for enough analysis at the front end to protect design time, programme certainty, and deal viability later.
Most failed HIAs don't fail because the site is impossible. They fail because the assessment is narrow, late, or too generic to support a real planning judgment.
A significant gap in HIA practice is the failure to quantify non visual impacts like noise, dust, and vibration, and their cumulative effect. UK planning guidance, including London's 2024 Practice Note, explicitly requires this assessment, yet many reports still lean on subjective visual description, as highlighted in London's heritage impact practice note.pdf).

This is the most common mistake on active urban sites. Teams focus on verified views and façade appearance but miss how servicing, activity, vibration, dust, or changed patterns of use may affect significance.
A practical example is a mixed use scheme next to a historic building where the architecture is restrained and visually acceptable, but the operational pattern introduces late deliveries, plant noise, or intensified rear yard activity. The setting can still be harmed even if the CGI looks polite.
Developers often say, “the setting is already compromised.” Sometimes that's true in part, but it doesn't create a free pass. Existing harm may not count as a positive precedent.
What works better is a disciplined argument. Identify what significance still survives, what contribution the setting still makes, and which parts of the proposal improve or erode that contribution. Subjective frustration isn't a planning strategy.
Previous poor development doesn't automatically lower the evidential burden for the next proposal.
Unverified visualisations can do real damage. If a proposal depends on careful townscape justification, your images need to be prepared and presented properly. Loose, flattering visuals may help an internal pitch, but they won't help once the authority starts testing the evidence.
For developer teams reviewing consultants, it also helps to understand who is best placed to lead different kinds of design response. This overview from Hutter Architects on architect types is a useful reminder that restoration and heritage sensitive work often need a different skill set from straightforward new build delivery.
“Use sympathetic materials” is not mitigation. “Reduce bulk where possible” is not mitigation either. A planner, lender, or committee member needs to know what will change in practice.
Use specific actions instead:
Even where harm is identified, the application still needs a coherent planning balance. Too many HIAs stop at “less than substantial harm” and leave the wider planning team to improvise the justification. That weakens the whole submission.
The strongest approach links the HIA to a wider planning statement, design and access material, and a realistic delivery story. If the scheme creates public benefit, articulate it clearly and consistently across the pack.
An HIA becomes commercially useful only when its findings are translated into decisions. A PDF sitting in the planning folder won't help the appraiser, credit team, or investment committee unless someone converts heritage conclusions into cost, programme, and underwriting signals.
The formal three stage process for HIAs, standardised by CIfA IEMA in 2021, was designed to provide a factual statement of change that supports early stage viability and finance modelling. By tracking constraints and compliance readiness, this structured approach helps reduce dead deals and allows property developers and capital operators to deploy capital with higher confidence, as described in Bassetlaw's HIA guidance summary.

Start with the practical consequences of the report, not the prose. If the HIA says the proposal causes less than substantial harm unless materials are upgraded, massing is reduced, and roof plant is screened, each of those points needs a place in the model.
A simple translation looks like this:
Include a short summary in the evidence pack. Keep it factual and auditable.
| Risk item | HIA finding | Commercial effect | Required action |
|---|---|---|---|
| Setting sensitivity | Proposal affects identified heritage setting | Potential redesign and planning negotiation | Test lower massing option |
| Material requirements | Standard palette may not be acceptable | Build cost pressure | Price alternative specification |
| Construction effects | Non visual impacts may require control measures | Programme and prelims pressure | Add management plan allowance |
| Policy balance | Harm requires clear justification | Greater planning risk | Strengthen public benefits case |
This format helps underwriters and internal committees understand what matters without reading the full report line by line.
Heritage risk should sit in the same decision log as abnormal costs, tenure assumptions, and finance terms.
The most reliable process is simple:
What doesn't work is leaving the HIA with the planning consultant while the rest of the team keeps appraising an outdated scheme. That disconnect is exactly how dead time and false confidence enter the deal.
The final test is whether the heritage workstream is decision ready. Use this checklist before acquisition, before submission, and before credit sign off.

A good HIA doesn't remove all risk. It makes the risk visible early enough for the team to decide whether to redesign, reprice, or walk away.
If you want to connect heritage constraints to viability, planning, and lender ready underwriting in one place, Domus gives UK development teams a structured workflow from site review through to investment decision. That means fewer disconnected spreadsheets, a clearer audit trail, and a stronger basis for deciding whether a heritage affected scheme still works.
From Domus
Domus gives UK developers a structured platform to run development appraisals, residual land value models, planning viability assessments, and cashflow — all in one place.
Domus