Most architecture firms plan capacity by feel. The principal has a rough sense of who is busy, staffing decisions get made in the hallway, and the first real signal that someone is overloaded is when a deadline slips or a good architect burns out. Capacity and resource planning for architecture firms does not have to be a heavyweight discipline with complicated software, but it does need to be more deliberate than gut feel, because the cost of getting it wrong is missed deadlines on one side and idle, unbillable time on the other.
The goal is simple: know who has room and who is stretched, staff projects against reality, and see a crunch coming before it arrives. This piece lays out a practical way to get there without turning your studio into a spreadsheet factory.
What capacity planning really means in a studio
Capacity planning is just matching the work you have committed to against the people available to do it, across time. In architecture it is complicated by phases that demand different intensities of effort, consultant coordination that comes in bursts, and the reality that your people are not interchangeable. A junior cannot pick up a principal's redlines. So capacity is not one number, it is a picture of who can do what, and when.
Start by making current load visible
You cannot plan capacity you cannot see. Before any forecasting, the studio needs a clear view of what each person is actually working on right now. This is where a shared board and a team queue earn their keep: when every task has an owner and a visible status, you can look across the studio and see who is carrying five active tasks and who is carrying one. That picture alone catches most overloads before they become problems.
- See how many active tasks each person owns across all projects
- Spot who is blocked and therefore idle even though they look busy
- Notice when one project is quietly consuming one person entirely
- Catch the person who never says no and is silently drowning
Use real time data, not assumptions
Feel is a poor guide to how long work actually takes. The phases you chronically underestimate, the project types that demand more coordination than you budgeted, these only become visible when you have honest time data to look at. You do not need minute-by-minute precision. Rough, honest hours logged against tasks and phases are enough to reveal the patterns, and those patterns are what let you staff the next project realistically instead of optimistically.
The firms that plan capacity well are simply the ones that replaced I think he is busy with I can see he is busy.
Plan around phases and their peaks
Effort is not evenly spread across a project. Construction documents is heavy and sustained. Design development spikes when consultant coordination lands. Construction administration is spiky and reactive. If you plan as though a project consumes a steady amount of someone every week, you will be wrong in both directions. Mapping the phase peaks across your active projects shows you where two crunches are about to collide, which is exactly the collision you want to see coming a month out, not the week it hits.
Separate presence from project time
There is a difference between how long someone was at work and how much of that went to billable project work. A day clock-in and clock-out captures presence and overall load. Per-task time captures where the project hours actually went. Keeping these separate gives you two honest numbers instead of one confused one, and it protects your people, because the point of tracking is to balance load, never to police individuals.
Turn the picture into decisions
Capacity data is only worth collecting if it changes what you do. When the board shows someone overloaded, you rebalance the queue. When time data shows a project type consistently running over, that is a scoping and fee conversation for the next one. When two phase peaks are about to collide, you either move a deadline, bring in help, or set expectations early. The planning is not the point; the decisions it enables are.
Keep it light or it will not last
Elaborate resource-planning systems tend to collapse under their own weight in a studio, because nobody has time to feed them. The version that survives is lightweight: a visible board, honest time data collected with almost no friction, and a short weekly look at who is stretched. That is enough to run a firm far better than gut feel, and it is sustainable because it rides on the work people are already doing.
Planning capacity with Spreadbox
Spreadbox gives you the raw material for real capacity planning without extra overhead. Kanban task boards and a team queue make each person's current load visible at a glance, so overloads and idle blocked time surface on their own. Per-task time tracking and a separate day clock-in and clock-out give you honest hours for both project work and presence, without conflating the two. Project status tracking lets you see how phase peaks line up across your active projects, and Spreadie, the built-in AI assistant, can summarize where the studio's time is going from what has been logged. Because all of it rides on the work your team is already doing on the board, planning capacity stays light enough to actually keep up.