A change order is how extra work stays fixed-price and friendly: you name the change, price it, and the customer approves it before you do the work. Here's the flow in Mastro.
When to raise one
Raise a change order whenever the job moves beyond the signed quote — the customer asks for an addition, or you uncover hidden work (see change orders without the awkward conversation for how to handle the chat).
Step 1 — Raise it from the job
From the project, open Change orders and raise a new one. Describe the change in plain language — what and why — and set the price.
Step 2 — Send it for approval
The change order goes to the customer for approval. Until they approve, it's pending — the original fixed price still stands.
Step 3 — Customer approves with a signature
The customer approves the change (with a signature via the portal). Now it's on the record: agreed change, agreed price, agreed by both sides.
Step 4 — Do the work, and the price updates
Only once it's approved do you carry out the extra. The change order updates the job's total, so the final invoice already reflects everything that was agreed — no awkward reconciliation at the end.
Why this protects you
The owner approval queue means nothing gets added to a job — or a bill — without a clear yes. That protects the customer from surprises and protects you from disputes: every extra is documented and approved before a tool is lifted.
Good habits
- Raise it before you build it, always.
- Keep the description plain — the customer should understand exactly what they're approving.
- One change, one order — easier to approve and easier to track than a bundle.
Next: share the client portal so approvals are a tap away for the customer.