Send a quote before the lead's coffee gets cold.
Good inquiries wait while someone rebuilds the same quote.
Est. deploy 3–5 weeksSee the walkthrough
Sales & Quoting · Construction
Prepare change orders from approved field facts.
Extra work gets documented after it is forgotten.
For: Project managers and the team responsible for sales & quoting in construction.
01 · The outcome
What good looks like.
The team has a change-order packet held for commercial approval, with source evidence and an explicit approval before any external action. Track approved change work documented before invoicing against a baseline; do not assume automation improves it.
A connected workflow that uses field directive, approved labor rates, material records, and contract reference to assemble a costed draft with source evidence and flag scope disagreements. It produces a change-order packet held for commercial approval.
Where AI helps, and where a person decides.
AI can assemble a costed draft with source evidence and flag scope disagreements. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The project manager verifies the source facts and approves the final action.
Project manager is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- Project manager: Capture the source and scope
- Project manager: Review the proposed outcome
- Project manager: Release only the approved version
- Project manager: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: A project manager authorizes change-order preparation. Connect only field directive, approved labor rates, material records, and contract reference. The project manager confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to assemble a costed draft with source evidence and flag scope disagreements. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check a change-order packet held for commercial approval against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: Project manager has recorded approval or a reason to hold the item.
After explicit approval, save a change-order packet held for commercial approval in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review approved change work documented before invoicing each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=construction-change-order
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- CONSTRUCTION-CHANGE-ORDE-DEMO-001
- Trigger
- A project manager authorizes change-order preparation.
- Owner
- Project manager
- Prepared output
- a change-order packet held for commercial approval
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Approved change work documented before invoicing
Start with your tools.
Connect Procore, QuickBooks, Microsoft 365 through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
Try this week / no DAVID required
A useful first step.
This week, have your project manager time five examples of this work. Use redacted copies of field directive, approved labor rates, material records, and contract reference to make a change-order packet held for commercial approval manually, then list which fields required judgment.
What to measure.
- Approved change work documented before invoicing
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Follow up on every undecided consult.
Families leave a consult without a clear next step.
Est. deploy 4–6 weeksSee the walkthrough
Keep accepted treatment from falling through.
Accepted plans sit unscheduled after checkout.
Est. deploy 4–6 weeksSee the walkthrough
Want this running in your business in 2–4 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.