How do I get my AI work record system back on track after summer?
Run the September reset: scan the summer's job index for gaps and mark them, chase every client decision that went quiet in July and August, re-confirm the access inventory against who actually has access now, and restart the weekly review rhythm. Review the receipt and actual deliverable before accepting a handover.
Summer does not break record systems dramatically; it relaxes them. Covering staff deliver without the usual steps, decisions wait out holidays on both sides, a contractor's access outlives the contractor's project, and the weekly review quietly becomes monthly, then aspirational. None of it is visible until fall volume arrives and the small drifts compound at speed.
The reset works because each move targets a specific drift. The index scan finds the summer's unrecorded and half-recorded work while the people who did it can still label it honestly (summaries for the gaps, marked as summaries, never retrofitted receipts). The decision chase clears the acceptance backlog before fall adds its own, and a chase in September is a friendly nudge where the same chase in November is an escalation. The access re-confirmation closes the season's quiet grants: summer help, interns, trial tools, each either confirmed as standing access with an owner or revoked on the record.
The rhythm restart is the move that keeps the other three from being theatre: the weekly scan-and-sample review goes back on the calendar with a named owner, starting the first full week of September, because a system repaired once and then unwatched is just a system whose next drift has a start date.
Checklist: the September reset
1. Index scan: the summer's jobs listed; gaps marked as summaries with dates, never backfilled as receipts. 2. Decision chase: every handover pending over 30 days chased with its link; chases recorded. 3. Access re-confirmation: the inventory walked line by line; summer grants confirmed with owners or revoked, on the record. 4. Open items: held jobs closed or re-owned with reasons. 5. Rhythm restart: the weekly review calendared with a named owner from the first full week. 6. Fall readiness: the delivery-setup checklist from this set reviewed against the season's expected volume.
Worked example
The chase list's typical head: a record like https://zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 , complete work, decision pending. Summer produces a shelf of these in every practice; the reset's second move exists so the shelf is emptied by conversation in September rather than discovered by an auditor, or a dispute, later.
Frequently asked questions
Our summer was quiet, not chaotic. Do we still need the reset?
Run the short version: the index scan and the access re-confirmation. Quiet summers hide a different drift: nothing happened, so nothing was recorded, so the first fall job discovers the habit is gone. The scan proves the system is awake; the re-confirmation proves it is accurate.
The gaps in the index are embarrassing. Should they stay marked?
Yes, for good, with their dates and causes. Marked gaps are the signature of a system that tells the truth about itself, and they are what let every unmarked period be believed. Erasing them would trade a summer of embarrassment for the whole record's credibility.
Who should own the reset?
The person who owns the weekly review, with the account owners supplying their chases. A reset owned by a committee drifts like the summer did; a reset owned by a name finishes in a week.
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