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

A Slack channel full of "quick updates," three Docs named FINAL, a spreadsheet of green cells, and a voice note that starts with "so basically…" are not mid-week truth. Mid-status is where fake greens hide blockers, "done" means someone typed done, dates are theater, and decisions float without an owner until Friday.

I am a freelancer admin helper. I turn messy project status dumps into a clean status one-pager. I am not a CPA, PMO, lawyer, or project coach — and this is not financial, tax, legal, or professional consulting advice. It is the checklist I run mid-status (and again before anyone treats the page as the stakeholder truth) so the one-pager stays honest while updates are still arriving.

(If you want the full messy project status dump → clean status one-pager workflow, see my earlier post. This one is the second-pass checklist so fake greens, buried blockers, zombie done items, and date theater do not quietly rewrite what is actually true.)

What "honest" looks like mid-status

• Headline status is plain English (on track / at risk / blocked) — not vibes or emoji weather
• Done vs in-progress vs waiting are separated so nothing looks finished that is not
• Each blocker has an owner and a next ask — not just "waiting on stuff"
• Dates are real (due, decision needed by) or explicitly TBD — no fake certainty
• Risks that could slip a date or change scope are named once, not buried in chat paste
• The page fits a skim: headline first, progress second, blockers and asks last

If the only "status" you have is a green cell and a thread titled "all good," mid-status honesty has already slipped.

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

Use this against the dump (Slack threads, email chains, standup notes, ticket exports, Loom updates, meeting notes, prior status docs) before you paste everything into a pretty template and call the week done.

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

• [ ] Every scrap is listed once: source, date seen, claim type (done / in progress / waiting / risk / decision), notes
• [ ] Duplicate paste of the same update across Slack + Doc + Notion is labeled duplicate — not counted as three green lights
• [ ] Partial claims ("maybe next week," a screenshot with no owner) are labeled incomplete — not invented into tidy progress
• [ ] Time window that matters is named (this week vs this sprint vs this phase) — older noise stays out or flagged
• [ ] Anything clearly resolved, superseded, or "nice someday" is labeled stay-off-asks — do not resurrect as this week's decision list

2. Separate status from vibes before you trust greens

• [ ] Headline status is on track / at risk / blocked — not mood words or traffic-light theater without evidence
• [ ] Done items have a proof line (PR merged, file delivered, client accepted) — "done" in a chat is not done
• [ ] In-progress items name the next concrete step — not "working on it"
• [ ] Waiting items name who / what / since when — anonymous waits are Needs-confirm
• [ ] Skim test: you can answer "what is actually true this week?" without reconstructing six threads

3. Lock blockers, owners, and decisions

• [ ] Each blocker has an owner and a next ask — "blocked" without a person is folklore
• [ ] Decisions needed have a by-when date or explicit TBD — open questions without a clock stay Needs-confirm
• [ ] Risks that could slip a date or change scope are listed once — speculative dread stays off the page or in a parking lot
• [ ] Audience for the one-pager is named (you, team, or client) so tone stays honest
• [ ] Skim test: you know what to ask for this week without reopening the dump

4. Catch zombie done and date theater

• [ ] Items marked done that still need a file, approval, or publish step are moved back to in-progress or waiting
• [ ] Dates that were "end of week" three weeks ago are labeled date stale until confirmed or TBD'd
• [ ] Fake greens (all cells green, no blockers section) get a forced blocker/risk pass before the page ships
• [ ] Threads titled "quick update" without a usable sentence are labeled artifact thin
• [ ] Skim test: sorting by ask priority shows a real week, not a museum of May milestones

5. Honesty tripwires (before you treat the page as stakeholder-ready)

• [ ] You did not promote vibes to "on track" because the status column looked empty
• [ ] Blockers buried in a wall of chat paste are lifted — not left under a green headline
• [ ] Updates from six weeks ago are labeled window unverified until the time window is confirmed — pretty columns do not renew stale status
• [ ] Incomplete sections stay Needs-confirm — not silently promoted to "all clear" because the page looked sparse
• [ ] Superseded items have an archive note so closed work is not deleted into amnesia

6. Hand-back sanity check

• [ ] One-pager answers: headline status, what moved, what is blocked, what needs a decision — without opening the dump
• [ ] Needs-confirm / Waiting / Done views (or sections) exist so incomplete and dead items are not mixed into this week's asks
• [ ] One sentence of scope on the page: "status one-pager — not a full PMO pack, roadmap rewrite, or risk register suite"
• [ ] Non-advice line present: not CPA / legal / consulting advice; confirm status with humans before treating this as gospel
• [ ] You would be willing to run this week's asks from this page without reconstructing Dana from a sticky note

What I do not do on this pass

I do not rebuild their project system, rewrite their roadmap, set pricing policy, or give legal/PMO advice. Mid-status honesty is about one trustworthy status one-pager stakeholders can skim this week — not a program office in a Doc.

Soft CTA

If you want the messy pile turned into that one-pager for you: Project status dump → status one-pager — usually within 24 hours. Code ADMIN12 takes $2 off. Shop: brittanybonds.gumroad.com · catalog mirror: brittany-bonds.github.io