When Staffing and Budgets Don't Talk: A Cautionary Case Study

This case study is a fictional illustration. "Meridian Studio" is not a real firm, and every number in the story is invented to make the mechanics concrete — but the failure pattern it depicts, staffing plans and project budgets living in disconnected systems, is among the most common operational problems in project-based firms. If parts of this story feel uncomfortably familiar, that's the point.

The firm

Meridian Studio is a 35-person architecture firm with a healthy portfolio: two institutional projects in construction documents, a mixed-use development in design development, a handful of smaller renovations, and a steady stream of feasibility studies. Utilization is high. Everyone is busy. By every visible measure, the firm is thriving.

Meridian plans staffing the way many firms its size do: a weekly resourcing meeting and a shared spreadsheet — people down the side, projects across the top. Separately, the finance lead tracks each project's fee budget in the accounting system, broken down by phase the way the contracts are written: schematic design, design development, construction documents, construction administration.

Note the word separately. The staffing plan counts hours. The budgets count dollars. Nothing connects them.

The slow leak

In March, the mixed-use project hits a rough patch in design development. The client keeps revising the program; the design team keeps absorbing the revisions. The project architect, doing exactly what good project architects do, pulls in help — a few extra hours from one designer, then a second designer for "a week or two," then most of an intern's time.

Every one of those staffing decisions is reasonable. Every one is made in the staffing meeting, looking at the staffing spreadsheet, which answers the only question it can answer: who has hours available? The intern does. Done.

Here's what nobody in that meeting can see: the DD phase budget for the mixed-use project was scoped at roughly 1,400 hours of effort. By late March, the team has burned about 1,250 of them — with the phase maybe 60% complete. At the firm's average billing cost, the extra staffing is consuming roughly $18,000 of fee per month beyond plan. The phase budget will be fully consumed five weeks before the phase is done.

Nobody is hiding this. Nobody is being careless. The information simply lives in two systems that are never in the same room.

The discovery

In mid-May, the finance lead closes the quarter and runs the project profitability report. The mixed-use project's design development phase comes in at 138% of budgeted labor — the overage is roughly $45,000, all of it already spent. The firm's options at this point are all bad:

Request additional fee. The client relationship is good, but the program revisions were absorbed without contemporaneous documentation or a timely additional-services conversation. Asking for money two months after the fact, with no paper trail, goes about as well as you'd expect: a partial concession, and goodwill spent.
Eat the overage. The remaining phases now have to carry the loss. The CD phase budget gets quietly squeezed, which pressures the team to under-resource documentation — the classic setup for errors, RFI storms, and CA pain later.
Make it up on volume. Take more work to cover the margin gap, with the same planning blind spot still in place. This is how one project's leak becomes a firm-wide pattern.

Meridian does some of all three. The year ends profitable, but two points of margin lower than planned — invisible in any single week, very visible in the annual numbers.

The post-mortem

What makes this case instructive is when the information existed. The hours were in the staffing spreadsheet every single week. The budget was in the accounting system the whole time. The overrun was knowable by week three — when the fix was a five-minute conversation: flag the program churn, document it, and either get the additional service approved or scope the absorption deliberately.

Instead it was discovered at week eleven, when the only conversation left was about who eats the loss.

The gap between week three and week eleven is the entire cost. Not the extra hours — those might have been spent anyway. The cost was making staffing decisions for eight weeks without the one number that gave them financial meaning.

What reconciliation actually means

"Reconciling staffing against budget" sounds like accounting overhead, but it reduces to one question asked continuously, per project, per phase:

At the rate we're staffing this phase, do the planned hours land inside the phase budget — and if not, when exactly do we run out?

To answer it weekly, a firm needs three things in one view:

Planned allocations by week — who is on the project, for how many hours, going forward (not just historically).
Phase budgets in hours or dollars — the contract's fee structure, broken down the way the work is actually delivered.
The projection of one against the other — a burn line that shows the crossing point before it happens.

Some firms build this with a disciplined operations person and a heroic spreadsheet. It can work — until the person who maintains it leaves, or the firm grows past what a hand-reconciled model can carry (we've written about where staffing spreadsheets break down).

This is also, candidly, the problem Resource was built around: weekly project projections show budget burn by phase alongside staffing projections for the same weeks, so the week-three conversation actually happens in week three. Phase budgets, allocations, and PTO live in one place, and the crossing point shows up on a timeline instead of in a quarterly report.

The checklist

Whatever tools you use, Meridian's failure is avoidable with four habits:

Put phase budgets where staffing decisions are made. If the resourcing meeting can't see fee burn, it's allocating blind.
Project forward, not just backward. Timesheets tell you what was spent; only projected allocations tell you when you'll run out.
Make scope absorption a decision, not a default. When the client churns the program, the project lead should be choosing between "additional service" and "deliberate absorption" — in writing, that week.
Review the burn line weekly. Five minutes per project. The overruns you catch at 60% of budget are negotiable; the ones you catch at 138% are just losses.

The firms that do this aren't smarter than Meridian. They've just closed the gap between when an overrun becomes knowable and when it becomes known.