TL;DR: Resource planning for a UK architecture practice means working out who does what, across which projects, before you commit to a commission. Done well, it protects fee budgets per RIBA stage, catches variations before they’re written off, and gives Directors a view of margin while there’s still time to act. Most practices are running this on informal checks and spreadsheets. This post covers what makes architect resource planning different, where margin leaks when it goes wrong, and what a working system looks like.
Resource planning sits at the front of almost every margin problem an architecture practice faces. A 10 to 20-person practice typically manages around 80 live projects simultaneously, according to the RIBA Business Benchmarking Report 2025. Before a new commission is confirmed, the typical process is a Director glancing at the team and making a judgment call.
Nobody checks what’s left in the Stage 3 budget on the residential scheme due next month. Nobody flags that one of the four people you need is carrying three jobs already. The commission gets confirmed, and the planning happens afterwards.
Generic resource planning content will tell you to define the scope, allocate tasks, and review weekly. That advice isn’t wrong. It’s just written for teams running sequential projects with tidy task lists, not for a practice juggling 80 concurrent jobs across RIBA Stage 0 to 7, with sub-consultants to coordinate, fixed-fee proposals to protect, and variations that disappear before anyone invoices them.
This post covers what resource planning actually means in a practice context, why the standard approach doesn’t fit, and how the right system connects your resourcing decisions to the fee budget before the margin is gone.
What is resource planning for an architecture practice?
Resource planning for an architecture practice is the process of forecasting who is needed on which projects, when, and at what capacity, before a commission is confirmed rather than after it starts running over. It covers staff allocation across concurrent RIBA stages, sub-consultant coordination, and the connection between planned hours and the fee budget the proposal was built on.
That last part is what most generic definitions miss. In a practice context, resource planning isn’t just a scheduling exercise. The hours you plan connect directly to the fee proposal you’ve already sent. Plan them wrong and you’re not just over-stretched. You’re delivering work at a loss before the project has properly started.
How is resource planning different from capacity planning?
Capacity planning tells you how much work your team can absorb in total. Resource planning tells you who should do which part of it, and whether the hours match the fee budget per stage. You need both: capacity planning sets the ceiling, resource planning allocates what sits under it. A practice without a resource plan is running on capacity assumptions alone.
The post we published on capacity planning for architects covers the utilisation rate trap in detail: specifically, why planning against 7 or 8 billable hours per person per day is a fiction, and what the RIBA’s own data says about what Directors and Partners actually bill. If you haven’t read it, start there first.
Resource planning builds on that. Once you know the real available hours per person, the question becomes: who should be doing what, across which jobs, and at which RIBA stage? That’s the problem this post addresses.
Why generic resource planning advice doesn’t work for an architecture practice
Three things make architect resourcing structurally different from the step-by-step guides you’ll find anywhere else.
RIBA stages lock in fee budgets at the start. Most of your work is fixed-fee. That fee is allocated by stage: Stage 1 gets a certain percentage, Stage 4 gets another. When you allocate resources to a project, you’re not just assigning tasks. You’re committing hours against a budget that was set months ago. If your Stage 4 team is already running two other heavy stages concurrently, the fee budget for the new project won’t survive contact with reality.
Sub-consultants are resources you plan for but can’t directly schedule. Structural engineers, M&E consultants, landscape architects: they appear in your fee proposal as cost items, but they run their own diaries. Coordinating their input into a stage delivery requires resource planning that goes beyond your own team’s calendar. Most practices track sub-consultant time loosely, or not at all.
The volume is genuinely unusual. An average 10–20 person practice manages around 80 live projects simultaneously. That’s not a project pipeline. It’s a portfolio. Scheduling software designed for teams running five or ten concurrent projects doesn’t hold 80 jobs across seven RIBA stages without a system built for the purpose.
How poor resource planning becomes a fee recovery problem
When resources aren’t planned against fee budgets per RIBA stage, hours accumulate without being tracked against what was quoted. Variations get absorbed rather than flagged. Sub-consultant costs land late and get written off. By the time a project is near invoice, the gap between hours delivered and hours billed is already fixed. Resource planning is where fee recovery is won or lost, not at the invoice stage.
This is where WIP (work in progress) reporting matters. WIP is the value of work delivered but not yet invoiced. In a practice, the gap widens when variations get absorbed into the base contract rather than raised as additional services. The time gets logged. The additional fee never gets raised. The variation ends up as a write-off.
Research published in May 2026 found that the average UK professional services firm waits 105 days between completing work and receiving payment, and 76% track WIP manually or not at all. That gap is where margin quietly disappears.
In our latest implementation, a 12-person London practice recovered £17,500 of previously unbilled time in the first six months after go-live. In the twelve months that followed, £28,000 in scope changes was invoiced that would previously have been written off. Neither number came from billing harder. Both came from a system where the gap between hours delivered and hours billed was visible in real time, before the invoice stage.
Benchmarking data from professional services firms shows that 10% scope creep on a 60% margin project cuts that margin to 54%. On a fixed-fee commission, absorbing one change request without raising an additional service isn’t a rounding error.
What does a resource plan for a 6–25 person practice actually need?
Realistic available hours per person, per role. Not theoretical 7-hour days, but actual available hours after leave, CPD, business development, and non-project time. The Xero app stack guide for architects covers how practices typically structure their toolset, but the hours calculation has to come first.
A complete view of existing commitments before confirming a new project. This means knowing what stage every person is delivering, what remains in the fee budget for each job they’re on, and whether any of those jobs are over-running.
Sub-consultant time tracked alongside internal time. If sub-consultant costs live in an email thread and internal time lives in a spreadsheet, you don’t have a resource plan. You have two separate guesses.
A live connection between the resource plan and the fee proposal. When someone logs hours to a job, those hours should reduce the remaining stage budget in real time, not at month-end when the damage is done.
Research across professional services firms finds 44% use no dedicated scheduling software at all, with Google Sheets the most common tool at 28%. For a sole practitioner, a spreadsheet is manageable. For a practice of six or more running 50–80 concurrent jobs, a spreadsheet means maintaining three versions of the same information, and none of them are current.
How WorkflowMAX connects resource planning to project profitability
WorkflowMAX holds all four inputs in a single system. The capacity module gives a live view of each person’s available hours, built from their actual configured working week rather than a flat 7.5-hour assumption. The job structure maps existing commitments: every live job, every stage budget, every remaining hour. Sub-consultants are tracked as cost items tied to the job, not as a separate process.
The connection that makes this genuinely useful is the link between the resource plan and WIP. When a team member logs time, those hours reduce the stage budget in real time. Directors see a live margin view per job. When a project goes over fee, an automated alert fires before the stage closes. That’s the window for a conversation about variations and additional services, while it’s still worth having.
This is also why getting the implementation right matters. The system’s value depends on the configuration: how jobs are structured, how stages are set up, and how sub-consultant costs are tracked. A misconfigured WFM installation produces the same margin blind spots as a spreadsheet, just with more steps. We spend the first week of every implementation mapping the practice’s actual workflow before touching the platform. That four-week process is what turns a capable system into one that works specifically for your practice.
Fix the front end, not the invoice
Resource planning and fee recovery are the same problem, approached from opposite ends. Plan resources well and you know, before a commission starts, whether the fee budget is realistic. If something slips, you see it while there’s still time to raise an additional service rather than writing it off at month-end.
Most practices fix the right-hand end: chasing time logs, running WIP reports, catching write-offs. The more durable fix is the left-hand end: a resource plan connected to the fee proposal before the project starts.
If you’d like to see how WorkflowMAX is configured for a practice your size, book a 30-minute discovery call. Or if you want to assess fit before committing to an implementation, the App Fit Sprint is the right starting point.
