What should I set up in January so client proof is automatic all year?
Set up six things in January: the recording connection as the default route for client work, the delivery standard (every deliverable a handover), a job index that fills itself, the quarterly tax pull dates, retention dates per class, and the access review. Done once, they make proof a byproduct of the year instead of a project at its end.
Every December scramble is a January decision that was postponed. The six moves on this page are chosen for leverage: each one removes a recurring manual act for the whole year. The default route is the keystone; once client work flows through the connection by default, receipts mint themselves, and every other system on this page becomes a view over records that exist.
The delivery standard and the index convert records into client-facing proof without extra labour: deliverables assemble as handovers, the index lists them by client as they ship, and acceptance decisions land on the records. The calendar moves protect the year's ends: quarterly pulls scheduled now (the estimated-tax page in this set has the method) mean the accountant package assembles from finished quarters, and retention dates set in January mean December's cleanup is executing decisions, not making them under deadline.
The access review is the year's safety item: inventory every agent connection that can touch client work, name its owner, and set the quarterly re-check dates while the calendar is open. Total cost: one focused afternoon. Total saving: every future version of the scramble you did last year.
Checklist: the January setup
1. Default route: client work runs through the connection; exceptions require a named reason. 2. Delivery standard: every deliverable a handover with recorded acceptance; the client note updated to say so. 3. Job index: generated from shipped handovers, by client, reviewed monthly. 4. Tax calendar: four quarterly pull dates and the year-end package date, in the calendar now. 5. Retention: dates per class (delivery, financial, access) written into the index header. 6. Access inventory: connections, owners, quarterly review dates set. Completion test: a job run today appears in the index with its receipt and handover, untouched by hand.
Worked example
The completion test's passing shape is any live record, for example https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 : steps recorded as the work ran, acceptance recorded on it, findable from the index. January's job is making that the automatic fate of every job of the year, not the achievement of a careful few.
Frequently asked questions
It is not January. Is this page useless to me?
No: the setup works any month, and the remaining year still benefits. January is simply the only month where the whole year is ahead of the decision, which is why the page is written for it. Starting in March beats starting in December.
We set this up last year and it drifted by June. What is different this time?
Drift comes from standards held by effort. The completion test is the difference: the index shows what shipped recorded, so drift appears as visible gaps within a month, while correction is still cheap, instead of as a December discovery.
How long does the setup actually take?
An afternoon for a small practice: an hour on the route and standard, an hour on the index and calendar, an hour on access. The retention dates take longest per minute because they are real decisions, which is exactly why January beats December for making them.
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