Embedded and remote working arrangements
Event lead knowledge transfer sessions
The new lead starts on Monday, the outgoing lead leaves on Friday, and no one has booked time for the conversation in between.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Knowledge transfer works best as a few short, scheduled sessions, each tied to a topic and to something that can be shown: a document, a log, a supplier thread. Close each session with written notes and a list of what is still unclear.
Aim to transfer what is not already written down. The files themselves belong in the handover pack.
Choose the topics
| Session | What is covered | What is shown |
|---|---|---|
| 1. Event overview | Purpose, audience, programme shape, key dates | Brief, programme draft, timeline |
| 2. Decisions and authority | Open decisions, approvers, what is already committed | Decision log, authority agreement |
| 3. Suppliers and venue | Who is appointed, status of contracts, concerns | Supplier list, correspondence, quotes |
| 4. Money and registration | Budget position, spend to date, registration status | Budget summary, platform view (permitted access only) |
| 5. Risks and next 30 days | Known risks, next deadlines, who is waiting for what | Risk list, status sheet |
Run each session
- Circulate the topic and the documents to read at least one working day before.
- Keep it to 45 to 60 minutes, with the incoming lead asking the questions.
- Record the answers in writing, marking each item as confirmed, uncertain or unknown.
- Agree any follow-up with owners and dates before the session ends.
What not to hand over
Do not hand over attendee lists, personal data or an employer's confidential documents just to make the transfer easier. Link to where they are held and let the data owner decide who sees them.
The handover pack should hold references and structured notes. Uncertain or unresolved items stay visible rather than being tidied away.
If the outgoing lead is not available
- Use the written status sheet and decision log as the first source.
- Run the sessions with the sponsor or the named colleague instead and mark gaps as unknown.
- Contact suppliers with the sponsor to confirm the current position rather than guessing it.
Worked example · Fictional example
A cooperative federation's training summit
Fictional organisation and figures, to show the level of detail that is useful.
A fictional cooperative federation runs a summit for about 320 participants. The outgoing lead has eight working days before leaving, and the sponsor books five 45-minute sessions across them.
Session 3 reveals that the venue hold lapses on a Friday and the deposit invoice is unsigned. It is marked as an urgent item with the treasurer as owner, and the incoming lead confirms both within the week.
Use this yourself
Knowledge transfer session plan
Copy into a shared document and complete one block per session.
- Session topic and date:
- Outgoing and incoming lead, and sponsor attending or not:
- Documents to read beforehand:
- Evidence to be shown in the session:
- Questions the incoming lead wants answered:
- Answers recorded: confirmed, uncertain, unknown:
- Follow-up actions with owner and date:
- Items passed to the handover pack:
- Data or confidential files referred to by link only (data owner approval):
Handle it in-house, or bring in help?
Your team can usually handle this when
- The outgoing lead is available and the event is straightforward.
- Documents already exist and are current.
- The sponsor can attend the first sessions.
Outside planning help earns its fee when
- The lead is leaving at short notice with little written down.
- Several suppliers and committees each hold part of the picture.
- The event is close and the incoming lead has to be effective within days.
Want transfer sessions planned and recorded?
An embedded event project manager can run the sessions with an incoming or outgoing lead and keep the log that makes the transfer checkable. A project lead can help you set the topics, collect the evidence and finish with a handover pack. Share the leaving date and what is already written.
Questions organisers ask
How many sessions are enough?
Three to five short sessions cover most events. More is useful when the event is large or the documents are thin.
Can sessions be remote?
Yes, if the documents are shared in advance and notes are written during or straight after the call.
What if the outgoing lead is reluctant?
Keep to the agreed handover steps and mark any gap as unknown. Escalate to the sponsor if key information is withheld.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.