Change Orders

Once a version is Contracted, every scope or dollar change goes through a Change Order. The Contract itself never moves — Change Orders sit on top of it.

When You Need One

Use a Change Order whenever the customer asks for something that wasn't in the signed contract:

• Adding a new room or new equipment
• Swapping a product for a different one
• Increasing or reducing cable runs on something already in the contract
• Removing scope the customer no longer wants

If the contract hasn't been signed yet (the version is still Draft), you don't need a Change Order — just edit the project directly.

Drafting a Change Order

1. From a Contracted project's Details page, open the Change Order Drafting modal.
2. Add new rooms or new line items the same way you would in a draft project.
3. To modify a baseline line (something in the original contract), pick it from the list and use the Modify action — for example, to add or remove cable runs.
4. To remove a baseline line, use the Remove action.
5. Save the draft. The CO sits in Draft state until you're ready to submit it.

Submitting and Approving

A CO moves through three states on the way to applied:

• Draft — work in progress, only visible internally, no impact on project totals.
• Submitted — flagged as ready for internal review (estimator → manager, or similar). Still no impact on totals.
• Approved — applied to the project. The CO's net dollar change is now added to the project's total contract value.

You can also Reject a Submitted CO that doesn't make sense — that ends its life right there and it never applies.

Voiding an Approved CO

If an Approved CO turns out to be wrong, you can void it. Voiding rolls its impact back out of the project totals as if it had never been approved. The voided CO stays in the history for audit purposes.