Change Order Review
Review a proposed change order against the original contract. Flags items that were already in scope, items with excessive pricing, items missing backup, and computes a recommended CO value.
What it does
Change Order Review takes the original contract or scope plus a proposed CO and evaluates each CO line item against the contract. Every line gets a status — JUSTIFIED / DISPUTED / EXCESSIVE / MISSING_BACKUP — with a contract-section reference explaining why. The engine also flags classic CO-gaming tactics: scope creep, inflated markup, vague line-items, duplicate charges.
Output includes a recommended CO value (sum of JUSTIFIED lines at supported prices) and savings relative to the requested CO amount.
When to use it
- CO request just landed — decide how to respond.
- Negotiating a CO that feels bloated.
- Auditing approved COs across a project for pattern analysis.
What to upload
- Original contract / PO / scope of work (the reference)
- Proposed change order document
Step by step
Open the engine
Sidebar → Engines → Change Order Review.
Upload contract + CO
Both required.
Run
30–60 seconds.
Read the verdict card
CO title + amount + recommended amount + verdict (JUSTIFIED / PARTIALLY_JUSTIFIED / DISPUTED / EXCESSIVE).
Review each line
Filter by status. Click a line to see contract-section reference and note.
Check manipulation flags
If present, the engine has detected CO-gaming patterns. Read carefully before responding.
Understanding the results
CO title, CO number, requested amount, recommended amount, savings, verdict.
This CO / original contract value — helpful context for whether a CO is large or small in proportion.
Every CO line item, status, in-original-scope flag (YES / no), contract reference, note.
Red-bordered section listing any detected CO-gaming tactics (duplicate billing, vague line items, excessive markup, already-in-scope).
2–3 sentence executive summary.
Every control, explained
Run analysisOne run.
Try with sample dataBridgeport CO #3 — $847K request on a $45M contract with a documented scope dispute.
Filter by statusNarrow to DISPUTED, EXCESSIVE, MISSING_BACKUP, or JUSTIFIED.
Export PDFNegotiation-ready report with recommended amount, contract references, line-item detail.
Export XLSXRaw line-item data.
Chain to NegotiationOpen Negotiation Intelligence with this CO's leverage points pre-loaded.
Chains
Chains into
Chained from
Exports
- PDF — negotiation-ready report with contract references.
- XLSX — raw line-item data.
- CSV — flat status + amount list.
Troubleshooting
Engine cites the closest matching section; contracts with unusual numbering systems can throw it off. Use chat to correct.
Upload the backup documentation (T&M sheets, subcontractor quotes) as a third document.
The Bridgeport sample is designed to show manipulation flags firing — the engine is intentionally showing its worst-case output. Real-world COs score milder on average.