Who owns the record when several employees and agents work on one client account?
The client account owns the record, and a named person owns the account's records. Review the receipt and actual deliverable before accepting a handover.
Shared accounts create a familiar failure: the record of a client's work is smeared across three employees' sessions and two agents' histories, owned by everyone in the sense that excuses anyone. When the client asks, or a contributor leaves, the smear becomes the story. The fix is a distinction this file uses throughout: producers make steps; owners keep records.
Producer labels stay granular and factual: each step names the person, the agent, or the contributor pairing that ran it, because provenance questions (the six-month question, the rights question) are answered at step level. Ownership sits one level up, at the account: one named owner per client account, responsible for the index's completeness for that account, for chasing its acceptances, and for producing its packets on request. The owner changes by recorded transfer, the leaver discipline in this set, never by drift.
Agent contributors sharpen the need: an agent's steps belong to the account's record the moment they land in the job, not to the agent's platform history. That single rule, work for an account lives in the account's record, is what lets teams swap agents, models, and staff mid-engagement without the client's history fragmenting across every tool the work ever touched.
Template: the account record-ownership sheet
Per client account: 1. Record owner: one named person, with a named deputy. 2. Contributors: the employees and agents who produce steps on this account, listed. 3. Producer rule: every step labelled at run time; unlabelled steps are treated as defects in the weekly review. 4. Owner duties: index completeness, acceptance chasing, production on request, transfer on departure. 5. Transfer record: when ownership changes, the date, the parties, and the state of open items, filed with the account's index. Review: the sheet is re-confirmed quarterly and at every team change.
Worked example
The producer layer is visible on any shared job's record, for example https://zambo.dev/handover/508a46e2-8d6e-4099-bd12-7ae461c72c55 , where the producing party is recorded on the work as delivered to its recipient. Ownership is the layer above that record: the named person who would produce it, explain it, and chase its open decision, whether or not their hands made any of its steps.
Frequently asked questions
Does the client own the record, or do we?
Both, at different layers, and the contract should say so: the client owns their deliverables and their copies of the handovers; the practice owns its working records and index, with production duties to the client as the contract sets. This page's "account owns the record" is the internal rule that keeps either layer producible.
An agent did most of the work. Is the agent the producer of record?
The steps say so, step by step, which is accurate and sufficient. Ownership never follows production volume; it follows the assignment on the sheet, held by a person who can be asked questions.
What happens when the owner is away?
The deputy named on the sheet acts, which is why the deputy exists. An ownership model that pauses for holidays will fail exactly during the December questions it was built for.
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