Fee Scales vs Client Expectations: Why the Gap Keeps Growing.
Clients now expect renders, walkthroughs and polished boards before planning is even submitted. Most fee scales were never built to cover that work.
What clients expect before planning has quietly changed
Ten years ago, a planning application meant a site plan, a set of elevations and a written statement nobody outside the office read closely. That baseline has moved. Clients now arrive at a first meeting having seen a competitor's marketing render, a developer's flythrough on Instagram, or a neighbour's scheme presented as a polished street scene. They assume that level of visual output is standard, not an upgrade they need to pay extra for.
This shift has a mechanism behind it. Planning committees and objecting neighbours respond differently to a rendered street scene than they do to a line elevation. A rendering shows how a proposed extension sits against the brick of the terrace next door; an elevation drawing asks the viewer to imagine it. Agents and applicants have noticed this, which means visuals now get pushed earlier in the process, as a persuasion tool aimed at planning officers and consultees, not just a presentation nicety for the client's benefit.
The change happened slowly enough that fee proposals haven't caught up. Most practices still describe pre-planning work in RIBA Stage 2 and Stage 3 language, drawings, coordination, design development, while the deliverable clients actually expect has drifted towards Stage 4-grade visual output: photoreal exteriors, sometimes a short film, delivered before a single application form has been submitted.
The deliverable moved two stages forward. The fee proposal didn't move at all.
Where the standard fee scale still assumes 2005-era deliverables
Percentage-of-construction-cost fee scales, and most bespoke stage-fee tables built from them, price "planning drawings" as measured drawings plus a written Design and Access Statement. That's the deliverable the fee structure was built to cover. It doesn't name a rendered image set, because when those scales were last meaningfully revised, rendering meant outsourcing to a specialist visualiser with a week's turnaround.
The Design Council's guidance on Design and Access Statements calls for "accurate and informative illustrations", diagrams and artists' impressions based on the application drawings, but stops well short of requiring photoreal renders. Highland Council's design statement guidance goes slightly further, mentioning high-quality illustrations and "possibly 3D models". Local authority templates from boroughs like Kensington & Chelsea encourage photographs and contextual diagrams to help officers and the public follow the design reasoning. None of this is a statutory requirement for rendered visuals. It's guidance that has quietly normalised a richer visual set, even while no fee scale anywhere names it as a line item.
The result: what used to be six pages of policy text and a site plan is now expected to carry contextual visuals, massing studies, and for larger schemes, a short narrative film. The document has grown. The fee attached to it hasn't.
Visualisation was historically treated as an optional add-on, quoted separately from the core fee and the first thing cut when a client pushed back on cost. That made sense when it was a genuinely separate scope with its own supplier and its own invoice. It makes much less sense now that a rendered image set is often the thing that gets the application past committee, and yet it's still the first line struck through in a fee negotiation.
Small practices absorb the gap by doing the extra visual work unpaid, treating it as the cost of winning the job rather than a scope that should be billed on its own terms.
The hidden cost: hours spent that were never priced in
A single external render used to mean commissioning a specialist visualiser: a brief, a week's turnaround, a fee that arrived as its own invoice line. That cost structure justified charging it separately in the proposal, because it genuinely was a separate cost.
That justification has eroded. When a full set of camera angles for a scheme, exterior and interior handled separately, can be produced in-house inside a single working session using a tool like Shoot rather than commissioned out, practices stop treating it as a discrete cost centre. It gets folded into "general fee" instead, and margin erodes on every job that includes it, because the labour is real even when the invoice line has disappeared.
Client expectations compound the problem. Once one client receives a free walkthrough because a junior in the practice generated it in an afternoon and nobody billed for it, the next client expects the same as standard. The fee scale never catches up, because nobody in the practice sat down and rewrote the proposal template to reflect what's now routinely included.
This is worth stating plainly: it's a pricing problem, not a tooling problem. The tools got faster. The fee proposal didn't get rewritten to reflect what's now bundled inside it. Those are two separate failures, and only one of them is fixable with software.
| Deliverable | 2015 assumption | 2026 reality |
|---|---|---|
| Exterior render | Outsourced, 1 week turnaround, separate invoice | Produced in-house in an afternoon, often unbilled |
| DAS visuals | Site plan and elevation extracts | Contextual stills, massing studies, sometimes a short film |
| Client walkthrough | Premium add-on, quoted separately | Increasingly expected as standard inclusion |
What a realistic pre-planning scope actually contains in 2026
A believable pre-planning package in 2026 tends to contain a consistent set of parts: two or three exterior stills showing the scheme from likely public viewpoints, one interior key view where the interior matters to the application, a site-context image placing the scheme against its neighbours, and a short DAS narrative built around those images rather than written first and illustrated as an afterthought.
Generating that full set of camera angles, exterior and interior handled separately, is now achievable inside a single working session rather than a commissioned week, using a tool like Shoot. That changes the underlying economics of quoting for it. It doesn't remove the professional judgement involved in choosing which views actually support the planning argument, but it does mean the practice controls the schedule instead of waiting on an external visualiser's queue.
Assembling the Design and Access Statement itself no longer needs a graphic designer or a separate InDesign job pulled in specifically for the document. Layout's dedicated Design and Access Statement template starts with placeholder text and image frames already structured to the document, so the visuals produced for the application slot directly into a layout built for that purpose rather than being dropped into a generic Word document.
None of this eliminates the labour. It just moves where the hours sit, from a third-party supplier's invoice to an afternoon inside the practice. That's precisely why the fee proposal needs to name the deliverable explicitly. Burying it inside "planning application preparation" hides the hours from the client and from the practice's own margin tracking.
Moving the labour in-house doesn't make it free. It just makes it invisible on the invoice unless someone deliberately names it.
How to rebuild a fee proposal that reflects the real workload
Start by separating "planning drawings" and "planning visuals" as distinct line items in the fee letter, even when both are delivered from the same underlying 3D model. The client should see the visual work named and valued as its own scope, not absorbed silently into a single lump sum for "planning stage fees". Naming it is what makes it negotiable rather than assumed.
Quote pre-planning visualisation as a fixed scope: a defined number of views, one round of revisions, a clear cut-off. An open-ended "renders as required" clause invites scope creep from a client who, having seen how quickly the first image came back, assumes a second, third and fourth view cost nothing extra to request.
Treat the speed of in-house tools as a margin opportunity rather than a reason to discount. Charging the market rate for a render set that now takes an afternoon rather than a week is not overcharging. The client isn't paying for the hours; they're paying for a rendered street scene that helps get their application through committee. That value hasn't changed just because production got faster.
Build a simple internal benchmark to underpin this rather than guessing at renegotiation time. Track how many credits and hours a typical pre-planning visual set actually costs to produce, exterior stills, an interior view, a context image, then price the line item against that figure. A practice running Shoot for the image set and Layout for the DAS build can log both time and credit spend per project and use that history to quote the next one with confidence rather than a rough estimate pulled from memory.
The tools got faster. Nobody rewrote the fee proposal to reflect what's now included.
Where this is heading for practice fee structures
As visualisation becomes cheaper to produce, the market won't tolerate practices billing it at old day-rate assumptions built around a week's outsourced turnaround. But it also won't tolerate practices giving it away for free indefinitely, because the labour, the judgement about which views to show, and the risk of getting the DAS narrative wrong all remain real costs that someone has to absorb.
Fee scales built around RIBA Plan of Work stages will need a visible sub-line for visual communication, distinct from technical drawing, because clients increasingly judge a practice on both separately. A practice that produces excellent technical drawings but a weak, generic image set will lose the comparison to a competitor who treats the two as equally deliberate outputs.
Small practices that name and price this work properly will out-compete those still folding it into an undifferentiated lump sum, because clients increasingly ask for it itemised anyway. When a client can see "planning drawings: £X" and "planning visuals: £Y" as separate figures, they can make an informed decision about what they're buying rather than assuming the render was thrown in for free.
The practices adapting fastest are the ones treating visualisation output as a competitive differentiator worth charging for, not a cost centre to minimise or hide. That's a pricing decision, not a software decision, but it's a decision that gets much easier to make once the actual hours and credits behind the work are tracked rather than guessed at.
Name the deliverable, fix the scope, price it against real data. That's the whole fix, and none of it requires waiting for RIBA to update the Plan of Work.
The takeaway: the gap between fee scales and client expectations won't close on its own, because nobody updates a fee scale by accident. Practices that itemise planning visuals as their own line, benchmark the real hours and credits behind them, and quote a fixed scope instead of an open-ended promise will price the work correctly. Everyone else will keep absorbing it as the quiet cost of winning the job.
Keep reading.
Try ArchAdemia Tools for yourself
Draw it, model it, render it, publish it. One place, built for architects and small practices. Plans from £29 a month, all in.