Capacity Planning for Architecture Studios: A Practical Guide

In a 15-person architecture studio managing 20 projects, workload allocation lives in one place: the principal's head. That works until it doesn't — and when it fails, it fails quietly. Your best designer is on six projects. Your junior architect hasn't had mentorship in months because their project architect is drowning. Nobody says anything until someone quits.

The invisible problem

Architecture has a unique capacity challenge. Unlike software teams where one person works on one project, architects routinely work across 3-5 projects simultaneously. A project architect might spend Monday and Tuesday on a CD set, Wednesday reviewing submittals for a project in CA, and Thursday-Friday on an SD presentation.

This makes workload invisible. Everyone looks busy. But "busy" and "productive" aren't the same thing. And "busy" and "sustainable" definitely aren't.

A simple framework

You don't need complex software to start. You need three things:

1. Know your capacity

Each person has a weekly capacity measured in available hours. For a full-time architect, that's roughly 36-38 billable hours per week (accounting for admin, meetings, and overhead). Part-time staff, interns, and consultants have different numbers.

Write these down. This is your supply.

2. Know your demand

Each project phase requires a certain number of hours per week from each role. A project in CD might need 20 hours/week from a project architect and 30 hours/week from a technical designer. A project in SD might need 15 hours/week from a designer and 5 hours/week from a principal for reviews.

Map this out per project, per phase. This is your demand.

3. Compare and adjust

When demand exceeds supply for any person, you have four options:

• - Delay: Push a project phase start date back
• - Redistribute: Move hours from one team member to another
• - Reduce scope: Negotiate fewer deliverables for the phase
• - Hire: Bring in contract help or hire

The key is seeing the conflict before it becomes a crisis. A heatmap view — showing each team member's utilization by week — makes overallocation obvious at a glance.

The 8-week window

Capacity planning isn't useful at the annual level (too vague) or the daily level (too granular). The sweet spot for architecture studios is an 8-week rolling window.

Eight weeks gives you enough horizon to:

• - See upcoming crunches before they hit
• - Coordinate phase transitions across projects
• - Make hiring decisions with enough lead time
• - Have honest conversations with clients about timeline impacts

Update it weekly. It takes 15 minutes once you have the system in place.

Common patterns to watch for

The hero pattern: One person is allocated to 120% every week. They deliver, but they're running on fumes. This is the #1 cause of burnout and quiet quitting in architecture studios.

The bottleneck pattern: A principal or senior designer is the reviewer on every project. Their review capacity becomes the constraint on the entire studio's throughput.

The feast-famine pattern: Three projects enter CD simultaneously. The team is crushed for 8 weeks, then underutilized for 4. Better pipeline management smooths this out.

The invisible junior pattern: Junior staff aren't allocated enough meaningful work. They sit idle or do busywork while seniors are overloaded with tasks that could be delegated.

Making it sustainable

Capacity planning isn't a one-time exercise. It's a weekly habit that takes 15 minutes and saves hours of firefighting. The goal isn't perfect utilization — it's sustainable utilization.

Target 75-85% allocation for each team member. The remaining 15-25% absorbs the unexpected — the RFI that takes all afternoon, the client meeting that runs long, the code review that surfaces a major issue.

Studios that plan capacity systematically report fewer overtime weeks, lower turnover, and — counterintuitively — higher revenue per employee. When people aren't burning out, they do better work, faster.