What AI work records should I clean up in October before year-end?
A handover brings the recorded AI work and its verifiable receipts into one proof link. Review the evidence behind each claim, check what was and was not observed, then Accept or Flag.
October is the last month when year-end problems are cheap. Clients still answer, memories of spring jobs are still recoverable from the people who did them, and there are ten working weeks to fix what the cleanup finds. The same list attempted in late December is a different, sadder exercise.
Unaccepted handovers lead the list because they are money-adjacent and time-sensitive: a client who has not recorded a decision by October may be unreachable by December, and an acceptance chased in autumn is a conversation, while one chased at year-end is an escalation. Held jobs come second: every open job should end October either closed with its record complete or carrying a recorded reason it remains open, so the year-end index contains no mysteries. Index gaps third: find them now, while the work's participants can still say what happened, and mark the unrecoverable ones honestly rather than discovering them during the accountant package build.
Exports close the list: run the year's verification test from your own storage (the vendor-exit page in this set has the method), because discovering an export problem in October is an errand and discovering it in January is a crisis.
Checklist: the October cleanup
1. Pending decisions: list every handover awaiting acceptance older than 30 days; chase each with the link and a deadline. 2. Held jobs: close each, or record the reason it stays open and its owner. 3. Index gaps: compare the index against invoices for the year; mark missing records with dates and causes. 4. Exports: pull the year's records into your storage; recompute one receipt per quarter from the export alone. 5. Access sweep: remove connections for finished projects and departed people. 6. File the cleanup note: what was found, what was fixed, what remains open into the new year.
Worked example
Item 1's raw material looks like https://zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 : a complete five-step job, acceptance still pending. In October that is a two-line email with a link. In January it is an open item in the annual report and a question in the accountant package. Same record, different month, different cost.
Frequently asked questions
Why October and not November?
November works too, minus the margin. October leaves room for the slow replies, the client who needs their own internal approval, and the export problem nobody expected. Cleanup lists always find one surprise; the calendar should have room for it.
A client will not respond to the acceptance chase. What do we record?
Record the chases themselves on the job: dates sent, the link, the silence. An unaccepted handover with a documented chase history is a defensible position; one with no history is an oversight, and the difference is entirely in these October minutes.
Should the cleanup delete anything?
Deletion follows the retention schedule, not the cleanup mood. October closes, transfers, and exports; it deletes only what the schedule already condemns, and records that it did so.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai