Answers
The partner on the account changes. What does the next one inherit?
What a successor should inherit is the decisions the account already carries — not a folder of e-mails to mine and a calendar of calls nobody wrote up. With Arroway the account remembers instead of the person: each decision taken with that client is written down as it happens, approved by a person, and read by the next partner's AI the moment they open the work. The handoff meeting stops being the only transfer — and stops being the place where whatever nobody thought to mention is lost.
Last updated September 1, 2026
What leaves is what nobody wrote down
The deliverables stay. What leaves with the departing partner is the reasoning around them: the approach the client refused in the first month, the topic to raise only in writing, the commitment made out loud that the contract does not mention, who on the client's side actually decides. None of it lives in a document, because none of it was ever a document — it was a judgement made on a call, and it went wherever the person who made it went.
The account remembers in the same motion as the work
Each of those judgements becomes a short rule at the moment it is made: the assistant working alongside the partner writes it down, and a person approves or corrects it in a quick review afterwards. It is not a knowledge-transfer project run at the end, when whoever is leaving has one week and every reason to describe the account as tidy. The successor reads the record kept while the account was being worked, not a summary written to close it.
Access ends with the person; the record stays with the account
Taking someone off a project ends their access and nothing else. What they wrote remains — with their name, its origin and its history intact, still served on every read of that account. That is what makes the change survivable in both directions: the firm does not lose what the departing partner knew, and the successor can see who decided each thing and when, instead of inheriting a pile of assertions with nobody behind them.
What it looks like in practice
A partner leaves and hands over three accounts in a two-hour call. Six weeks later the successor proposes, in good faith, precisely the approach the client refused at the start of the relationship — the reason was political, it was never in any document, and it did not come up in a two-hour call covering three accounts. Nothing was hidden and nobody was careless. The handoff was simply the wrong instrument for the kind of thing being handed over. Had the refusal been written down when it happened — one line, with the reason, approved by the partner — the successor's assistant would have read it before drafting the proposal, and said so.
Questions people ask about this
- Is this not just a well-maintained account wiki?
- The difference is who keeps it current and where it gets read. A wiki is a second place someone has to remember to update, and a place the next partner has to remember to open. Here the writing happens as a side effect of the work, and the reading happens at the start of the assistant's work whether or not anyone thinks to look — and each entry says who decided it and carries the condition that ends it, which a page of prose does not.
- The successor uses a different AI tool from the partner who left. Does that matter?
- No. The record belongs to the account, not to an assistant, and it is served to whichever assistant the next person has connected. This is the case that makes it obvious why the memory has to live outside the tools: a change of person is usually also a change of setup.
- What happens to what the departing partner wrote about the client?
- It stays with the account, under their name. Access ends; authorship does not — erasing it would destroy knowledge belonging to the people who stayed, and would leave nobody able to answer who decided a thing. If a particular position no longer holds, someone replaces or archives it on purpose, rather than it vanishing as a side effect of somebody leaving.
Where this is verifiable
Product documentation on this site (How it works, Install), the sanctioned product spec in the repository, 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/handoff-between-partners-on-the-same-account