Why your project looks profitable — until it isn't

A mid-size consulting team finishes a €200K engagement. The forecast had showed a 28% gross margin throughout delivery — healthy by any measure. The final P&L settles at 11%. The project director is surprised. The finance manager is not. This is a pattern that repeats across the industry more often than anyone formally admits, and it's almost never caused by incompetent delivery. It's caused by three specific, structural problems in how firms track economics during a project, not after it.

The three hidden margin killers

1. Overhead allocated as a flat percentage

Most firms allocate overhead to projects as a single blended rate — something like "22% of direct labour costs." This number is derived annually, during budgeting, from last year's cost base. The problem is that it treats all overhead as equivalent, when in practice overhead is highly variable across categories. Software licences don't scale linearly with revenue. Office costs don't track headcount perfectly. Sales and marketing costs are entirely front-loaded in the pipeline phase, not during delivery.

The result: projects that run longer than planned absorb disproportionate overhead because the flat rate doesn't reflect the time dimension. A 4-month project that slips to 6 months will show the original margin estimate in the forecast right up until close, then suddenly settle 8-12 points lower when actual overhead is allocated.

2. Senior resources spending untracked hours

In most firms, time tracking compliance is highest among junior staff and lowest among partners and senior directors. The informal logic is reasonable enough: senior people are busy, their time is hard to categorise, and chasing them for timesheet entries feels like it has low ROI.

The cost of this is substantial. A partner at an effective hourly rate of €220 who spends six hours per week on "quick calls," deck reviews, and client relationship management across a project — but doesn't log those hours — creates an invisible cost of over €5,000 per month against the project budget. On a four-month engagement, that's €20,000 in untracked cost. Applied to a €200K project, that's 10 margin points that never appear in any forecast.

3. Scope creep absorbed without contract adjustment

Every consulting firm has a policy about scope creep. In practice, the policy is rarely enforced at the project level. Change requests get deprioritised when the client relationship feels fragile. Additional deliverables get added "just this once" to smooth over a difficult conversation. Individual team members make local decisions to absorb extra work without escalating.

These decisions are rarely visible in the financial model because the cost absorption happens before anyone updates the project budget. By the time a formal review occurs, the work has been done, the hours logged, and the contract remains unchanged.

Why monthly P&L reviews don't catch this

The obvious response to margin erosion is better reporting cadence. Monthly P&L reviews, project health dashboards, budget-to-actual comparisons — these are standard practice at most firms of any size. And yet they consistently fail to surface these margin killers in time to act.

The reason is data latency. Monthly reviews depend on complete timesheet data, fully allocated overhead, and accurate revenue recognition — none of which are available in real time. Timesheet approval workflows introduce two to three weeks of delay between hours worked and hours visible in the financial model. Overhead allocation happens during the monthly close, not continuously. Revenue recognition follows billing milestones that may be 30 to 60 days behind delivery.

The result: by the time a monthly review flags a margin problem, you are typically looking at data that is 4 to 6 weeks old. On a 3-month project, that's the difference between catching a problem mid-project and catching it at close.

By the time a monthly review flags a margin problem, you are typically looking at data that is 4 to 6 weeks old. On a 3-month project, that's the difference between catching a problem mid-project and catching it at close.

What good practice looks like

The firms that consistently maintain healthy margins aren't fundamentally better at delivering work. Their teams face the same scope pressures, the same senior time allocation problems, the same overhead complexity. What separates them is the speed at which they see the financial reality of each project.

Good practice means timesheets closed weekly — not monthly — with a clear separation between billable and non-billable hours, reviewed by project managers rather than just finance. It means overhead allocated continuously using per-category methods, not a blended annual rate. And it means a standing conversation between project leadership and finance every two weeks on budget-to-actual, not a monthly surprise.

The €200K project that landed at 11% margin wasn't doomed at delivery. It was doomed at the point when the data systems couldn't tell anyone what was happening until it was too late to change course. The fix is rarely more rigour in delivery. It's almost always better visibility during it.