DEV Community: Brittany Bonds

The before-you-send checklist I use so a transcript action-item list still matches what was committed

Brittany Bonds — Tue, 22 Sep 2026 00:29:58 +0000

The before-you-send checklist I use so a transcript action-item list still matches what was committed

Mid-action honesty is necessary. Before-you-send is different. The morning you decide "I will email / Slack / paste this list as the plan" is when an invented owner is still looking assigned, a due date nobody said is still looking calendar-ready, a decision is still padded in as a task someone can "own," an open question is still marked closed so the list looks tidy, a filler quote is still dressed up as work, two duplicate follow-ups are both about to ship, and a superseded line from earlier in the call is still live beside the real commitment.

I am Brittany Bonds, a freelancer admin helper. I turn messy Zoom/Meet transcripts into a clean action-item list. I am not a CPA, project manager, lawyer, or meeting facilitator, and this is not project-management, legal, or contractual advice. It is a practical before-you-send checklist for keeping owners, verbs, dues, and open questions visibly honest before anyone treats the list as what the call committed.

This is complementary to my earlier posts, not a rewrite. My first-pass workflow is How I turn a Zoom transcript into a clean action-item list. The second pass is The mid-action checklist I use so a transcript action-item list stays honest. This third pass is the before-you-send check: the moment when someone may share, assign, or chase from the list.

What "honest enough to send" looks like

Send filter shows real commitments only — not filler, duplicates, or superseded folklore still greening
Task / decision / open question / ask are still separated — nothing looks assignable that is still unclear
Every send-ready row has owner, verb + outcome, and evidenced due or is labeled ask / TBD
Decisions sit in a decisions section — not padded into the task list as if someone owns shipping them
Open questions stay open — not closed because the list looked tidier that way
Duplicate "follow ups" about the same topic are one row — not two owners about to get the same email
You can answer "who owns what, by when, what's still undecided?" without reopening the transcript

If the only send plan you have is a sticky labeled "blast the green owners," before-you-send honesty has already slipped.

The before-you-send checklist

Use this against the near-final action-item list and the live artifacts (transcript / Otter/Fireflies export, attendee notes, prior list if any) before anyone treats the sheet as this week's plan truth.

1. Kill invented / duplicate / superseded inflation before anyone hits send

[ ] Invented owners ("team", blank that looks assigned, guessed names) are ask — do not leave them greening Assigned
[ ] Duplicate follow-ups about the same topic are one row — not two chase lines
[ ] Superseded or walked-back lines from earlier in the call are archived — not still looking live
[ ] Filler (jokes, status theater, "sounds good") stays out — not invented into tidy rows
[ ] Skim test: Send shows live commitments only, not a museum of filler and ghosts

2. Separate task, decision, question, and ask before anyone trusts the plan

[ ] Type is task / decision / open question / ask — not a single Task checkbox for everything
[ ] Decisions sit in decisions — padded-as-task folklore is not a plan
[ ] Open questions stay open — closed-for-tidiness is not a commitment
[ ] Rows without owner, verb + outcome, or amount of work clarity are ask — missing identity is not a send list
[ ] Skim test: a new teammate can answer "what is actually assignable today?" from the list alone

3. Lock due dates, owners, and transcript sources

[ ] Due dates exist only when evidenced in the transcript / notes — invented Friday folklore stays guess / ask / TBD
[ ] Every send-ready row maps to a transcript line (or named note) — "I remember we agreed" without a row is not a plan
[ ] Soft scope / as-of is named once (this call only / this week) — older closed noise stays out or flagged
[ ] Private / sensitive lines the attendees said to keep out stay out of any share view
[ ] Skim test: sorting by owner shows one live line per real commitment, not doubles across export + notes

4. Honesty tripwires (before you treat the list as send-ready)

[ ] You did not promote "owner column looks green" to "all assigned and ready to blast"
[ ] Incomplete sections stay Needs-confirm / incomplete — not silently promoted to send-ready because the list looked sparse
[ ] Raw dump artifacts (unfinished paste, named complainers, draft notes) are out of the send view
[ ] Skim test: a stranger can answer "who owns what, by when, what's still undecided?" from the list alone

Soft CTA

If you have a messy Zoom/Meet transcript and want a clean action-item list in 24 hours: actionitems on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not project-management, legal, or contractual advice — just admin cleanup so the plan story matches the transcript.

The week-of chase checklist I use so an AR sheet still matches what is open

Brittany Bonds — Mon, 21 Sep 2026 22:40:07 +0000

The week-of chase checklist I use so an AR sheet still matches what is open

Mid-AR honesty is necessary. Week-of chase is different. The morning you decide "I will chase from this sheet today" is when a paid PDF is still greening Open, a duplicate filename is still summed twice, a credit memo is still filed like a payment that cleared the wrong invoice, a partial still looks like the full balance, a superseded invoice is still on the chase list, and an invented due date is still looking official enough to email about.

I am Brittany Bonds, a freelancer admin helper. I turn messy invoice PDF piles into a clean accounts-receivable sheet. I am not a CPA, bookkeeper, lawyer, tax advisor, or collections agent, and this is not financial, tax, legal, collections, or accounting advice. It is a practical week-of chase checklist for keeping open balances, statuses, and invoice identities visibly honest before anyone treats the sheet as the chase list.

This is complementary to my earlier posts, not a rewrite. My first-pass workflow is How I turn a pile of invoice PDFs into an AR sheet. The second pass is The mid-AR checklist I use so an accounts-receivable sheet stays honest. This third pass is the week-of chase check: the moment when someone may email, call, or escalate from the open column.

What "honest enough to chase" looks like

Open filter shows real money still open — not paid PDFs, duplicates, or voided folklore still greening
Open / partial / credited / void / ask are still separated — nothing looks chaseable that is still unclear
Every chase-ready row has customer, invoice #, amount remaining, and evidenced due date or is labeled ask
Credits reduce the right invoice (or sit as linked negatives) — not misfiled as payments that zero the wrong row
Superseded and replaced invoices are archived — not still on today's chase list beside this week's open balance
Aging buckets (if you use them) use remaining open + evidenced due — tidy buckets that ignore partials are theater
You can answer "who still owes what, by which invoice, as of when?" without reopening the PDF folder

If the only chase plan you have is a sticky labeled "blast the open column," week-of chase honesty has already slipped.

The week-of chase checklist

Use this against the near-final AR sheet and the live artifacts (invoice PDF folder, payment notes, credit memos, bank matches if provided) before anyone treats the sheet as this week's chase truth.

1. Kill paid / duplicate / superseded inflation before anyone hits send

[ ] Paid invoices are marked paid (with paid date when known) — do not leave them greening Open
[ ] Duplicate PDFs of the same invoice # + amount are one row — not two chase lines
[ ] Superseded, voided, or replaced invoices are archived — not still looking live
[ ] Estimates / quotes that look like invoices stay out unless marked billed
[ ] Skim test: Open shows live money only, not a museum of paid and void ghosts

2. Separate open, partial, credit, and ask before anyone trusts the chase filter

[ ] Status is open / partial / credited / void / ask — not a single Open checkbox for everything
[ ] Partials show amount paid + amount remaining — full original still open is silent-partial theater
[ ] Credits / credit memos are separate negatives or linked credits — not misfiled as payments that clear the wrong invoice
[ ] Rows without customer name, invoice #, or amount are ask — missing identity is not a chase list
[ ] Skim test: a new teammate can answer "what is actually chaseable today?" from the sheet alone

3. Lock due dates, aging, and PDF sources

[ ] Due dates exist only when evidenced on the PDF / notes — invented Net-30 folklore stays guess / ask
[ ] Aging buckets (0–30 / 31–60 / 61+) use remaining open + evidenced due — tidy buckets that ignore partials stay incomplete
[ ] Every chase-ready row maps to a PDF (or named export) — folder folklore without a row is not AR
[ ] Soft cutoff / as-of is named once — older closed noise stays out or flagged
[ ] Skim test: sorting by invoice # shows one open line per invoice, not doubles across PDF + export

4. Honesty tripwires (before you treat the sheet as chase-ready)

[ ] You did not promote "folder looks empty of red" to "all open and ready to blast"
[ ] Incomplete sections stay Needs-confirm / incomplete — not silently promoted to chase-ready because the sheet looked sparse
[ ] Private / pricing / legal lines the client said to keep out stay out of any share view
[ ] Raw dump artifacts (unfinished paste, named complainers, draft notes) are out of the chase view
[ ] Skim test: a stranger can answer "who owes what, by which invoice, what's still open?" from the sheet alone

Soft CTA

If you have a pile of invoice PDFs and want a clean AR sheet in 24 hours: arsheet on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not financial, tax, legal, collections, or accounting advice — just admin cleanup so the open story matches the PDFs.

The before-you-share checklist I use so a status one-pager still matches the thread

Brittany Bonds — Mon, 21 Sep 2026 20:41:45 +0000

Mid-thread honesty is necessary. Before-you-share is different. The morning you decide "this one-pager is what we send" is when an older "sounds good" is still greening as a decision, a FINAL_v3 attachment is still masquerading as current, a zombie open answered five replies up is still on the Opens list, a due date invented for the table is still looking official, and a Slack "I think we're aligned" is hitchhiking into the share as status.

I am Brittany Bonds, a freelancer admin helper. I turn long client email threads into a clean status one-pager. I am not a CPA, project manager, lawyer, or communications coach, and this is not financial, tax, legal, or contractual advice. It is a practical before-you-share checklist for keeping stated status, decisions, opens, owners, and attachments visibly honest before anyone treats the page as stakeholder truth.

This is complementary to my earlier posts, not a rewrite. My first-pass workflow is How I turn a long client email thread into a status one-pager. The second pass is The mid-thread checklist I use so a status one-pager stays honest. This third pass is the before-you-share check: the moment when someone may treat the page as the locked stakeholder story.

What "honest enough to share" looks like

Status is one plain sentence grounded in the newest reliable messages — not subject-line weather or a Slack vibe
Decisions made vs still open are separated — quoted "sounds good" is not automatically a decision
Owners and due dates appear only when the thread states them — otherwise they stay open questions
Conflicting last messages are flagged as conflict — not smoothed into one green paragraph
Attachments and links are listed with what they claim — "FINAL_v3" folklore is labeled ask
Zombie opens already answered higher in the chain are closed — not still greening Opens
You can answer "where are we, what's decided, what's open?" without reopening the whole thread

If the only share plan you have is a sticky labeled "send the one-pager," before-you-share honesty has already slipped.

The before-you-share checklist

Use this against the near-final one-pager and the live artifacts (forwarded thread, .eml, PDF print, Gmail select-all, Slack paste of the same chain) before anyone treats the page as stakeholder truth.

1. Kill status drift before the page leaves

[ ] Status (1 line) is grounded in the newest reliable messages — not the subject line, not a week-old "circling back"
[ ] Soft cutoff (last N messages / since date X) still matches what the page claims to cover
[ ] Out-of-office and auto-replies are not counted as human status
[ ] Skim test: you can answer "where are we right now?" without opening Slack

2. Separate decisions, opens, and conflicts before anyone trusts the green story

[ ] Decisions made are only lines that clearly settled something — "sounds good" / emoji reactions stay ask unless the thread locks them
[ ] Open questions are unanswered asks or conflicting statements — not vibes
[ ] Conflicting last messages are labeled conflict — not averaged into one tidy paragraph
[ ] Blockers name who/what is waited on or sit as incomplete
[ ] Skim test: a new teammate can answer "what's decided vs still open?" from the page alone

3. Lock owners, dates, attachments, and zombie opens

[ ] Owners and due dates exist only when stated — blank cells that look assigned are worse than an honest gap
[ ] Invented due dates are either evidenced or labeled guess / ask — not locked because the table looked empty
[ ] Attachment folklore (FINAL, FINAL_v2, final_REAL) is listed with claim type or ask — filenames are not truth
[ ] Zombie opens already answered higher in the thread are closed or parked — do not leave them greening Opens
[ ] Duplicate paste of the same ask across email + Slack + Doc is one open or one labeled duplicate — not three
[ ] Skim test: sorting Opens shows live asks only, not a museum of already-answered ghosts

4. Honesty tripwires (before you treat the page as share-ready)

[ ] You did not promote vibe-alignment to "all decided" because the Opens column looked empty of red
[ ] Incomplete sections stay Needs-confirm / incomplete — not silently promoted to "ready" because the page looked sparse
[ ] Private / pricing / legal lines the client said to keep out stay out — do not invent redaction by guessing
[ ] Raw dump artifacts (unfinished paste, named complainers, draft notes) are out of the share view
[ ] Audience (client / internal / future you) is written once so tone does not rewrite facts
[ ] Skim test: a stranger can answer "where are we, what's decided, what's open?" from the page alone

Soft CTA

If you have a long client email thread and want a clean status one-pager in 24 hours: threadstatus on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not financial, tax, legal, or contractual advice — just admin cleanup so the status story matches the thread.

The month-close checklist I use so a bank CSV category sheet still matches the period

Brittany Bonds — Mon, 21 Sep 2026 18:43:12 +0000

The month-close checklist I use so a bank CSV category sheet still matches the period

Mid-category honesty is necessary. Month-close is different. The morning you decide "this category sheet is the month" is when last month's as-of is still on the header, transfers are still greening as expenses, duplicate merchant rows are still summed twice, personal bleed is still locked as business, guessed categories are still coded as fact, and a raw CSV artifact is hitchhiking into the share.

I am Brittany Bonds, a freelancer admin helper. I turn bank or CSV exports into a clean monthly category sheet. I am not a CPA, bookkeeper, lawyer, or tax advisor, and this is not financial, tax, legal, or accounting advice. It is a practical month-close checklist for keeping stated categories, transfers, duplicates, and unknowns visibly honest before anyone treats the sheet as the closed month.

This is complementary to my earlier posts, not a rewrite. My first-pass workflow is How I turn a bank or CSV export into a monthly category sheet. The second pass is The mid-category checklist I use so a bank CSV category sheet stays honest. This third pass is the month-close check: the moment when someone may treat the sheet as the locked period.

What "honest enough to close" looks like

One as-of date and one period window sit at the top — not three conflicting "through the 31st" notes
Transfers, refunds, and payments are labeled as such — not silently greening expense totals
Duplicate merchant / same-day paste rows are one line or labeled duplicates — not double-counted spend
Personal vs business bleed is separated or marked ask — not locked as business because the month looked tidy
Guessed categories stay guessed or Needs-confirm — not coded as fact
Raw dump artifacts are out of the share view
You can answer "spend by category this period?" without reconstructing six CSV exports

If the only close plan you have is a sticky labeled "send the category totals," month-close honesty has already slipped.

The month-close checklist

Use this against the near-final category sheet and the live artifacts (bank CSV, credit-card export, prior month sheet, notes) before anyone treats the sheet as this period's closed truth.

1. Kill as-of and period drift before the sheet leaves

[ ] One as-of date and one period window sit at the top — not three conflicting notes in different tabs
[ ] Totals are recalculated vs that window — not copied from last month's export
[ ] Everything still showing "this month" when the export ends on the 28th is labeled period drift until recalc
[ ] Skim test: you can answer "through when?" without opening Slack

2. Separate transfers, refunds, and true spend before anyone trusts the totals

[ ] Transfers between own accounts are labeled transfer — not expense
[ ] Refunds and chargebacks are labeled refund — not negative mystery spend that quietly shrinks a category
[ ] Unknown merchant rows stay Needs-confirm — not silently promoted to "misc" because the sheet looked empty of red
[ ] Skim test: you can answer "what actually left the business this period?" without reconstructing six exports

3. Lock sources, duplicates, and guessed categories

[ ] Each complete-looking row has a source (CSV line, statement date, note) — orphan amounts without a source are Needs-confirm
[ ] Duplicate paste across checking + card + prior export is one row or one labeled duplicate — not two spend totals
[ ] Categories filled from "probably software" folklore are labeled guessed — not locked as coded
[ ] Merchant-name drift is normalized with aliases in notes — not three ghost vendors
[ ] Skim test: sorting by category shows one spend line per activity, not a museum of doubles

4. Honesty tripwires (before you treat the sheet as close-ready)

[ ] You did not promote vibes to "all business" because the personal column looked empty of red
[ ] Incomplete sections stay Needs-confirm — not silently promoted to "ready" because the sheet looked sparse
[ ] Raw dump artifacts (unfinished CSV paste, named complainers, draft notes) are out of the share view
[ ] Skim test: a stranger can answer "spend by category this period?" from the sheet alone

Soft CTA

If you have a messy bank or CSV export and want a clean monthly category sheet in 24 hours: ujamx on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not a CPA. Not financial, tax, legal, or accounting advice — just admin cleanup so the category story matches the period.

The pre-share checklist I use so a utilization sheet still matches the period

Brittany Bonds — Mon, 21 Sep 2026 17:52:55 +0000

Mid-period honesty is necessary. Pre-share is different. The morning you decide "I will send this week's / month's utilization to a client, partner, or myself as truth" is when last period's as-of is still sitting on the header, billable theater is still greening the %, non-billable work is still dumped into a foggy "admin" bucket, duplicate timer exports are still summed twice, guessed categories are still locked as coded, and a raw CSV leftover quietly hitchhiking into the share.

I am a freelancer admin helper. I turn messy billable vs non-billable dumps into a clean utilization sheet. I am not a CPA, bookkeeper, lawyer, payroll, or tax advisor — and this is not financial, tax, legal, payroll, or accounting advice. It is the checklist I run before anyone treats the sheet as this period's utilization truth (the final pass before a report, invoice support tab, or capacity conversation) so as-of drift, billable theater, duplicate hours, guessed categories, and raw dump artifacts do not become the share story.

This is complementary to my earlier posts — not a rewrite. For the full messy billable vs non-billable dump → clean utilization sheet workflow, see How I turn a messy billable vs non-billable dump into a clean utilization sheet. For the mid-period honesty pass while dumps are still arriving, see The mid-period checklist I use so a utilization sheet stays honest. This third pass is the pre-share check: mid-period honesty is not enough once someone else will treat the sheet as done.

What "honest enough to share" looks like

One as-of date and period window sit at the top — not three conflicting "through Friday" notes
Billable / non-billable / unknown are still separated — nothing looks billable that is still unclear
Utilization % is recalculated from those buckets vs that as-of — not copied from last export
Duplicate timer + calendar + Slack paste rows are one line or labeled duplicates — not double-counted hours
Guessed categories are labeled guessed or Needs-confirm — not locked as coded
Raw dump artifacts are out of the share view
You can answer "billable vs non-billable this period, by client?" without reconstructing six exports

If the only share plan you have is a sticky labeled "send the % column," pre-share honesty has already slipped.

The pre-share checklist (run it before anyone hits send)

Use this against the near-final utilization sheet and the live artifacts (timer exports, calendar blocks, invoice stubs, prior utilization sheets) before anyone treats the sheet as this period's utilization truth.

1. Kill as-of and period drift before the sheet leaves

[ ] One as-of date and one period window sit at the top — not three conflicting notes in different tabs
[ ] Hours are recalculated vs that window — not copied from last week's export
[ ] Everything still showing "this week" when the export ends last Friday is labeled period drift until recalc
[ ] Skim test: you can answer "through when?" without opening Slack

2. Separate billable / non-billable / unknown before anyone trusts the %

[ ] Status is billable / non-billable / unknown / ask — not mood words or a single checkbox for everything
[ ] Unknown rows stay Needs-confirm — not silently promoted to billable because the % looked low
[ ] Non-billable dumps into "admin" / "misc" are split or labeled — not one foggy bucket that hides capacity
[ ] Skim test: you can answer "what is actually billable this period?" without reconstructing six timers

3. Lock sources, duplicates, and guessed categories

[ ] Each complete-looking row has a source (timer export, calendar, invoice stub) — orphan hours without a source are Needs-confirm
[ ] Duplicate paste across timer + calendar + Slack is one row or one labeled duplicate — not two hour totals
[ ] Categories filled from "probably client work" folklore are labeled guessed — not locked as coded
[ ] Client/name drift is normalized with aliases in notes — not three ghost clients
[ ] Skim test: sorting by client shows one hour line per activity, not a museum of doubles

4. Honesty tripwires (before you treat the sheet as share-ready)

[ ] You did not promote vibes to "all billable" because the % looked empty of red
[ ] Incomplete sections stay Needs-confirm — not silently promoted to "ready" because the sheet looked sparse
[ ] Raw dump artifacts (unfinished CSV paste, named complainers, draft notes) are out of the share view
[ ] Skim test: a stranger can answer "billable vs non-billable this period, by client?" from the sheet alone

Soft CTA

If you have a messy billable vs non-billable dump and want a clean utilization sheet in 24 hours: utilizationsheet on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not a CPA. Not financial, tax, legal, payroll, or accounting advice — just admin cleanup so the utilization story matches the period.

The before-you-send checklist I use so a one-page client brief still matches the ask

Brittany Bonds — Mon, 21 Sep 2026 17:02:08 +0000

The before-you-send checklist I use so a one-page client brief still matches the ask

The one-page brief can look finished long before the ask is settled. Two goals can survive from meeting notes into Slack, an opinion can get dressed up as a decision, and an open question can become a requirement because it has a tidy heading. Add a remembered budget and a missing stakeholder, and “I think we're aligned” can rewrite the send.

I am Brittany Bonds, a freelancer admin helper. I turn messy meeting notes into a clean one-page client brief. I am not a CPA, lawyer, strategist, or engagement attorney, and this is not legal, financial, tax, or contractual advice. It is a practical notes-to-brief checklist for keeping stated facts, decisions, questions, and constraints visibly separate before a page leaves the draft folder.

This is complementary to my earlier posts, not a rewrite. My first-pass workflow is How I turn messy meeting notes into a one-page client brief. The second pass is The mid-brief checklist I use so a one-page client brief stays honest. This third pass is the before-you-send check: the moment when someone may treat the one-pager as the locked ask.

What “honest enough to send” looks like

A primary goal is clear, or competing goals are labeled conflict / ask
Decisions are supported by a source, while opinions remain opinion or assumption
Open questions are visibly open, with an owner or a clear next ask
Budget, timeline, scope, tools, and audience match the latest source — or the mismatch is recheck
The stakeholder list includes the person who can quietly veto the direction
The send note does not claim alignment that the brief itself cannot show

If the only proof of alignment is “I think we're aligned,” I stop before sending.

The before-you-send checklist

Use this against the brief and its source trail: meeting notes, Slack, email, calendar, prior brief, intake form, and decision log. The goal is visible uncertainty, not a green-looking page.

1. Reconcile the ask, not just the wording

[ ] Write the requested outcome in one sentence and name the audience — client, internal team, or both
[ ] If notes and Slack contain two goals, keep both visible and label the conflict; do not pick the easier one because it fits the page
[ ] Compare the brief's “success” line with the latest source; a polished synonym may not be the same ask
[ ] Mark anything that came from one person's interpretation as opinion or assumption, not client-confirmed fact

2. Separate decisions from questions

[ ] Give each locked decision a source, date, or named decision-maker when available
[ ] Keep “should we,” “could we,” and “what about” items under open question — a heading does not turn them into requirements
[ ] Add an owner or next ask to material questions; “TBD” alone is not a handoff
[ ] Do not convert “we can probably do that” into scope, deliverable, or acceptance criteria
[ ] Skim test: a reader can count the unresolved questions without guessing which green bullets are still negotiable

3. Stop constraint drift at the send boundary

[ ] Recheck budget, timeline, scope, tools, format, and brand or audience limits against the latest source
[ ] Put conflicting values side by side as recheck — do not average a $2,000 guess and a $3,000 note into “flexible budget”
[ ] Label changed constraints with their source and date; old context is not current permission
[ ] Skim test: the brief says what is included, excluded, and still waiting for confirmation

4. Find the quiet veto before it finds the send

[ ] List the approver, day-to-day contact, reviewer, and anyone whose sign-off can stop the work
[ ] Check whether the quiet veto appears in the source trail even if they were absent from the meeting
[ ] Name the missing approval as ask rather than treating silence as consent
[ ] Keep private names, credentials, and sensitive raw notes out of the share view
[ ] Skim test: the recipient knows who can approve, who can comment, and what happens if that person has not answered

5. Challenge the alignment sentence

[ ] Replace “I think we're aligned” with the exact points that are confirmed, open, or conflicting
[ ] Read the brief once as a skeptical recipient: what would you reasonably think is now locked?
[ ] Make the send ask specific — confirm goal, owner, constraint, decision, or open question — instead of asking for a vague thumbs-up
[ ] Leave a visible needs confirmation marker where sending would otherwise create a false record
[ ] Final skim: the brief and send message tell the same story without requiring a Slack archaeology project

Soft CTA

If you want messy meeting notes turned into a clean one-page client brief: hubuve on Gumroad. Use code ADMIN12 for $2 off. Shop the live catalog or browse the GitHub Pages catalog.

I am not a CPA, and this is not legal, financial, tax, or contractual advice — just admin cleanup so the brief you send still matches the ask you can actually support.

The week-of close checklist I use so a receipt spreadsheet still matches the month

Brittany Bonds — Mon, 21 Sep 2026 00:09:52 +0000

Mid-month cleanup is necessary. A week-of close is different. This is the pass I run when someone is about to rely on the receipt spreadsheet for a reimbursement send, a bookkeeping handoff, a tax folder drop, or a simple “are we caught up for the month?” conversation. At that point, a dual date is not a harmless note, a personal lunch still looking business is not a rounding error, and a Slack message saying “I think we’re caught up” cannot quietly turn an incomplete dump into a closed month.

I am a freelancer admin helper. I turn a month of receipt photos into a clean spreadsheet. I am not a CPA, bookkeeper, tax advisor, or auditor — and this is not financial, tax, legal, or accounting advice. It is a practical spreadsheet and close checklist for keeping stated facts, photo evidence, and unresolved questions separate.

This is complementary to my earlier posts, not a rewrite. For the full receipt-photo dump → clean spreadsheet workflow, see How I turn a month of receipt photos into a clean spreadsheet. For the mid-month pass while dumps are still arriving, see The mid-month checklist I use so a receipt spreadsheet stays honest. This third pass starts with the close boundary and the intended handoff: what can the sheet honestly say this week?

What “honest enough for a week-of close” looks like

The month boundary and as-of date are explicit — not an old export wearing a current-looking filename
One receipt maps to one row, with date, vendor, amount, and currency confirmed, missing, or marked ask — not two conflicting photos silently merged into one total
Personal purchases cannot masquerade as business just because they sat in the same camera roll
Tips sit with the base fare (or ask) — floating tip screenshots are not a second expense
Category is stable enough to hand off — mid-sheet drift and “software somehow” folklore are labeled, not averaged
Slack recollections are labeled folklore or needs recheck unless the photo or a source supports them
A reader can tell what was photo-backed, what was estimate-only, and what still needs confirmation without reconstructing a message thread

If the only close evidence is a message titled “I think we’re caught up,” the week-of pass has already slipped.

The week-of close checklist (run it before anyone treats the sheet as truth)

Use this against the near-final spreadsheet and the live artifacts: the camera roll, Drive folder, email forwards, screenshots, bank-app captures, prior month export, and reimbursement notes. The point is not to make every row green. The point is to make every row legible.

1. Set the close boundary before you trust the total

[ ] Write the month (or date range), timezone rule if travel mattered, and what “included” means for this close
[ ] Keep older months and prior exports as sources, not as current truth — superseded rows are labeled prior or recheck
[ ] List dumps that were not reviewed — a late email forward or a second phone’s camera roll should not disappear into a blank cell
[ ] Skim test: you can answer “as of when, for which cards/accounts, under what include rule?” without opening Slack

2. Match each receipt to one row

[ ] Use date, vendor, amount, and a short description to match the photo — not only a vague label such as “lunch”
[ ] If two photos show the same receipt, keep one as duplicate and do not double-count the total
[ ] If one photo could map to two rows, do not invent a second expense just because the sheet has room
[ ] Record an amount only when it was readable on the receipt or supported by a source — never fill a blank with a remembered round number
[ ] Separate tip-only screenshots from the base fare when the close rule needs both; otherwise state why they stay grouped
[ ] Skim test: every included receipt has one row, and every unresolved match is visible from that row

A dual date or dual amount is not a formatting problem. It may be a timezone shift, a refunded charge, a tip added later, or two visits collapsed into one photo. The sheet can say date conflict — needs photo recheck and still be useful. It cannot honestly say “closed” while leaving both values active.

3. Keep personal bleed out of the business total

[ ] Flag personal, mixed, or unknown purchases with an explicit status — do not leave them looking reimbursable because the camera roll was messy
[ ] If a receipt was already client-reimbursed or paid on a different card, mark it stay-off for this close rather than counting it twice
[ ] “Probably business” and “I usually expense that” stay ask or folklore — they are not categories
[ ] Skim test: the business total does not include a row the evidence says was personal, reimbursed elsewhere, or unknown

4. Pin tips, currency, and category before the handoff

[ ] Tips sit on the same row as the base fare, or are labeled ask / n/a — floating tip screenshots are not a second vendor
[ ] Currency is named once per row (USD / other / ask) — mixed currencies without a note are not one month total
[ ] Category uses one stable vocabulary for the close — mid-sheet renames and “software somehow” folklore stay in notes as ask
[ ] Do not average two categories into a tidy label because the sheet looked sparse of red
[ ] Skim test: sorting by category and currency does not invent a cleaner story than the receipts support

5. Reconcile the close without letting Slack rewrite it

[ ] Mark each row as photo-backed, source-backed, estimate, duplicate, personal, out-of-range, or ask using a small, consistent vocabulary
[ ] Put the evidence for a material amount in Source or Notes: receipt photo, email forward, bank capture, or named document
[ ] Label “I think we’re caught up,” “that was about forty,” and similar messages as folklore unless a later check supports them
[ ] Resolve duplicate sightings and stale totals before updating the month total
[ ] Do not use a Slack reaction, a green cell, or an unchallenged old export as a substitute for a close result
[ ] Skim test: someone reviewing the sheet can distinguish photo-backed spend from remembered spend in under a minute

6. Honesty tripwires (before you treat the month as closed)

[ ] You did not promote vibes to “caught up” because the sheet looked tidy
[ ] Incomplete rows stay ask — not silently promoted to closed because the week felt busy
[ ] Raw dump artifacts (unlabeled screenshots, named complainers, draft notes, secret card digits) are out of the share view
[ ] Skim test: a stranger can answer “what is still missing, which rows are soft, and what total is honest for this month?” from the spreadsheet alone

Soft CTA

If you have a month of receipt photos and want a clean spreadsheet in 24 hours: wxbclt on Gumroad ($15). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not a CPA. Not financial, tax, legal, or accounting advice — just admin cleanup so the month-close line still matches what the receipts support.

The week-of count checklist I use so an equipment asset register still matches what is on hand

Brittany Bonds — Sun, 20 Sep 2026 22:33:26 +0000

The week-of count checklist I use so an equipment asset register still matches what is on hand

Mid-register cleanup is necessary. A week-of physical count is different. This is the pass I run when someone is about to rely on the register for a board packet, an insurance conversation, a move, a renewal, or a simple “what do we actually have?” handoff. At that point, a dual serial is not a harmless note, “somewhere” is not a location, and a Slack message saying “I think we still have it” cannot quietly turn a last-seen item into on-hand truth.

I am a freelancer admin helper. I turn messy equipment dumps into clean asset registers. I am not a CPA, bookkeeper, insurance agent, or tax advisor — and this is not financial, tax, legal, insurance, or depreciation advice. It is a practical spreadsheet and physical-count checklist for keeping stated facts, observed facts, and unresolved questions separate.

This is complementary to my earlier posts, not a rewrite. For the full equipment dump → asset register workflow, see How I turn a messy equipment dump into a clean asset register. For the mid-register pass while identity, proof, and warranty details are still being cleaned up, see The mid-register checklist I use so an equipment asset register stays honest. This third pass starts with the physical count and the intended handoff: what can the register honestly say this week?

What “honest enough for a week-of count” looks like

The count boundary and as-of date are explicit — not an old export wearing a current-looking filename
One physical item maps to one row, with a serial or asset tag confirmed, missing, or marked ask — not two conflicting serials silently merged
Location and custodian are specific enough to check — home office, storage shelf B, or client site, not “somewhere”
Disposed, returned, replaced, loaned, or missing items cannot masquerade as active on-hand equipment
Warranty end is a sourced date or ask — “probably covered” is not a date
Slack recollections are labeled folklore or needs recheck unless the count or a source supports them
A reader can tell what was physically seen, what was record-only, and what still needs confirmation without reconstructing a message thread

If the only count evidence is a message titled “I think we still have it,” the week-of pass has already slipped.

The week-of count checklist (run it before anyone treats the register as truth)

Use this against the near-final register and the live artifacts: the prior register, serial photos, receipts, warranty documents, storage notes, loan records, return confirmations, and the locations where equipment is supposed to be. The point is not to make every row green. The point is to make every row legible.

1. Set the count boundary before you walk around

[ ] Write the count date, time window, and locations included — a Friday desk check is not automatically a whole-business count
[ ] State what “on hand” means for this pass: physically seen, confirmed by named custodian, or another documented rule
[ ] Keep older exports and prior counts as sources, not as current truth — superseded rows are labeled prior or recheck
[ ] List locations that were not checked — closed storage, a client site, a travel bag, or a home office should not disappear into a blank cell
[ ] Skim test: you can answer “as of when, in which places, under what on-hand rule?” without opening Slack

2. Match each physical item to one row

[ ] Use the serial, asset tag, model, and a short physical description to match the item — not only a generic name such as “the laptop”
[ ] If two serials appear for one item, keep both in notes and set the row to ask or recheck until one is verified
[ ] If one serial appears on two rows, do not count two physical items just because the register has two lines
[ ] Record a visible serial or asset tag only when it was actually seen in the count or supported by a source — never fill a blank with a guessed number
[ ] Separate included accessories or kits when the count rule needs separate custody; otherwise state why they remain grouped
[ ] Skim test: every counted item has one row, and every unresolved identity conflict is visible from that row

A dual serial is not a formatting problem. It may be a swapped sticker, a replacement device, a serial copied from an order, or two devices collapsed into one row. The register can say serial conflict — needs photo or owner confirmation and still be useful. It cannot honestly say “confirmed” while leaving both numbers active.

3. Replace “somewhere” with a checkable location

[ ] Name the current location at the level needed for a recheck: room, shelf, cabinet, bag, vehicle, client site, or custodian
[ ] If the item moved during the week, record the current location and the move note separately from the old location
[ ] “Someone has it,” “with ops,” and “somewhere in storage” stay ask, unowned, or recheck — they are not locations
[ ] For shared equipment, name the custodian or checkout record rather than assigning ownership by assumption
[ ] For a client-site, travel, or loaned item, record the expected return or next check as a note, not as proof that it is physically present
[ ] Skim test: another person could find or recheck the item using the register alone

4. Remove disposed ghosts from active on-hand

[ ] Compare each apparent on-hand row with return, sale, RMA, replacement, disposal, or loss evidence
[ ] Mark disposed, returned, replaced, loaned, missing, or unknown items with the agreed status — do not leave them active because the old row is convenient
[ ] Keep a disposed or historical record when useful, but make the status and as-of boundary unmistakable
[ ] If a replacement has a new serial, do not let the old serial inherit the new device’s on-hand status
[ ] Treat “we probably got rid of that” as recheck, not as a completed disposal record and not as active inventory
[ ] Skim test: the active on-hand count does not include a device that the evidence says was sold, returned, replaced, or otherwise gone

An old row can be valuable history without being current inventory. I would rather see “disposed — confirmation missing” than a tidy active row that creates a false count.

5. Date warranty facts instead of repeating folklore

[ ] Capture the warranty end from a certificate, order record, manufacturer portal, or other named source when available
[ ] Keep “registered?” separate from “warranty end” — registration status does not supply a missing end date
[ ] Leave the end date ask when the source says only “standard warranty” or someone says “it should still be covered”
[ ] Keep dual warranty dates visible until the source and the item identity agree
[ ] Do not extend, backdate, or infer coverage because the purchase year looks familiar
[ ] Skim test: every date in the warranty column has a source or an explicit unresolved label

6. Reconcile the count without letting Slack rewrite it

[ ] Mark each row as physically seen, custodian-confirmed, record-only, not located, disposed, or ask using a small, consistent vocabulary
[ ] Put the evidence for a material status in Source or Notes: count photo, serial sticker, return email, custodian confirmation, or named document
[ ] Label “I think we still have it,” “it is probably in the closet,” and similar messages as folklore unless a later check supports them
[ ] Resolve duplicate sightings and stale confirmations before updating the on-hand count
[ ] Do not use a Slack reaction, a green cell, or an unchallenged old row as a substitute for a count result
[ ] Skim test: someone reviewing the register can distinguish observed on-hand from remembered on-hand in under a minute

7. Run the handoff and board-or-insurance tripwires

[ ] The header states the as-of date, count scope, exclusions, and unresolved exception count
[ ] The active count, disposed count, unknown count, and recheck list can be explained without mental arithmetic across old tabs
[ ] Dual serials, vague locations, disposed ghosts, warranty gaps, and folklore are grouped in an exception view or clearly marked in-row
[ ] Raw photos, receipts, and private messages are linked or named appropriately without pasting unnecessary personal or secret information into the share view
[ ] The register says what it supports and what it does not — a count snapshot is not automatically a valuation, coverage decision, tax schedule, or depreciation conclusion
[ ] Final skim: a new reader can answer “what was actually seen, where, as of when, and what still needs confirmation?” from the register alone

Soft CTA

If you have a messy equipment dump and want a clean asset register with a visible question and exception list, assetssheet on Gumroad is $12. Code ADMIN12 gives $2 off. You can also browse the full shop or the catalog mirror. Use whichever is useful; there is no need to rush a count that still has unresolved serials or locations.

Not a CPA, bookkeeper, insurance agent, or tax advisor. Not financial, tax, legal, insurance, or depreciation advice — just practical admin cleanup so the week-of on-hand line says what the count can actually support.

The week-of kickoff checklist I use so a client onboarding one-pager still matches what is ready

Brittany Bonds — Sun, 20 Sep 2026 15:32:25 +0000

Mid-onboarding honesty is necessary. Week-of kickoff is different. The morning you decide "they are ready for kickoff / week one starts / send the welcome pack" is when dual start dates are still unresolved, access still says "later" with no owner, billing flags are still TBD folklore, kickoff agenda items are still living only in Slack, and a sticky that says "I think they're ready somehow" is still rewriting the ready-for-kickoff line.

I am a freelancer admin helper. I turn messy client onboarding dumps into a clean checklist one-pager. I am not a CPA, bookkeeper, lawyer, or engagement attorney — and this is not legal, financial, tax, or contractual advice. It is the checklist I run before anyone treats "they're onboarded" as week-one truth (the final pass before a kickoff call, a welcome send, or an "are we ready?" conversation) so dual-date fog, access silence, billing TBD folklore, and Slack vibes do not become the kickoff story.

This is complementary to my earlier posts — not a rewrite. For the full messy client onboarding dump → clean checklist one-pager workflow, see How I turn a messy client onboarding dump into a clean checklist one-pager. For the mid-onboarding honesty pass while dumps are still arriving, see The mid-onboarding checklist I use so a client checklist one-pager stays honest. This third pass is the week-of kickoff check: mid-onboarding honesty is not enough once someone else will treat ready-for-kickoff as done.

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

Legal/business name and primary contact match once (or the gap is labeled ask) — not two welcome emails left unresolved on the share view
Access items name tool + vault-link vs secret-handoff status — secrets never sit on the one-pager
Kickoff agenda and first deliverables are named once — folklore that "we'll cover it live" is not a checklist
Billing setup flags are flags only (payment method on file, W-9 requested, invoice contact) — not silently "done" because the call is tomorrow
Dual start dates / dual contacts / TBD items stay ask — not promoted to green because the calendar ping landed
You can answer "what is still missing, who owns it, by when, for this kickoff?" without reconstructing Slack

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

The week-of kickoff checklist (run it before anyone treats ready as truth)

Use this against the near-final checklist one-pager and the live artifacts (intake export, welcome email chain, Slack/Notion notes, prior checklist PDF, kickoff invite) before anyone treats "they're onboarded" as week-one truth.

1. Kill dual-date and dual-contact fog before the call

[ ] Legal/business name on the share view matches the signed or intake source (or is labeled ask) — not two spellings treated as the same client
[ ] Primary contact + backup are written once (or ask) — not three "who do we ping?" threads left open
[ ] Start / kickoff date is one clear calendar rule — dual welcome emails with different dates stay ask, not silently averaged
[ ] Skim test: you can answer "who is the client contact and when does week one start?" without opening Slack

2. Lock access, billing flags, and agenda before anyone shares "ready"

[ ] Access rows name the tool and whether vault link vs secret handoff is done — never paste passwords onto the page
[ ] "Access later" / "brand kit somehow" rows have an owner or stay ask — not blank cells that look finished for kickoff
[ ] Billing setup flags (payment method on file, W-9 requested, invoice contact) are flags only — not silently promoted to complete because the invite went out
[ ] Kickoff agenda and first deliverables are named once on the page — folklore that "we'll cover it live" is not a checklist
[ ] Skim test: you can answer "what is still missing for kickoff, who owns it?" without reconstructing three threads

3. Normalize status, owner silence, and folklore

[ ] Status vocabulary is done / pending / ask / blocked — blank rows stay Needs-confirm, not silently "ready"
[ ] Owner for each material open item sits in notes — folklore that "ops has it" is not a status
[ ] Evidence for "done" (form reply, vault link placed, invite accepted) sits in notes or source — folklore that "I think they're ready" is not a checklist
[ ] Slack "send them the usual" / sticky "Stripe somehow" folklore is in notes as folklore — not rewritten as a green row
[ ] Skim test: sorting by status shows one clear line per item, not a museum of vibes marked ready

4. Honesty tripwires (before you treat ready-for-kickoff as share-ready)

[ ] You did not promote vibes to "all set" because the sheet looked sparse of red
[ ] Incomplete sections stay Needs-confirm — not silently promoted to "ready for kickoff" because the week felt busy
[ ] Raw dump artifacts (unfinished intake paste, named complainers, draft notes, secret paste) are out of the share view
[ ] Skim test: a stranger can answer "what is still missing, who owns it, by when, for this kickoff?" from the one-pager alone

Soft CTA

If you have a messy client onboarding dump and want a clean checklist one-pager in 24 hours: onboardpage 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, tax, or contractual advice — just admin cleanup so the ready-for-kickoff line still matches what is ready.

The pre-share checklist I use so a budget variance sheet still matches the period

Brittany Bonds — Sat, 19 Sep 2026 17:26:59 +0000

Mid-period honesty is necessary. Pre-share is different. The morning you decide "this variance goes to the client / the board / the 'are we over?' conversation" is when category spellings are still fogging the share view, planned amounts still do not match the approved plan, spent and committed are still mashed into one number, the as-of date is still blank or three exports old, and a Slack "I think we're under somehow" is still rewriting the over/under line.

I am a freelancer admin helper. I turn messy budget vs spend dumps into a clean variance sheet. I am not a CPA, bookkeeper, lawyer, or tax advisor — and this is not financial, tax, legal, or accounting advice. It is the checklist I run before anyone treats over/under as this period's cash-or-board truth (the final pass before a client share, a board glance, or an "are we over?" conversation) so category fog, plan drift, spent-vs-committed mash, as-of silence, and Slack folklore do not become the share story.

This is complementary to my earlier posts — not a rewrite. For the full messy budget vs spend dump → clean variance sheet workflow, see How I turn a messy budget vs spend dump into a clean variance sheet. For the mid-period honesty pass while dumps are still arriving, see The mid-period checklist I use so a budget variance sheet stays honest. This third pass is the pre-share check: mid-period honesty is not enough once someone else will treat over/under as done.

What "honest enough for pre-share" looks like

Category / line names match the approved plan vocabulary (or the gap is labeled ask) — not three spellings of "ads" on the share view
Planned amounts still match the approved plan (or the gap is ask) — not silently rounded because the sheet looked sparse
Spent vs committed are labeled as different columns — not mashed into one "used" number before anyone shares
Period / as-of is one clear rule (month, week, export date) — not blank cells that look current
Slack / sticky folklore is in notes as folklore — not rewritten as the variance
You can answer "what is over or under this period, for which line, as of when?" without reconstructing Slack and three exports

If the only share plan you have is a calendar ping titled "budget??," pre-share honesty has already slipped.

The pre-share checklist (run it before anyone treats over/under as truth)

Use this against the near-final variance sheet and the live artifacts (approved plan PDF, bank/CSV export, invoice pile, Slack "we're under somehow," calendar reminders) before anyone treats over/under as this period's cash-or-board truth.

1. Kill category fog before the share conversation

[ ] Category / line names on share-soon rows match the approved plan vocabulary or are labeled ask — not mixed spellings treated as the same line
[ ] "Misc," "other," and "tools somehow" stay ask or get mapped — not silently promoted to a clean line because the share felt urgent
[ ] Dual plans or conflicting category trees stay ask — not silently forced to the friendlier tree
[ ] Skim test: you can answer "which plan line is this variance against?" without opening Slack

2. Lock planned, spent, committed, and as-of before anyone shares

[ ] Planned amounts still match the approved plan (or the gap is ask) — not silently rounded because the portal looked "close enough"
[ ] Spent vs committed are separate (or clearly labeled) — not mashed into one "used" cell before share
[ ] Period / as-of is a real calendar rule or named export date — not blank cells that look current
[ ] Skim test: you can answer "over or under for which line, as of when?" without reconstructing three exports

3. Normalize status, owner silence, and folklore

[ ] Status vocabulary is planned / spent / committed / ask — blank rows stay Needs-confirm, not silently "fine"
[ ] Owner / source for each material variance sits in notes — folklore that "finance has it" is not a status
[ ] Evidence for material over/under (export row, invoice, plan page) sits in notes or source — folklore that "we're under" is not a variance
[ ] Slack "I think we're fine" / "ads somehow" folklore is in notes as folklore — not rewritten as the over/under line
[ ] Skim test: sorting by variance shows one clear line per category, not a museum of vibes marked fine

4. Honesty tripwires (before you treat over/under as share-ready)

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

Soft CTA

If you have a messy budget vs spend dump and want a clean variance sheet in 24 hours: budgetsheet on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not a CPA. Not financial, tax, legal, or accounting advice — just admin cleanup so the over/under line still matches the period.

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

Brittany Bonds — Sat, 19 Sep 2026 16:04:23 +0000

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.

The week-of due checklist I use so an installment tracker still matches what is owed

Brittany Bonds — Fri, 18 Sep 2026 16:50:33 +0000

Mid-schedule honesty is necessary. Week-of due is different. The morning you decide "this installment is due and I will invoice / chase / treat next-due as cash truth" is when mid-month and on-delivery are still sitting where a calendar date should be, the amounts still do not add to the contract, a deposit already paid is still double-counting as installment #1, paid / due / waived / disputed is still blank, and a Slack "I think we're fine" is still rewriting the next-due line.

I am a freelancer admin helper. I turn messy payment-schedule dumps into a clean installment tracker. I am not a CPA, bookkeeper, lawyer, or tax advisor — and this is not financial, tax, legal, collections, or accounting advice. It is the checklist I run before anyone treats next-due as this week's cash truth (the final pass before an invoice, remittance ask, or "are we current?" conversation) so date fog, amount drift, deposit overlap, status silence, and Slack folklore do not become the due story.

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

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

Every due-soon row has a real calendar date — not mid-month / on-delivery / net-30 still pretending to be a date
Installment amounts still add to the contract (or the gap is labeled ask) — not "close enough" before you invoice
Deposits already paid are linked or marked — not double-counted as installment #1 this week
Status is paid / due / waived / disputed / ask — not blank vibes
Payer / client names are normalized — not three ghost payers for one job
You can answer "what is due this week, by whom, for how much?" without reconstructing Slack and a PDF

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

The week-of due checklist (run it before anyone invoices or chases)

Use this against the near-final installment tracker and the live artifacts (PDF plan, prior invoices, deposit receipts, Slack "half then somehow," calendar reminders) before anyone treats next-due as this week's cash truth.

1. Kill date fog before the chase starts

[ ] Mid-month / on-delivery / net-30-after-invoice rows due this week are mapped to one calendar date or labeled ask — not mixed as if they were the same kind of due
[ ] One as-of / "due through" note sits at the top — not three conflicting "this Friday" notes
[ ] Rows still showing last month's due when the plan moved are labeled date drift until recalced
[ ] Skim test: you can answer "what is due this week?" without opening Slack

2. Lock amounts, deposits, and status before anyone invoices

[ ] Installment amounts for this job still add to the contract (or the gap is ask) — not silently rounded because the invoice looked nicer
[ ] Deposits already paid are linked or marked paid — not sitting as installment #1 again
[ ] Status is paid / due / waived / disputed / ask — blank rows stay Needs-confirm, not silently "due"
[ ] Skim test: you can answer "what is still owed vs already paid?" without reconstructing three PDFs

3. Normalize payers, sources, and folklore

[ ] Each complete-looking row has a source (PDF plan, invoice, Slack confirmation) — orphan due amounts without a source are Needs-confirm
[ ] Payer / client name drift is normalized with aliases in notes — not three ghost payers
[ ] Slack "I think we're fine" / "they said next week" folklore is in notes as folklore — not rewritten as the next-due date
[ ] Skim test: sorting by due date shows one clear line per installment, not a museum of duplicates

4. Honesty tripwires (before you treat next-due as chase-ready)

[ ] You did not promote vibes to "all current" because the sheet looked sparse of red
[ ] Incomplete sections stay Needs-confirm — not silently promoted to "ready to invoice" because the week felt busy
[ ] Raw dump artifacts (unfinished PDF paste, named complainers, draft notes) are out of the chase view
[ ] Skim test: a stranger can answer "what is due this week, by whom, for how much?" from the sheet alone

Soft CTA

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

Not a CPA. Not financial, tax, legal, collections, or accounting advice — just admin cleanup so the due story matches what is owed.