IN THIS ARTICLE
Project handover: avoiding information loss when someone leaves (SME guide 2026)
Project management in SMEs
17.04.26
•
10 min
When an employee leaves an ongoing project, it’s not just a position that opens up. It’s a body of context, decisions, and customer relationships that risks disappearing. In an SME, where a project manager often handles several accounts alone, the impact can stall a project for weeks. The problem is rarely technical. It’s that no one has documented what matters. According to Panopto/YouGov, 42% of an organization’s institutional knowledge is held by a single individual. When that person leaves, that knowledge leaves with them. And in a project lasting 6 to 18 months, the amount of unwritten information is enormous: informal trade-offs, client preferences, and the reasons behind technical choices. The standard handover covers IT access, equipment, and administrative files. It does not cover the essential part: the handover of the project itself. This guide addresses that second handover.
What you really lose when a collaborator leaves a project
The cost of an employee leaving is not limited to recruitment. According to Gallup, replacing a technical professional (consultant, engineer, project manager) costs about 80% of their annual salary. For a profile earning €45,000 gross, that represents €36,000. But this figure measures only the visible part.
The invisible part: lost productivity. A Mellon Financial Corp. study (MIT Sloan Management Review) estimates that a professional takes 20 weeks, or nearly 5 months, to reach the productivity level of their predecessor. In a project-driven SME, the cost becomes concrete: delays on deliverables, loss of client trust, and repetition of decisions already made due to lack of traceability. AVEVA reports that 90% of projects incur overruns linked to information lost during a change of contact person.
The three types of information that disappear with the employee
Not all project information is equal. And not all information is documented the same way. When talking about information loss when someone leaves, you need to distinguish three layers.
Documented but scattered information
It's the easiest to recover, but the hardest to find again. The files exist: meeting minutes, emails, interim deliverables, tracking spreadsheets. But they are spread across a Drive, an email inbox, a Teams channel, and sometimes a paper notebook. A prospect from an engineering consultancy interviewed by 5Days summed it up: "I've been looking for 15 minutes, whereas if I had a centralized system, I'd save 15 minutes every time."
Unwritten contextual information
It's the most dangerous. Why the client rejected option A in March. What compromise was negotiated on scope. Who, on the client side, is the real decision-maker. According to Panopto, 80% of corporate knowledge is tacit. If your project decisions are not tracked, they are lost forever.
Relational information
In IT services firms and consulting firms, the client relationship is often embodied by a single person. When they leave, the client loses their trusted contact. It can't be documented in a file. But it's what determines whether the client renews or not.
Project handover checklist: the 8 items to pass on
The handover checklists you find online cover the administrative side: badge, equipment, access. They never cover the project. Here are the 8 elements an outgoing employee must pass on so that their successor can take over a project without starting from scratch.
No. | Element | What it covers |
|---|---|---|
1 | Progress status | Where each deliverable stands, which milestones have been passed, and which remain. Not a theoretical Gantt chart: the actual status. |
2 | Decisions made and trade-offs | The choices made, by whom, and why. Include the options ruled out and the reasons. This is what the successor will look for first. |
3 | Outstanding issues and risks | What has not been decided, what is blocking progress, what could go off the rails. What is left unsaid is more dangerous than what is said. |
4 | Contacts and stakeholder map | Who does what on the client side and internally. Who really decides. Who is the facilitator, who is the blocker. |
5 | Access to project tools and files | All access: project platform, Drive, repo, business tools. Not just generic IT access. |
6 | History of key meetings | Minutes from the key meetings. If minutes do not exist, at a minimum a summary of the 5 most important meetings. |
7 | Budget and financial commitments | What has been spent, what is committed, the remaining margins. Pending quotes and upcoming invoices. |
8 | Cross-project dependencies | The links with other projects, other teams, other providers. What the employee was managing informally. |
This list may seem heavy. In reality, if the project is well tracked with a structured tracking system, most of these elements already exist somewhere. The handover work then consists of bringing them together and putting them in context, not creating them from scratch.
How to organize the handover in practice
The departure is planned: structuring the last 4 weeks
When the notice period allows it, the handover should begin as soon as the departure is announced, not in the last week. The classic trap: postponing the handover because the employee is still "useful on the project". Result: the handover is done in 2 days, in a rush, and everyone leaves with gaps.
A realistic 4-week plan: weeks 1 and 2, the departing employee documents the 8 items on the checklist above. Week 3, oral handover with their successor (or the manager who will act as interim) on each ongoing project. Week 4, the successor takes over with the departing employee supporting. According to Gallup, only 12% of employees consider their onboarding satisfactory. A structured handover changes the game.
The departure is sudden: limiting the damage
Resignation without notice, illness, expedited mutual termination. The most common and least prepared case. Here, the lever is not the handover (there won’t be one), but the continuous documentation of the project.
If your projects are documented continuously, an employee can leave tomorrow without the project collapsing. If nothing is documented, even 3 months' notice won't be enough to make up for 12 months of unwritten context. That's the whole point of centralizing project information as you go, not at the time of departure.
The real question is not "how do you do a good handover". It's: "would our project survive an unexpected departure tomorrow morning?" If the answer is no, the problem is not the handover. It's the lack of project memory.
Blind Spot: The Impact on Customer Relationships
Handover guides talk about skills, files, and processes. They almost never talk about the client. Yet in service delivery (consulting, engineering, development), the departure of the project manager is often perceived by the client as a breach of trust. The client is left facing a new point of contact who does not know their context and asks questions that have already been dealt with. In the most serious cases, they call the contract into question.
Three actions to reduce the risk: notify the client as soon as the departure is confirmed. Hold a three-way handover meeting (outgoing, incoming, client) to transfer the relationship, not just the files. And provide the successor with a written briefing on each client: background, sensitive topics, and verbal commitments made.
FAQ: project handover and employee departure
Existe-t-il une obligation légale de passation dans le secteur privé ?
Combien de temps faut-il prévoir pour une passation projet ?
Qui doit piloter la passation : le manager ou les RH ?
Comment gérer la passation quand il n'y a pas encore de remplaçant ?
Quel est le cout réel d'une passation ratée pour une PME ?
Comment savoir si notre organisation est vulnérable aux départs ?
Project handoff is not a one-time event. It is the ultimate test of your ability to document and centralize information over the course of the project. The SMEs that handle departures well are not the ones that do the best handoffs. They are the ones where every meeting, every decision, and every document is accessible to the entire team, in real time. 5Days enables exactly that: centralizing the full history of a project and making it searchable, so that every departure becomes an operational non-event.
