Cost to Complete

Definition — what it is

Cost to complete is the forward-looking estimate of all cost still required to finish the remaining scope of a project, built up per cost code from remaining budget, remaining committed value, and the field's actual productivity. Added to cost incurred to date, it produces the estimated cost at completion, which is the basis for projected margin, over/under billing, and revenue recognition. Cost to complete is not the same as remaining budget: remaining budget is simply what is left of the plan, while cost to complete is a fresh judgment of what the remaining work will actually cost given what the field now knows. It is also not a single number for the job — a credible cost-to-complete is assembled line by line, because a project on plan in total routinely hides a line running hot behind a line running cold.

Also known as: Estimate to Complete, ETC, Cost to Finish, Remaining Cost Forecast

Why it matters — what it protects

Cost to complete is the number that decides whether a job is profitable, and everything financial downstream depends on it. Estimated cost at completion drives projected margin, the percent complete used for revenue recognition, and the over/under billing position, so an optimistic or stale cost-to-complete overstates earnings across the financial statements. This is the number sureties and auditors probe hardest, because it is the easiest one to shade.

It is the earliest honest signal of trouble. Actual cost tells you what has already happened; cost to complete tells you where you are heading, and a rising estimate to complete is the first quantitative evidence that a job is deteriorating. Teams that manage only against incurred cost are always reacting to losses instead of preventing them.

It converts field reality into financial consequence. When a superintendent reports that a crew is achieving 80 percent of the planned production rate, a proper cost-to-complete translates that into remaining labor dollars and a projected variance the office can act on. Without that translation, operational slippage stays trapped in the field until it emerges as a loss on the books.

It disciplines the difference between hope and evidence. The temptation is always to assume the remaining work will go to plan even when the completed work did not, which quietly defers recognition of a loss that is already baked in. A rigorous cost-to-complete forces the team to reconcile its forecast with its own productivity history, which is exactly why the discipline of building it up per line matters.

Lifecycle — how it moves

1. Baseline from budget

   The initial cost to complete equals the revised budget, since no cost has been incurred. From here it should diverge from remaining budget as the field reveals actual productivity and pricing.

2. Cost capture

   Actual cost to date is posted and accrued per line so the starting point for the forward estimate is complete. Missing accruals make remaining work look larger or smaller than it is.

3. Productivity assessment

   For self-perform work, actual units-per-hour is compared to the estimate's production rate to project remaining labor cost. This is the analytical heart of cost-to-complete and the step most often replaced by wishful straight-lining.

4. Commitment and remaining-scope pricing

   Remaining committed value on subcontracts and open POs is added, and uncommitted remaining scope is priced at current market rather than stale budget. Buyout still pending is a common source of surprise here.

5. Risk and known-change loading

   Known risks, pending changes not yet in the budget, and probable rework are loaded into the forecast so the estimate reflects what the team actually expects, not just what is contracted.

6. Roll-up to estimate at completion

   Line-level cost-to-complete is added to cost incurred to produce estimated cost at completion and projected margin. Offsetting line variances are preserved rather than netted, so the risk profile stays visible.

7. Review and challenge

   Executives challenge the forecast against productivity history and prior periods' accuracy. A cost-to-complete that never moves, or moves only at the end, signals it is being rolled forward rather than re-derived.

8. Feed to financial reporting

   The accepted estimate at completion feeds percent complete, revenue recognition, and the WIP schedule. Its integrity is therefore the integrity of the reported earnings.

Anatomy — the data it carries

Cost code

The grain at which cost to complete is built, because a per-job single figure hides offsetting line risk.

Cost incurred to date

Actual plus accruals, the floor the forward estimate sits on. Must be complete or the whole forecast tilts.

Remaining budget

What is left of the plan, the naive comparison point that cost to complete should be tested against, not equated to.

Remaining committed value

Unbilled value on executed subcontracts and POs, the most certain component of remaining cost.

Uncommitted remaining scope

Work not yet bought out, priced at current market. The least certain and most surprise-prone component.

Actual production rate

Units per labor hour achieved to date versus the estimate's assumption, the driver of the self-perform labor forecast.

Projected remaining quantity

Units still to install, from the takeoff net of installed. Errors here scale the entire remaining-labor estimate.

Known changes and pending scope

Directed or probable changes not yet in the budget, loaded so the forecast reflects expected reality.

Risk and contingency allocation

Probable rework, weather, and identified risks, carried explicitly rather than assumed away.

Cost to complete

The forward estimate of remaining cost per line, the object itself.

Estimate at completion

Cost incurred plus cost to complete, the number that drives projected margin and revenue recognition.

Forecast basis note

The stated rationale for each line's forecast — productivity, quote, judgment — so reviewers can challenge the reasoning, not just the number.

Failure modes — how it breaks

Remaining budget used as cost to complete

The team simply carries remaining budget forward as the estimate to complete, ignoring that completed work already overran. The forecast assumes the rest of the job will magically outperform the part already built, and the loss stays hidden until the money runs out.

Straight-line productivity assumption

Remaining labor is projected at the estimated production rate even though the field is achieving 80 percent of it. The forecast systematically understates remaining labor cost, and the gap compounds every period the assumption survives.

Netting offsetting variances

A hot line and a cold line are combined into a total that looks on plan, so the forecast hides a real overrun behind an unrelated saving. When the saving turns out to be timing rather than performance, the overrun stands alone and larger than anyone expected.

Uncommitted scope priced at stale budget

Remaining work not yet bought out is carried at the original budget while the market has moved. The buyout comes in high, and the surprise lands late in the job when there is no room to recover it.

Forecast frozen until the end

Cost to complete never moves period to period because it is rolled forward rather than re-derived. All the deterioration surfaces in one late adjustment, the classic pattern behind sudden profit fade in the final quarter of a job.

Known changes and rework excluded

Directed changes and probable rework are left out because they are not yet in the budget, so the forecast is contractually tidy but operationally false. The cost is real and arrives regardless of whether the paperwork caught up.

Accruals missing from cost incurred

The starting point excludes incurred-but-unbilled cost, so the forecast begins from an understated base. Remaining cost looks smaller than it is, and the estimate at completion is optimistic by the size of the missing accruals.

Metrics — how it is measured

Estimate at completion trend

Movement of estimated cost at completion across periods. Steady upward drift is the clearest early evidence of a deteriorating job.

Cost-to-complete versus remaining budget gap

How far the forward estimate has diverged from naive remaining budget. A gap near zero late in a job is often a warning that the forecast is not being re-derived.

Forecast accuracy at completion

How close each period's estimate at completion was to eventual actual. The definitive measure of forecasting discipline.

Productivity-adjusted labor forecast share

Proportion of self-perform lines forecast from actual production rate rather than straight-lined budget. Measures analytical rigor.

Late forecast movement

Share of total forecast change that occurs in the final quarter of the job. High values indicate a frozen-then-corrected forecast.

Uncommitted remaining exposure

Remaining scope not yet bought out, valued at current market. The unpriced risk still sitting in the forecast.

The AI shift — what actually changes

Conversational

Cost to complete becomes something you interrogate rather than accept. You ask which lines are still forecast at the estimated production rate despite the field achieving less, which remaining scope is carried at stale budget while the market has moved, and how much of the total forecast change is landing in the last quarter — and get the specific lines and productivity data cited.

Generative

The forecast is drafted from evidence rather than assumption. Given cost incurred, installed quantities, and actual production rates, a model builds a line-by-line cost to complete, projecting remaining labor from achieved productivity and pricing uncommitted scope at current rates, and states the basis for each line so a human can challenge the reasoning instead of re-deriving it.

Orchestrated

Cost to complete stops being a periodic manual exercise. It pulls installed quantities from field reporting, remaining committed value from commitments, and known changes from the change log, and it keeps the estimate at completion synchronized with the job cost report and WIP schedule so revenue recognition is never running on a stale forecast.

Autonomous

The routine re-derivation runs unattended: incurred cost and accruals refreshed, remaining labor projected from live productivity within tolerance, uncommitted scope re-priced, and any line whose forecast moves materially or diverges from productivity evidence flagged — while humans own the risk loading, the treatment of known changes, and any forecast that would change reported earnings.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — You suspect the cost-to-complete on a job is optimistic and want to pressure-test it.

Pressure-test this project's cost to complete. For every self-perform cost code, compare the production rate assumed in the remaining-labor forecast against the actual units-per-hour achieved to date, and re-project remaining labor at the achieved rate; quantify the difference. Identify remaining scope that is not yet committed and is still valued at original budget while current market pricing has moved. Show me offsetting variances that are being netted into an on-plan total, and separate them. Tell me how much of the total forecast change to date has occurred in the last quarter of the schedule. Cite the productivity data and commitments behind each finding, and give me a revised estimate at completion if the forecast were rebuilt from actual productivity.

What good output looks like: A rebuilt, productivity-based estimate at completion that exposes straight-lined labor, stale uncommitted pricing, and netted variances, with the earnings impact of correcting each quantified and cited.

Follow-ups:

• Which lines are the biggest hidden overruns once you stop netting them?
• What is the earnings impact if we adopt the productivity-based forecast?
• Which uncommitted scopes should we buy out now to cap the exposure?

Generative — Building the period's cost to complete from field productivity and commitments.

Build a line-by-line cost to complete for this job from the data attached. For each cost code, start from cost incurred plus accruals, then forecast remaining cost: for self-perform lines, project remaining labor using the actual units-per-hour achieved to date and the remaining quantity from the takeoff; for subcontracted lines, use remaining committed value plus any recorded changes; for uncommitted scope, price at current market and note it as an estimate. Load known changes and probable rework explicitly. Roll up to an estimate at completion and projected margin without netting offsetting lines. For every line, state the basis of the forecast — productivity, quote, judgment — and flag any line where the data does not support a confident forecast.

What good output looks like: A per-line cost to complete rolled up to an estimate at completion, with self-perform labor derived from actual productivity, uncommitted scope market-priced, offsetting lines preserved, and a stated basis and confidence flag per line.

Follow-ups:

• Redo it with a downside case: labor at the worst production rate we have seen this job.
• Show the estimate at completion with and without the known-but-unpriced changes.
• Which lines carry the most forecast risk, ranked by potential dollar swing?

Orchestrated — You want cost to complete assembled from the connected systems and kept in sync downstream.

Assemble this period's cost to complete across the connected systems and keep it consistent with everything downstream. Pull cost incurred and accruals from the job cost data, installed quantities from field progress reporting, remaining committed value from the commitment records, and directed or pending changes from the change log. Re-derive remaining labor from achieved productivity and re-price uncommitted scope at current market. Roll up to estimate at completion, and reconcile it against the projected final cost on the job cost report and the percent complete feeding revenue recognition, flagging any inconsistency between them. Return the cost to complete, the estimate at completion, and a reconciliation note listing anything that does not agree across the three, with the source records cited.

What good output looks like: A cross-system cost to complete reconciled against the job cost report and revenue recognition, with disagreements between the three surfaced and attributed rather than silently averaged.

Follow-ups:

• Where the job cost report and cost to complete disagree, which is stale and why?
• Show the revenue recognition impact of adopting this estimate at completion.
• List the field quantities you used and flag any that look inconsistent with cost incurred.

Autonomous — Standing policy for how cost to complete should be maintained between reviews.

Maintain cost to complete continuously under these rules. Refresh cost incurred and accruals as cost posts. Re-derive self-perform remaining labor from the latest achieved production rate, but only within your forecast tolerance — where the productivity-based forecast diverges from the standing forecast by more than the threshold, flag it for the project manager rather than overwriting it. Re-price uncommitted remaining scope at current market and flag material moves. Keep the estimate at completion reconciled with the job cost report and the percent complete used for revenue recognition. Never load or remove a known change, never set the risk or rework allowance, and never adopt a forecast that would change reported earnings without human approval — route those with the productivity evidence and your reasoning, and give me a weekly exception queue of lines that diverged, moved materially, or reconcile poorly.

What good output looks like: A continuously re-derived cost to complete where routine productivity and pricing refreshes are automatic within tolerance, risk loading and earnings-affecting forecasts stay human-owned, and every material divergence is escalated with evidence.

Follow-ups:

• Show me the lines you flagged for productivity divergence and how the PM resolved them.
• Report your forecast accuracy this quarter against eventual actual cost.

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Remaining budget as forecast

   Cost to complete is just remaining budget. It ignores completed-work performance, so losses stay hidden until the money runs out.

1. Level 1 — Manually re-estimated

   The team re-judges remaining cost per line each period, but largely from experience rather than measured productivity. Better than remaining budget, still vulnerable to optimism.

2. Level 2 — Productivity-based

   Self-perform labor is forecast from actual units-per-hour, uncommitted scope is market-priced, known changes and risk are loaded explicitly, and offsetting lines are preserved. The forecast is evidence-based.

3. Level 3 — Assisted and integrated

   The forecast is drafted from field productivity and commitments, reconciled against the job cost report and revenue recognition, and divergences are flagged for review.

4. Level 4 — Operated

   Routine re-derivation runs unattended within tolerance, while humans own risk loading, treatment of known changes, and any forecast that would change reported earnings.

Common questions

Why is cost to complete not just remaining budget?

Because remaining budget assumes the rest of the job goes exactly to plan, even when the completed work did not. Cost to complete is a fresh judgment of what the remaining work will actually cost given the productivity, pricing, and risk the field has revealed. Using remaining budget as the forecast is the single most common way a job's loss stays hidden until the budget is exhausted, at which point nothing can be done about it.

How does cost to complete affect reported profit?

Directly and powerfully. Estimated cost at completion is cost incurred plus cost to complete, and it sets both the projected margin and the percent complete used to recognize revenue under a cost-based input method. An understated cost to complete overstates percent complete, which overstates recognized revenue and earnings. This is precisely why sureties and auditors scrutinize it, and why the discipline of re-deriving it from evidence each period is a matter of financial integrity, not just project control.

Why build cost to complete per line instead of one number for the job?

Because a single job number nets offsetting risks and hides the ones that matter. A project can look on plan in total while a self-perform line runs badly over and an unrelated subcontract line runs under, and the moment the under turns out to be timing rather than performance, the overrun stands alone. Building it per cost code preserves the risk profile and forces the forecast to confront each scope on its own evidence.