A construction project controls leader owns the one reconciled view of cost, schedule and forecast across the portfolio. Most contractors try to solve that with software first. The gap is not a data gap, it is an accountability gap: two teams running one job on two sets of information, with nobody senior enough to say which is true.
The forecast moved eleven points in one month and nobody could say when it actually moved. That is the day a contractor starts wanting a construction project controls leader.
Not whether. When. The number changed at some point between the last report and this one, and the honest answer from the project team was that the cost had probably been there for weeks, sitting in a sequence change that made complete sense on site and was never priced. It reached the ledger the month it got invoiced.
That is the moment a contractor discovers it has a project controls problem. It rarely feels like one. It feels like a reporting problem, which is why the first instinct is to buy something.
Why does better reporting software not fix a project controls problem?
Because the missing information was never in the system. It was on site, in a decision somebody made for good reasons and did not experience as a commercial decision at all. Software moves numbers faster. It does not create the number nobody wrote down.
This is worth being precise about, because it is not a competence failure and it is not laziness. It is how the roles are drawn.
The commercial function sits where the contracts, valuations and reporting live. The execution function sits where the work is. The person accountable for the money is often on site twice: once at groundbreaking, once at handover. Everything in between reaches them as a document. That structure is deliberate and mostly sensible, and it produces one reliable failure: execution makes a call that is entirely sound in the field and carries a commercial consequence nobody flags for weeks, while the commercial side holds a position that is correct on paper and lands on a sequence that stopped being possible two months ago.
Ask a site team what is still outstanding that has to go into the forecast, and the honest answer is often that they do not know yet. The thing that will cost the money has not announced itself. So the number gets built from what was written down, and the part that would have changed it stays on site.
No dashboard closes that gap, because the gap is not in the reporting. It is in who is accountable for reconciling two views before one of them becomes the official one.
What does a construction project controls leader actually own?
They own the single reconciled forecast and they are accountable when the field view and the ledger view disagree. That is the whole job in one sentence: not producing the report, but deciding which number is true, early enough that the decision is still a decision.
Everything else follows from that. Cost coding discipline, the earned-value method if the firm uses one, schedule integration, change-order tracking, the monthly rhythm: those are the instruments. The accountability is the role. Where the exposure sits in procurement rather than reporting, the seat to look at is the buyout director.
Which is why the reporting line matters more than the job description. A construction project controls leader buried under preconstruction becomes an advocate for the estimate. Buried under operations, they become an advocate for the field. The seat only works when it reports somewhere that has no stake in which version wins, which in most contractors of this size means the president or the COO.
Here is the distinction that gets lost when firms write the ad:
| Dimension | Project controls analyst | Project controls leader |
|---|---|---|
| Produces the report | Yes | Sometimes, and increasingly not |
| Reconciles field and ledger | Escalates the difference | Owns the resolution |
| Reports into | Cost or operations manager | COO or president |
| Called when the forecast moves | To explain the variance | To explain why it was not seen sooner |
| Hired for | Systems fluency, discipline | Judgment under disagreement |
The left column is a real and valuable role, and many firms need one before they need the right column. Confusing the two is how a contractor hires a capable analyst, gives them a leader’s title, and then wonders in month nine why the forecast still surprises everybody. The time model has its own version of this seat, covered in our note on the scheduling manager. On unit-price heavy civil work the cost half of the seat is the heavy civil cost engineer, who forecasts by pay item rather than by cost code.
What separates a strong project controls leader from a competent analyst?
The willingness to hold a number that two senior people disagree with, and to be specific about the uncertainty in it rather than hiding behind a range. Systems fluency is common. Standing in front of a president and saying the job is worse than the field thinks is not.
Test for it directly. The interview question that separates the field is not about software or method: it is what did you do the last time your forecast and the project manager’s forecast were materially apart, and what happened next. Selah runs this as a cost manager search.
The weak answer describes a process. The strong answer describes a conversation, and usually names a cost to the candidate for having had it.
Three other things worth screening for, in the order they tend to matter:
- Whether they have worked both sides of the split. Someone who has only ever sat in the office has never felt why the site team made the call they made, and they read every variance as a discipline problem.
- Provisional sums and how they talk about them. Each provisional sum is an admission that nobody made a decision in time. A candidate who defends them as prudence has not been the person carrying them at handover.
- How they handle verbal instruction. Construction runs on it: someone says proceed, the work happens, the paperwork catches up weeks later or never. The risk never sits with the person who gave the instruction. It falls on whoever has to prove, months later, what was agreed. A controls leader who has no view on this has not been close enough to the exposure.
That last one is the quiet one, and it is where the real money sits.
What does the market for this role look like?
Thin, and thinner than the estimating or project management market, because the people who can do it are not looking. Controls sits inside a broad hiring squeeze without having its own visible job title in most firms, so the shortage never shows up as an advertised vacancy.
The scale of the squeeze is documented. The 2025 AGC and NCCER workforce survey found that 91.7 percent of the 1,041 contractors answering the salaried-hiring question reported difficulty filling salaried positions, against 91.9 percent for craft roles. Two figures, one conclusion: the salaried bench is as hard to fill as the craft bench, and it gets a fraction of the attention.
Part of the scarcity is structural. There is no clean career path into the seat. People arrive from estimating, from cost management, from scheduling, occasionally from construction accounting, and each route leaves a different gap. The Bureau of Labor Statistics tracks cost estimators and construction managers as separate occupations; project controls as most contractors mean it does not map cleanly onto either.
In Texas and across the Southeast, where backlog has been strong enough that most capable controls people are fully occupied, the practical consequence is that this hire is almost never made from an applicant pool. It is made by approaching someone who is not looking, which is a different exercise entirely.
It is also a hire that frequently cannot be advertised. Posting for a project controls leader tells the market, and often the owner, that the contractor does not currently trust its own numbers. That is confidential executive search for mandates that cannot be publicly posted, and it is why the seat is usually filled through a direct approach rather than a job board. The mechanics are set out in how a confidential construction search actually runs.
Who this is not for
A project controls leader is the wrong hire for some contractors, and a few situations make it premature:
- Firms running one or two concurrent projects. A capable project manager and a good cost manager cover it. Adding a controls layer to a portfolio that one person can hold in their head creates reporting, not clarity.
- Contractors whose problem is genuinely a systems problem. If the data exists, is accurate, and simply takes three weeks to assemble, that is an implementation project, not a hire.
- Anyone reading this as a case for an earned-value mandate. Method is downstream of accountability. A firm that installs the method without the seat gets a more elaborate version of the same disagreement.
- Owner-side program teams. The role exists there too, with a different shape, and most of what is written above is about the contractor side of the table.
The reader this is written for is a general contractor, heavy civil firm or specialty contractor in Texas, the Southeast or elsewhere in the United States, with enough concurrent work that no single person holds the whole picture, and a month in recent memory where the forecast moved and nobody could say when.
Questions about hiring into this seat? Talk to us.
Sources and further reading
- OEWS 13-1051 estimators - US Bureau of Labor Statistics occupational data
- OEWS 11-9021 managers - US Bureau of Labor Statistics occupational data
- 2025 Workforce Survey - AGC and NCCER
- Construction Spending - US Census Bureau
- FAR 52.243-4, Changes - federal change-order clause