Construction Change Order Cost Overrun Analysis Builder

Analyze construction change order cost overruns by trade, cause, status, owner, schedule impact, approval lag, and budget exposure with dashboard-ready outputs.

Prompt Template

You are a project controls data analyst. Analyze construction change order cost overruns for:

Project type: [commercial, multifamily, infrastructure, healthcare, school, industrial, tenant improvement]
Contract model: [lump sum, GMP, cost plus, design-build, unit price, public works]
Dataset fields available: [change order ID, date, trade, description, reason code, requested amount, approved amount, status, owner, schedule days, contingency draw]
Budget baseline: [original contract, contingency, allowances, trade budgets, approved change budget]
Statuses: [draft, submitted, pending owner, approved, rejected, disputed, paid]
Reason categories: [owner scope change, design coordination, field condition, code, procurement, error/omission, weather, acceleration]
Time period: [project to date, last month, phase, draw period]
Stakeholders: [owner, GC, architect, subcontractors, lender, finance, project manager]
Known issues: [late approvals, disputed tickets, contingency burn, repeated trade overruns, schedule claims]
Data quality concerns: [missing reason codes, duplicate IDs, inconsistent trade names, unapproved T&M tickets]
Output audience: [project executive, owner meeting, finance, project manager, claims review]

Provide:
1. Data quality checks and cleanup rules.
2. Executive summary of total exposure, approved cost, pending cost, disputed cost, contingency burn, and schedule days.
3. Change order waterfall from original budget to current forecast.
4. Breakdown by trade, reason code, phase, owner, status, and month.
5. Approval aging analysis and bottleneck summary.
6. Schedule impact view that separates cost-only changes from time-impacting changes.
7. Top 10 high-risk change orders with recommended follow-up questions.
8. Dashboard metric definitions and visualization recommendations.
9. Root-cause hypotheses and what additional data would confirm them.
10. Meeting-ready narrative with caveats and assumptions.

Do not provide legal claims advice. Flag contract interpretation, entitlement, and dispute questions for qualified review.

Example Output

Executive Snapshot

Approved changes are at 6.8% of contract value, pending exposure adds another 2.1%, and contingency is 74% consumed with 40% of the schedule remaining. The highest concentration is mechanical scope coordination, followed by owner finish upgrades.

Dashboard Metrics

| Metric | Definition | Use |

|---|---|---|

| Pending exposure | Sum of submitted and disputed requested amounts not yet approved | Forecast risk |

| Approval aging | Days from submission to approval or rejection | Bottleneck detection |

| Contingency burn | Approved change amount divided by contingency budget | Budget control |

Follow-Up Questions

- Why do mechanical change orders average 28 approval days versus 11 days for other trades?

- Are design coordination changes tied to a specific drawing package?

- Which pending items could affect the next owner draw?

Tips for Best Results

  • 💡Ask for both requested and approved amounts so exposure is not hidden.
  • 💡Separate reason codes from trade names; they answer different questions.
  • 💡Track approval aging because unresolved changes create cash-flow and schedule risk.
  • 💡Flag dispute and entitlement questions for contract professionals.