Accepted documents stay locked
Once a proposal or contract is accepted, it is locked. Changes happen in a change order.
Change Orders
Change orders that handle scope creep in writing
When the client asks for more after they said yes, write it down. A change order shows what changed and what it costs, and the client approves it with one link.
- 01
- Accepted proposals and contracts are locked, so the original stays as agreed.
- 02
- Each scope change becomes a versioned change order with the money impact.
- 03
- AutoPilot labels new requests against the accepted proposal for your review.
1Record updatedContext stays attached to the work.Now
2Team follow-upContext stays attached to the work.3m
3Client notifiedContext stays attached to the work.4m
change order software
What is change order software?
Change order software records a change to agreed work, shows what it costs, and collects the client's approval. In Workspace369, an accepted proposal or contract is locked. Scope changes become versioned change orders that show line-by-line differences and the money impact, and the client approves them by secure link.
Product reference
Reviewed October 12, 2026 by the Workspace369 Product Team. Availability can vary by plan, region, and workspace configuration.
Read the Workspace369 documentationWhat it covers
Scope changes without the argument.
Change orders in Workspace369 leave the signed document alone and record every change beside it.
Versioned change orders
Each change order is a new version, so you can see how the scope moved over time.
Line-by-line differences
See each line that was added, removed, or changed, and the effect on the total.
Client approval by secure link
The client reviews the change and approves it from a secure link.
Amended document preview
Preview the amended document before it goes out.
Included, possible change, or uncertain
AutoPilot compares a new client request with the accepted proposal and labels it. You decide what to do.
Built into the operating flow
From a new request to an approved change.
Change orders connect to proposals, contracts, requests, invoices, and the client's secure approval link.
- 01
A request comes in
The client asks for something new. AutoPilot compares it with the accepted proposal and suggests a label.
- 02
You review the label
The label is included, possible change, or uncertain. It is always for your review and never decides on its own.
- 03
Create the change order
Add the new scope as a versioned change order. The differences and the money impact show line by line.
- 04
Client approves, invoice follows
The client approves by secure link. Approved changes fold into the invoice.
Inside Workspace369
See how a change order stays beside the signed original.
Follow the record through the views teams use to act, review progress, and keep the next step clear.Product view 01
Accepted proposals and contracts are locked, so the original stays as agreed.
When the client asks for more after they said yes, write it down. A change order shows what changed and what it costs, and the client approves it with one link.
1Record updatedContext stays attached to the work.Now
2Team follow-upContext stays attached to the work.3m
3Client notifiedContext stays attached to the work.4m
Product view 02
Each scope change becomes a versioned change order with the money impact.
Change orders connect to proposals, contracts, requests, invoices, and the client's secure approval link.
Product view 03
AutoPilot labels new requests against the accepted proposal for your review.
Show what changed, what it costs, and who approved it.
1TriggerClient activityAutomated
2ConditionMatch the right recordChecked
3ActionContinue the workflowNext
Examples
Change order flows teams repeat.
These examples show how a scope change moves through connected client work. They are product workflows, not promised business outcomes.
Scope Creep to Approved Change
- 1Client asks for an extra deliverable
- 2AutoPilot labels it a possible change
- 3You review and create a change order
- 4Client approves by secure link
- 5Approved change folds into the invoice
Included Request
- 1Client sends a new request
- 2AutoPilot labels it included
- 3You confirm it is in the accepted scope
- 4Work continues with no change order
Common operating scenarios
Handle scope creep with a record.
These examples describe how the feature fits into connected client work. They are product workflows, not promised business outcomes.
Extra deliverables
When a client adds work, write it as a change order. The differences and the new total are on one page.
Fast client approval
Send the change order by secure link. The client sees an amended document preview and approves it.
Review new requests
AutoPilot, the AI in Workspace369, compares a new request with the accepted proposal. It labels it included, possible change, or uncertain, for your review.
Where it connects
One record can carry the work forward.
Change orders connect to proposals, contracts, requests, invoices, and the client's secure approval link.
Common questions
Change Orders questions
What is scope creep?
Scope creep is when the work grows beyond what was agreed, usually a little at a time and without a change in price. A change order records each addition so the price follows the scope.
How do I handle scope creep with a client?
Compare the request with the accepted proposal. If it is new work, create a change order that shows the added lines and the cost, and ask the client to approve it before you start.
What happens to the original proposal or contract?
Once accepted, it is locked. Every later change is a versioned change order beside it.
What does AutoPilot do with a new request?
AutoPilot compares the request with the accepted proposal and labels it included, possible change, or uncertain. It is always for your review and never decides on its own.
How are approved changes billed?
Approved changes fold into the invoice.
Work from one connected system
Turn the next scope change into a change order.
Start free and bring this workflow into the rest of your workspace.