DEV Community

Brittany Bonds
Brittany Bonds

Posted on

The mid-week checklist I use so a weekly priorities one-pager stays honest

The mid-week checklist I use so a weekly priorities one-pager stays honest

The same task listed twice — once from Slack, once from the sticky note — both greened as Top 3. A "priority" nobody asked for this week, invented because the page looked thin. Client B work folded into Client A's week. Capacity assumed at forty focused hours when the dump shows twelve. A stale backlog from last month still greening Monday. Two weeks mashed into one spine. That is not mid-week truth. Mid-week is where folklore becomes a fake priorities page — double-listed tasks, phantom priorities, scope blur, capacity inventing, stale backlog, and a pretty one-pager pretends the dump agreed with itself.

I am a freelancer admin helper. I turn messy task dumps into a clean weekly priorities one-pager. I am not a CPA, coach, lawyer, or time-management advisor — and this is not financial, tax, legal, productivity-coaching, or time-management advice. It is the checklist I run mid-week (and again before anyone treats the page as what was actually open) so the priorities one-pager stays honest while tasks are still arriving.

(If you want the full task dump → weekly priorities one-pager workflow, see my earlier post: How I turn a messy task dump into a weekly priorities one-pager. This one is the second-pass checklist so double-listed tasks, phantom priorities, out-of-scope client work, capacity inventing, stale backlog resurrection, and mashup weeks do not quietly rewrite what was actually open.)

What "honest" looks like mid-week

  • Every real open task is one line — Slack + sticky of the same ask are merged, not two Top-3 slots
  • Priorities exist only when evidenced in the dump (or labeled ask / guess / TBD) — remembered "we definitely need X" folklore is not the week
  • One week spine — this Mon–Sun (or named window), not a mash of two weeks
  • Out-of-scope or other-client work is labeled out / excluded — not folded in so it still looks due this week
  • Assumptions are labeled assumption — not written as settled capacity or deadline
  • Source note + capture date exist — superseded or out-of-window backlog is labeled stale, not still greening Monday
  • Nothing invented beyond what the dump supports — guessed hours and phantom Top-3 items are not a week plan

If the only “plan” you have is a confident Top 5 and a folder titled “Monday will somehow know,” mid-week honesty has already slipped.

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

Use this against the dump (sticky photos, Slack exports, email threads, Notion dumps, calendar holds, old week page if any) before you paste everything into a pretty template and call the page Monday-ready.

1. Inventory the task dump

  • [ ] Soft scope is named (this client set / this week window / this capture) — out-of-scope noise stays out or flagged
  • [ ] Every source is listed once: task snippet, file/channel, capture date, owner if known, notes
  • [ ] Duplicate asks or the same task under two sources (Slack + sticky, email + Notion) are labeled duplicate — not two priority lines for one ask
  • [ ] Superseded or out-of-window backlog dumps are labeled stale — not resurrected as this mid-week page
  • [ ] Anything clearly canceled or parked by the client is labeled stay-off-live — do not invent it back into Top 3

2. Lock week spine, priorities, and capacity before you trust the page

  • [ ] Every Top 3–5 item has evidence or is labeled ask / guess / TBD — blank priorities that look complete are not the dump
  • [ ] Week window is locked or ask — remembered "this week somehow" folklore is not the calendar
  • [ ] One short week spine is locked or mashup weeks stay ask — dual spines are not both green
  • [ ] Capacity / hours assumptions are listed or marked ask
  • [ ] Skim test: you can answer “what is actually due this week, for whom, and what is still uncleared?” without reopening the dump

3. Kill double-lists / phantom priorities / capacity inventing

  • [ ] Same ask under two sources is one line — not two open Top-3 items
  • [ ] Missing priority slots stay missing / ask — do not invent filler so the page looks full
  • [ ] Other-client or out-of-scope work stays out / excluded or ask — do not rewrite Client B’s dump as Client A’s week
  • [ ] Assumptions are labeled assumption — do not rewrite them as settled deadlines or hours
  • [ ] Open questions stay open — do not mark them closed because the page looked tidier
  • [ ] Invented capacity the dump never supported stays guess / ask — not locked as the week’s hours
  • [ ] Stale backlog that belongs to another window stays stale — not still greening this Monday

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

  • [ ] Phantom priorities and uncleared owners are either evidenced or labeled guess / ask / TBD — not locked because the page looked thin
  • [ ] Open asks (unclear owner, unclear week window, mixed-client blur, stale dump vs this window) sit in one list — not scattered across threads
  • [ ] Superseded or canceled lines are archived once so they do not still look live
  • [ ] Anything still incomplete stays incomplete — do not greenwash a mid-week dump into a finished priorities page

Soft CTA

If you want the task dump cleaned into a weekly priorities one-pager for you: messy tasks in, Monday-ready page out in 24 hours — $12 on Gumroad. Code ADMIN12 takes $2 off. Full catalog: shop · GitHub Pages.

Not financial, tax, legal, productivity-coaching, or time-management advice. I organize the task dump; you own priorities, capacity, and how you use the page.

Top comments (0)