The mid-coverage checklist I use so an SLA tracker stays honest

A vendor PDF that says “99.9% uptime,” a support portal screenshot with response times in three units, a Slack thread that promises “priority coverage somehow,” a calendar note labeled “warranty??,” and a sticky that guesses “we’re covered” are not mid-coverage truth. Mid-coverage is where “fast response,” “business hours,” and “best effort” sit next to real targets like 4-hour P1, warranty windows stop matching what you bought, seats / regions / product SKUs drift, start and end dates never get written down, and “I think we’re fine” rewrites 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, or insurance advice. It is the checklist I run mid-coverage (and again before anyone treats “are we covered?” as cash-or-contract truth) so the SLA tracker stays honest while dumps are still arriving.

(If you want the full messy warranty/SLA dump → clean SLA tracker workflow, see my earlier post. This one is the second-pass checklist so metric fog, coverage drift, clock silence, and Slack folklore do not quietly rewrite what is still covered.)

What "honest" looks like mid-coverage

• Every row has vendor/product, commitment name, metric/target, coverage bounds (seats/regions/SKUs), start/end (or named rule → date), response clock trigger, status (active / expired / ask / superseded), source, and notes — not vibes
• Soft words (“fast,” “priority,” “best effort”) are either mapped to a measurable target or parked as ask — not mixed as if they were the same kind of commitment
• Coverage bounds match what was actually purchased (or the gap is labeled ask) — not silently “close enough”
• Start/end and what starts the response clock are written once — folklore that “support has it” is not a clock
• Open questions (missing end date, dual metrics, expired PDF still marked active) are listed once so the handoff is honest

If the only “SLA tracker” you have is a calendar ping titled “warranty??,” mid-coverage honesty has already slipped.

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

Use this against the dump (vendor PDF, portal screenshot, Slack “priority somehow,” calendar reminders, prior tracker exports) before you paste everything into a pretty covered-until column and call coverage current.

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

• [ ] Every scrap is listed once: source, date seen, claim type (dated commitment / active-closed / unknown / duplicate / incomplete), notes
• [ ] Duplicate paste of the same commitment across PDF + portal + Slack is labeled duplicate — not counted twice toward coverage
• [ ] Partial dumps (“we’re covered,” “priority somehow,” a Slack ping with no metric) are labeled incomplete — not invented into tidy rows
• [ ] As-of date that matters is named — older superseded PDFs stay out or flagged
• [ ] Anything clearly expired, cancelled, or belonging to another product is labeled stay-off — do not resurrect as this mid-coverage chase list

2. Lock metrics and coverage before you trust covered-until

• [ ] Every “active” row has a real metric/target or a soft word mapped to a measurable target in notes — not “fast response” left as a fake target cell
• [ ] Coverage bounds (seats, regions, SKUs, hours) are numbers/names (or ask) — not “enterprise somehow”
• [ ] Purchased vs promised coverage is checked once — gap labeled ask, not rounded away
• [ ] Warranty window vs support SLA vs uptime clause are labeled as different commitment types — not mashed into one “covered” cell
• [ ] Skim test: you can answer “what’s covered, how fast, until when, for which product?” without opening Slack

3. Kill clock silence and priority folklore

• [ ] Status vocabulary is named (active / expired / superseded / ask) — not blank cells that look current
• [ ] Evidence for active (PDF page, portal screenshot, order confirmation) sits in notes or source — folklore that “we’re covered” is not a status
• [ ] Dual metrics or conflicting response times stay ask — not silently forced to the friendlier number
• [ ] What starts the response clock (ticket open, severity set, business hours) is named or ask — not left blank so P1 looks instant
• [ ] Everything showing “active” when an end date has passed is labeled recheck until status is honest

4. Park guessed windows, TBD rows, and Slack folklore in the open

• [ ] Missing end dates sit as ask with what is missing — not invented to tidy the sheet
• [ ] “TBD,” “renews somehow,” and “business hours TBD” without a mapping stay ask — not locked as this Friday
• [ ] Owner (who owns chasing this vendor commitment) is named or unowned — folklore that “ops has it” is not ownership
• [ ] Anything you almost guessed (which PDF wins, whether seats include contractors, whether expired PDF still applies) stays in notes as guessed — not locked as truth
• [ ] Slack / sticky reminders that contradict the vendor PDF are labeled conflict — not silently preferred

5. Mid-coverage skim before you call covered-until “current”

• [ ] Covered-until / next-renewal row matches a quick mental check of known open commitments
• [ ] Ask rows and duplicate suspects are countable in under a minute
• [ ] Active list is consistent with purchased products (or clearly noted where it differs)
• [ ] You can hand the sheet to someone else without a 10-minute Slack tour
• [ ] Soft CTA only if useful: this is cleanup so coverage is easier to see — not advice on renegotiating vendors, filing claims, or legal interpretation

Soft CTA

If you want the messy warranty/SLA dump turned into a clean SLA tracker: https://brittanybonds.gumroad.com/l/slasheet

Shop: https://brittanybonds.gumroad.com/

Catalog mirror: https://brittany-bonds.github.io/

Code ADMIN12 for $2 off.

No fake CPA or lawyer claims — spreadsheet cleanup so your covered-until line is easier to track and hand off.