Cost-to-Complete Forecasting: The Number That Drives WIP, Banking, and Surety — and How to Get It Right
Cost-to-complete (CTC, also called ETC for estimate-to-complete) is the single most important forecast in construction accounting. It's the estimated remaining cost to finish a project. Combined with cost-to-date, it produces the total estimated project cost, which drives gross profit calculation, WIP schedule preparation, revenue recognition under percentage-of-completion, and the numbers bankers, sureties, and investors rely on.
Getting CTC right is hard because it's a forecast about future events — how much will it actually cost to finish this project given what we know today. Understated CTC overstates gross profit and leads to the dreaded profit fade when reality catches up at closeout. Overstated CTC hides real gross profit and distorts performance assessment. The goal is honest, disciplined forecasting — not optimism and not pessimism, but best current estimate based on the best current information.
CTC should include all remaining costs the project will incur:
Components of cost-to-complete
- Direct costs — remaining labor, materials, subcontracts, equipment rental
- Committed but unspent — POs and subcontracts with value remaining
- General conditions — site trailer, supervision, temporary utilities for remaining duration
- Warranty and callback reserve — expected callback costs
- Contingency for known unknowns — issues identified but not yet quantified
- Closeout costs — as-built preparation, punch list execution, final cleaning, commissioning
CTC should NOT include costs that won't be incurred — scope that was never authorized, items the owner will handle, items clearly outside the contract. The discipline is identifying what's actually going to be spent between now and project close.
Reliable CTC draws on multiple input sources:
CTC input sources
- Project manager's estimate by cost code — the primary input from the person running the project
- Superintendent's view of remaining labor hours — field-level understanding
- Subcontract buyout status — which subs are bought out and at what price
- PO commitments — outstanding POs with remaining value
- Change order pipeline — items under discussion with expected outcomes
- Historical actuals on similar work — benchmarks from past projects
- Schedule-driven costs — general conditions for the remaining duration
The PM estimate is foundational but should be supplemented by objective data. A PM saying "we have $200K to go on earthwork" should be checked against actual earthwork spent to date, percent complete on earthwork activities, and the subcontract with the earthwork sub.
CTC should be forecast at cost code level, not project level. Project-level forecasts hide problems that offset each other:
Cost code-level CTC methodology
- Each cost code has its own CTC estimate
- Sum of cost code CTCs equals project CTC
- Completed cost codes have zero CTC
- Well-progressed cost codes have well-understood remaining scope
- Early-stage cost codes carry more uncertainty — larger contingency appropriate
- Changes in one code don't silently offset changes in another
The granular view reveals the pattern. A project showing level overall CTC can hide earthwork trending $50K over and mechanical trending $50K under — a net zero that's not actually balance but two separate issues in different directions.
CTC should be reviewed and updated regularly, not just when the accounting department asks:
CTC review cadence
- Monthly at minimum — aligned with financial close
- More frequent on critical projects (biweekly) or during rapid-change periods
- Triggered reviews on major events — approved change order, delay event, scope change
- Formal review with project team, not just PM submitting alone
- Documented comparison to prior CTC — what changed and why
Monthly minimum is baseline because projects move fast enough that quarterly is too slow. Issues surfacing in a quarterly review may be 90 days old by the time action is possible.
Profit fade — gross profit declining over project life — is one of the most important patterns to detect:
Profit fade indicators
- Forecasted gross profit declining month over month
- Contingency being consumed faster than risk is being retired
- CTC increases not matched by revenue increases (change orders)
- Specific cost codes trending over budget
- Change order pipeline not converting — unapproved work still being done
- Schedule pressure leading to overtime or premium labor
Profit fade happening early gives time to act. Profit fade discovered at closeout is too late — the project is essentially complete and the lost profit is real.
Profit fade tracking is where CTC discipline pays off most visibly. Projects with honest CTC forecasting show profit fade early, enabling corrective action. Projects with optimistic CTC maintain healthy-looking profit until the final months, when reality forces large adjustments that damage trust with every stakeholder.
Multiple methods cross-check CTC reasonableness:
CTC cross-check methods
- Bottom-up — sum of individual cost code estimates
- Top-down — percent complete of total project times total estimated cost, minus cost to date
- Earned value — if EVM is implemented, EAC calculations from CPI trends
- Schedule-driven — general conditions for remaining duration
- Historical — similar projects' actuals applied to remaining scope
- Subcontract-based — where subs are bought out, their remaining contract value is the cost
When methods converge, confidence in the forecast is higher. When they diverge, investigation is required to understand which method is more reliable for the specific project circumstances.
Contingency within CTC should be explicit and managed:
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Contingency management in CTC
- Contingency line item in CTC — separate from line item estimates
- Contingency drawdown tracked — what's being consumed by what issues
- Contingency level appropriate for project stage — more at start, less at closeout
- Remaining contingency forecast — how much will we need given remaining risk
- Low remaining contingency with remaining risk = warning signal
Contingency that starts at 5% and is fully spent with 30% of the project remaining indicates either underestimated contingency at the start or accumulating problems. Either way it's a signal needing attention.
Change orders affect CTC in specific ways:
Change order treatment in CTC
- Approved change order — added to contract value (revenue) and added to CTC (cost)
- Pending change order — risk-adjusted treatment; include based on probability of approval
- Disputed change order — typically exclude from both revenue and cost until resolved
- Unapproved work being performed — include cost in CTC even if revenue uncertain
- Change order profit vs cost — ensure margin captured in approved changes
The unapproved-but-being-performed case is particularly dangerous. Cost is being incurred that will hit CTC; if approval doesn't come, the cost exists without corresponding revenue. CTC discipline requires recognizing this risk rather than hoping it resolves favorably.
CTC should include realistic closeout reserves:
Closeout reserve components
- Punch list execution — walks, callbacks, finish work
- Commissioning and testing — system startup costs
- As-built drawings — AE or in-house preparation
- O&M manuals and training — handover documentation
- Warranty reserve — 1-year callback expectations
- Legal and administrative closeout — final lien waivers, releases, documentation
Closeout costs are frequently underestimated because projects feel mostly done before these items are real. A project that's 95% complete by cost often has 5-10% of remaining effort on closeout — more if the commissioning is complex or warranty reserve needs are significant.
CTC accuracy affects multiple stakeholders:
CTC stakeholder impact
- Banking — bank covenants often tied to gross profit; CTC accuracy affects covenant compliance
- Surety — sureties review WIP and CTC; inaccurate forecasts damage surety relationship and capacity
- Owner — progress billings and payments based on percent complete; CTC affects billings
- Internal management — project decisions depend on reliable forecasts
- External auditors — CTC methodology and documentation reviewed in annual audits
Multiple stakeholders relying on CTC makes discipline especially important. A company with consistently accurate CTC builds stakeholder trust that becomes competitive advantage in bonding capacity, banking relationships, and reputation.
CTC forecasts should be documented:
CTC documentation practices
- Current CTC preserved with date and preparer
- Change log showing adjustments from prior forecast and reasons
- Supporting workpapers for significant items
- Sign-off from PM and controller on the forecast
- Backup for cross-check methods performed
- Retention for statute of limitations period — auditors and sureties may review
Documented CTC is defensible CTC. A forecast with clear methodology and documentation can be explained if questioned; one prepared ad hoc without documentation is hard to defend.
Cost-to-complete forecasting is one of the highest-stakes financial exercises in construction. Accurate CTC enables reliable WIP, trustworthy gross profit forecasts, banking covenant compliance, surety confidence, and internal decision-making. Disciplined CTC methodology draws on PM estimates supplemented by objective data, forecasts at cost code level, reviews monthly or more often, detects profit fade early, cross-checks with multiple methods, manages contingency explicitly, and treats change orders and closeout realistically. Companies with strong CTC discipline consistently report better financial predictability, stronger stakeholder relationships, and fewer end-of-project surprises. CTC isn't glamorous work, but it's where the real accounting of a construction company happens — the profit or loss on each project is fundamentally the CTC forecast made real.
Written by
Sarah Blake
Head of Product
Former AP Manager at a $200M construction firm, now leads product at Covinly. Writes about what AP teams actually need from automation — beyond the marketing promises.
View all posts