The short answer
Define the complete population of added, removed, substituted, repriced, or emergency work for a period; stratify high-value, late, repeated, and verbal changes; inspect approval timing, scope clarity, performance evidence, invoice linkage, and final acceptance; then expand when failures share a vendor, approver, property, or workflow.
Operational checklist
Mark your progress, then save a working copy. Selections reset when you leave this page. A checked box is not an approval or evidence of completion.
☐
Changed-scope denominator reconciled
☐
Risk strata defined
☐
Selection reproducible
☐
Request and authority checked
☐
Performance and invoice bridged
☐
Acceptance tested
☐
Common causes evaluated
0 of 7 marked
Key takeaways
- A change order is more than a revised total.
- Approval timing and actual performance are separate tests.
- Sampling starts only after the population is complete.
Reconcile the changed-scope population
Join work-order revisions, vendor quotes, messages, authorization events, invoices, credits, and completion records. Include canceled and zero-dollar changes; excluding them can hide scope movement.
Do not interpret contractual authority or emergency rules from this checklist. Use the approved policy and route disputes appropriately.
Test five evidence layers
| Layer | Review question | Failure signal | Follow-up |
|---|---|---|---|
| Request | What condition required change? | Vague “extra work” | Reconstruct scope |
| Authority | Who approved what and when? | Approval after performance without exception record | Hold or route review |
| Performance | What changed in the field? | Evidence cannot distinguish old/new scope | Verify separately |
| Invoice | Which lines and credits implement change? | Revised total without line bridge | Request variance detail |
| Acceptance | Was changed scope independently closed? | Invoice paid equals completion | Run acceptance check |
Expand on common-cause signals
Expand review when exceptions cluster by vendor, approver, property, change type, after-hours path, or system transition. Preserve the original sample and record why expansion boundaries changed.
Track evidence completeness separately from whether the work or price was appropriate.
Close with population, sample method, exceptions, and corrective owner
Name the reviewed population, cutoff, evidence version, decision owner, unresolved exceptions, next checkpoint, and downstream records updated. Preserve the superseded state; a clean current screen is not a substitute for the correction or exception history.
Reopen the record if the population, authority, source version, external outcome, or dependent report changes after sign-off.
Edge cases
- Emergency work preceded ordinary approval: test the documented exception path.
- Scope decreased but invoice did not: keep the credit question open.
- One message covers several properties: split evidence by work identity.
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.
Continue the workflow
Design maintenance authorization thresholdsInvoice-to-work-order variance reviewMaintenance completion acceptancePortfolio reconciliation sign-off samplingRevision history
2026-09-18
Initial Phase 5 operational article with distinct intent, original artifact, source limits, and AI-assisted technical review.