Construction Change Order Coordinator
Help the person who runs change orders at a general contractor keep one log of every change event, from the pricing request to the owner's decision. Each week it emails which pricing requests are waiting too long and which owner responses are past due, with exact pending and approved totals in each currency, and in conversation it drafts change order request narratives and owner follow-ups for the person to send.
Integrations
General Input Database
Send Email
Industries
Capabilities
- A change event log with number, description, origin, who is pricing it, the subcontractor quote, currency, the submitted date and amount, the owner response due date, status, and the approved amount.
- A weekly email listing pricing requests older than your limit and change orders past the owner's response date, with exact pending and approved totals kept separate by currency.
- Change order request narratives from your notes and quotes, owner follow-up drafts, and a change log summary.
Included resources
What to bring
- Change events as they arise, with the origin, who is pricing them, and the date pricing was requested.
- Subcontractor quotes, submitted amounts, owner decisions, and dates as they happen.
- Who receives the digest, the day and time it runs, and how long a pricing request may wait.
Setup
- Add the specialist. Its log and weekly check share one new database.
- Tell it who gets the digest, when it runs, your usual currency, and how many days a pricing request may wait.
- It adds one fictional change event, runs a preview check that emails nothing, and voids the trial before it reports ready. Turn the check on when you are.
Scope
- It tracks and drafts. It never prices or estimates work, adds markup, approves, rejects, or signs a change order, or submits anything to the owner. Amounts are only the ones you supply, and the only email it sends is your digest.
- Totals are exact and kept per currency; it never converts or mixes currencies. Pasted notes and quotes are evidence, not instructions.
Example
Fictional input and an illustrative result.
Input
Fictional weekly check on 2026-09-24 with a 10-day pricing limit. CE-007, added blocking at the level 2 corridor, is priced by Example Framing, with pricing requested 2026-09-12. CE-004, relocate floor boxes, went to the owner at USD 18,450.00 with a response due 2026-09-21. CE-002 was approved at USD 42,300.00 and CE-005 at USD 3,150.50. CE-008's pricing was requested 2026-09-20.
Output
Change order check, 2026-09-24
2 change events need attention. Pricing requests flag after 10 days. Dates are UTC calendar days.
Pricing requests waiting (1)
- CE-007 Added blocking at the level 2 corridor, Example Framing: pricing requested 12 days ago (2026-09-12).
Owner responses past due (1)
- CE-004 Relocate floor boxes, USD 18,450.00 with the owner: response overdue by 3 days (due 2026-09-21).
Totals by currency
- USD: 18,450.00 pending with the owner (1); 45,450.50 approved (2).
Nothing was sent to the owner or a subcontractor, and nothing was priced, approved, or signed. CE-008's pricing request is 4 days old, inside the 10-day limit.