Answers
How does an AI agency change the person on a client without losing what the account knows?
By keeping what the account knows in the account's own project, written as it is decided, instead of in the head of whoever is currently on it. When someone is taken off the client they lose access to that project, and everything they recorded there stays — under their name, with the date and the reason. The person taking over reads the client's rules in force on their first day, and their assistant reads the same set. The only thing that leaves with the person is what nobody ever wrote down, which is why the writing happens during the work rather than in a handover the week someone goes.
Last updated September 4, 2026
Rotation is normal; the reset is not
Staffing on an account changes for ordinary reasons — someone takes leave, someone moves to a bigger client, someone resigns. Each time, the account loses the part of its knowledge that was never written: what the client rejected in review and why, the wording they will not accept, the approval that has to happen before anything goes out. The new person rebuilds it by making the mistakes the last one already made, in front of the client. The client sees the reset, and reads it as the agency starting over.
The record is written during the work, not at the exit
A handover document is written by someone already halfway out, about work they have stopped thinking about, for a person who does not yet know what to ask. It captures the deliverables in flight and loses the standing rules. Here a standing rule goes in when it is decided: the client's veto in a review call becomes a rule that same day, approved by whoever owns the account. By the time anyone leaves, the account's knowledge is already where the next person — and the next assistant — will read it.
Access ends; authorship does not
Removing someone from a client ends their access to that project and nothing else. What they wrote stays with the account, still saying who wrote it and when, so the successor sees not only the rule but who set it and in what context. That matters most when a rule looks strange: the successor can ask the right person, or see that the client asked for it, instead of quietly deciding it was a mistake and undoing it.
What it looks like in practice
An agency moves a senior off a retainer account to open a larger one, and hands the retainer to someone who joined two months earlier. The handover is a call plus a document listing the work in flight. In week two the new person's assistant drafts a campaign quoting a testimonial from the client's own website. It comes back rejected: eight months earlier that client had asked that no named customer be quoted without a fresh written approval, because of something that happened before the agency was hired. It had never been written anywhere. The senior simply knew, the request had arrived in a call, and the handover document listed deliverables rather than standing rules. Recorded as a rule on the account the day it was made, that request would have been in the read before the assistant wrote a word — and the new person would never have needed to know it existed.
Questions people ask about this
- Do we have to write down everything a client ever says?
- No — only what should still hold next month. A decision that changes how work is done on the account is worth a sentence; the detail of one deliverable is not. The test is whether somebody arriving fresh would get it wrong without being told. If they would, it belongs to the account rather than to whoever happens to be on it.
- Can the person leaving take a copy with them?
- The account's material belongs to the project, and access to it ends with their membership. The agency keeps the record — that is the point of it living on the account — and can export it. What leaves with the person is only what they never recorded, which is exactly what this is meant to reduce.
- Two of our people share an account. Does that change anything?
- Same mechanism, and it pays off sooner. Both read the same rules in force, so a rule one of them agrees with the client does not have to be relayed to the other, and when one takes leave the other is not the only copy. Adding or removing a person changes who can reach the account, never what the account knows.
Where this is verifiable
Product documentation on this site (How it works, Install), the project membership and authorship rules in the sanctioned product spec, and the Privacy Policy for what happens to a person's record when they leave a project. Everything described here is behaviour the tools apply today, not roadmap.
https://www.arroway.app/en/answers/ai-agency-client-handoff-without-losing-context