Key takeaways
- When a consultant leaves, you do not only lose their expertise. You also lose all their years of experience: in-depth knowledge of their clients and the engagements they worked on, validated methods, sensitive topics
- The handover document does not solve the problem. Often written in a hurry during the final days, it captures 10% of what actually matters
- With Archesia, your collaborators' knowledge is indexed continuously. Not only at the moment of their departure
When a collaborator leaves, their memory leaves with them
A senior consultant resigns, goes on parental leave, or takes an extended sick leave. Whatever the reason, someone has to pick up their files. And that is where the void appears.
Who are the real decision-makers at the client? What commitments were made at the last steering committee? Why was the governance recommendation framed that way and not another? Which topics must never be brought up again?
None of this exists in a job description. It accumulates across engagements, meetings, and informal exchanges. And in most firms, it lives only in the head of the absent collaborator.
What disappears concretely
It is not talent that is hard to replace. It is contextual memory.
Concretely, here is what disappears when a consultant leaves a firm without a knowledge capture system:
Unwritten client context. The CEO’s communication preferences. The fact that a given stakeholder is nominally the decision-maker but that real decisions are made elsewhere. The politically sensitive topics that are best approached indirectly.
The real history of deliverables. Not the clean version sent to the client: the intermediate drafts, the annotations, the trade-offs, the reasons why certain options were ruled out.
The memory of exchanges. Informal emails, verbal feedback that was never formalised, commitments made on the margins of meetings.
Validated methods. What worked, what did not, and why. Information that would allow a successor to avoid repeating the same mistakes.
None of this appears in the shared drive. It exists scattered across emails, document versions, and meeting notes that never made it anywhere useful.
The myth of the handover document
The standard response to this problem is the handover document. “Before you go, put together a summary of your accounts.”
The result is almost always the same: a two-to-four-page Word file, written in the final days before departure, squeezed between client follow-ups and a transition meeting. It covers the obvious, glosses over the nuances, and misses the essentials.
This is not a problem of goodwill. It is a structural problem: you are asking someone to transcribe years of accumulated knowledge in a few hours. That is not possible.
And even when the document is done well, it quickly becomes obsolete. Clients evolve. Contacts change. Living knowledge continues, but it is no longer in the system.
When knowledge lives in the system
The only way to avoid losing knowledge at the moment of departure is to stop waiting until that moment to capture it.
Continuous indexing, no extra effort
In firms that use Archesia, indexing is continuous. Deliverables, emails exchanged with clients, meeting notes, working documents: everything is indexed in the background, in the course of normal activity. No additional effort required from consultants.
Ask the base, in writing or by voice
When someone leaves or steps away, the knowledge does not leave with them. It is already in the system. The successor can ask questions directly, in writing or by voice: “What topics are currently active with the Dupont client?” “What commitments were made over the last six months?” “Why was the recommendation on organisational structure framed that way?”
Semantic search does the rest: it does not search for keywords in file names. It understands the meaning of questions and surfaces relevant passages, regardless of how they were originally written.
What changes day to day
Knowledge capture stops being a separate project. It becomes a side effect of normal activity.
A staffing change without disruption
A consultant’s departure or absence shifts from a transition crisis to a routine staffing change. The successor is up to speed within one or two days. The client does not feel a break. The firm does not lose billable time during a re-onboarding phase.
Beyond departures: a search engine across all your engagements
Beyond absences, firms that index their activity continuously gain a search engine across all their missions. Building a proposal using the firm’s actual references. Finding a methodology used three years ago. Drawing cross-cutting lessons from ten engagements in a given sector. We document this in detail in the article on concrete use cases.
Turnover in consulting is a fact of life. The knowledge loss that comes with it is not: it is an organisational problem with a technical solution. To learn more, visit the consulting firms page or speak with us directly.
Frequently asked questions
Do consultants need to take specific actions to feed the knowledge base?
No. Indexing happens automatically from existing documents and emails. Consultants do not need to change their working habits. Knowledge capture is a side effect of normal activity, not an additional task.
Are confidential client documents accessible to all consultants?
No. Archesia respects the access rights you configure. Each consultant only accesses the missions and documents they are authorised to see.
Does this work for unplanned absences too?
That is precisely where the system makes the biggest difference. Sick leave, unexpected absence, abrupt departure: because knowledge has been indexed continuously, it does not depend on the collaborator's availability or cooperation. The base is there, immediately accessible, whatever the situation.
Is it useful when bringing in temporary reinforcement on an engagement?
Yes, and this is one of the most common use cases. When an external consultant or a junior joins an ongoing engagement, the base lets them get up to speed in minutes: client context, deliverable history, decisions made. No lengthy debrief with the rest of the team required.
How long does it take to index existing history?
Indexing of existing history happens automatically after your tools are connected. Import progress is visible in real time in the interface: you always know exactly where the indexing stands. Access to Archesia is managed through a waiting list, so each firm can be properly onboarded.