Utilisation looks good, teams are fully booked, and yet margin comes in lower than planned at year-end. This pattern runs through IT consultancies, management consultancies and engineering firms alike. The cause is rarely bad projects. It lies in project controlling that only shows what happened in the rearview mirror.
Anyone who evaluates hours, budgets and utilisation only at the month-end close can explain deviations. Correcting them is rarely possible by then. This is exactly where the difference lies between project controlling that stays a reporting ritual and project controlling that becomes a genuine steering instrument.
How missing project controlling affects the project level:
- Margin: exceeded budgets only become visible after billing, when nothing can be saved.
- Utilisation: teams look fully occupied even though a growing share of hours never appears on an invoice.
- Resources: bottlenecks and double-bookings only surface when projects are already late to start.
- Forecast: revenue planning is based on individual estimates instead of consolidated project data.
- Project costs: the actual total cost of a project is only known weeks after completion.
The most important points in brief:
- Project controlling connects hours, costs, utilisation and forecast into a steerable data basis.
- Five KPIs carry the commercial steering: realised hourly rate, billability, utilisation, forecast accuracy and project margin.
- Companies without systematic project controlling lose an average of 15 to 25 percent of planned margin.
- Excel works up to around ten parallel projects. Beyond that, upkeep effort grows faster than insight.
What project controlling must deliver in the project business
Project controlling plans, monitors and steers budgets, deadlines, resources and results throughout the entire project. So far, the textbook definition. In the project business of service providers, a second requirement is added: controlling must answer questions while something can still be changed.
A report that shows three weeks after month-end that a fixed-price project is 60 hours over plan documents a loss. A planned-versus-actual comparison that shows the same deviation in the second project week enables a decision: renegotiate, raise a change request, or adjust scope. Steer instead of document is therefore the benchmark against which every project controlling must be measured.
Operative and strategic project controlling
Operative project controlling steers individual projects and the running portfolio: hours, budgets, deadlines, deviations. It delivers the data basis for the weekly decisions of project management.
Strategic project controlling uses the same data for longer-term questions. Which client types are profitable? Which project types pay off, which only tie up capacity? Both levels need the same foundation: fully recorded project hours and cleanly allocated costs.
The six mandatory processes under DIN 69901-5
The standard DIN 69901-5 defines 15 processes for the project management steering phase, six of them mandatory: steering deadlines, steering changes, granting acceptance, steering resources, steering risks and steering goal attainment.
Notably: four of these six mandatory processes presuppose current effort and capacity data. Without reliable project time tracking, the standard remains a paper standard.
Which KPIs belong in project controlling in 2026?
Many KPI lists name a dozen metrics and still fail to help with steering. For project service providers, five figures have proven to carry the load. Each answers a concrete commercial question.
| KPI | Answers the question | Core formula |
|---|---|---|
| Realised hourly rate | What do we actually earn per hour worked? | (Project revenue minus project costs) / actual hours |
| Billability | How much working time is billable? | Billable hours / total hours × 100 |
| Utilisation | How well is available capacity booked? | Booked time / available time × 100 |
| Forecast accuracy | How reliable is our revenue planning? | Actual revenue / forecast revenue × 100 |
| Project margin | What is left per project? | (Project revenue minus project costs) / project revenue × 100 |
Realised hourly rate
The quote says €150 per hour. The post-calculation shows €118 because extra hours on fixed-price work, goodwill effort and discounts erode the rate. On mixed billing from time-and-material, fixed price and change requests, this gap is the norm, not an outlier.
The realised hourly rate makes it visible: project revenue minus project costs, divided by hours actually worked. The metric is the single most direct indicator of revenue leakage.
Billability
Billability measures the share of working time that can be invoiced to a client. A consultant with 160 monthly hours, 112 of them on client projects, achieves 70 per cent. The metric is frequently confused with utilisation. The commercial difference is decisive: utilisation measures activity, billability measures value creation.
The billability KPI article explains why fully occupied teams still lose margin.
Utilisation
The utilisation rate shows how much of available capacity is actually booked. It is the central figure for staffing and bench management. Viewed in isolation, however, it misleads, because it counts internal work just as much as billable work.
Only in combination with billability does an honest picture of commercial performance emerge.
Forecast accuracy
A revenue forecast that misses by 20 per cent two months later leads to premature hires and tight liquidity buffers. A forecast only becomes reliable when it cleanly separates three figures: running project revenues, weighted pipeline, and available resources.
Forecast accuracy measures retrospectively how close projection and actuals were to each other. The step-by-step build-up is described in the article on forecasting in the project business.
Project margin
Project margin condenses all other KPIs into the result: what actually remains per project? The decisive factor is the timing of measurement. A margin that only appears in the post-calculation arrives too late for steering.
Anyone who continuously compares hours and costs against budget recognises tipping projects weeks earlier.
Which methods have proven themselves in everyday work
Methods are tools, not ends in themselves. Four procedures cover most steering situations in the project business in practice.
Planned-versus-actual comparison
The planned-versus-actual comparison continuously sets planned hours, costs and deadlines against actual values. It is the foundation of every other method. Automated rather than manually maintained, it becomes an early warning system.
Earned Value Analysis
Earned Value Analysis links degree of completion, planned value and actual costs. It answers whether the effort invested so far matches the progress achieved.
Milestone trend analysis
Milestone trend analysis projects at each reporting date when milestones will actually be reached. Drifting deadlines become visible as a trend before they escalate. Particularly valuable for long-running engineering projects with many trades.
Traffic light controlling
Traffic light controlling condenses the status of many parallel projects into green, yellow and red. As a communication format for management and clients this works well. The assessment needs hard criteria from planned-versus-actual data, though, otherwise every colour remains a matter of negotiation.
Why Excel controlling fails at project scale
Up to around ten parallel projects, much can be steered with spreadsheets and experience. Beyond that, the equation tips. Hours sit in the time tracking tool, costs in accounting, planning in Excel lists. Every evaluation begins with manual consolidation, and every version of the spreadsheet is already outdated when sent.
The consequences are quantifiable: companies without solid project controlling lose an average of 15 to 25 per cent of planned margin. At five million euros of project volume and a 20 per cent target margin, that amounts to up to €250,000 per year, distributed across many inconspicuous individual cases.
How to tell when the spreadsheet is at its limit
- Planned-versus-actual comparisons are produced manually and only at month-end.
- Margin development per project cannot be tracked continuously.
- Forecasts are based on individual estimates from project managers.
- Upkeep effort grows faster than insight.
- Nobody can spontaneously answer which clients are profitable.
If three of these apply, waiting is already costing money. The switch then ceases to be a tool question; it becomes a margin question.
{{blog-cta}}
Where margins tip unnoticed: three special cases
The largest margin losses rarely arise at the core of a project. They arise at the edges, where work is done without anyone having costed or billed it.
Hypercare phases after go-live
After go-live, the team informally stays with the client: fixing bugs, supporting users, stabilising processes. Five consultants with four hours each per week over six weeks adds up to 120 uncosted consulting hours.
Retainer mandates without volume controlling
Retainers seem predictable and therefore slip out of view. If the agreed volume is quietly exceeded by ten per cent monthly, a consultancy with eight retainer clients quickly loses a mid five-figure sum per year.
Change requests on fixed-price projects
Small additions are delivered within the fixed price because renegotiating seems more effort than the work itself. In aggregate, exactly these hours push the realised hourly rate downward. How to record and bill change requests correctly is described in the relevant article.
How is AI changing project controlling?
41 per cent of German companies now actively use AI. In controlling and accounting it is only 17 per cent, according to the Bitkom AI Study 2026. Exactly the area where margin, utilisation and forecast are decided is therefore lagging behind marketing and sales.
The reason is rarely a lack of will. AI evaluations are only as good as the data beneath them. Anyone who keeps project hours, costs and planning in separate systems has no foundation for automated deviation detection or forecast support. What is realistically achievable in 2026 and where pilot projects fail is shown in the articles on AI in project controlling and AI agents in project controlling.
Querying KPIs instead of building evaluations
The fastest route to a KPI is now a question. The ZEP Assistant, the integrated chat assistant in ZEP, answers controlling questions directly from the recorded project data: "How much budget do we have left for project X?" or "How many hours has team A booked on project Y last month?"
The difference from classic reporting lies in the timing. Previously the answer came at month-end, after export and reconciliation. Now it comes in the moment the question arises. The data basis remains the same: the continuously recorded project hours, budgets and assignments.
The assistant respects roles and permissions; every query and action is documented in the audit trail. Available as standard from ZEP Compact.
Project controlling with ZEP: one data basis instead of five tool breaks
The technical prerequisite for everything above is unspectacular: every project hour is recorded where budgets, rates and planned values also reside. That is exactly how ZEP's project controlling software works.
Project hours are booked directly onto projects, tasks and clients, with stored hourly and daily rates per employee. Planned hours and budgets sit alongside them; the planned-versus-actual comparison arises continuously rather than at month-end. Resource planning shows who is available when, before pipeline projects turn into capacity conflicts.
In ZEP Compact this creates the delivery layer: tasks, hours, resources and controlling on one data basis. ZEP Professional adds proposal management and invoicing and closes the loop from calculation to billed hour: project-to-bill without media breaks.
Next steps
Anyone who wants solid project controlling in 2026 does not need a big bang. Three steps are enough to start.
First: calculate the realised hourly rate for your three largest projects and compare it to the quoted rate. The difference shows your actual steering gap in euros.
Second: consistently separate billable and non-billable hours in time tracking. Without this separation, every KPI stays an estimate.
Third: time how long a current planned-versus-actual comparison across all projects takes today. If it exceeds half a day per month, you have a system problem, not a diligence problem. ZEP can be tested free for 14 days with your own projects rather than demo data.
FAQs
How does project controlling differ from classic business controlling?
Classic controlling steers recurring business processes in fixed periods. Project controlling steers time-limited undertakings with their own budget, their own team and changing requirements. It therefore needs ongoing planned-versus-actual data per project rather than monthly cost-centre reports.
What is the difference between billability and utilisation?
Utilisation measures how busy employees are, regardless of what they are doing. Billability measures the share of working time that can be invoiced to a client. A team can be 95 per cent utilised and still achieve only 60 per cent billability.
How often should project KPIs be evaluated?
For operational steering: weekly, daily for critical projects. A monthly rhythm is only sufficient for the strategic level. Anyone who only sees deviations at the month-end close can barely course-correct on short project timelines.
Which KPI is most important in project controlling?
If only one metric were possible: the realised hourly rate. It compresses additional effort, discounts and unbilled work into a single figure per project.
From when does project controlling software pay off over Excel?
As a rule of thumb, from around ten parallel projects or from the point at which evaluations tie up more than half a day per month. A concrete calculation with margin loss, working time and opportunity costs shows the actual ROI.
Does a company with 30 employees need a dedicated controller?
Usually no dedicated role yet, but defined responsibility and a system that automates evaluations. How to achieve financial transparency without a dedicated controller is a question of the right tools and processes.
