Construction cost overruns almost never arrive as surprises in the data. In hindsight, the patterns that drove the overrun are usually visible in the project record weeks or months before the cost impact was recognized and reported. The problem isn't that the signals weren't there. It's that no one connected them in time to act.
There are five operational signals that, when they appear together or in sequence, reliably precede construction cost overruns on commercial projects. They're not predictions. They're observations about conditions already present in the project data. Catching them when they first appear is the difference between a scheduling adjustment and a change order.
1. Consistent Crew Count Shortfalls
The schedule was built assuming a concrete framing crew of six. The daily logs for the past two weeks show the crew consistently arriving at four or five. The superintendent has noted it. The PM has seen it. The activity's current versus baseline position is still within tolerance because the float hasn't been consumed yet.
This is the most common early-stage signal, and it's the one most often tolerated too long because the schedule impact isn't visible yet. A crew running 15 to 25 percent below planned size on a float-limited activity will consume that float over 8 to 12 days. Once the float is gone, the activity is on the critical path and any further shortfall has direct cost implications: overtime, resequencing, or acceleration.
The signal to track isn't "is the activity behind baseline?" but "is the crew size below plan, and how much float remains?" Those two numbers together tell you whether you have a developing cost risk or a manageable variance.
2. RFI Aging on Cost-Sensitive Items
An RFI sitting in the structural engineer's queue for 14 days on a question about mechanical equipment room dimensions looks like a documentation lag. But if the concrete work for that room is in the look-ahead for the coming week, and the RFI affects the placement of embedded conduit stubs, that 14-day lag is a direct cost event: the concrete pour either waits (delay cost) or proceeds without the information and requires subsequent remediation (rework cost).
RFI-driven rework is one of the higher-cost items in construction change order history. The fix for embedded work that didn't get the right answer before pour is expensive: core drilling, sleeve installation, sequence disruption for subsequent trades. Most of these situations trace back to an RFI that sat too long while the work that needed the answer was approaching.
The pattern to monitor: RFI age in relation to the schedule position of the affected work. An RFI that's 5 days old with the affected activity 20 days out is low urgency. An RFI that's 10 days old with the affected activity in the 14-day look-ahead is a cost risk with a short correction window.
3. Repeated Look-Ahead Slippage
A three-week look-ahead schedule is a short-range planning tool. Activities listed for Week 3 in the look-ahead should, in general, complete by the end of Week 3. When activities consistently appear in the look-ahead for 2 or 3 consecutive weeks without completing, it's a signal that something structural is affecting progress on that scope, not weather-related single-event delays, but systematic underperformance.
The pattern is detectable only if you're comparing look-aheads across weeks, which almost never happens manually because it requires pulling historical look-ahead files and doing a comparison that has no standard format. But the information is usually in Procore or Buildertrend. It just hasn't been read longitudinally.
Repeated look-ahead slippage on float-limited activities is a reliable leading indicator of cost pressure because it typically means that schedule recovery acceleration is coming (overtime, additional crew mobilization, or resequencing) and those actions have predictable cost profiles. Catching the slippage pattern in Week 2 rather than Week 4 means the correction is less expensive and the acceleration directive is less disruptive.
4. Submittal Review Cycle Overruns
Construction contracts specify review periods for submittals, typically 10 to 14 days. When actual review cycles run 50 percent or more over that period, it creates downstream cost pressure. Long-lead material procurement depends on approved submittals. Fabrication can't start without approval. Field installation can't proceed without the approved material.
Submittal overruns tend to cluster by document type (structural steel shop drawings from a particular fabricator, mechanical equipment submittals from a particular engineer's office) and they tend to be predictable from early patterns in the project. The owner's project representative who reviews structural submittals in 18 days when the contract allows 14 will continue to do so unless escalated, and the cost impact compounds as more submittals flow through the same review queue.
Tracking submittal review cycle time per document type and per reviewing party, and comparing it to the contract allowance, is an underutilized early warning tool. Most submittal logs track status but not cycle time performance. The projects that catch submittal overruns early are the ones that review the age distribution of their open submittal log weekly.
5. Unresolved Owner Decision Points
Construction projects regularly reach decision points where owner input is needed to proceed: material selections, scope additions or reductions, equipment substitutions, finishes selections on fit-out work. When these decisions sit unresolved while the work that depends on them approaches, it creates one of two cost outcomes: work stops and waits (delay cost) or work proceeds on a speculative basis and is corrected later (rework cost).
Owner decision latency is often undertracked because it's uncomfortable to document formally. A pending decision from the owner is a relationship-sensitive item that PMs tend to manage through informal channels rather than formal schedule impact notices. But the cost impact when a decision is 2 weeks late on a 4-week delivery item is real and documentable. Tracking which pending owner decisions are connected to what upcoming activities, with how many days remaining before the decision affects the schedule, is a legitimate cost risk tool and a legitimate basis for proactive owner communication.
Reading These Signals Together
The five signals above are most valuable when read in combination. A project showing two of them in the same trade scope in the same week is in a materially different risk position than a project showing each one individually in different scopes. The combination of crew count shortfall, look-ahead slippage, and an aging RFI on the same building section is a pattern that reliably precedes an acceleration directive or a change order, not because any one element necessarily causes it, but because the combination indicates that a scope is running under conditions that can't sustain the baseline schedule without intervention.
Most project management software tracks these items separately. Cost overrun prediction requires reading them together. The projects where cost overruns are caught early enough to manage rather than absorb are the ones where someone is reading those five signals across the same scope and connecting the dots before the decision window closes.
In hindsight, the signals were there. Reading them in time is the part worth investing in.