The mid-scope checklist I use so a one-page project scope stays honest

A deliverable that was never in the brief. A deadline someone "remembered" from Slack. Two versions of "done" living in the same paragraph. Out-of-scope work labeled nice-to-have so it still looks in. Assumptions treated as client commitments. A vague brief padded into a confident one-pager. That is not mid-scope truth. Mid-scope is where folklore becomes a fake SOW — invented deliverables, fake dates, dual definitions of done, out-of-scope padding, and a pretty page pretends the brief agreed with itself.

I am a freelancer admin helper. I turn messy vague briefs into a clean scope one-pager. I am not a CPA, bookkeeper, lawyer, tax advisor, or contract negotiator — and this is not financial, tax, legal, or contractual advice. It is the checklist I run mid-scope (and again before anyone treats the page as what was agreed) so the scope one-pager stays honest while the brief is still arriving.

(If you want the full vague brief → scope one-pager workflow, see my earlier post when it is live. This one is the second-pass checklist so invented deliverables, fake dates, dual "done" definitions, out-of-scope padding, assumption-as-commitment folklore, and superseded notes do not quietly rewrite what the brief actually said.)

What "honest" looks like mid-scope

• Every real deliverable is one line — duplicates and restatements are merged, not counted twice
• Dates exist only when evidenced in the brief (or labeled ask / guess / TBD) — invented milestones are folklore, not the plan
• "Done" is one definition — two competing success criteria stay ask, not both greened
• Out-of-scope items are labeled out — not folded into nice-to-have so they still look in
• Assumptions are labeled assumption — not written as client commitments
• Source note + capture date exist — superseded Slack folklore is labeled stale, not still greening the page
• Nothing invented beyond what the brief dump supports — guessed phases are not a SOW

If the only “scope” you have is a confident paragraph and a folder titled “client somehow agreed,” mid-scope honesty has already slipped.

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

Use this against the dump (vague brief, email thread, sticky notes, old one-pager if any) before you paste everything into a pretty template and call the page agreed.

1. Inventory the brief dump

• [ ] Soft scope is named (this project / this phase / this capture window) — out-of-scope noise stays out or flagged
• [ ] Every source is listed once: brief snippet, email, call note, capture date, claim type (deliverable / date / constraint / unknown), notes
• [ ] Duplicate asks or the same deliverable under two phrasings are labeled duplicate — not two lines for one outcome
• [ ] Superseded or walked-back notes are labeled stale — not resurrected as this mid-scope page
• [ ] Anything clearly replaced by a newer client note is labeled stay-off-live — do not invent it back into the one-pager

2. Lock deliverables, dates, and "done" before you trust the page

• [ ] Every deliverable has evidence or is labeled ask / guess / TBD — blank cells that look complete are not the brief
• [ ] Dates and milestones are locked or ask — remembered Slack dates are not the plan
• [ ] One definition of done is locked or competing definitions stay ask — dual success criteria are not both green
• [ ] Constraints (budget ceiling, tools, access, review rounds) are listed or marked ask
• [ ] Skim test: you can answer “what is in, what is out, by when, and what done means?” without reopening the email thread

3. Kill invented-deliverable / out-of-scope / assumption inflation

• [ ] Same outcome under two phrasings is one line — not two open deliverables
• [ ] Nice-to-haves that were never in the brief stay out or ask — do not invent them as in-scope to green the page
• [ ] Assumptions are labeled assumption — do not rewrite them as client commitments
• [ ] Open questions stay open — do not mark them closed because the one-pager looked tidier
• [ ] Screenshot / Slack folklore with no brief line is either added once with capture note or labeled out-of-scope — ghost lines are not a SOW
• [ ] Guessed phases with no brief evidence stay guess / ask — not locked as the plan

4. Park open asks, tidy-page lies, and superseded notes

• [ ] Invented deliverables are either evidenced or labeled guess / ask / TBD — not locked because the page looked thin
• [ ] Open asks (missing date, unclear done, out vs in conflict, assumption vs commitment) sit in one list — not scattered across threads
• [ ] Superseded or walked-back notes are archived once so they do not still look live
• [ ] Anything still incomplete stays incomplete — do not greenwash a mid-scope dump into a finished contract

Soft CTA

If you want the vague brief cleaned into a scope one-pager for you: messy brief in, one-page scope out in 24 hours — $12 on Gumroad. Code ADMIN12 takes $2 off. Full catalog: shop · GitHub Pages.

Not financial, tax, legal, or contractual advice. I organize the brief dump; you own the client decisions and how you use the page.