Project management and project controls are two different jobs. A project manager leads the project and makes the decisions; project controls measures where the project actually stands against cost, schedule and risk, and tells the project manager what those decisions should be based on. Small projects usually get both from one person. Larger or higher-risk ones need them split, because doing both properly at once is close to impossible once a programme gets complex.
That's the short answer. The part most guides skip is how to tell which situation you're actually in, and what it costs you when the split is missing.
What's the Difference Between Project Controls and Project Management?
Project management owns the outcome: scope, budget, programme, quality, stakeholders, and the authority to make trade-off decisions between them. Project controls owns the evidence: it measures cost and schedule performance, tracks risk, manages change, and reports on where the project is heading before it gets there. The Association for Project Management defines project controls as covering seven core elements: managing time, managing cost, managing risk, managing change, reporting and performance management, information management, and associated communications. APM describes the discipline as “the practice of assessing if the proposed work is worth doing, of preparing for work before it is done, of thinking about what might go wrong before it is done, and of doing something about it if it does.”
Put plainly: a project manager decides what to do. Project controls tells them, with numbers, whether what they're doing is working.
| Project Management | Project Controls | |
|---|---|---|
| Owns | The outcome: scope, budget, programme, quality | The evidence: schedule and cost data, forecasts, risk register |
| Decides | Trade-offs, priorities, stakeholder commitments | Nothing binding. Recommends, flags, forecasts |
| Typical tools | Stakeholder plans, RAID logs, governance reports | Primavera P6, EVM, cost/schedule integration, risk models |
| Fails silently when | Decisions get made without good data behind them | Data gets produced but nobody with authority acts on it |
| On a small job | One person, wearing both hats | Usually folded into the PM's own admin |
| On a large or complex job | A dedicated project manager or director | A dedicated planner, scheduler or controls team |
Neither role works well without the other. A project manager without controls is flying on instinct. A controls function without an empowered project manager is producing reports nobody uses.
What Does a Project Controls Function Actually Do?
Day to day, project controls is analytical and largely non-decision-making work. It typically covers:
- Schedule management. Building and maintaining the programme in Primavera P6 or a comparable tool, tracking progress against baseline, and running the critical path.
- Cost control and earned value. Tracking committed and actual spend against budget, and, on larger programmes, Earned Value Management to compare planned, earned and actual cost so a variance shows up while there's still time to act on it.
- Risk analysis. Maintaining the risk register and, on programmes where it matters, running a Quantitative Schedule Risk Analysis to model how much float and cost contingency the programme really needs, rather than guessing.
- Change control. Logging and assessing the cost and schedule impact of every instructed change before it gets baked into the baseline unchallenged.
- Performance reporting. Turning all of the above into something a project manager, client or board can actually read and act on.
None of this involves telling the client “we're doing X instead of Y.” That decision sits with the project manager. Controls exists to make sure the decision is an informed one.
What Does a Project Manager Do That Project Controls Doesn't?
A project manager carries authority. They agree scope changes with the client, resolve conflicts between the programme and the commercial position, decide where to spend contingency, and answer for the outcome. Project controls can tell them the critical path just moved by three weeks; only the project manager decides whether to accelerate, absorb the delay, or raise it as a claim.
On UK contracts this distinction is sometimes contractual, not just organisational. Under NEC3 and NEC4, “the Project Manager” is a defined term with specific duties: certifying compensation events, accepting or rejecting the Accepted Programme, instructing changes, and administering the contract on the client's behalf. That's a different thing again from the delivery-side project manager running the contractor's team, and different again from a project controller producing the numbers both sides argue over. On a tender or contract document, knowing which “project manager” is meant matters more than the generic job title suggests. Our NEC4 Programme Requirements guide covers the contractual Project Manager's duties around the Accepted Programme in detail.
Do You Need Project Controls, Project Management, or Both?
It depends on scale, risk and contract form, not on job titles.
Small, low-complexity projects. One experienced project manager can usually run the programme, track cost and manage risk themselves, provided the schedule stays simple enough to update without a dedicated tool. This is common and it's fine, right up until the project grows past what one person can hold in their head.
Mid-size or contractually exposed projects. This is where controls earns its keep even without a full team. A project manager under an NEC4 contract, for instance, needs a properly maintained Accepted Programme to support compensation event assessments. Get that wrong and every subsequent claim is weaker. A part-time or outsourced planner covering the schedule and cost tracking, reporting into the project manager, is usually the right shape here.
Large, complex or multi-stakeholder programmes. You need both, separated, and ideally not sharing the same person's attention. A dedicated project manager focused on delivery and stakeholders, and a controls function, whether an in-house team or an external project controls consultancy, focused on schedule integrity, cost performance and risk. On programmes with genuine dispute exposure, that controls discipline is also what makes a future extension-of-time claim defensible instead of reconstructed under pressure.
The honest test: if your project manager is too busy managing stakeholders and commercial issues to keep the programme rigorously updated, you don't have a controls gap you can wish away. You have one that's already costing you visibility.
What Goes Wrong When a Project Has Management but No Controls?
The project manager makes decisions on a programme that's quietly gone stale. Progress gets recorded loosely, float gets consumed without anyone tracking it, and by the time a delay becomes obvious it's already too late to recover cheaply. Worse, if that delay ends up disputed, a programme that was never health-checked against a recognised standard makes any subsequent forensic delay analysis far harder to defend, because the records it depends on were never kept to a standard that survives scrutiny.
The reverse failure exists too, though it's less common: a controls function producing detailed, accurate reports that a disempowered or absent project manager never acts on. The data was right. Nobody used it.
Get the Split Right Before It Costs You
Planned works as the project controls function, the planning and scheduling engineer, or both, across construction, energy and infrastructure projects, on NEC3/4, JCT and FIDIC contracts, delivered in the UK and remotely for international clients. If you're not sure whether your project has a controls gap or a management gap, that's usually the first thing worth an outside, senior look.
Book a Free Consultation to talk through where your project stands, or run your current programme through the Free P6 Check tool to see whether the schedule underneath your reporting is actually sound. See our project controls service for what a dedicated controls function covers.
Frequently Asked Questions
Is a planner the same as project controls?
Not quite. A planner or scheduler typically owns one part of project controls, the programme itself, in Primavera P6 or a similar tool. Project controls is the wider discipline, which also covers cost, risk, change and reporting. On smaller projects a planner may effectively be doing most of the controls job alone; on larger ones, planning is one role within a bigger controls team.
Can one person do both project management and project controls?
Yes, and on small projects it's normal. The risk is capacity, not competence: once a programme gets complex enough that keeping the schedule, cost tracking and risk register genuinely current takes real hours each week, a project manager doing that alongside stakeholder and commercial management usually starts cutting corners on one or the other, and it's rarely the client-facing work that gets cut.
Does project controls have decision-making authority?
No, not typically. Project controls analyses and reports; the project manager (or, on NEC contracts, the contractually defined Project Manager) holds the authority to act on that information, agree changes and commit the client's or contractor's position.
What's the difference between a project controls consultant and a project management consultant?
A project controls consultant is brought in for the analytical function: building or fixing the programme, running cost or schedule risk analysis, or providing an independent health check. A project management consultant is brought in to run or support delivery and hold client relationships. The two are sometimes the same person on a small engagement, but on larger ones they're usually separate briefs.
When should a project bring in dedicated project controls rather than relying on the project manager?
As soon as tracking cost, schedule and risk properly starts competing for the project manager's time with stakeholder and commercial work, or as soon as the contract has real time-and-cost exposure, an NEC4 compensation event regime or FIDIC claims clauses, where a defensible programme matters if things go wrong. Waiting until there's already a dispute is the most expensive time to start.