The before-you-share checklist I use so a recurring-costs sheet still matches what renews

A recurring-costs sheet can look budget-ready while its story is already wrong: a ghost trial still greens monthly burn; the same card is counted twice under two names; an annual charge is quietly divided into twelve tidy months without a label; a canceled tool remains in the share view; a Slack “looks fine” rewrites the stack; or a superseded dump still ships as this period’s renewals.

Before-you-share is different from a mid-renewal cleanup. This is the pass I run when the sheet is about to leave my hands and someone else may treat every line as what actually renews.

I am Brittany Bonds, a freelancer admin helper. I turn messy subscription dumps into clean recurring-costs sheets. I am not a CPA, bookkeeper, lawyer, or tax advisor, and this is not financial, tax, legal, bookkeeping, budgeting, or cancellation advice. It is an administrative proof-checking routine, not a recommendation about what anyone should keep, cancel, or budget.

This complements How I turn a subscription dump into a recurring-costs sheet and The mid-renewal checklist I use so a recurring-costs sheet stays honest. Those live posts cover the first-pass workflow and the mid-renewal honesty cleanup. This third pass is the pre-share evidence check — not a rewrite of either.

What “honest enough to share” looks like

• Every renewal row and burn total maps to a bank/CSV crumb, receipt, invoice, or a labeled ask — nothing invented for a tidy budget preview.
• Trial, annual, and monthly strength stay labeled; hard monthly burn only appears when a source supports it.
• Same-card duplicates under two names stay merged or labeled duplicate — they are not two renewals.
• Slack guesses and “looks fine” stay labeled guess / ask — not finance-confirmed.
• Superseded or out-of-window dumps are labeled stale or removed from the share view.
• Canceled tools stay flagged once — not silently rewritten as active renewals.
• An emoji reaction or vague “lgtm” is not treated as a locked stack unless the sheet states what was confirmed.

If the only share instruction is “send the clean recurring sheet,” pre-share honesty has already slipped.

The before-you-send checklist

Use this against the near-final sheet and live evidence: the original subscription dump (bank/CSV, receipts, app invoices, card statements), prior period sheet if any, and the mid-renewal scratch trail. The goal is not to make every cell complete. The goal is to make uncertainty visible before the sheet becomes someone else’s budget source of truth.

1. Freeze renewal rows to what actually renews

• [ ] Every renewal row maps to a source crumb, screenshot, export, or a labeled ask — no orphan row gets a confident “this is the stack” look.
• [ ] Ghost trials, template filler, and “bonus” tools that never appeared in the dump stay out or labeled proposed / ask — polish is not permission.
• [ ] Duplicate entries under two phrasings (same card, two merchant names) are merged or marked duplicate — one renewal is not two burn slots because it looked tidy twice.
• [ ] Tool naming stays close to the source; a polished synonym may not be the same product or plan.
• [ ] Skim test: a reader can point from each row back to a source, or see that it still needs confirmation.

An invented renewal row is not automatically useless. It is a proposal. The misleading part is leaving it dressed as what already renews for the period.

2. Keep amount and cadence strength-honest

• [ ] Soft notes (“about twenty a month,” “roughly annual”) stay soft — they are not upgraded to hard monthly burn for neatness.
• [ ] Hard amounts keep a receipt, statement line, date, or confirmer when available — silence is not consent.
• [ ] Annual vs monthly stays labeled; dividing annual into twelve without a note is a rewrite, not a cleanup.
• [ ] Trial vs paid stays labeled; a free trial greening burn is a false renewal.
• [ ] Canceled or paused tools stay flagged canceled / paused / ask — do not leave them active for a prettier stack.
• [ ] Skim test: a reader can tell which lines are locked, which are soft, and which still need confirmation.

This is a consistency check, not budgeting or cancellation advice. I am recording what the dump disclosed, not deciding what anyone must keep.

3. Retire stale dumps before they travel

• [ ] Walked-back, canceled, or out-of-window tools are labeled stale or removed from the share view — they do not still green monthly burn.
• [ ] When bank, receipt, and app invoice disagree, keep the conflict visible as recheck — do not pick the easier amount because it fits the template.
• [ ] Capture or last-checked date exists for material totals — “I cleaned this last week” is not a freshness rule.
• [ ] Raw scratch, rejected options, and unresolved conflicts stay in the evidence trail but out of the clean share view.
• [ ] Skim test: a reader can tell whether each line describes the current dump, an older period, or something still needing confirmation.

A stale renewal line is historical context. The misleading part is leaving it dressed as this period’s share-ready burn.

4. Challenge the Slack “looks fine”

• [ ] Replace “they said looks fine” with the exact tools, amounts, or date range that were confirmed, parked, or never named on the sheet.
• [ ] An emoji reaction, “lgtm,” or vague thumbs-up is labeled by what it covered — it does not silently rewrite burn totals.
• [ ] If Slack approved a different version than the sheet you are about to send, stop and reconcile — do not ship the prettier draft under the older reaction.
• [ ] Make the share ask specific — confirm this tool, this annual split, this cancel flag, this period — instead of asking for another vague thumbs-up.
• [ ] Leave a visible needs confirmation marker where sharing would otherwise create a false record of agreement.
• [ ] Final skim: I can answer “what source supports this line, what still needs confirmation, and what did Slack actually cover?” for every share-ready row.

If a row fails one of these checks, I would rather send a visible needs confirmation label than make the recurring-costs sheet look complete by guessing.

Soft CTA

If you have a messy subscription dump and want it organized into a clean recurring-costs sheet, recurringsheet on Gumroad is $12. Code ADMIN12 takes $2 off. Browse the full shop or the catalog mirror on GitHub Pages.

Not a CPA. Not financial, tax, legal, bookkeeping, budgeting, or cancellation advice — just an admin checklist for keeping a shared recurring-costs sheet tied to what actually renews.