How Long Does a Planning Appeal Take? Get 2026 UK Timelines
By Domus
By Domus
You open the refusal notice, skim the reason for refusal, then jump straight to the programme and funding tabs in your appraisal. That is the moment the appeal process starts.
The planning issue matters, of course. But the first commercial question is usually simpler. How long does a planning appeal take, and what does that delay do to the deal?
For a developer, an appeal isn’t just a planning event. It affects land value, debt drawdown timing, contractor procurement, option exercise dates, professional team costs and the credibility of your programme with equity partners. For a lender, it changes underwriting risk. A scheme that still works with a controlled delay can stay alive. A scheme that only works if everything lands on the original programme often falls apart fast.
I’ve seen this become the dividing line between projects that recover and projects that drift. The teams that cope well don’t treat an appeal as an administrative nuisance. They treat it as a live risk item with a cost, a timetable range and a decision tree. The teams that struggle usually do the opposite. They plug in a hopeful date, assume the appeal clock runs cleanly, and only revisit the numbers when legal, finance and delivery pressure has already built up.
That’s why generic answers rarely help. The official timetable gives you a starting point. It doesn’t tell you what the delay means for your specific land position, your capital stack or your fallback options.
A refusal often lands after months of design work, consultant input and negotiation with the case officer. By the time it arrives, the cost isn’t theoretical. You’ve already spent money, tied up management time and probably built expectations into a board paper or funding conversation.
The immediate mistake is to ask only whether you can win on appeal. The better question is whether an appeal is the best commercial route from this point.
A capable team usually does four things quickly.
First, isolate the refusal reasons. Some refusals are appealable on strong planning grounds. Others are really telling you that a revised application may be faster and cheaper.
Second, check the procedural clock. Appeals must be lodged within 6 months of the local planning authority decision or due date, according to the UK Planning Inspectorate guidance on appeals average timescales for arranging inquiries and hearings.
Third, rebuild the programme. Not the old one with an appeal inserted. A fresh one.
Fourth, assess funding impact. If your debt or equity assumptions depend on a narrow start date, delay can become the bigger problem than the refusal itself.
Commercial test: If the scheme only works on the original timetable, the refusal has exposed a viability weakness, not created one.
The appeal itself is only one part of the delay. There’s also the pre appeal period while your team assembles the case, updates evidence, aligns consultants and decides on the best route. That time is easy to ignore because it sits outside the formal Planning Inspectorate process. It still costs money.
A straightforward example makes the point. A developer buys subject to planning, gets refused, then assumes an appeal adds time before consent. In reality, the delay can affect option expiry risk, interest carry, consultant re appointments, landowner expectations and contractor pricing assumptions. If the project already had a thin margin, the refusal can move it from awkward to non bankable.
For land buyers and promoters, this is often the point to compare appeal against disposal, redesign or a tactical re submission. Teams dealing with a refused site can use a more structured refusal triage process through resources such as refusal to land, but the key principle is broader. Don’t let the emotional instinct to “fight the refusal” replace a commercial review.
When clients ask how long does a planning appeal take, they’re rarely asking for a neat published median. They’re asking something more practical.
Can we hold this site long enough?
Can we keep funders onside?
Will the delay still leave enough margin to justify staying in?
Those are the right questions. The published timescale is only the beginning.
Procedure is not an admin detail. It affects how much you spend, how long your capital is tied up, how much management time the case absorbs, and how comfortable a lender will be with the programme you are showing them.
A client may want the fastest route. The better question is whether the case can credibly stay on that route once the Inspector reviews the issues. If the answer is no, a cheap early assumption usually turns into a more expensive correction later.

| Procedure | Median Timescale (s78) | Best For | Key Consideration |
|---|---|---|---|
| Written representations | 16 weeks | Straightforward planning disputes where written evidence can do the work | Fastest mainstream route, but weak documents are exposed quickly |
| Hearings | 22 weeks | Cases needing discussion and clarification in front of an Inspector | More interactive, but still requires disciplined written preparation |
| Inquiries | 31 weeks | Complex, contested or high impact cases with technical evidence and adversarial scrutiny | Most formal route. Team, evidence and advocacy quality matter heavily |
Recent Planning Inspectorate reporting shows a clear hierarchy. Written representations are usually quickest, hearings sit in the middle, and inquiries take longest. Householder appeals tend to move faster than general section 78 appeals. Inquiry times have also improved against older historic averages, as noted earlier.
That is useful baseline information. The commercial point is simpler. Each step up in procedure usually means higher consultant fees, more internal decision making, and a greater risk that your original appraisal assumptions stop matching the case you are running.
Written representations are the standard route for a large share of planning appeals.
They suit cases where the planning merits can be established on paper through policy analysis, drawings, technical work and a well structured planning statement. If the dispute is really about whether the authority has applied policy too narrowly, or whether your evidence is stronger on design, heritage, highways or character, written reps can be efficient.
Efficiency depends on the quality of the file.
Developers sometimes treat written reps as the budget option and strip out work too early. That is usually false economy. A weak planning statement, inconsistent drawings, or a technical report drafted for application stage rather than appeal stage can sink the case without anyone getting the chance to explain away the gaps in person.
Written reps usually make sense where:
From a cost-control perspective, written reps are attractive because they can reduce attendance time, advocacy costs and the number of consultants who need to stay engaged through the whole appeal. But they only save money if the material is right first time.
Hearings sit between paper appeals and full inquiry procedure. The Inspector leads a structured discussion. The parties answer questions directly. The process is less formal than an inquiry, but it still rewards disciplined preparation.
This route often works well where the core facts are not heavily disputed, but planning judgment needs to be tested in real time. Mixed issues can also suit a hearing. A scheme may be broadly acceptable in principle, with debate focused on effect, weight and balance rather than a long list of factual disputes.
Commercially, hearings can be awkward to price if the team has not thought through roles in advance. The planning lead needs to know the file thoroughly. Technical advisers need to attend only if they add value. Clients need to resist the urge to turn up with a crowd. More people in the room rarely improves the case, but it often increases cost and dilutes message discipline.
I usually advise clients to treat a hearing as a targeted exercise. Decide who answers which point. Decide which issues matter to the decision. Keep the team lean.
An inquiry is a different level of commitment.
If the scheme faces substantial policy conflict, organised opposition, multiple technical disciplines, or factual disputes that need cross-examination, inquiry procedure becomes more likely. That changes the risk profile of the appeal, not just the timetable.
At inquiry stage, three things tend to happen at once. Evidence that was acceptable for application purposes often needs to be rewritten or expanded. Advocacy matters much more because witnesses are being tested, not just read. Internal client decisions start coming faster, because concessions, rebuttal points and tactical choices cannot always wait for the next weekly call.
That has a direct budget effect. Counsel fees, expert witness time, proofing sessions, statement drafting and internal management time can all rise sharply. If debt is already running, the carrying cost of a longer programme sits on top of the professional fees. For a marginal deal, that can be the point where appeal is still planningly arguable but commercially hard to justify.
You do not choose procedure in isolation, but you do control how realistically you assess the likely route at the start.
If a case has obvious inquiry characteristics, model it that way. If there is a reasonable prospect of written reps but the authority is likely to push for oral examination, carry both scenarios in the appraisal. If a hearing looks realistic, budget for the right specialists rather than assuming the planner can cover every technical issue alone.
The practical difference between the three routes is not just speed. It is exposure.
Written reps expose the quality of the documents. Hearings expose the quality of the explanation. Inquiries expose the quality of the whole case, including evidence, witnesses, advocacy and client decision making.
That is why route selection matters so much to developers and lenders. It is an early warning sign for cost, programme risk and the amount of contingency the deal needs.
Official medians are useful. They aren’t a project programme.
A developer who relies on a national figure alone is usually missing the variable that matters most in real life. Where the appeal sits, how the case behaves, and how well the file has been assembled.

This is the part many appraisals miss.
LandTech analysis shows appeals from councils such as Liverpool and Newcastle average 37 weeks, while faster authorities can achieve 19 to 20 weeks. That location specific difference can add up to 11 extra weeks against the national mean, according to LandTech’s analysis of what makes a planning appeal take longer.
That’s not a rounding error. For a live development deal, that can alter land strategy, debt assumptions and investor patience.
A national answer to how long does a planning appeal take may be directionally helpful. It is not enough for site specific risk management. If one authority tends to move more slowly, your holding period shifts. So does your comfort on contingency.
A case becomes slower when it requires more interpretation, more evidence and more challenge. That can happen even on a modestly sized scheme.
A refusal tied to a single narrow issue may still move relatively cleanly if the evidence is already in place. A refusal tied to design, heritage, highways and policy conflict at once is harder to run, even before anyone says the word inquiry.
Multiple refusal reasons that overlap. These cases often create duplicated work across consultants.
Late emerging technical issues. If a key report still needs major revision, your appeal preparation period stretches before submission.
Contentious local context. Strong third party pressure doesn’t automatically change the planning merits, but it can make the process heavier and more demanding.
A weak application history. If the original submission was inconsistent, the appeal team spends time repairing the record instead of advancing the case.
Teams sometimes talk about delay as though it arrives from outside. In practice, appellants often contribute to it.
A planning statement that doesn’t answer the refusal reasons directly, a design case that still reads like an application document, or technical notes that don’t align with the drawings all make an appeal harder to run. Even if the Inspectorate timetable remains intact, your own side creates friction.
What usually works: a smaller set of documents that answer the refusal squarely, with each consultant working to the same planning narrative.
What doesn’t work is flooding the file with material that hasn’t been edited into a coherent case. More paper isn’t the same as better evidence.
Lenders often receive a headline appeal assumption in a monitoring report or revised appraisal. If that assumption is based only on national medians, the underwriting view may be too optimistic.
A site in a slower authority with a messy technical record isn’t carrying generic appeal risk. It is carrying specific appeal risk. Credit teams should want to know whether the programme reflects local variation, whether the refusal reasons are tightly defined, and whether the evidence set is appeal ready.
That is where project reviews improve. Instead of asking, “What is the average appeal timeline?”, ask:
| Better question | Why it matters |
|---|---|
| Which authority is involved and what is its pattern? | Local variation can materially alter programme risk |
| How many live technical disciplines are in dispute? | More moving parts usually mean more management and slower progress |
| Is the appeal file being rebuilt or simply recycled from the application? | Recycled material often leaves weaknesses untouched |
The published timetable is the outer frame. Your authority, your evidence quality and your case complexity fill in the picture. That’s why two appeals that look similar on a spreadsheet can behave very differently in practice.
The right way to handle appeal risk in an appraisal is not to guess a single date and move on. Build a range, assign consequences to each scenario, and understand what breaks first.
That sounds obvious. Many teams still don’t do it.
They update the planning line, leave the finance logic largely untouched, and assume the rest of the model will absorb the delay. It won’t. Timing changes ripple through the whole scheme.

When a refusal lands, I’d usually want to see three programme cases built into the appraisal.
Base appeal case. Your most realistic assumption based on procedure, authority context and current evidence quality.
Slower case. A case that captures additional delay from procedural complexity, consultant rework or authority drag.
Fallback case. A scenario where appeal is abandoned or overtaken by redesign, disposal or a new application route.
Good systems are essential here. If you’re still reworking versions across disconnected spreadsheets, scenario control gets messy fast. Teams that want a more auditable setup often look at tools built for development modelling, such as development appraisal software, because the issue isn’t only calculation. It’s governance around assumptions.
An appeal delay doesn’t just push start on site. It can affect several lines at once.
Finance costs. Interest carry extends if debt is live, and commitment assumptions may need to change if funding documents were built around an earlier planning milestone.
Professional fees. Planning consultants, solicitors, technical advisers and counsel may all stay engaged for longer or return to update evidence.
Land holding costs. Option, promotion, overhead or ownership costs continue while the site remains undelivered.
Procurement timing. If contractor engagement shifts, tender assumptions may no longer line up with the original delivery plan.
Sales and revenue phasing. The development may still work, but the cash profile changes, which affects covenant comfort and equity recycling.
Take a medium sized residential scheme. The original appraisal assumed a smooth route from decision to implementation. The refusal arrives. The team now faces an appeal and the likely delay extends the pre commencement period by several months.
In a weak model, the planner updates one date and the scheme still appears bankable.
In a detailed model, the team tests what happens if:
That second model gives management something useful. It shows where the sensitivity sits.
If the scheme only survives on a single optimistic appeal assumption, that is not a timing issue. It is a structural risk in the deal.
A better appraisal treats an appeal as a sequence of decisions, not a block of waiting time.
For example:
| Decision point | Appraisal question |
|---|---|
| Refusal received | Is appeal still the highest value route versus redesign or exit? |
| Appeal preparation begins | Do updated professional costs still support the original land basis? |
| Procedure becomes clearer | Does likely route change holding risk or funding conditions? |
| Mid process review | If delay increases, do we keep funding the same scheme? |
Management teams rarely fail through lack of arithmetic. They fail because they don’t revisit the commercial decision at the right moments.
A lender doesn’t need a heroic planning narrative. It needs evidence that the borrower understands the impact of delay and has modelled it.
The strongest borrower updates I see usually include:
A revised programme with a range. Not one fixed appeal end date presented as certainty.
A note on route and evidence status. Is the case likely to remain document led, or is it becoming more formal and more resource intensive?
Revised cashflow logic. The lender wants to know when cash is required, not just when planning may arrive.
Clear trigger points for re approval. If the appeal moves outside the expected range, what gets reviewed and by whom?
Some bad habits are repeated often enough to be worth naming.
Don’t bury the delay in contingency. Contingency is not a substitute for programme risk analysis.
Don’t use a national median as your sole assumption. As covered earlier, that can miss local and case specific drag.
Don’t leave equity timing untouched. Investors care about duration as much as headline return.
Don’t present “appeal pending” as a neutral status. It is an active commercial condition with cost attached.
If you’re presenting a refused site to a board, investment committee or credit team, the appeal section should answer three questions cleanly.
What is the likely route?
What is the likely timetable range?
What happens to value and cash if the slower case materialises?
If those answers are weak, the planning strategy probably is too. A good appraisal doesn’t eliminate uncertainty. It makes uncertainty visible early enough for someone to act on it.
An appeal can’t be rushed into being good. But it can be made slower by poor preparation, inconsistent documents and loose case management.
The teams that protect timetable best are not always the ones with the strongest refusal facts at the start. They’re often the ones that organise the case properly and stop self inflicted delay.

This sounds basic. It is still where many files go wrong.
Your appeal documents should answer the decision notice directly. Not loosely. Not by repeating the application narrative. Directly.
If the refusal is about design and heritage, don’t let highways material dominate the file because it already exists. If the authority’s issue is policy conflict, your planning case must confront that conflict clearly rather than circling around it.
One lead planning narrative. Every supporting report should reinforce the same core case.
Updated technical evidence where needed. If a report is stale or poorly aligned to the scheme, repair it before submission.
Clean drawing control. Nothing wastes time faster than teams arguing over superseded plans.
Appeals often trigger scope creep. More advisers join, more commentary appears, and no one fully owns the final case.
That rarely helps.
A tighter structure usually works better:
| Role | What they need to own |
|---|---|
| Planning lead | Overall strategy, refusal response, procedural discipline |
| Technical leads | Only the live issues that genuinely affect the appeal |
| Solicitor or counsel where needed | Legal framing, advocacy support, document discipline |
| Client lead | Commercial decisions, approvals, and funding communication |
The best appeal teams don’t produce the most paper. They produce the clearest case.
Many delays begin before validation because the file isn’t in good enough shape. Others arise later because the appellant tries to fix weaknesses mid process.
That is expensive and avoidable.
A disciplined pre submission review should check:
Consistency across documents. Planning statement, drawings and technical notes must all describe the same proposal.
Plain answers to the refusal. If the Inspector has to infer your argument, the case is already weaker than it should be.
Site visit readiness. Access, visibility and on site context should support the written case rather than surprise the Inspector.
Some of these are procedural. Most are managerial.
Late evidence changes
If a key point appears for the first time late in the process, everyone else may need time to respond.
Trying to re run the application
An appeal is not a second application wrapped in new stationery.
Weak internal approvals
If the client team cannot sign off instructions quickly, consultant progress stalls.
Poor communication with stakeholders
You don’t need performative engagement, but you do need clarity among the people funding and managing the site.
If your wider team needs a refresher on the planning path before refusal and appeal issues arise, a practical background resource such as this planning permission guide can help anchor internal discussions. On the appeal itself, though, the core point is simpler. Keep the process focused and don’t create avoidable moving parts.
A sensible appeal manager reviews timetable assumptions throughout the process. Not every week for the sake of it. But often enough to catch slippage early.
That review should include planning and commercial inputs together. If the planning lead sees a complication, finance needs to know. If lenders need an updated range, they should hear it before a formal covenant conversation becomes necessary.
Good appeal management is not passive waiting. It is active coordination between planning, technical, legal and finance teams.
What works
Sharp issue definition. Narrow the case to the points that matter.
Evidence discipline. Submit fewer, stronger documents rather than a pile of half integrated material.
Fast client decisions. Delay inside your own team still counts as delay.
Commercial oversight. Keep the appraisal and funding narrative current while the appeal runs.
What doesn’t
Emotional escalation. Anger at a refusal often produces expansive arguments that weaken the case.
Consultant duplication. Two advisers saying similar things rarely doubles persuasiveness.
Optimistic silence with lenders. A delayed conversation is usually a harder conversation.
A planning appeal takes time. Your job is to make sure none of that time is wasted by your own side.
A refusal creates pressure because it attacks certainty. Programme certainty. Value certainty. Funding certainty.
That pressure is exactly why an appeal needs to be managed as a business risk, not parked as a planning issue while the rest of the project carries on.
The developers and lenders who handle this well do three things consistently. They use realistic route assumptions. They model timing as a range rather than a promise. And they keep planning, finance and decision making connected throughout the process.
That is the full answer to how long a planning appeal takes. It takes as long as the formal process requires, plus whatever extra risk your authority context, case complexity and internal discipline add to it. You won’t control every external factor. You do control whether the scheme is prepared for them.
The strongest schemes are rarely the ones with no planning friction. They are the ones where the team spotted the risk early, priced it properly and kept optionality alive.
If the refusal has already arrived, the job now is not to wait optimistically. It is to decide clearly. Appeal, revise, hold, refinance, or exit. Then model that decision.
That mindset usually improves outcomes well beyond appeals. Better planning intelligence at the front end, tighter appraisals and cleaner governance reduce the number of surprises that become expensive later. In development, speed helps. But informed timing is what protects value.
Domus helps UK property teams connect planning, viability and finance in one workflow, so appeal risk, programme changes and funding implications can be assessed against a shared project baseline instead of scattered spreadsheets and email chains. If you want a better way to stress test refused sites, model delays and present clearer evidence to investment and credit teams, explore Domus.
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