The Four Controls Every Capital Project Needs in Place Before Work Starts

Most project governance failures aren't caused by bad teams or bad luck. They're caused by starting execution without the four basic controls in place — a locked schedule baseline, a full project budget, a live risk register, and a defined reporting cadence. By the time the gap is obvious, it's expensive to close.

Project manager reviewing a schedule and budget on a dual monitor setup at a capital project site office

Here is the scenario that plays out on capital projects more often than anyone wants to admit: three months into construction, the owner’s rep is asked how the project is tracking against budget. The honest answer is that nobody knows — because the budget tracker only covers the prime contract, the change order log is three weeks behind, and the supporting documentation that affects the contingency has not yet been finalized.

Or: six weeks before substantial completion, the schedule shows the project on time — because the contractor keeps updating percent complete without anyone verifying what “complete” actually means in the field.

Neither of these is a contractor problem. Both are governance problems. And both are entirely preventable if four basic controls are in place before execution begins.

Why controls fail before they start

The most common reason project controls don’t work is that they’re set up as reporting mechanisms rather than management tools. A schedule that exists to satisfy a contractual requirement but isn’t actually reviewed in meetings isn’t a control — it’s paperwork. A budget tracker that only covers the prime contract but ignores design fees, owner-furnished equipment, and contingency isn’t a budget — it’s a partial picture.

Controls work when they’re integrated — when the schedule, budget, risk register, and reporting cadence are treated as a single system. A schedule delay affects the budget. A cost variance often signals an unreported risk. A risk that materializes produces a change order. These aren’t separate conversations; they’re the same conversation. If your controls aren’t tracking them together, you’ll always be one step behind the project.

The four controls — and what each one actually has to do

Schedule baseline

A schedule is not a baseline. A schedule becomes a baseline when it’s locked, accepted in writing by both parties, and saved separately from all future updates — so that every subsequent update is measured as a variance against the original.

Without a locked baseline, the contractor can keep updating “percent complete” without ever showing you what slipped. The schedule always looks like it’s progressing. But you have no way to measure whether you’re behind until you’re too far behind to recover at a reasonable cost.

The baseline also needs to include things the contractor doesn’t control: owner decisions, required testing and other work restricted to the owner’s scope, and design team response times. If those aren’t on the schedule, they can’t be tracked — and when they delay the project, the contractor has a legitimate basis for a time extension claim.

Full project budget

The prime contract contains many of the factors that ultimately shape the total cost of a capital project. The budget tracker that only covers the prime contract is missing design fees, owner-furnished equipment, technology systems, furniture, permits, inspections, owner oversight costs, and contingency — all of which are real project costs that need to be tracked and forecast.

The number that matters is forecast at completion: total project cost if the project continues on its current trajectory. That number needs to be updated every time scope, cost, or schedule changes — not once a quarter when finance requests it.

Contingency deserves specific attention. A contingency that’s 5% and drawn as change orders are approved is a different situation than having a 5% at balance completion. Tracking remaining contingency against remaining project risk is one of the most useful early warning signals in project financial management.

Risk register

A risk register that gets built at project kickoff and reviewed once a quarter isn’t managing risk — it’s documenting it. The value of a risk register is in weekly or bi-weekly review: what’s changed, what’s materialized, what mitigation actions are overdue, what new risks have emerged.

The seven example entries in the Starter Kit reflect the most common risk categories on capital projects: labor availability, subsurface conditions, owner decision delays, change order scope creep, owner required testing and work, permitting, and design errors. None of these are exotic. All of them are recoverable if caught early. All of them are expensive if they go unmanaged.

Risk registers also serve an accountability function. When a risk that was identified and logged materializes, you have a documented record of when it was known and what mitigation was planned. That matters in disputes.

Reporting cadence

Reporting cadence is the mechanism by which everything else stays current. A weekly field progress meeting creates accountability for the look-ahead schedule. A monthly budget review creates accountability for forecast accuracy. A monthly risk review creates accountability for mitigation actions.

Without a defined cadence — specific meetings, specific participants, specific content — the controls degrade. The schedule update gets submitted but not reviewed. The budget gets updated but not discussed with ownership. The risk register gets opened at closeout to see what was logged.

The cadence recommended in the Starter Kit isn’t complex: field meeting weekly, schedule and cost reviews bi-weekly and monthly, executive status report monthly, contractor performance review quarterly. Eight defined touchpoints. Assigned owners for each. That structure is what keeps a project’s controls alive through execution.

When to use this kit

The best time to deploy these controls is before the Notice to Proceed (NTP) — before the contractor mobilizes and before any work gets underway. The second-best time is right now, regardless of where the project is.

Projects already in execution can still benefit from establishing a retroactive baseline, auditing the existing budget against actual costs, building a risk register from current project conditions, and formalizing a reporting cadence that doesn’t currently exist. It’s harder than doing it at kickoff. It’s significantly easier than trying to untangle financial exposure at closeout.


Need more than a template?

The Starter Kit gives you the structure. Filling it with accurate data, maintaining it through execution, and using it to make real management decisions requires time and expertise that most owner’s organizations don’t have sitting on the bench.

CMA’s PMP®-certified principals embed with owner organizations to establish and run exactly this kind of project controls framework — or to assess what’s in place and close the gaps. Schedule a free, no-obligation consultation to discuss your project’s current governance structure.

Free Template Kit

Project Controls Tracker

Ready-to-use client-side control templates: a schedule baseline checklist, a full-project budget tracker with 11 cost categories, a risk register with 7 pre-loaded example entries, and a status reporting cadence guide. Designed for owner's reps and client-side PMs.

No spam. Unsubscribe any time.