Track scope changes with clear status, approval history, and budget impact so change work does not become margin leakage.
Manage change orders with dedicated records and traceable lifecycle history.
Draft → Sent → Approved or Rejected. Each transition is logged and validated by workflow rules.
Project change orders number per job (for example, ACME-CO-1, ACME-CO-2). Service contract amendments use a similar per-service sequence (for example, ACME-CA-1, ACME-CA-2). No global counter — every job has its own sequence.
A timing tag tracks whether the change order is for upcoming work or retroactive work. Reports separate the two so you know what's a plan and what's a fix-up.
Keep each change order tied to one clear scope so ownership and budget impact stay unambiguous.
Add materials, labor, equipment, or free-text lines to a change order. Catalog references are optional — you can add a line that's not in your database when the field calls for it.
Export any change order as a branded PDF in one click. Minimal layout, clean margins, the kind of document you actually want in a customer file.
Send a change order to a client via a share link. They review, approve, or reject — no login friction. The approval feeds back into your workflow automatically.
Once a change order is approved, its total updates the project or service budget baseline automatically. Variance tracking and billing percentages update without manual cleanup.
A practical five-step process from scope change to approved financial update.
Create a change order from active project or service context, then define scope, timing, and line-item impact.
Share change order details for client review through low-friction send options and clear status updates.
Capture approval outcomes quickly so teams can move forward with confidence or revise when needed.
Apply approved change value to project financial context so downstream reporting and billing reflect current scope.
Use audit history to answer who approved what and when, especially on disputed or retroactive scope changes.
Treat scope change as a structured operational process, not an informal side note on the estimate.
Use job-level numbering that is easier for teams and clients to reference during approvals and billing discussions.
Separate planned changes from retroactive fixes so reporting and operational accountability stay honest.
Update financial context automatically on approved changes so project reporting and billing align with current scope.
Data flows through the platform. Here's where this feature fits.
Project / Service → Change Orders Tab
Every project and service has a Change Orders tab under the Costs section. List, create, approve, export — all from the same place you're already working on the job.
Approved CO → Budget Rollup
When a change order is approved, its total flows into the project or service budget baseline automatically. Variance and progress billing update without a manual step.
Progress Billing → Updated Completion %
As approved changes increase budget scope, completion percentages recalculate so draws stay accurate after scope changes.
Share Link → Client Approval
Send a change order link to your client. They approve or reject without a login. The underlying record transitions automatically.
7-day free trial. No credit card required. Pick your trade and start estimating.
We use cookies for analytics and to improve your experience. Cookie Policy