The week-of renewal checklist I use so an SLA tracker still matches what is covered

Mid-coverage honesty is necessary. Week-of renewal is different. The morning you decide "this coverage renews / we might claim / covered-until is cash-or-contract truth" is when soft words like "fast," "priority," and "best effort" are still sitting where a measurable target should be, seats / regions / SKUs still do not match what was purchased, start and end dates plus what starts the response clock are still blank, an expired PDF is still marked active, and a Slack "I think we're fine" is still rewriting the covered-until line.

I am a freelancer admin helper. I turn messy warranty/SLA dumps into a clean SLA tracker. I am not a CPA, bookkeeper, lawyer, or vendor negotiator — and this is not legal, financial, warranty, insurance, or vendor-negotiation advice. It is the checklist I run before anyone treats covered-until as this week's renewal or claim truth (the final pass before a renew decision, a support claim, or an "are we still covered?" conversation) so soft-word fog, coverage drift, clock silence, expired ghosts, and Slack folklore do not become the renewal story.

This is complementary to my earlier posts — not a rewrite. For the full messy warranty/SLA dump → clean SLA tracker workflow, see How I turn a messy warranty/SLA dump into a clean SLA tracker. For the mid-coverage honesty pass while dumps are still arriving, see The mid-coverage checklist I use so an SLA tracker stays honest. This third pass is the week-of renewal check: mid-coverage honesty is not enough once someone else will treat covered-until as done.

What "honest enough for week-of renewal" looks like

• Soft words ("fast," "priority," "best effort") are mapped to a measurable target or parked as ask — not mixed as if they were renewal-ready commitments
• Coverage bounds (seats, regions, SKUs, hours) still match what was purchased (or the gap is labeled ask) — not "close enough" before anyone renews
• Start/end and what starts the response clock are written once — folklore that "support has it" is not a clock
• Status is active / expired / superseded / ask — not an expired PDF still marked active
• Slack / sticky folklore is in notes as folklore — not rewritten as the covered-until date
• You can answer "what is still covered this week, until when, for which product?" without reconstructing Slack and a PDF

If the only renewal plan you have is a calendar ping titled "warranty??," week-of renewal honesty has already slipped.

The week-of renewal checklist (run it before anyone renews or claims)

Use this against the near-final SLA tracker and the live artifacts (vendor PDF, portal screenshot, order confirmation, Slack "priority somehow," calendar reminders) before anyone treats covered-until as this week's cash-or-contract truth.

1. Kill soft-word fog before the renew conversation

• [ ] Soft words ("fast," "priority," "best effort," "business hours TBD") on renew-soon rows are mapped to a measurable target or labeled ask — not mixed as if they were the same kind of commitment
• [ ] Warranty window vs support SLA vs uptime clause are still labeled as different commitment types — not mashed into one "covered" cell before renew
• [ ] Dual metrics or conflicting response times stay ask — not silently forced to the friendlier number because renewal felt urgent
• [ ] Skim test: you can answer "what is the real target we are renewing against?" without opening Slack

2. Lock seats, regions, SKUs, and clocks before anyone claims

• [ ] Coverage bounds (seats, regions, SKUs, hours) still match what was purchased (or the gap is ask) — not silently rounded because the portal looked "enterprise somehow"
• [ ] Start/end dates are real calendar dates or named rules mapped to dates — not blank cells that look current
• [ ] What starts the response clock (ticket open, severity set, business hours) is named or ask — not left blank so P1 looks instant at claim time
• [ ] Skim test: you can answer "covered for which product, how fast, until when?" without reconstructing three PDFs

3. Normalize status, expired ghosts, and folklore

• [ ] Status vocabulary is active / expired / superseded / ask — blank rows stay Needs-confirm, not silently "active"
• [ ] Everything still showing "active" when an end date has passed is labeled expired or recheck — not left green for renewal week
• [ ] Evidence for active (PDF page, portal screenshot, order confirmation) sits in notes or source — folklore that "we're covered" is not a status
• [ ] Slack "I think we're fine" / "they said priority" folklore is in notes as folklore — not rewritten as the covered-until date
• [ ] Skim test: sorting by end date shows one clear line per commitment, not a museum of expired ghosts marked active

4. Honesty tripwires (before you treat covered-until as renewal-ready)

• [ ] You did not promote vibes to "all covered" because the sheet looked sparse of red
• [ ] Incomplete sections stay Needs-confirm — not silently promoted to "ready to renew" because the week felt busy
• [ ] Raw dump artifacts (unfinished PDF paste, named complainers, draft notes) are out of the renew view
• [ ] Skim test: a stranger can answer "what is still covered this week, until when, for which product?" from the sheet alone

Soft CTA

If you have a messy warranty/SLA dump and want a clean SLA tracker in 24 hours: slasheet on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not a CPA. Not legal, financial, warranty, insurance, or vendor-negotiation advice — just admin cleanup so the covered-until line still matches what is covered.