Project controls are often mistaken for monthly reporting.
That is too narrow.
Project controls are the connected processes you use to plan the scope, cost and programme; measure performance while the work runs; explain variance; manage risk and change; and give decision-makers information early enough to act.
The distinction matters. A report tells you what happened. Control helps you decide what happens next.
Many contractors have reports. Far fewer have control.
If your monthly pack tells you what happened but not what to do next, it is history, not control.
This is the commercial discipline used on major infrastructure programmes, right-sized for SME contractors and Tier 2 and Tier 3 businesses.
What project controls mean in practical terms
A project control system gives you a structured answer to five questions:
- What did we agree to deliver?
- What did we allow for in cost and time?
- Where are we now?
- Why has the position moved?
- What decision will protect the outcome?
A baseline is the agreed reference point against which performance is measured. It normally covers scope, cost and programme.
Without a baseline, you can still produce figures. You cannot reliably explain variance.
Project management and project controls are different
Project management leads and coordinates the work. It sets direction, allocates responsibility and makes decisions.
Project controls supplies the analysis those decisions rest on.
That includes testing the cost forecast, tracking programme movement, assessing the effect of change and identifying risks before they become expensive problems.
The two functions should work together. Neither replaces the other.
A project manager may know that a subcontract package is slipping. Project controls should show what that means for completion, preliminaries, procurement, margin and contractual entitlement.
That is the difference between awareness and control.
The six components of project controls for contractors
1. Cost control
Cost control starts before the job reaches site. It continues until final account.
You need a clear line from the estimate to the approved budget, commitments, actual cost, cost to complete and forecast outturn.
Practical cost control includes:
- reviewing the estimate and cost allowances;
- setting the cost baseline;
- allocating budgets to work packages or cost codes;
- tracking orders, commitments and invoices;
- assessing cost to complete;
- explaining variances;
- monitoring trends;
- testing the effect on your margin.
A cost report should not simply say that a package is overspent. It should explain why, identify the likely final position and state what action is available.
This is the foundation of effective SME construction cost management.
2. Schedule control
Schedule control turns the programme into a live management tool.
You need a baseline programme, regular progress updates and a clear understanding of the critical path. The critical path is the sequence of activities that determines the planned completion date.
You should also monitor float. Float is the available time before a delay to an activity affects a key date or completion.
Schedule control asks:
- Are activities progressing as planned?
- Which work fronts are slipping?
- Has the critical path changed?
- Is float being used?
- What decisions or information are now urgent?
- Is the forecast completion date still credible?
An updated programme that does not explain movement is only a new set of dates. It is not effective control.
For delay, extension of time and compensation event matters, keep the programme and commercial records aligned. Our guidance on delay analysis and extensions of time explains why late reconstruction weakens a contractor’s position.
3. Risk and contingency control
A risk register is useful only when people review it and act on it.
Each risk should have an owner, a response, a target date and an assessment of its possible time and cost effect.
Contingency is not spare profit. It is an allowance for identified uncertainty. Contingency control tracks what has been allocated, what has been drawn down and what remains.
A working process should cover:
- identifying new risks;
- assessing probability and impact;
- quantifying likely cost and programme effects;
- assigning mitigation actions;
- approving contingency drawdown;
- reviewing residual exposure.
A risk that sits unchanged in a register for six months is not being controlled. It is being stored.
Under NEC contracts, the early warning process should connect to your risk, programme and forecast records. Read our guide to NEC4 early warnings and the Clause 15 process.
4. Change and configuration control
Change control protects the agreed baseline.
It identifies a proposed change, assesses its effect, obtains approval, implements the decision and records the current version of the project information.
For contractors, this often means tracking:
- instructions;
- design revisions;
- scope changes;
- compensation events;
- variations;
- access changes;
- revised specifications;
- changes to construction sequence.
Each change should be tested for cost, time, risk, resource and contractual effect.
Configuration control is the discipline of knowing which drawing, specification, programme or instruction is current. If people build from different versions of the information, the resulting cost and delay become difficult to separate.
On NEC4 projects, keep early warnings and compensation events linked but distinct. Our NEC4 compensation event guide explains why time and cost must be assessed together.
5. Earned value
Earned value provides a way to compare planned work, completed work and actual cost.
In plain English, it asks whether the value of work completed matches the time and money used to deliver it.
You do not need to begin with complicated terminology. The useful questions are:
- How much work did we plan to complete?
- How much have we actually completed?
- What has that work cost?
- Are we producing the planned output for the resources used?
Earned value can highlight productivity and trend problems earlier than a simple spend report. It needs reliable scope, cost and programme data, however.
A later post in this project controls cluster will cover Earned Value Without the Jargon: What PV, EV, AC, CPI, SPI and EAC Actually Tell a Contractor in more detail.
6. Reporting and data
Reporting is the output of control, not the control itself.
You need one usable view of cost, programme, risk, change and decisions. You do not need forty pages of coloured charts that nobody reads.
A useful report should show:
- current cost and forecast outturn;
- programme status and forecast completion;
- key variances;
- live risks and mitigation;
- approved and pending change;
- commercial actions;
- named owners;
- decisions required from management.
The test is simple: can the reader understand the position and act on it?
If not, improve the information before adding more pages.
WBS, CBS and OBS: the structures behind useful reporting
Three integrated structures help organise project controls:
- WBS, Work Breakdown Structure: breaks the scope into manageable parts, such as work areas, packages or activities.
- CBS, Cost Breakdown Structure: groups cost by discipline, resource, package or contract.
- OBS, Organisation Breakdown Structure: shows who owns and is responsible for each area.
When these structures align, you can report by work area, trade, package or responsible manager without rebuilding the information each month.
That alignment also exposes gaps. If a cost exists without an owner, or a programme activity has no corresponding budget, someone needs to resolve the control structure.
Why project controls matter to an SME contractor
Margin leakage is usually visible late.
A small productivity movement, an unpriced instruction, an unrecorded delay or an overdue payment may look manageable in isolation. Together, they can change the commercial result.
The earlier you see the movement, the more choices remain.
You may still be able to:
- resequence the work;
- challenge a forecast;
- notify an event;
- protect a payment position;
- adjust procurement;
- allocate additional resource;
- agree a mitigation plan.
Late information removes options. Early information creates them.
That is why project controls for contractors must connect cost, programme, risk, change and contract administration. A cost report that ignores the programme is incomplete. A programme report that ignores margin is incomplete.
A proportionate starting point for smaller contractors
Do not build systems designed for a major infrastructure programme.
Start with a minimum viable control set:
- One cost baseline covering the approved budget, commitments, actual cost and forecast cost to complete.
- One programme baseline showing the planned sequence, key dates, critical path and current forecast.
- One change and risk register with owners, impacts, actions and status.
- One cost and value reconciliation rhythm so applications, earned value, cost and forecast are reviewed together.
- One page of reporting that states the position, the variance and the decisions needed.
The system should be proportionate to the project. It should also be maintained consistently.
A simple control system that people use is better than an advanced system that sits out of date.
Common project controls failure patterns
| Failure pattern | What it means in practice |
|---|---|
| Reporting without a baseline | You can describe movement but cannot prove what it moved from. |
| Baselines never updated after agreed change | The report compares current work with an obsolete position. |
| Registers nobody reviews | Risks and changes remain visible but unmanaged. |
| Cost and programme tell different stories | The forecast lacks a credible explanation. |
| Data lives in individual inboxes | The project depends on personal memory and cannot be audited easily. |
| Controls become a monthly paperwork exercise | The team records history instead of managing the next decision. |
Do not confuse presentation with control.
The purpose is not to make the project look organised. The purpose is to identify the truth early and give the team a plan it can act on.
What comes next in this project controls cluster?
The following posts will examine each part in more detail:
- cost control and forecasting for contractors;
- schedule control and programme updates;
- risk and contingency management;
- change and configuration control;
- earned value without the jargon;
- reporting that gets used by project teams and directors.
The wider commercial context also matters. Payment records, notices and cash flow form part of the same control environment. See our UK construction payment process guide.
Frequently asked questions
What is the difference between project management and project controls?
Project management leads and coordinates the job. Project controls provides the analysis of cost, time, risk and change that supports management decisions.
They should operate together. Project controls does not replace leadership or site management.
Do I need project controls on a small project?
You need a proportionate level of control on any project where cost, programme, risk or contractual obligations matter.
A smaller project may need one integrated tracker and a short monthly review. It does not need a large corporate system.
Do I need expensive software?
No. You need reliable baselines, clear ownership, consistent records and a review process people will maintain.
Scheduling and cost systems can help, but software cannot correct poor data or unclear responsibilities.
What does a project controls review actually look at?
A review normally tests the cost baseline, current forecast, commitments, programme, critical path, risks, changes, payment position and supporting records.
It also asks whether these records tell the same story and whether management has clear decisions to make.
Where do I start if I have no baseline?
Start by establishing the best available position. Review the contract, estimate, approved budget, current programme, commitments, actual cost, known changes and outstanding risks.
Document the assumptions. Do not pretend the reconstructed baseline is perfect. Use it as a controlled starting point and improve it as better evidence becomes available.
How BHD Limited supports contractors
BHD Limited brings the commercial discipline of major infrastructure programmes to contractors and SMEs in a proportionate form.
BHD Commercial's team brings 25 years' experience across construction, defence and infrastructure. Our team are members of the relevant professional body.
We support clients across the UK, with West Midlands roots. Our head office is at 66 Paul Street, London EC2A 4NA, with a regional office at 4-5 Victoria Square, I11, Wolverhampton, WV1 1LD.
Through our project controls, quantity surveying and commercial management services, we help contractors establish integrated cost, schedule and risk control, supported by quantity surveying, cost consultancy and commercial management, so the numbers are tested early and decisions are made before they become urgent.
Conclusion
Project controls are not a reporting task.
They are the working system that connects scope, cost, programme, risk, change and responsibility. They show where the job stands, why it has moved and what you can still do about it.
The principle is straightforward:
Early rather than late. Truth rather than presentation. A usable plan rather than a descriptive report.
You do not need an oversized process. You need proportionate controls that your team can operate and management can use.
If you want a straight view of where your control gaps are, request BHD Limited’s free Commercial Health Check. We will review the position, identify the exposed areas and discuss what you can act on next.