How do I track the work my team does for clients?
Track the work itself, not reports about it: one recorded job per deliverable, steps saved as they run by whoever (or whatever agent) does them, and a daily view across jobs. Review the receipt and actual deliverable before accepting a handover.
Team tracking usually means a second job: the work, plus the narration of the work into boards, threads, and standups. Narration drifts from reality within days and consumes the hours it claims to save. Record-based tracking deletes the second job: the trail the work leaves is the tracking.
The unit is the job, one per deliverable, owned by a named person even when agents do most steps. Steps land as the work happens, with producer labels, so a lead can see not only progress but composition: which steps the agents ran, which a person ran, where a job is stuck (its last step is old), and what is awaiting a client decision. The day view across jobs turns that into the morning read: yesterday's completions, today's open handovers, the exceptions worth a conversation.
Client visibility comes free with the same objects, which is the structural advantage over internal trackers: the handover the client receives is the job you tracked, not a report derived from it. Internal-only work stays in internal jobs. The boundary is set by job design, once, instead of by redaction every time something is shared.
Checklist: record-based team tracking
1. One job per deliverable, named [client]-[deliverable], owner named. 2. Steps saved during the work by the doer, human or agent, labelled. 3. Client-facing and internal work in separate jobs. 4. Morning read: the day view, exceptions only (stale last step, held handover, unresolved flag). 5. Weekly: sample two jobs per person against their deliverables; coach the gaps in labelling, not in effort. 6. Monthly: the job index per client feeds billing and the retainer packet.
Worked example
One tracked job reads like the public record at https://zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 : five steps, current state visible, no narration needed to know where it stands. A lead with twenty such jobs has a dashboard made of the work itself.
Frequently asked questions
Does this replace our project management tool?
It replaces the tracking layer, not necessarily the planning layer. Plans, assignments, and deadlines can live where they live; the record answers the different question of what actually happened, which planning tools answer only by self-report.
Team members resist recording steps. How do we start?
Start with the delivery end: require the handover for client work, and let the steps accumulate as the cheapest way to build it. Recording adopted as a delivery tool sticks; recording adopted as surveillance does not, and the difference is real.
Can agents and humans really share one job record?
Yes, that is the design: steps carry producer labels precisely so mixed work reads as one job with a visible division of labour, instead of two partial trails in two systems.
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