The mid-change checklist I use so a change-order one-pager stays honest

A Slack ping that says “while you’re in there…,” an email with three versions of the same add, a PDF titled “CO_FINAL_v2_USE_THIS,” a sticky that guesses “about two days somehow,” and a call note that claims “they said yes” with no written acceptance are not mid-change truth. Mid-change is where duplicate requests from Slack + email + PDF inflate the log, scope bleed into base work rewrites the delta, missing dollar/impact lines hide the real ask, “verbal yes” fog looks like approval, zombie superseded versions still look live, guessed dates/prices lock as fact, and open asks never get listed once.

I am a freelancer admin helper. I turn a messy change-request dump into a clean change-order one-pager. I am not a CPA, lawyer, tax advisor, or contract attorney — and this is not legal, financial, tax, or contractual advice. It is the checklist I run mid-change (and again before anyone treats the one-pager as signed-off truth) so the change-order page stays honest while dumps are still arriving.

(If you want the full messy change-order notes → clean change-order one-pager workflow, see my earlier post. This one is the second-pass checklist so duplicate asks, scope bleed, verbal-only yeses, zombie versions, and guessed dollars do not quietly rewrite the page.)

What "honest" looks like mid-change

• Every row has request, requester, date seen, status (proposed / approved / rejected / parked / ask), dollar or hours impact (or ask), source, and notes — not vibes
• Duplicate change requests across Slack + email + PDF are labeled once — not three lines for the same add
• Base-scope work is stay-off or labeled clarification — not mixed into the change delta
• “Verbal yes” without written acceptance stays ask / pending — not locked as approved
• Open questions (missing impact, conflicting versions, guessed dates) are listed once so the handoff is honest

If the only “change order” you have is a sticky titled “about two days somehow,” mid-change honesty has already slipped.

The mid-change checklist (run it before / while you clean)

Use this against the dump (Slack threads, email forwards, call scribbles, PDF “final” versions, ticket comments) before you paste everything into a pretty green “approved” column and call the one-pager ready.

1. Inventory the change-request dump (same day you open the pile)

• [ ] Every scrap is listed once: source, date seen, claim type (new work / clarification / already-included / duplicate / incomplete / unknown), notes
• [ ] Duplicate paste of the same ask across Slack + email + PDF is labeled duplicate — not counted three times toward the change log
• [ ] Partial dumps (“while you’re in there…,” “about two days somehow,” a ping with no owner) are labeled incomplete — not invented into tidy rows
• [ ] As-of / project window that matters is named — older superseded CO PDFs stay out or flagged
• [ ] Anything clearly cancelled, deferred to another product, or belonging to a different job is labeled stay-off — do not resurrect as this mid-change chase list

2. Lock request, date, owner, and impact before you trust the totals

• [ ] Every “include” row has a real request summary or is labeled ask — not blank cells that look priced
• [ ] Requester and date seen are written once (or ask) — not three conflicting “who asked / when” stories left unresolved
• [ ] Dollar or hours impact is a number or ask — not “about two days somehow” locked as the fee line
• [ ] Approver (who can say yes on their side) is named or unowned — folklore that “they’re fine with it” is not ownership
• [ ] Skim test: you can answer “what changed, who asked, what’s still fuzzy on impact?” without reopening Slack

3. Kill duplicate / superseded / verbal-only fog

• [ ] Status vocabulary is named (proposed / approved / rejected / parked / ask) — not blank cells that look signed
• [ ] Evidence for approved (email reply, signed CO, ticket acceptance) sits in notes or source — “they said yes on the call” alone is not approval
• [ ] Zombie superseded versions (CO_FINAL_v2 still looking live next to v3) are labeled superseded — not left competing as current
• [ ] Scope bleed into base work is tagged clarification / already-included — not silently billed as a new change
• [ ] Everything showing “approved” when acceptance is still verbal-only or missing is labeled recheck until status is honest

4. Park guessed dollars, Slack folklore, and open asks in the open

• [ ] Missing required fields sit as ask with what is missing — not invented to tidy the one-pager totals
• [ ] “TBD,” “about two days somehow,” and “usual add” without a mapping stay ask — not locked as this week’s change fee
• [ ] Anything you almost guessed (which PDF wins, whether the Slack ping was the same as the email, whether verbal yes counts) stays in notes as guessed — not locked as truth
• [ ] Slack / sticky reminders that contradict the latest written dump are labeled conflict — not silently preferred
• [ ] Open asks are listed once — not scattered as footnotes nobody will find at handoff

5. Mid-change skim before you call the one-pager ready

• [ ] Proposed / approved / rejected / parked / ask counts match a quick mental check of known open items
• [ ] Ask rows and duplicate-request suspects are countable in under a minute
• [ ] Totals never invent missing dollars or dates — blanks stay ask
• [ ] You can hand the one-pager to someone else without a 10-minute Slack-and-PDF tour
• [ ] Soft CTA only if useful: this is cleanup so change requests, impact, and acceptance are easier to see — not advice on contracts, pricing, or legal enforceability

Soft CTA

If you want a change-request dump turned into a clean change-order one-pager: https://brittanybonds.gumroad.com/l/changeorders

Shop: https://brittanybonds.gumroad.com/

Catalog mirror: https://brittany-bonds.github.io/

Code ADMIN12 for $2 off.

No fake CPA or lawyer claims — spreadsheet/one-pager cleanup so your change-order dump is easier to track and hand off.