Mid-status honesty is necessary. Before-you-share is different. The morning you decide "I will send this status one-pager to the stakeholder / client today" is when a fake green still greening the headline, a blocker still buried under "quick update" paste, a zombie Done still looking finished, a date that was theater last Tuesday still looking firm, a decision with no owner still floating, and a raw Slack dump quietly hitchhiking into the share view.
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 the day I am about to share (the final pass before anyone treats the page as the stakeholder truth) so fake greens, buried blockers, zombie done items, date theater, and decision orphans do not ship.
This is complementary to my earlier posts — not a rewrite. For the full messy project status dump → clean status one-pager workflow, see How I turn a messy project status dump into a clean status one-pager. For the mid-status honesty pass while updates are still arriving, see The mid-status checklist I use so a status one-pager stays honest. This third pass is the before-you-share check: mid-status honesty is not enough once a real human is about to read it as settled.
What "honest enough to share" looks like
- Headline status is plain English (on track / at risk / blocked) — not vibes, weather emoji, or a green cell with no sentence
- Done vs in-progress vs waiting are separated — 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
- Decisions that shipped have an owner and a date — orphans are labeled Needs-confirm or cut
- Raw dump artifacts (Slack screenshots, unfinished notes, named complainers) are out of the share view
- You can answer "what is true right now?" without reconstructing twelve Looms
If the only share plan you have is a sticky labeled "send status?" before-you-share honesty has already slipped.
The before-you-share checklist (run it before anyone hits send)
Use this against the near-final status one-pager and the live artifacts (Notion page, standup notes, Slack threads, sheet of greens, Loom) before anyone treats the page as the stakeholder-facing truth.
1. Kill fake green before a human reads the headline
- [ ] Headline status is a sentence a stakeholder would defend — not a lone green cell or "all good"
- [ ] At-risk / blocked items are visible in the skim, not only in a buried comment
- [ ] Soft "looking fine" folklore is labeled assumption or cut — vibe is not status
- [ ] Skim test: the first three lines answer on track / at risk / blocked without opening the dump
2. Separate done, in-progress, and waiting so zombie Done cannot ship
- [ ] Done means evidence of done — not someone typed Done in a thread
- [ ] In-progress has a next step and an owner — not an eternal "working on it"
- [ ] Waiting has who we wait on and what we asked — not "blocked somehow"
- [ ] Skim test: sorting by state does not put unfinished work in the Done column
3. Surface blockers with owner and next ask before the meeting
- [ ] Every blocker names a person (you or a named person on their side) — not "the client" or blank
- [ ] Every blocker has a next ask you would actually say aloud — not "follow up somehow"
- [ ] Duplicate blockers under three names are merged — the reader should not chase the same ask thrice
- [ ] Soft emoji / "looks good" side-notes stay ask — not rewritten as cleared blockers
4. Dates and decisions must survive a stakeholder skim
- [ ] Due / decision-needed-by dates are calendar days or labeled TBD — do not invent "Friday somehow"
- [ ] Date theater from last week is refreshed or flagged — stale firm dates do not ship as current
- [ ] Decisions that the page claims are settled have an owner and a date — orphans are Needs-confirm or cut
- [ ] Risks that could slip a date or change scope are named once in plain English — not buried under progress paste
5. Before-you-share tripwires
- [ ] You did not leave a fake green on the headline to make the page look tidy
- [ ] You did not bury a real blocker under "quick updates" so the skim looked calm
- [ ] You did not leave zombie Done items so the Done column looked full
- [ ] Soft scope of this status page is named (this engagement / this workstream) — other stacks stay out or flagged
- [ ] One sentence of scope on the page: "status one-pager — not a full PMO, legal advice, or a roadmap"
- [ ] Non-advice line present: not CPA / legal / tax / consulting advice; confirm live status with humans before treating this as gospel
- [ ] You would be willing to sit in the room while this exact page is read aloud
6. Last skim before send
- [ ] Page answers: what is true, what is blocked, who acts next, what is TBD — without opening the dump
- [ ] Needs-confirm / At-risk / Blocked sections (or filters) are visible — not deleted so the page looks tidy for the share
- [ ] You know which items are say-today vs wait-for-confirm
- [ ] Anything that should not drive a stakeholder meeting (fake greens, zombie Done, date theater, decision orphans, raw Slack paste) is already off the share view
What I do not do on this pass
I do not run their project, set their roadmap, rewrite their Slack culture, or give legal/tax advice. Before-you-share honesty is about one trustworthy status one-pager a human can skim without getting lied to by fake greens, buried blockers, zombie Done, date theater, or decision orphans — not a full PMO suite in a Doc.
Soft CTA
If you want the messy dump turned into that status 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
Top comments (0)