# Profit Fade Analysis

> The report that tracks how a job's estimated gross margin erodes from bid to close, exposing which projects lose money slowly and why - and whether the fade was predictable.

- Source: https://briq.ai/acu/object/profit-fade-analysis
- Department: Reporting, Forecasting & Analytics (https://briq.ai/acu/department/reporting)
- Catalog code: RPT 301 · Level: Advanced · Track: Finance · 12 min read
- Also known as: Margin Fade, Fade Analysis, Gross Profit Fade, Job Slippage Analysis

## Definition

Profit fade analysis measures the decline in a job's projected gross profit over the life of the project, comparing the margin at bid or buyout to the margin at each subsequent forecast and at final close. It is a diagnostic report that isolates the direction and cause of margin change: whether it came from cost overruns, scope changes billed below margin, unrecovered change work, or estimate error. Its central insight is that most construction losses are not sudden - they accrue quietly across reporting periods, and a job that ends 6 points below bid usually showed the fade months earlier in the cost-to-complete if anyone was watching. It is not the same as a budget vs. actual snapshot; profit fade is a longitudinal view of the margin forecast itself, tracking how the estimate at completion moved and why.

## Why it matters

Profit fade is the pattern that surety underwriters and lenders read most carefully, because it reveals whether a contractor's forecasts are honest. A firm whose jobs consistently fade from bid to close is either bidding too optimistically or losing control in execution, and either way its work-in-progress schedule cannot be trusted at face value. Consistent fade is one of the fastest ways to lose bonding capacity, regardless of whether the company is still profitable in aggregate.

It exposes losses that aggregate reporting hides. A company can report a healthy blended margin while a third of its jobs are quietly fading, because the winners subsidize the losers on the income statement. Fade analysis forces each job to answer for itself, which is the only way to find out whether the business is genuinely profitable or just averaging its way out of trouble.

The report is where estimating accountability lives. When a job fades, the analysis has to distinguish an estimate that was wrong from execution that failed, and that distinction determines whether the fix is in the takeoff or in the field. Contractors that never separate the two keep re-bidding the same optimistic assumptions and re-losing money on the same work.

Fade timing is itself a signal. A margin that fades steadily from period one is usually an estimating problem; a margin that holds and then drops sharply near close is usually an execution or claims problem - unrecovered change work, a subcontractor default, or a schedule overrun burning general conditions. Reading the shape of the fade curve tells you where to look before you read a single cost code.

## Lifecycle

1. **Baseline margin capture** — The bid margin and the buyout margin are recorded as the fade baseline. Buyout margin is usually the more honest starting point because it reflects real subcontract and material prices rather than estimate allowances, and the gap between bid and buyout margin is itself worth watching.
2. **Periodic forecast** — At each close, the estimate at completion is recomputed from actuals plus cost-to-complete, and the projected margin is compared to the prior period. This is the heartbeat of the analysis: fade is the period-over-period change in projected margin, not just the gap from bid.
3. **Cause attribution** — Each period's fade is decomposed into drivers - cost overrun, low-margin change work, unrecovered changes, general-conditions burn, or estimate correction. Attribution is the hard part and the whole point; a fade number without a cause is just anxiety.
4. **Cross-job aggregation** — Fade is rolled up across the portfolio to find patterns: whether a particular project type, estimator, region, or client consistently fades. The portfolio view turns individual jobs into a systemic diagnosis.
5. **Forecast integrity check** — The fade history is used to test whether current forecasts are believable. A job that has never revised its margin all year is often not being forecast honestly, and a suspiciously stable forecast gets scrutiny before it collapses at close.
6. **Intervention** — Where fade is real and continuing, management acts - a recovery plan, a claim for unrecovered changes, a subcontractor conversation, or a decision to accept the loss and protect the relationship. The report's value is realized here or not at all.
7. **Post-close reconciliation** — At final close, actual margin against bid margin becomes the historical record. The fade is finalized and attributed, and the lessons feed estimating and operations for the next similar job.
8. **Estimating feedback loop** — Systematic fade on a job type is fed back into the estimate assumptions - a labor productivity factor, a general-conditions rate, a contingency level - so the next bid does not repeat the loss. Skipping this step is why the same fade recurs.

## Anatomy

- **Bid margin** — Estimated gross profit percentage at award. The original promise the job was sold on, and the top of the fade curve.
- **Buyout margin** — Margin after subcontracts and major materials are bought out. Often the truest baseline because allowances have become real prices.
- **Current projected margin** — Gross profit percentage from the latest estimate at completion. The number that moves each period and defines the fade.
- **Period-over-period fade** — Change in projected margin since the last close, in points. The heartbeat metric - a job that fades every period is out of control.
- **Cumulative fade from bid** — Total margin points lost from bid to the current forecast. The headline, but only meaningful once attributed to cause.
- **Fade cause code** — The attributed driver - overrun, low-margin change, unrecovered change, GC burn, estimate error. Without it the report cannot drive a fix.
- **Estimate at completion** — Projected final cost from actuals plus cost-to-complete. The denominator of the margin, and the number most vulnerable to optimism.
- **Approved change margin** — The margin earned on change orders, often lower than base contract margin. Low-margin change growth dilutes overall margin even with no overrun.
- **Unrecovered change work** — Extra work performed but not yet approved or paid. A frequent and dangerous fade driver because it hides as cost with no offsetting revenue.
- **General conditions burn rate** — Time-dependent overhead consumed per period. A schedule slip fades margin here even when direct costs are on plan.
- **Contingency drawdown** — How much of the estimate's contingency has been consumed and how fast. Early full consumption is a leading fade indicator.
- **Forecast revision date** — When the projection was last genuinely updated. A stale forecast masks fade that has already happened.

## Failure modes

- **The frozen forecast** — A project manager stops revising the cost-to-complete because a revision would show a loss. The margin holds artificially flat for months and then collapses at close when reality can no longer be deferred. The frozen forecast is the single most common way fade is hidden until it is unrecoverable.
- **Fade without attribution** — The report shows margin dropping but never assigns a cause, so management sees a problem it cannot act on. An unattributed fade number generates meetings and no decisions, and the same fade recurs next quarter.
- **Low-margin change work mistaken for overrun** — Margin dilutes because change orders were priced at a lower margin than the base contract, not because costs ran over. The team hunts for an execution problem that does not exist while the real issue is a pricing discipline problem in the change process.
- **Unrecovered change work booked as cost** — Extra work is performed on a promise and the cost lands in the ledger, but the change order is never approved and the revenue never materializes. The fade looks like an overrun; it is actually a claims and documentation failure.
- **Winners masking losers in the aggregate** — The portfolio margin looks healthy, so nobody drills into the jobs that are fading. The subsidy runs until a strong quarter ends, and then the accumulated losers surface all at once with no cushion left.
- **Overhead absorption confused with job fade** — A change in how indirect costs or equipment rates are absorbed shifts a job's margin without any real performance change. Treating an absorption change as fade sends the team chasing a phantom.
- **No estimating feedback** — A job type fades every time, the analysis correctly attributes it to an optimistic productivity assumption, and the estimating standard is never changed. The report diagnoses the disease and the company keeps prescribing the same bid.

## Metrics

- **Cumulative fade from bid** — Margin points lost from award to current or final. The core outcome metric across a job and a portfolio.
- **Period fade rate** — Average margin points lost per reporting period. A steady negative rate signals a systematic problem, not a one-time event.
- **Fade frequency** — Share of jobs that finish below bid margin. A high frequency undermines the credibility of every forecast the company produces.
- **Fade concentration** — How much total fade comes from the worst jobs. High concentration means a few projects, not a broad problem - and a targetable fix.
- **Forecast revision frequency** — How often the estimate at completion is genuinely updated. Low frequency is a leading indicator of frozen forecasts and late surprises.
- **Bid-to-buyout margin change** — Points gained or lost between estimate and buyout. Isolates estimating optimism from execution.
- **Unrecovered change balance** — Dollar value of extra work performed without approved change orders. A rising balance is fade waiting to be recognized.

## The AI shift

- **Conversational** — Instead of building a fade curve by hand across periods, you ask how each job's projected margin has moved since bid, which jobs are fading fastest, and whether a given fade is coming from overrun, low-margin changes, or unrecovered work - with the period-by-period forecasts and the driving transactions cited so the causal story is auditable.
- **Generative** — The analysis narrative is drafted from the underlying forecast history: a job-level explanation of when the margin turned, what drove each period's fade, and whether the current forecast is internally consistent, written in the language an executive committee or surety would expect and grounded in the specific cost-to-complete revisions that moved the number.
- **Orchestrated** — Fade stops being reconstructed after the fact. Each period's margin change is decomposed automatically by tracing it to job cost variances, change-order margins, unrecovered change balances, and general-conditions burn, then cross-checked against the WIP schedule and the schedule of values so the attributed cause is tied to real records rather than a manager's memory of the month.
- **Autonomous** — The monitoring runs continuously: forecasts that have gone too long without revision flagged as integrity risks, margin turns detected as they happen with a drafted cause attached, unrecovered change balances tracked against fade, and portfolio patterns surfaced by estimator, client, and job type - while humans decide whether a fade is real, own every forecast revision, and make every intervention and estimating-standard change.

## Prompts

### Conversational — Preparing the quarterly margin review for ownership and the surety.

```text
Analyze profit fade across all active jobs this quarter. For each, show bid margin, buyout margin, prior-period projected margin, current projected margin, period fade in points, and cumulative fade from bid. Attribute each job's fade to a primary cause: cost overrun, low-margin change work, unrecovered change work, general-conditions burn, or estimate correction. Flag any job whose forecast has not been revised in more than 60 days as a forecast-integrity risk regardless of its reported margin. Rank by cumulative fade in dollars and tell me where the fade is concentrated.
```

**Expected output:** A ranked, attributed fade table separating estimating from execution and flagging frozen forecasts - not a single blended margin number.

**Follow-ups:**

- For the three worst faders, is this an estimating problem or an execution problem?
- Which jobs are holding suspiciously flat, and what would a realistic forecast show?
- How much of total portfolio fade comes from unrecovered change work we could still pursue?

### Generative — You need to write the fade narrative for a job the executive committee is asking about.

```text
This job bid at 14 percent gross margin and is now forecasting 8 percent. Draft the profit fade narrative for the executive committee. Read the period-by-period cost-to-complete revisions, identify when the margin turned and by how much each period, attribute the fade to specific drivers with the supporting cost and change records, distinguish estimate error from execution, and state plainly whether the current 8 percent forecast is credible or likely to fade further. Write four to six sentences in factual, non-defensive language, and note what recovery, if any, is realistic.
```

**Expected output:** A grounded, period-aware narrative that names when and why the margin turned and judges the current forecast honestly, with records cited.

**Follow-ups:**

- Redraft to include a claim recovery scenario for the unrecovered change work and its margin effect.
- Write a one-paragraph version for the surety that does not overstate recovery prospects.
- What estimating assumption, if wrong, best explains this fade, and how should we change it?

### Orchestrated — A job's margin dropped this period and you need the cause traced across systems.

```text
This job's projected margin fell 3 points this period. Trace the fade across systems: decompose the margin change into cost overruns by code, change-order margin dilution, unrecovered change work, and general-conditions burn; reconcile it against the WIP schedule and the schedule of values; check whether any of the cost should map to a pending change event that would add revenue; and verify the cost-to-complete assumptions against the current schedule. Return one attribution summary with each component tied to the specific records that support it, and flag anything uncertain rather than guessing.
```

**Expected output:** A decomposed, records-cited attribution of the margin drop reconciled to WIP and SOV, with uncertainty flagged and pursuable recovery identified.

**Follow-ups:**

- If unrecovered changes are a driver, draft the change-order requests we should be pursuing.
- Update the estimate at completion for the confirmed drivers and show the revised margin.
- Which other jobs run by the same team show the same fade signature?

### Autonomous — Standing policy for continuous fade monitoring across the portfolio.

```text
Monitor profit fade continuously across all active jobs under these rules. Each period: recompute projected margin from actuals and cost-to-complete, measure period and cumulative fade, and attribute any material fade to a primary cause with supporting records attached. Flag any forecast not genuinely revised in 60 days as an integrity risk, any job fading for three consecutive periods, and any rising unrecovered change balance. Surface portfolio patterns by estimator, client, and job type. Never revise a cost-to-complete, change a margin forecast, or alter an estimating standard without my approval, and route every confirmed fade with your attribution and recommended action to me.
```

**Expected output:** A continuously attributed fade watch with a short exception queue and full audit trail, where every forecast and estimating change stays with a person.

**Follow-ups:**

- Show me every integrity-risk forecast and every three-period fader this week.
- Which of your fade attributions did I overrule, and how should you adjust?
- Summarize the estimating-standard changes your portfolio patterns would justify.

## Maturity ladder

- **Level 0 — Level 0 - Discovered at close** — Margin fade is only known when the job finishes and the final number lands below bid. There is no periodic view and no chance to intervene.
- **Level 1 — Level 1 - Tracked** — Projected margin is compared to bid each period in a spreadsheet. Fade is visible but rarely attributed to a cause, so it drives worry more than action.
- **Level 2 — Level 2 - Attributed** — Each period's fade is decomposed into overrun, change margin, unrecovered work, and GC burn, and the portfolio is aggregated by estimator, client, and job type.
- **Level 3 — Level 3 - Assisted** — Margin turns are detected as they happen with drafted causes, frozen forecasts are flagged, and attribution is traced automatically to cost and change records for review.
- **Level 4 — Level 4 - Operated** — Fade monitoring runs continuously inside guardrails - recomputation, attribution, integrity flags, and pattern detection - while humans own every forecast revision, intervention, and estimating-standard change.

## FAQ

### Why do sureties care so much about profit fade?

Because fade tells them whether a contractor's work-in-progress schedule can be trusted, and the WIP is the foundation of the surety's entire view of the company. A firm whose jobs routinely fade is either bidding optimistically or losing control in execution, which means its reported backlog margin is overstated and its equity is softer than it looks. A surety would rather underwrite a contractor with thinner margins that hold than a contractor with fat bid margins that fade, because the second one's forecasts cannot be relied on when a job goes wrong.

### Is all fade bad?

No. Some fade is honest recognition catching up with reality - a forecast being revised down because the job genuinely got harder is healthier than a forecast frozen to avoid showing the loss. Small, well-attributed fade that stabilizes is normal. What is dangerous is fade that is unattributed, fade that repeats across a job type, and forecasts that show no fade at all for months and then collapse, because a suspiciously stable margin usually means the forecast is not being kept honest.

### How do you tell an estimating problem from an execution problem?

Look at the shape and timing of the fade and at the bid-to-buyout margin change. Fade that appears immediately at buyout, before any work is performed, is almost always estimating - the bid assumed prices or productivity the market did not support. Fade that appears mid-job as cost overruns against a sound budget is execution. A large gap between bid margin and buyout margin points at the estimate; steady erosion of a good buyout margin points at the field.

## Related objects

- [Work in Progress (WIP) Schedule](https://briq.ai/acu/object/wip-schedule)
- [Cost to Complete](https://briq.ai/acu/object/cost-to-complete)
- [Budget vs. Actual Report](https://briq.ai/acu/object/budget-vs-actual)
- [Bonding Capacity Report](https://briq.ai/acu/object/bonding-capacity-report)
- [Change Order Request (COR)](https://briq.ai/acu/object/change-order-request)
- [Revenue Recognition (ASC 606)](https://briq.ai/acu/object/revenue-recognition)