DEV Community

Brittany Bonds
Brittany Bonds

Posted on

The week-of notice checklist I use so a key-dates one-pager still matches what binds

Mid-dates honesty is necessary. Week-of notice is different. The morning you decide "I will send the notice / let this renew / act on this date this week" is when an unresolved amendment conflict still greening two calendars, a "30 days" window with no act-by day suddenly means Friday somehow, a side-letter Slack still sitting off the sheet, timezone fog never got labeled, a stale PDF still looks binding, and auto-renew folklore is about to stick without a human check.

I am a freelancer admin helper. I turn messy contracts and SOWs into a clean key-dates one-pager. I am not a CPA, bookkeeper, lawyer, or tax advisor — and this is not financial, tax, legal, or contractual advice. It is the checklist I run the week I am about to act on a date (the final pass before anyone spends calendar time on notices, renewals, or kickoffs) so the key-dates one-pager still matches what binds when the week starts.

This is complementary to my earlier posts — not a rewrite. For the full contract or SOW → key-dates one-pager workflow, see How I turn a contract or SOW into a key-dates one-pager. For the mid-dates honesty pass while crumbs are still arriving, see The mid-dates checklist I use so a key-dates one-pager stays honest. This third pass is the week-of notice check: mid-dates honesty is not enough once you are about to spend real calendar time on an act-by day.

What "matches what binds" looks like week-of

  • Every date you plan to act on this week is still live — superseded, unsigned, and stale PDFs are off the act list
  • One canonical source per milestone — you are not about to notice or renew off two conflicting amendment calendars
  • Notice windows have a concrete act-by calendar day or are flagged Needs-confirm before anyone sends
  • Who owes the action is a real name (you or a named person on their side) — not "someone / the client"
  • Timezone / business-day rule is explicit or flagged — not "close of business somehow"
  • Auto-renew / terminate / kickoff language you will rely on this week has evidence or ask — vibe Slack is not the PDF
  • You can sort "act this week" and get a short list you would actually defend in a room

If the only week plan you have is a sticky labeled "renew somehow Friday," week-of notice honesty has already slipped.

The week-of notice checklist (run it before Monday action)

Use this against the near-final key-dates one-pager and the live stack (signed PDF/DOCX, amendments, email side-letters) before anyone treats the sheet as this week's notice / renew / kickoff calendar.

1. Pull stale and superseded off the act list

  • [ ] Superseded SOWs / unsigned drafts are labeled stale — not still greening this week's act list
  • [ ] Dates that already fired (past notice windows, closed renewals, completed kickoffs) are archived or filtered out of "act this week"
  • [ ] Soft "we talked about moving it" folklore still has a status — silence is not automatically still-binding
  • [ ] Stacks you already replaced with a newer signed amendment are labeled superseded — do not act on the old PDF
  • [ ] Skim test: every row left on the act-this-week list is something you would still defend as binding today

2. One milestone, one act — kill twin calendars before you send

  • [ ] Base vs amendment for the same milestone is one act row — twin calendars are merged or conflict-flagged
  • [ ] The clause / page you will reference matches the canonical version on the sheet
  • [ ] Side-letter ghosts that change dates are merged or labeled Needs-confirm — not left off while the base still greening
  • [ ] Skim test: sorting by milestone shows one live act per real obligation

3. Lock act-by day, timezone, and owner before you spend calendar time

  • [ ] Notice windows have an act-by calendar day or are labeled Needs-confirm — do not invent "Friday somehow"
  • [ ] Timezone / business-day rule is named or flagged — do not invent "close of business local"
  • [ ] Who owes the action is a named person (you or someone on their side) — not "the client" or blank
  • [ ] You know which rows are act-today vs wait-for-confirm on date, owner, or conflict
  • [ ] Skim test: you could say the date, meaning, and owner on a call without reopening the Drive dump

4. Auto-renew, terminate, and kickoff must be evidenced this week

  • [ ] Auto-renew language you will let stick has clause evidence or is labeled assumption / ask
  • [ ] Terminate / non-renew notice you plan to send cites the window that is still open — not a missed window dressed as this week
  • [ ] Kickoff / delivery dates this week have source or ask — Slack "next Monday somehow" stays Needs-confirm
  • [ ] Soft emoji / "looks good" side-letters stay ask — not rewritten as the signed calendar
  • [ ] Skim test: sorting by next act shows a short list you would actually send or let renew from

5. Week-of honesty tripwires

  • [ ] You did not invent an act-by day just to fill the column before Monday
  • [ ] You did not pick the prettier PDF in a base-vs-amendment conflict to make the week look tidy
  • [ ] You did not leave stale SOWs on the act list so the calendar looked full
  • [ ] Soft scope of this act week is named (this engagement / this counterparty) — other stacks stay out or flagged
  • [ ] One sentence of scope on the sheet: "key-dates one-pager — not legal advice, a full CLM, or a renewal strategy"
  • [ ] Non-advice line present: not CPA / legal / tax / contractual advice; confirm binding dates with humans before treating this as gospel
  • [ ] You would be willing to sit in the room while this exact act-this-week list is read aloud

6. Last skim before notice / renew / kickoff

  • [ ] Sheet answers: what binds this week, by when, who acts, what is Needs-confirm, what is off the act list — without opening the dump
  • [ ] Needs-confirm / Stale / Superseded / Conflict sections (or filters) are visible — not deleted so the sheet looks tidy for the week
  • [ ] You know which items are send-or-act-today vs wait-for-confirm
  • [ ] Anything that should not drive a Monday notice (twin calendars, vibe renewals, undated stickies, timezone fog, stale PDFs) is already off the act view

What I do not do on this pass

I do not rewrite their contract, set renewal policy, draft the legal notice for them, or give legal/tax advice. Week-of notice honesty is about one trustworthy key-dates one-pager a human can act from without getting lied to by stale PDFs, twin calendars, missing act-by days, side-letter ghosts, timezone fog, or fake auto-renew folklore — not a full contract suite in a Sheet.

Soft CTA

If you want the messy stack turned into that key-dates one-pager for you: Contract or SOW → key-dates one-pager — usually within 24 hours. Code ADMIN12 takes $2 off. Shop: brittanybonds.gumroad.com · catalog mirror: brittany-bonds.github.io

Top comments (0)