Free 5-day trial — no credit card, no commitment. Get started →
mataee
Toggle sidebar
What a project overrun really costs: anatomy of a budget blowout in an architecture firm

Photo de Julia Taubitz sur Unsplash

Architects & Engineering

What a project overrun really costs: anatomy of a budget blowout in an architecture firm

27 December 2025 · 9 min read · Mataee

Every architecture firm has its story of a project that went off the rails. Not a spectacular collapse, no. Rather a slow, silent erosion, where hours accumulate without anyone sounding the alarm. The kind of project that, on paper, showed comfortable profitability -- and which, at final accounting, cost more than it earned.

Here is the story (fictional, but realistic) of Residence Les Jardins d'Etienne. A 24-unit residential project. A standard brief. A methodical drift.

The project on paper -- a promising brief

Residence Les Jardins d'Etienne is 24 apartments in a 5-story building, a private developer as project owner, and a full project management mission entrusted to the firm. From sketch to handover, including construction supervision.

The budget forecast is clear:

  • Total fees: 180,000 EUR excl. tax
  • Estimated hour budget: 2,250 hours (i.e., an average billing rate of 80 EUR/h)
  • Average loaded cost: 48 EUR/h per team member
  • Forecast margin: 72,000 EUR, or 40%

The assigned team:

  • 2 architects (one senior, one junior)
  • 1 project manager at half-time
  • 1 intern as reinforcement during the ESQ (Sketch) and APS (Preliminary Design) phases

The schedule is set for 18 months. Phases are distributed according to the MOP law. Milestones are established. Everything seems under control.

This is precisely the moment things start to slip.

Months 1-3: the first invisible overruns (ESQ to APS)

Month 1: the phantom meetings

The developer is enthusiastic. They want to "move fast." From the second week, they call an additional alignment meeting. Then another to present the sketch to the sales director. Then a third to adjust the product mix.

Each meeting lasts 2 hours. With preparation and minutes, count 4 hours per occurrence. Over three months, 6 meetings not planned in the contract are added to the schedule.

Result: +24 hours

Warning signal: More than 2 unplanned project owner meetings per month from the sketch phase. This is the first symptom of a project where contractual framing is vague.

Month 2: sketch iterations

The sketch approved? Not quite. The developer wants to "explore a variant with a through-lobby." Then "test an option with studios instead of 2-bedrooms on the typical floor." Each variant means a half-day of work for the junior architect, plus a review by the senior.

In total, 5 sketch iterations instead of the planned 2.

Result: +35 hours

Warning signal: The sketch budget is 85% consumed when the phase is only 60% validated. The gap between consumption and progress is the first reliable indicator of an overrun.

Month 3: the intern and the learning curve

The intern assigned to the BIM modeling of the APS plans is competent, but they're discovering the firm's software. The training time and rework of their deliverables by the junior architect was not budgeted.

Result: +40 hours (20h of intern production beyond plan, 20h of rework by the junior)

Warning signal: Any team change or integration of a junior profile without hourly reallocation mechanically generates an extra cost. An intern's productivity on unfamiliar software is approximately 50% that of a trained team member.

End of month 3 -- status report:

Phase Hours budgeted Hours consumed Variance
ESQ (Sketch) 200 h 259 h +59 h
APS (Preliminary Design, partial) 150 h 190 h +40 h
Cumulative 350 h 449 h +99 h

Nobody worries. "We'll catch up in the next phases." This is the most dangerous phrase in project management.

Months 4-9: the grey zone where everything accelerates (APD to PRO)

Modifications during the PRO phase

The project enters the PRO (Detailed Design) phase. The building permit is filed. The developer returns with modification requests: repositioning the boiler room, adding a larger bike storage for zoning compliance, revising the windows for commercial reasons.

Each modification during the PRO phase costs 3 to 5 times more than during sketch. Here, 4 substantial modifications require plan revisions, specification updates, and quantity adjustments.

Result: +80 hours

Warning signal: Any modification during the PRO phase that isn't formalized through an amendment is a pure loss. The reflex of "doing the client a favor" is the primary factor behind overruns in firms.

Underestimated technical coordination

Technical synthesis meetings with engineering consultants (structural, mechanical, electrical) prove more complex than expected. The project is in a seismic zone, requiring additional iterations with the structural engineer. The project manager goes from half a day per week to a full day on this brief.

Result: +30 hours of unplanned coordination

Warning signal: When the project manager exceeds 50% of their time on a single brief while their planned allocation was 25%, it's a strong signal that technical complexity was underestimated at quoting stage.

The regulatory change

During the APD (Detailed Preliminary Design) phase, a new accessibility decree requires adjustments on 8 apartments. Bathrooms must be redesigned, circulation paths verified. It's nobody's fault, but the additional work is very real.

Result: +45 hours

Warning signal: Regulatory changes aren't predictable, but their impact can be quantified and negotiated with the project owner. Without precise time tracking, it's impossible to justify an amendment.

End of month 9 -- status report:

Phase Hours budgeted Hours consumed Variance
ESQ (Sketch) 200 h 259 h +59 h
APS (Preliminary Design) 300 h 340 h +40 h
APD (Detailed Preliminary Design) 400 h 445 h +45 h
PRO (Detailed Design) 500 h 610 h +110 h
Cumulative 1,400 h 1,654 h +254 h

At this stage, 62% of budgeted hours are consumed, but only 55% of the project is delivered in terms of phases. The gap is established.

Ready to track your time differently?

Free 5-day trial — no commitment, no credit card.

Get started

Months 10-18: the construction site, a land of surprises (EXE to DET)

Site meetings: the silent hemorrhage

The contract specified biweekly site meetings. From the first month, the general contractor requests a weekly schedule. The developer approves. The project manager doesn't dare refuse.

Each site meeting means: 1h of travel, 2h on site, 1h of minutes. That's 4 hours per occurrence.

Over 8 months of construction, we go from 16 planned meetings to 32 actual meetings. The cost of site supervision explodes.

Result: +120 hours (for more on this frequently underestimated item, see our analysis of the true cost of site meetings)

Warning signal: Switching from biweekly to weekly meetings mechanically doubles the DET budget. It's the most frequent and costliest drift during the construction phase.

Inspection reports and deficiency tracking

More meetings means more minutes. Add to that pre-delivery inspections, letters to contractors, formal notices for delays. The project manager devotes considerable time to the administrative management of the construction site.

Result: +60 hours of drafting and document follow-up

Warning signal: The administrative time / technical time ratio during the DET phase should not exceed 40%. Beyond that, it's a sign that the construction site is generating too many uncontrolled contingencies.

The phantom amendments

Throughout the project, several additional services could have been the subject of amendments: the sketch iterations, the PRO modifications, the switch to weekly meetings. None was negotiated.

Why? Because without reliable time tracking, the firm had no quantified data to justify the request. "We can feel things slipping" isn't enough when facing a developer. You need tables, hours, budget-versus-actual comparisons by phase.

The final tally: +420 hours, 18,900 EUR of lost margin

The project is delivered. The developer is satisfied. The firm discovers the extent of the damage.

Summary table: budget vs. actual

Phase Hours budgeted Actual hours Variance Extra cost (at 45 EUR/h loaded)
ESQ (Sketch) 200 h 259 h +59 h 2,655 EUR
APS (Preliminary Design) 300 h 340 h +40 h 1,800 EUR
APD (Detailed Preliminary Design) 400 h 445 h +45 h 2,025 EUR
PRO (Detailed Design) 500 h 610 h +110 h 4,950 EUR
EXE/VISA 250 h 266 h +16 h 720 EUR
DET/AOR 600 h 750 h +150 h 6,750 EUR
Total 2,250 h 2,670 h +420 h 18,900 EUR

What the numbers reveal

  • Fees received: 180,000 EUR excl. tax
  • Actual project cost: 2,670 h x 48 EUR/h = 128,160 EUR
  • Actual margin: 51,840 EUR, or 28.8%
  • Forecast margin: 72,000 EUR, or 40%
  • Lost margin: 20,160 EUR

The project remains profitable -- it's not a catastrophe. But 20,160 EUR of evaporated margin on a single project is the equivalent of 4 months of an intern's salary. Or the budget for a competition. Or the cash flow that's missing when a client pays late.

And above all: this scenario repeats on every project when the firm has no real-time visibility into its hourly consumption.

What could have been saved

With time tracking by phase and by team member implemented from the start:

  • The sketch iterations would have triggered an alert as early as month 2, allowing reframing of the scope or negotiation of an amendment.
  • The extra cost of PRO modifications would have been documented and billed: 4,950 EUR recoverable.
  • The switch to weekly meetings would have been costed in real time and negotiated with the project owner: 6,750 EUR recoverable.

Estimated potential savings: 11,700 EUR of preserved margin, more than half of the overrun.

The 3 warning signals to monitor to never suffer an overrun again

The story of Les Jardins d'Etienne is not inevitable. Every overrun had a precursor signal. Here are the three indicators to monitor to anticipate rather than endure.

1. Hourly consumption rate exceeds 60% at mid-phase

If you've consumed more than 60% of budgeted hours when the phase has only progressed 50%, the overrun is virtually certain. That's the moment to decide: reframe the scope, reallocate resources, or prepare an amendment.

This simple ratio -- hours consumed / hours budgeted vs. actual progress -- is the best leading indicator of overrun. But you need reliable data to calculate it.

2. More than 2 unplanned project owner meetings per month

Meetings are the most underestimated expenditure item in firms. Each unplanned contractual meeting represents an average of 4 hours of work (preparation, travel, meeting, minutes). Two additional meetings per month means 96 hours per year -- the equivalent of 2.5 weeks of an architect's work.

To explore this topic further, consult our article on architecture project profitability.

3. Any team change without hourly reallocation

Replacing an experienced team member with a junior or intern without adjusting the hour budget creates an invisible productivity deficit. The rule of thumb: plan a coefficient of 1.5 to 2 on estimated hours for a profile learning the firm's tools.


Residence Les Jardins d'Etienne is a fictional project. But the mechanisms described are universal. They occur every day, in firms of all sizes, on projects of all types.

The difference between a firm that suffers these overruns and one that controls them rarely comes down to the talent of the architects or the quality of the projects. It comes down to something much more prosaic: the ability to measure, in real time, the time spent on each phase, by each team member, on each project.

Without this data, there are no warning signals. Without warning signals, there are no corrective actions. And without corrective actions, each new project reproduces the same overruns -- in complete good faith.

Ready to track your time differently?

Free 5-day trial — no commitment, no credit card.

Related articles