How I turn messy change-order notes into a clean change-order one-pager

Slack pings, "quick adds," and email threads that say "while you're in there…" are not a change order. They are scope creep with no paper trail.

Here is the workflow I use when someone dumps a pile of mid-project extras and wants one page (or sheet) that shows what changed, what it costs, and what still needs a yes.

What "good enough" looks like

• Every requested change is one line with a clear status (proposed / approved / rejected / parked)
• Original scope vs the add is visible without digging through chat
• Price / hours impact is filled or marked unknown — not vibes
• Who requested it and who can approve it are named
• In-scope leftovers are not mixed into the change list

Intake checklist

1. The original brief / SOW / scope one-pager (whatever they started with)
2. The messy notes: Slack, email, call scribbles, ticket comments
3. Their status language (proposed / client-ok'd / billed / dead) — even if messy
4. Pricing unit they use (fixed fee, hourly, T&M) and currency
5. Who can approve extras on their side

The pass order that saves time

1. Inventory — list every mid-project ask with requester + rough ask.
2. Map to original scope — tag each as new work, clarification, or already-included.
3. Normalize status — Proposed, Approved, Rejected, Parked / later.
4. Price the delta — hours or fee impact, or "unknown — needs estimate."
5. Build the one-pager / sheet change log + approval column + notes.
6. Hand back — the page/sheet only; no client negotiation done for them unless they asked separately.

One-pager / sheet columns that work

Column	What goes here
Change #	Short ID (CO-01…)
Request	One-line description of the extra
Source	Slack / email / call / ticket
Requested by	Who asked
Vs original scope	New / clarification / already included
Status	Proposed / Approved / Rejected / Parked
Impact	Hours or fee delta (note currency)
Approver	Who can say yes
Decision date	When it was approved or killed
Notes	Dependencies, blockers, related CO

Common traps

• Treating every clarification as billable new work (or the reverse)
• Logging the ask but not the approver
• Leaving "quick adds" in chat with no CO number
• Mixing already-included polish into the change list so the client feels nickeled
• Writing a legal amendment when a one-page change log would unlock the next sprint

Soft handoff

When the page is done, send:

• The change-order one-pager or sheet
• A short list of Proposed items still waiting on an approver
• One suggested next step (approve CO-02/03, park the rest, or estimate the unknowns)

That is the whole job. No full contract rewrite required for a mid-project extras cleanup pass.

---

I do this as a 24-hour DFY service for freelancers and small businesses ($12 for messy change-order notes → change-order one-pager/sheet). Shop: https://brittanybonds.gumroad.com/l/changeorders — code ADMIN12 for $2 off. Full catalog: https://brittanybonds.gumroad.com/ and https://brittany-bonds.github.io/