Percent Complete

Definition — what it is

Percent complete is the measure of how much of a contract's total work has been performed as of a point in time, expressed as a proportion and used to recognize revenue and derive over/under billing. The dominant method in construction is cost-to-cost, where percent complete equals cost incurred to date divided by estimated cost at completion, but it can also be measured by installed units, by milestones, or by an assessed physical-progress judgment. It is not the same as percent billed, which follows the pay-application schedule, nor the same as the schedule's percent-of-time-elapsed, which follows the calendar. Because percent complete is the lever that translates cost into recognized earnings, its integrity is inseparable from the integrity of the estimate at completion beneath it: understate remaining cost and percent complete overstates, pulling profit forward that has not been earned.

Also known as: Percentage Complete, Progress Percentage, Completion Percentage, POC

Why it matters — what it protects

Percent complete is the mechanism by which construction revenue is recognized, so it sits directly on the income statement. Under a cost-based input method, earned revenue is percent complete times contract value, and a small movement in the figure moves reported profit for the whole company. This is why percent complete is one of the most consequential and most scrutinized numbers a contractor produces.

It is the honest broker between cost and billing. Over/under billing exists precisely because billed amounts and earned amounts diverge, and percent complete is what defines earned. A percent complete that is stale, soft, or measured inconsistently corrupts the over/under position and, through it, the entire WIP schedule and the working-capital picture.

Cost-to-cost percent complete has a built-in vulnerability that makes method choice matter. Because it divides cost incurred by estimated cost at completion, front-loaded cost — expensive mobilization, stored materials, early equipment — can make a job look further along than it physically is, overstating earned revenue. Recognizing where cost-to-cost misleads, and adjusting for stored materials or using an alternative measure, is a mark of accounting maturity.

It disciplines the relationship between physical reality and financial reporting. The temptation is to let percent complete drift on an optimistic estimate rather than confront a rising cost to complete, which quietly overstates earnings until the correction forces a fade. Keeping percent complete tied to a rigorously re-derived estimate at completion is what keeps reported progress honest.

Lifecycle — how it moves

1. Method selection

   The contractor selects the percent-complete method — cost-to-cost, units-installed, milestones, or physical assessment — and applies it consistently. The choice must fit the work and be stable across periods for earnings to be comparable.

2. Cost and quantity capture

   Cost incurred to date, or installed quantities, are captured as of cutoff. Missing accruals or uncounted stored materials distort the numerator and therefore the percentage.

3. Estimate-at-completion refresh

   For cost-to-cost, the denominator is refreshed from cost to complete. This is where percent complete inherits all the integrity risks of the forward forecast; a stale estimate at completion makes percent complete overstate.

4. Adjustment for distortions

   Stored materials not yet installed and front-loaded costs are adjusted out where they would overstate physical progress, so cost-to-cost does not credit work that has not been performed.

5. Calculation

   Percent complete is computed per job and, where needed, per phase, and applied to contract value to derive earned revenue. Consistency of grain matters as much as consistency of method.

6. Cross-check against physical progress

   The financial percent complete is sanity-checked against the superintendent's physical assessment and the schedule. A large gap between the two is a red flag that cost is running ahead of, or behind, actual installation.

7. Feed to revenue and over/under

   The figure flows into revenue recognition and the over/under calculation on the WIP schedule. Its downstream reach is why an error here is a financial-statement error, not a project-control one.

8. Period trend review

   Percent complete is trended and reconciled against prior periods, because non-monotonic movement — completion going backward — signals a corrected estimate and often an emerging loss.

Anatomy — the data it carries

Method

Cost-to-cost, units, milestones, or physical assessment. Determines what percent complete actually measures and must be consistent across periods.

Cost incurred to date

For cost-to-cost, the numerator — actual plus accruals. Sensitive to accrual completeness and to front-loaded cost.

Estimated cost at completion

The denominator for cost-to-cost. Percent complete inherits every optimism or staleness in this forecast.

Installed quantity and total quantity

For units-based measurement, the physical numerator and denominator, which resist the front-loading distortion cost-to-cost suffers.

Milestone schedule and weights

For milestone measurement, the defined completion points and their revenue weights, which must sum coherently to 100 percent.

Stored materials adjustment

Cost of materials purchased but not installed, backed out so paid-for-but-unbuilt work does not inflate progress.

Physical percent complete

The superintendent's independent field assessment, the reality check on the financial figure.

Contract value

The revenue base percent complete is applied to, including approved changes, so earned revenue reflects current scope.

Earned revenue to date

Percent complete times contract value, the output that flows to the income statement.

Prior-period percent complete

Last period's figure, carried so movement — and any backward movement — is visible and explainable.

Method-consistency flag

Marker that the same method was applied as prior periods, guarding against a method switch that silently changes earnings.

Failure modes — how it breaks

Front-loaded cost overstating progress

Under cost-to-cost, heavy early mobilization, equipment, or stored materials make the job look further along than the physical work justifies. Earned revenue is pulled forward, and it must be given back later when physical progress lags the money spent.

Stale estimate at completion inflating the percentage

The denominator is not refreshed while cost keeps posting, so percent complete rises toward 100 while the job is physically well short. The overstatement is corrected only when the estimate is finally updated, producing a fade.

Method inconsistency between periods

Switching from cost-to-cost to milestones, or measuring some jobs one way and some another, makes earned revenue incomparable across periods and jobs. Earnings appear to move when only the ruler changed.

Uncounted accruals distorting the numerator

Cost incurred but not invoiced is excluded, so percent complete understates in the period the cost was earned and jumps when the invoice posts. Progress appears to lurch on invoice timing rather than work performed.

Financial and physical progress diverging unnoticed

The cost-based percentage is never cross-checked against the superintendent's field assessment, so a job spending ahead of installation reports healthy progress. The divergence is the early signal, and ignoring it defers the reckoning.

Completion moving backward without explanation

Percent complete drops from one period to the next because the estimate at completion rose, but the movement is presented without cause. A backward step is almost always an emerging loss, and burying it delays the response.

Stored materials never backed out

Materials paid for but sitting in the yard are counted as incurred cost, crediting progress for work not performed. Percent complete overstates until the materials are actually installed, mis-timing earnings.

Metrics — how it is measured

Percent complete versus physical assessment gap

Difference between the cost-based figure and the field's physical judgment. A persistent gap signals front-loading, stale estimates, or misreporting.

Percent-complete movement per period

Progress recognized each period. Backward movement or a late surge both flag estimate corrections rather than genuine work.

Stored-materials share of incurred cost

Proportion of cost that is paid-for-but-uninstalled material. High values mean cost-to-cost is overstating physical progress.

Method-consistency rate

Share of jobs measured with the same method across periods. Inconsistency makes earned revenue incomparable.

Estimate-at-completion refresh rate

How often the denominator is genuinely re-derived. A rarely refreshed denominator produces a drifting, overstated percentage.

Earned-versus-billed alignment

How closely earned revenue tracks billings, an indirect check that percent complete and billing are telling the same story.

The AI shift — what actually changes

Conversational

Percent complete becomes something you can challenge, not just accept. You ask which jobs have a large gap between cost-based and physical progress, which are riding a stale estimate at completion, and how much of incurred cost is stored materials inflating the figure — and get the specific jobs and the underlying cost and field data cited.

Generative

The calculation is drafted with its adjustments and cross-checks. Given cost incurred, estimate at completion, installed quantities, and stored materials, a model computes percent complete each way, backs out stored materials, reconciles the cost-based figure against physical progress, and presents the earned revenue with the divergences and their likely causes stated for review.

Orchestrated

Percent complete stops being an isolated calculation. It pulls cost from the job cost report, the estimate at completion from cost to complete, installed quantities from field reporting, and stored materials from receiving, computes and adjusts the figure, and flags any job where the cost-based and physical measures disagree with the source records attached — so the number that drives revenue is triangulated, not single-sourced.

Autonomous

The routine computation runs unattended: percent complete derived and stored-materials-adjusted consistently, cross-checked against physical progress, and any job where the two diverge or where completion moved backward flagged — while humans own the method, the treatment of stored materials and front-loading, and any percent complete that changes recognized revenue.

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 want to know whether reported percent complete is honest before it hits revenue.

Audit percent complete across this portfolio before it feeds revenue recognition. For each job, show the cost-to-cost percent complete and, where available, the superintendent's physical assessment, and rank jobs by the gap between them. Identify jobs where the estimate at completion has not been refreshed this period, since a stale denominator inflates the figure. Quantify stored materials counted in incurred cost that have not been installed, and recompute percent complete with them backed out. Flag any job whose percent complete moved backward since last period and explain the estimate change behind it. Cite the cost, estimate, and field data behind each finding, and tell me the earned-revenue impact of correcting the distortions.

What good output looks like: A percent-complete audit that ranks financial-versus-physical gaps, isolates stale denominators and stored-materials distortion, explains backward movement, and quantifies the earned-revenue impact of correcting each.

Follow-ups:

• Which jobs are pulling profit forward through front-loaded cost, and by how much?
• For the biggest financial-versus-physical gaps, which number do you trust and why?
• Recompute total earned revenue with stored materials backed out everywhere.

Generative — Computing percent complete with proper adjustments for the period close.

Compute percent complete for these jobs for the period close. Use cost-to-cost as the primary method, with cost incurred plus accruals over the current estimate at completion, and back out stored materials that have been paid for but not installed. Where units-installed data exists, also compute a units-based percent complete as a cross-check. Apply the result to current contract value to derive earned revenue per job. Compare the cost-based figure to the superintendent's physical assessment and flag any job where they diverge by more than the threshold. Carry prior-period percent complete so movement is visible, and flag any job whose completion moved backward with the estimate change that caused it. Return the computations, adjustments, cross-checks, and earned revenue, with divergences and their causes stated.

What good output looks like: Percent complete computed with stored-materials adjustment and a units-based cross-check, applied to contract value, with physical-progress divergences and backward movement flagged and explained rather than smoothed.

Follow-ups:

• Show earned revenue with and without the stored-materials adjustment.
• For jobs with a big physical-versus-cost gap, propose which measure to report and why.
• Confirm the method matches what we used last period for each job.

Orchestrated — You want percent complete triangulated across systems before it drives revenue.

Derive percent complete across the connected systems for this period. Pull cost incurred and accruals from the job cost report, the estimate at completion from each job's cost to complete, installed quantities from field progress reporting, stored materials from receiving, and the physical assessment from the superintendent's report. Compute cost-to-cost percent complete, back out stored materials, and produce a units-based figure where data allows. Reconcile the cost-based measure against physical progress and against the units-based measure, and flag every job where the three disagree materially. Hand the reconciled percent complete to revenue recognition and note any job whose earned revenue would change if the physical measure were adopted instead. Return the figures, the triangulation, and the exceptions with source records cited.

What good output looks like: A triangulated percent complete reconciled across cost, units, and physical assessment, with material disagreements and their revenue impact flagged and each measure sourced, before it feeds revenue.

Follow-ups:

• For the jobs where the three measures disagree, which is most defensible for reporting?
• Show the revenue difference between the cost-based and physical measures per flagged job.
• Which jobs' estimates at completion are stale enough to invalidate the cost-based figure?

Autonomous — Standing policy for computing and monitoring percent complete.

Compute and monitor percent complete continuously under these rules. Use the standing method per job, apply cost incurred plus accruals over the current estimate at completion, and always back out stored materials. Cross-check the cost-based figure against the superintendent's physical assessment and the units-based measure where available, and flag any material divergence. Flag any job whose completion moves backward, any job on a stale estimate at completion, and any job where stored materials are a large share of incurred cost. Never change the percent-complete method, never adjust the estimate at completion, never decide the treatment of front-loaded cost, and never release a percent complete into revenue recognition without human approval — route those with the triangulation evidence, and give me an exception queue of divergences, backward movements, and stale-estimate jobs rather than every routine calculation.

What good output looks like: A monitored percent complete where routine computation and cross-checking are automatic, method and estimate choices stay human-owned, and every divergence, backward move, or stale-estimate distortion is escalated with evidence before revenue.

Follow-ups:

• Show me the jobs you flagged for physical-versus-cost divergence and how they were resolved.
• Report how often the cost-based figure has overstated physical progress this year.

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

Maturity — locate yourself honestly

0. Level 0 — Guess or percent billed

   Percent complete is estimated loosely or proxied by percent billed. Revenue recognition is disconnected from actual progress and fade is inevitable.

1. Level 1 — Cost-to-cost, unadjusted

   Percent complete is computed cost-to-cost each period. It is consistent, but stored materials and front-loading distort it and it is rarely cross-checked against the field.

2. Level 2 — Adjusted and cross-checked

   Stored materials are backed out, the estimate at completion is refreshed, and the cost-based figure is reconciled against physical progress. Percent complete is honest and its movement is explainable.

3. Level 3 — Triangulated and assisted

   The figure is derived across systems, computed multiple ways, and divergences between cost, units, and physical progress are flagged for review before revenue.

4. Level 4 — Operated

   Routine computation, adjustment, and cross-checking run unattended, while humans own the method, stored-materials treatment, and any percent complete that changes recognized revenue.

Common questions

Why is cost-to-cost the dominant method if it can be distorted?

Because it is objective, auditable, and directly tied to the cost data a contractor already maintains, which makes it defensible and consistent. Its weakness is that front-loaded cost — mobilization, equipment, stored materials — can make a job look further along than it physically is. Mature teams keep cost-to-cost but back out stored materials and cross-check against physical progress, which preserves the method's objectivity while correcting its known distortion.

How can percent complete go backward?

It goes backward when the estimated cost at completion rises faster than cost is incurred, because cost-to-cost divides cost by that estimate. A jump in the estimate to complete means the same cost incurred now represents a smaller share of a larger total, so percent complete falls. Backward movement is almost always the signal of an emerging loss being recognized, which is why it must be explained rather than smoothed over.

Should stored materials count toward percent complete?

Generally not, because they represent cost paid but work not yet performed, and counting them credits progress for materials still sitting in the yard. Backing them out keeps the cost-based percentage aligned with physical installation, so earned revenue is not pulled forward. Owners may still pay for properly stored and secured materials on a pay application, but that is a billing question separate from how much work has actually been earned.