Worked example 02 · Contractor operations

The extra work is done.
The revenue is missing.

A field instruction needs a traceable path into an approved scope, a current budget, and a billable record.

$45,648

Potential net recovered value / year
After recurring control costs.

Research-based composite. Business figures, savings and risk ratings are modeled assumptions. Proposed controls have not been validated with a business.

The bottleneck

Where the work gets stuck.

The proposed bottleneck is the unowned handoff between field identification, commercial review and billing release. A change can be physically complete while administratively invisible. Improving quote speed alone will not correct an approval that never reaches billing.

The proposed improvement

Change how the work moves.

Connect every change to evidence, authorized direction, an updated budget and a billing record.

82% to 94%Eligible value billed · modeled

$51,840Additional annual billings · modeled

Read the business situation

A foreman receives a request for extra work while the crew is on site. Photos stay on one phone. The PM estimates the price days later. Approval arrives in an email but the job budget and billing schedule are not updated. At closeout, the company reconstructs what happened and negotiates from incomplete records. Some valid work is never recovered.

35 employees, eight active projects and 15 eligible changes per month averaging $2,400 each. All quantities are scenario assumptions.

Follow the work.

Proposed workflow: make the next action and responsibility explicit.

01Capture changeSame-day change ID

02Review authorityScope + notice + cost

03Approve / directAuthorized record

04Update jobBudget + contract value

05Bill + reconcileOne owned status log

What needs to change

Capture at the workfrontForeman records change ID, instruction, date, location, labor, material, photos and affected drawing on the same day.

Contract-specific routingPM checks authorized direction, notice requirements and schedule effects. Establish a documented escalation route for urgent work under the applicable contract.

Single change status logTrack identified, notified, priced, submitted, approved, entered, billed and collected separately. Every next action has one owner and due date.

Weekly reconciliationPM and billing match signed changes to revised contract value, cost forecast and billing schedule. Escalate aging changes before closeout.

How to verify the bottleneck

Hypothesis	Evidence to inspect	Proposed test
Changes are never recorded	Match field diary and time tickets to change IDs.	Sample ten extra-work events from completed jobs.
Proposals wait for complete backup	Time-stamp identification, pricing and submission.	Separate missing evidence from PM workload.
Approval is not transmitted to billing	Trace approved changes to budget and next invoice.	Reconcile all approvals on two active projects.
Nonrecovery has another cause	Separate invalid scope, nonpayment and documentation failure.	Interview PM and billing using dispute reason codes.

The capacity calculation

Measure	Calculation	Modeled implication
Eligible change value	15 changes/month x $2,400	USD 36,000/month
Baseline billed value	82% x $36,000	USD 29,520/month
Target billed value	94% x $36,000	USD 33,840/month
Bottleneck removed	Complete record moves through a defined owner	Unapproved work stays visibly unresolved

Example: change-to-billing control log

Change ID / value	Evidence and status	Next action / owner
CO-017 / $2,400	Directed; photos + hours complete	Price and submit / PM / next day
CO-018 / $3,100	Approved; budget not updated	Enter + advise billing / PM / today
CO-019 / $1,700	Billed; collection outstanding	Follow agreed terms / billing lead

The implementation plan

Days 1-7PM + billing lead

Audit ten changes; map authority and billing cutoff requirements.

Evidence: Agreement on eligible population and baseline recovery.

Days 8-14Foreman + coordinator

Pilot one change ID and evidence record on two jobs.

Evidence: At least 90% same-day capture; all approvals traceable.

Days 15-30PM + commercial lead

Review aging and pending direction twice weekly.

Evidence: No approved item missing from budget reconciliation.

Days 31-90Billing + analyst

Follow invoices through collection and credit adjustments.

Evidence: Matched change cohorts; mature collection outcomes.

What to measure

Measure	Definition	Target	Owner / review
Same-day capture	Changes logged same day / identified changes	At least 95%	Foreman / daily
Approval-to-budget time	Working days from approval to budget update	At most 1 day	PM / weekly
Eligible value billed	Billed eligible value / eligible change value	82% to 94%	Billing / monthly
Collectible uplift	Incremental receipts net credits / incremental billings	Test 95% assumption	Billing / monthly

How to validate the result

Use change cohorts rather than comparing a busy month with a quiet month. Establish which scope is eligible, hold direct work cost constant, and follow the incremental billings through receipts and credits. A 30-day pilot validates process use; collection benefits may require 90 days or longer.

Show the financial effect.

This models recovered collectible value from eligible extra work already performed. It is not payroll savings.

Financial line	USD
Annual eligible value	$432,000
Incremental billings	$51,840
Expected collectible uplift	$49,248
Recurring annual administration	$3,600
Annual net collectible uplift	$45,648
First-year net benefit	$32,540

What if the improvement is smaller?

Adjust the share of the modeled improvement achieved. Control and setup costs stay the same.

Modeled improvement achieved100%

ANNUAL NET ESTIMATE$45,648FIRST YEAR AFTER SETUP$32,540

First year: 10 benefit months, less the full setup allowance. Results are illustrative, not a guarantee.

This is a recovery model for eligible work already performed at the same direct cost. It is not payroll savings. If the target requires new scope, extra direct costs or disputed entitlement, recalculate the model before using it.

Baseline inputs and calculations

These inputs describe the 100% modeled case. The slider changes the share of the proposed improvement achieved.

Illustrative assumption	Value	Units
Eligible changes	15	per month
Average eligible value	2,400	USD/change
Calendar months	12	months/year
Baseline billed share	82%	fraction
Target billed share	94%	fraction
Expected collection share of uplift	95%	fraction
Recurring administration	300	USD/month
One-time implementation allowance	5,500	USD
Benefit months in first year	10	months

Annual eligible value: 15 x $2,400 x 12

Incremental billings: $432,000 x (94% - 82%)

Expected collectible uplift: $51,840 x 95%

Recurring annual administration: $300 x 12

Annual net collectible uplift: Expected collections less administration

First-year net benefit: Annual net x 10/12 - $5,500

What is included and excluded

No acceleration of existing receivables, financing benefit, new sales or automatic full collection is counted. The 95% collection assumption applies only to incremental billed value. Actual write-offs, concessions and additional direct costs reduce the result.

The dispute example describes a mechanism already represented by the recovery-rate model. Its expected-loss reduction is explanatory and must not be added to annual collectible uplift.

Make each risk actionable.

Eight modeled risks. Assessment horizon: one six-month project.

0Critical6High2Moderate0Low

Current ratings are scenario assumptions. Select a risk to see its mitigation, owner and response.

01CommercialEligible extra work lacks contemporaneous proof and becomes unrecoverable.16 · High

The risk: Eligible extra work lacks contemporaneous proof and becomes unrecoverable.

Existing control · assumed: Texts, photos and timesheets held separately.

Proposed mitigation: Create same-day change ID with scope, direction, labor, material and schedule evidence.

Owner & timing: Project manager
Day 7 from pilot start.

Warning trigger: Extra work has no complete record by end of shift.

Contingency: Reconstruct available evidence promptly; escalate disputed scope through agreed process.

How to verify: Complete change file and customer review trail.

Review & status: Weekly during pilot.
Proposed; unvalidated.

Modeled current: L4 × I4 = 16. Target: L3 × I4 = 12.

02AuthorityA verbal field instruction is mistaken for authorized commercial approval.12 · High

The risk: A verbal field instruction is mistaken for authorized commercial approval.

Existing control · assumed: Foreman relies on whoever requested work.

Proposed mitigation: Map authorized representatives and instruction route for each contract.

Owner & timing: Commercial lead
Before pilot.

Warning trigger: Direction comes from someone outside the authority list.

Contingency: Escalate urgent direction to authorized PM; document safety and continuity exceptions.

How to verify: Authority matrix and authorized written direction.

Review & status: Weekly during pilot.
Proposed; unvalidated.

Modeled current: L3 × I4 = 12. Target: L2 × I4 = 8.

03TimingA required notice is late, impairing recovery or schedule relief.12 · High

The risk: A required notice is late, impairing recovery or schedule relief.

Existing control · assumed: PM recalls dates from email.

Proposed mitigation: Record contract-specific notice dates and assign backup reminders.

Owner & timing: Project coordinator
Day 7 from pilot start.

Warning trigger: Notice action due within two working days remains open.

Contingency: Escalate to commercial lead for immediate contract-specific review.

How to verify: Notice log, receipt evidence and review record.

Review & status: Weekly during pilot.
Proposed; unvalidated.

Modeled current: L3 × I4 = 12. Target: L2 × I4 = 8.

04BillingAn approved change is omitted from revised value or an invoice.12 · High

The risk: An approved change is omitted from revised value or an invoice.

Existing control · assumed: Approval remains in a PM inbox.

Proposed mitigation: Reconcile signed approvals to budget and billing schedule weekly.

Owner & timing: Billing lead
Day 14 from pilot start.

Warning trigger: Approved change absent from budget after one working day.

Contingency: Correct current billing record or next eligible application; document timing.

How to verify: Signed change linked to budget revision and invoice.

Review & status: Weekly during pilot.
Proposed; unvalidated.

Modeled current: L4 × I3 = 12. Target: L2 × I3 = 6.

05ScheduleAdded scope is priced without disruption or capacity effects.12 · High

The risk: Added scope is priced without disruption or capacity effects.

Existing control · assumed: Price includes direct hours and material only.

Proposed mitigation: Review crew load, sequence, supervision and completion effects before proposal.

Owner & timing: Project manager
Day 10 from pilot start.

Warning trigger: Change adds hours without a reviewed schedule impact.

Contingency: Prepare resource options and negotiate authorized scope/date direction.

How to verify: Cost build and schedule-impact review.

Review & status: Weekly during pilot.
Proposed; unvalidated.

Modeled current: L3 × I4 = 12. Target: L2 × I4 = 8.

06Data qualityDuplicate IDs or inconsistent versions create double billing or contradictory scope.9 · Moderate

The risk: Duplicate IDs or inconsistent versions create double billing or contradictory scope.

Existing control · assumed: Separate personal spreadsheets.

Proposed mitigation: Use unique IDs, controlled revisions and one approved status owner.

Owner & timing: Project coordinator
Day 10 from pilot start.

Warning trigger: Duplicate ID or two conflicting approved versions found.

Contingency: Freeze affected billing item; reconcile supporting files with PM.

How to verify: Duplicate check and revision history.

Review & status: Weekly during pilot.
Proposed; unvalidated.

Modeled current: L3 × I3 = 9. Target: L2 × I3 = 6.

07CollectionApproved and billed amounts remain unpaid or are offset later.12 · High

The risk: Approved and billed amounts remain unpaid or are offset later.

Existing control · assumed: Collection assumed after approval.

Proposed mitigation: Track collection separately; review credits and disputes by cause.

Owner & timing: Billing lead
Day 21 from pilot start.

Warning trigger: Incremental billings exceed terms without agreed resolution.

Contingency: Escalate through commercial route; revise collectibility assumption.

How to verify: Invoice, cash receipt and credit reconciliation.

Review & status: Weekly during pilot.
Proposed; unvalidated.

Modeled current: L3 × I4 = 12. Target: L2 × I4 = 8.

08AdoptionCrews bypass a cumbersome form and extra work returns to informal channels.8 · Moderate

The risk: Crews bypass a cumbersome form and extra work returns to informal channels.

Existing control · assumed: Forms completed at week end.

Proposed mitigation: Pilot a short mobile-friendly record with one photo attachment path.

Owner & timing: Field superintendent
Day 14 from pilot start.

Warning trigger: Capture compliance below 90% for two weeks.

Contingency: Observe field capture; simplify required data without losing proof.

How to verify: Capture completeness audit against daily work diaries.

Review & status: Weekly during pilot.
Proposed; unvalidated.

Modeled current: L4 × I2 = 8. Target: L2 × I2 = 4.

View the risk map

Likelihood ↑

Impact increases →

Each number matches a risk in the register. Select an occupied cell to open a risk.

Higher likelihood and impact move a risk toward the top right. The Target view shows conditional ratings after the proposed controls.

Where several risks share a cell, it opens the first listed risk. All remain available in the register above.

What could one risk cost?

A large, legitimate scope change becomes a documentation dispute on one project.

Scenario	Probability × event loss	Expected loss
Before	40% × $25,000	$10,000
With proposed controls	20% × $25,000	$5,000
Expected-loss reduction	Before less after	$5,000
Separate mitigation cost	Over this risk horizon	$1,000
Net modeled risk benefit	Reduction less mitigation cost	$4,000

The $25,000 event impact represents unrecovered eligible value after direct work costs have already been incurred. Probabilities are assumed, not derived from public posts.

The dispute example describes a mechanism already represented by the recovery-rate model. Its expected-loss reduction is explanatory and must not be added to annual collectible uplift.

How the ratings work

Score = likelihood × impact, each rated from 1 to 5. Scores 1–5 are Low, 6–11 Moderate, 12–19 High and 20–25 Critical. These are scenario judgments over the stated assessment horizon.

Likelihood: 1 below 5%; 2 from 5% to below 20%; 3 from 20% to below 40%; 4 from 40% to below 70%; 5 at least 70%. Impact: 1 below $1,000; 2 below $5,000; 3 below $20,000; 4 below $75,000; 5 at least $75,000 or potentially severe safety consequences. Impact-5 safety or technical issues require specialist review regardless of score.

Research sources & assumptions

What's your process for reviewing change orders? ↗Reddit · r/ConstructionManagers contributorsPublic thread opened. Advice varies by contract and project; no legal conclusions adopted.
Change order negotiations as owner rep ↗Reddit · r/ConstructionManagers contributorsIndexed post and comment excerpts. Anecdotal negotiation advice; not a recovery-rate study.
Protecting Contractor Margins with a Strong Change-Order Process ↗LinkedIn · Sam Andrus, EMBAPublic authored post opened. Professional commentary promoting an article; no audited savings figures used.
Contractor Gaps in Bidding Process Cause Change Orders ↗LinkedIn · Cory SuppesPublic authored post opened. Bid-stage perspective; does not establish entitlement to any change.

Public discussions informed the problem selection. LeanLine Advisory developed the composite scenario, diagnosis and proposed controls. All company profiles, financial inputs and risk ratings are illustrative assumptions. The sources do not establish an industry-wide ranking of these issues.

One bottleneck.
A measurable difference.

Find a problem that feels familiar.

The crew arrives.
The work is not ready.