The mid-schedule checklist I use so an installment tracker stays honest

A PDF payment plan, a sheet with dates in three formats, a Slack thread that says “half up front then the rest somehow,” a calendar reminder labeled “balance??,” and a sticky that guesses “they’re current” are not mid-schedule truth. Mid-schedule is where “mid-month,” “on delivery,” and “net 30 after invoice” sit next to real calendar dates, installment amounts stop adding to the contract, deposits already paid quietly overlap the first row, paid / due / waived / disputed never get written down, and “I think we’re fine” rewrites 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 mid-schedule (and again before anyone treats next-due as cash truth) so the installment tracker stays honest while dumps are still arriving.

(If you want the full messy payment-schedule dump → clean installment tracker workflow, see my earlier post. This one is the second-pass checklist so date fog, amount drift, status silence, and Slack folklore do not quietly rewrite what’s still owed.)

What "honest" looks like mid-schedule

• Every row has client/job, installment #, due date (or named rule → date), amount, status (paid / due / waived / disputed / ask), source, and notes — not vibes
• Installment amounts add to the contract (or the gap is labeled ask) — not silently “close enough”
• Deposits already paid are linked or marked so they do not double-count as installment #1
• Date rules (“mid-month,” “on delivery,” “net 30 after invoice”) are either mapped to a calendar date or parked as ask — not mixed as if they were the same kind of due date
• Open questions (missing amount, dual due dates, disputed row, unknown payer) are listed once so the handoff is honest

If the only “installment tracker” you have is a calendar ping titled “balance??,” mid-schedule honesty has already slipped.

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

Use this against the dump (PDF plan, spreadsheet, Slack “half then somehow,” calendar reminders, prior tracker exports) before you paste everything into a pretty next-due column and call cash current.

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

• [ ] Every scrap is listed once: source, date seen, claim type (dated installment / paid-closed / unknown / duplicate / incomplete), notes
• [ ] Duplicate paste of the same installment across PDF + sheet + Slack is labeled duplicate — not counted twice toward remaining
• [ ] Partial dumps (“about half,” “they’re current,” a Slack ping with no amount) are labeled incomplete — not invented into tidy rows
• [ ] As-of date that matters is named — older cancelled plans stay out or flagged
• [ ] Anything clearly superseded, waived in writing, or belonging to another job is labeled stay-off — do not resurrect as this mid-schedule chase list

2. Lock dates and amounts before you trust next-due

• [ ] Every “due” row has a real calendar date or a named rule mapped to a date in notes — not “mid-month” left as a fake date cell
• [ ] Installment amounts are numbers (or ask) — not “half,” “balance,” or emoji
• [ ] Running total of installment amounts vs contract/total is checked once — gap labeled ask, not rounded away
• [ ] Deposit / retainer already paid is linked to the right installment or marked paid separately — not left to double-count
• [ ] Skim test: you can answer “what’s next due, how much, for which job?” without opening Slack

3. Kill status silence and payer fog

• [ ] Status vocabulary is named (paid / due / waived / disputed / ask) — not blank cells that look current
• [ ] Evidence for paid (receipt, bank note, sheet mark) sits in notes or source — folklore that “they paid” is not a status
• [ ] Dual due dates or conflicting amounts stay ask — not silently forced to the friendlier date
• [ ] Payer / client name drift (Acme / ACME LLC / “their AP”) is normalized with aliases in notes — not three ghost installment lines
• [ ] Everything showing “current” when a disputed row is still open is labeled recheck until status is honest

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

• [ ] Missing amounts sit as ask with what is missing — not invented to tidy the sheet
• [ ] “TBD,” “on delivery,” and “after invoice” without a mapping stay ask — not locked as this Friday
• [ ] Owner (who owns chasing this installment) is named or unowned — folklore that “sales has it” is not ownership
• [ ] Anything you almost guessed (which PDF wins, whether deposit counts as #1, whether waived needs a credit memo) stays in notes as guessed — not locked as truth
• [ ] Slack / sticky reminders that contradict the schedule PDF are labeled conflict — not silently preferred

5. Mid-schedule skim before you call next-due “current”

• [ ] Next-due row matches a quick mental check of known open plans
• [ ] Ask rows and duplicate suspects are countable in under a minute
• [ ] Remaining total is consistent with contract minus paid (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 installments are easier to see — not advice on pricing, collections, or deal structure

Soft CTA

If you want the messy payment-schedule dump turned into a clean installment tracker: https://brittanybonds.gumroad.com/l/installmentsheet

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 next-due line is easier to track and hand off.