A change order template that makes the next step clear.

Use a brief before issuing an invoice.

A change brief describes proposed work and its commercial terms. An invoice requests payment for an agreed charge; it should not be the first place a client discovers that the scope or fee changed.

“Change order,” “scope addendum” and “change brief” can mean different things in different agreements. Use the name that fits your process. The content and approval record matter more than the label.

Copy the template and add the actual details.

CHANGE BRIEF · [reference] · [revision]
Prepared on: [date]
Project: [name]
Prepared by: [agency and contact]
Prepared for: [client and contact]
Original agreement: [reference / date / relevant scope]

REQUEST
[What changes and why.]

DELIVERABLES
[Specific work you will produce.]

EXCLUSIONS
[Work not included in this change.]

DEPENDENCIES AND ASSUMPTIONS
[Inputs, access, decisions or approvals required.]

FEE
Net additional fee: [currency and amount]
Tax: [label, percentage and amount, if applicable]
Client total: [currency and amount]
Payment terms: [agreed terms]

DELIVERY
Additional delivery days: [number and day basis]
Delivery implications: [effect on dates and dependencies]

APPROVAL
[Who confirms scope, fee and timing; how and by when.]
[Which original terms continue to apply.]

SIGN-OFF, IF REQUIRED
Prepared by: [name / role / date / signature]
Accepted by: [name / role / date / signature]

Remove fields that are irrelevant, but do not remove a real dependency or approval requirement just to fit the document onto one page.

A worked website change.

Aster Studio is preparing a journal collection for Harbor’s website. This is an illustrative scenario, not a real customer case study.

Use the actual applicable tax treatment and agreed payment terms. Do not copy the example’s tax rate without checking it.

Review the terms before sharing.

• Client, project, reference and revision match the proposed change.
• Deliverables are specific enough to establish what “done” means.
• The fee says whether tax is included or added, and totals agree.
• Additional days say whether they are business or calendar days.
• Dependencies explain what can affect the revised date.
• The authorized approver and approval method are identified.
• Signature images have not been mistaken for recorded approval.
• Internal cost or margin notes are absent from client-facing text.

For a scope exchange, list removed work and replacement work. For a deferred request, avoid wording that accidentally commits a price or delivery date.

Inspect the public demonstration PDFs.

The samples show how a brief and an invoice present scope and fees at different points in the workflow. They do not show approval by a real customer.

The free workspace includes document previews. Protected customer PDF exports require activated export services, which are not yet enabled on the public deployment.