For finance & ops teams running the close
The close is monthly. The chasing shouldn't be.
The checklist is the same every month, and so is the scramble. Day three, half the schedule is still open — you're waiting on accruals from one person, the intercompany rec from another — and the list doesn't chase anyone. You do, every single month, one DM at a time, right up against the deadline.
Sarah · Day 3, 9:20am
close is day 5 — still need the marketing accruals and the intercompany rec. who's got them?
○ day 3 of 5 — half the schedule still open
Mike · Day 3
accruals coming, end of day probably
○ promised — not posted
thread staged with our recurring cast
01 · What Ayven does with the same checklist — set it once
The close runs on a schedule instead of on your memory.
Ayven runs the close as a recurring routine — the same checklist, on the same schedule, every month. She reopens each line with its owner, asks each person individually in Slack or Teams, follows up before the deadline instead of after, and where a line links to the tracker she checks it actually posted rather than taking the reply's word for it.
02 · The register — one close status you can trust
A line isn't "done" until the tracker says it posted.
Ayven APP · Day 4, 4:20pm
The intercompany rec was linked to a tracker task, so I checked it instead of taking the "posted" message at its word — the task actually closed there. Here's the close status: what's confirmed, what's outstanding, and who owns the gap.
the close status is composed from what's verified, not from what was promised
03 · It's real — the product, not a promise
The recurring close, set up once.
threads shown are staged with our recurring cast · screenshots are the live product
04 · The honest answer — you already have a checklist
A month-end close checklist is a list, not a chaser.
You almost certainly have a close checklist already — a spreadsheet, a template in your close software, a shared doc. Keep it. The problem was never the list. A list sits there; it doesn't ask Mike for the accruals or notice the reval is late. That part has always been a person — you — doing it by hand. Ayven runs the list you have as a routine and does the asking.
The checklist doesn't chase
A month-end close checklist tells you what's outstanding; it can't ask the person who owes it. So the chasing falls to whoever owns the close, every month, at the worst possible time.
a list is a record, not a follow-upThe same names go quiet every month
The close process is predictable and so are its gaps — the same lines, the same owners, the same "coming end of day." Ayven asks each owner individually and follows up on the ones who don't answer, one at a time.
per-person, not an @channelThe escalation lands before day 5
A gap you learn about at the deadline is a problem. A gap Ayven flags on day 4 — with who owns it and what's blocking — is still fixable. The follow-up moves earlier, not louder.
flagged before, not discovered afterVerified where the line links
When a close line links to a tracked task — Jira, YouTrack, or Asana — Ayven checks it actually posted before marking it done, instead of taking "reconciled" at its word. The status reflects the ledger, not the chat.
checked in the tracker where linked"Our close software already sends reminders."
It does — to email, where the last three reminders died alongside everything else. A reminder isn't a chase: it fires on a timer and stops. Ayven asks each owner where they actually work, tracks who hasn't posted, follows up individually, and when someone stays quiet she changes the approach instead of resending the same nudge — repeat pings to the same person are spaced at least a day apart, and every chase has a point where it stops and reports the gap to you instead.
Set up the close once. Let it run itself.
Start freegive her the checklist and the owners · she reopens it every month, asks, chases, and flags the gaps before the deadline