Name the successor before the leaving date, not after. Then move three things in order: the knowledge (why the brief, sources and limits are what they are), the rights (approval and change permissions), and the open work (held actions, pending corrections, the next certificate renewal). File the transfer in the agent's record so nobody can mistake who owns it.
What does an agent owner hold, and who runs the handover?
An agent owner answers for one agent's results and bounds. They hold the brief, decide which sources it reads, agree its limits with the process owner, watch its certificate and act when it lapses. Our explainer on what an agent owner is sets out the role in full. When that person leaves, every one of those duties still exists on the morning after, and the successor needs the skills our guide to AI agent skills by role lists for owners.
The process owner runs the handover, because they own the business process the agent serves and will still be there. The departing owner does the work of explaining. The successor accepts the agent only when they understand it. The distinction matters in the explainer on process owners: the process owner decides what the agent should achieve; the agent owner decides how this agent gets there.
What are the steps?
- Process owner: names the successor as soon as the departure is known. A named person, a deputy, and a date the transfer takes effect.
- Departing owner: writes the agent note. One page: what the agent does at each depth, why each limit is set where it is, which sources are sealed or signed and which are declared, the house rules added and why, and the corrections that recur.
- Departing owner and successor: walk the record together. Ten recent allowed actions, ten held, every refusal and any withheld attempt from the last month. The successor should be able to explain each verdict and the bound that decided it.
- Agent, depth 1: continues to read and draft. Nothing changes for the agent during the walk-through unless its certificate is near expiry.
- Process owner: transfers rights. The successor gets the owner's change rights; the departing owner's are removed on the effective date, not on their last day of access.
- Successor: checks the certificate. If the agent's certificate lapses within the next few weeks, the successor plans renewal now. An agent certificate lapses after 90 days, and a lapse drops the agent to depth 1.
- Process owner: files the transfer in the agent's record: who, from when, and the agent note attached.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Name successor | Keeps working as before | current | Process owner |
| Write agent note | Nothing | none | Departing owner |
| Walk the record | Its past verdicts are the material | none | Both owners |
| Keep running | Reads, drafts and executes within bounds | current certified depth | Reviewers and approvers |
| Transfer rights | Nothing | none | Process owner |
| Check certificate | Re-runs certification if due | as certified | Successor |
| File transfer | Nothing | none | Process owner |
What knowledge has to move, beyond the settings?
Settings are the easy part; they are already in the system. The hard part is the reasoning behind them. Why the refund limit sits at 200 and not 500. Why one data feed is excluded even though it looks useful. Why the agent drafts but never sends letters to customers in arrears. Without the reasons, the successor either leaves everything frozen or loosens a limit that was tight for a good reason.
The agent note should also list what is in flight: corrections the owner had banked but not yet turned into brief changes, a source about to be retired, a request from the team for more depth. A successor who inherits these as surprises loses weeks.
For agents that hand conversations to people, such as an agent that hands a live chat over to a person, check the routing too: if the departing owner was a named destination for escalations, those must move as well.
Which controls make the handover safe, and what evidence do they leave?
No gap in ownership. The agent always has a named owner. Evidence: the ownership history in the record, with no period empty.
Rights move on a set date. The departing owner's change rights end when the successor's begin. Evidence: the permissions log.
Successor competence checked. A business can require the successor to hold a current certificate for the depths the agent runs at before they accept it. Evidence: the certificate number checked at source and noted on the transfer.
No changes during the handover. Limits, sources and brief stay as they are until the successor has walked the record. Evidence: no configuration changes between the naming date and the effective date, or each one approved by the process owner.
What should you measure?
- Days between departure notice and named successor. Shorter is better.
- Held actions waiting on the departing owner on their last day. The target is none.
- Corrections that recur in the month after handover, compared with the month before. A rise suggests reasoning was lost.
- Configuration changes in the first month by the successor, and whether each was explained in the record.
Where does it usually go wrong?
Ownership defaults to the line manager. The agent quietly passes to whoever managed the leaver, who has no time for it. Our view is set out in every AI agent needs an owner with a name: a default owner is not an owner.
The certificate lapses in the gap. Nobody is watching the renewal date, the agent drops to depth 1, and the team assumes something broke.
Access is removed before knowledge is transferred. The leaver's account is closed early and the agent note never gets written.
The successor tidies up. A new owner sees limits that look over-cautious and loosens them before understanding why they were set.
Where the Academy fits
Pryme Intelligence Academy's Operator track includes modules on reading the workspace, keeping knowledge current and when something goes wrong, which is the ground a successor needs to cover. A successor holding Certified Pryme Operator can show it by number or QR code through VerifyDoc.ai, and the admin view shows when it expires.
Questions people ask
Can two people share ownership of an agent?
It is better not to. Name one owner and one deputy. Shared ownership tends to mean that each person assumes the other is watching the certificate and the corrections.
Should the agent be re-certified when the owner changes?
Not automatically, because the agent itself has not changed. Re-certify if the successor changes the brief, sources or limits, or if the certificate is close to lapsing anyway.
What if the owner leaves without notice?
The process owner takes temporary ownership the same day, freezes changes, and names a successor within days. The verdict record lets the new owner rebuild the reasoning that was never written down.