Completa Pro workflow
Document the change before the extra work.
Keep new conditions, added work, price effects, schedule effects, and approval tied to the original job.
Direct answer
A change order should explain what changed, why it changed, and what it does to scope, price, and schedule before the added work proceeds.
Four phases
How the workflow works.
- 01
Record the trigger
Capture the customer request, discovered condition, product change, code requirement, or other event that created the change.
- 02
Describe the exact difference
Show added, removed, or revised tasks and keep the original scope available for comparison.
- 03
State the consequences
Make the price, milestone, schedule, material, and access effects visible before approval.
- 04
Get the decision into the record
Keep approval, rejection, expiration, or revision with the version that governed the work.
What stays in the record
- Original scope
- Change reason and evidence
- Price and schedule effect
- Customer decision and version
Related workflows
EstimatingTurn the work you already understand into a customer-ready estimate with visible scope, assumptions, options, and exclusions.Client communicationUse project messages to preserve decisions, questions, access details, progress, and next steps with the work they affect.Project recordsConnect scope, versions, messages, milestones, money, evidence, and closeout instead of reconstructing the job later.
Take the workflow into your next job.
The operating details live in Completa Pro.