Planning and workload tools
Event handover pack builder
Someone is leaving the event, or someone new is joining, and the handover currently lives in one person's head.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
…
The short answer
The builder turns what you know into a downloadable handover checklist and a structured manifest: current status, where files and links are kept, outstanding decisions and tasks, owner roles and deadlines.
Files and links are recorded as references only. Unresolved items stay visible, and the tool never asks for employer source documents or attendee lists.
What to enter
- Handover date, the role handing over and the role receiving. Use roles, not personal names.
- Current status in a few lines.
- One row per item: a file, a link, an outstanding decision or a task in progress.
- For files and links, write where they are kept or the link itself. Do not paste the contents.
- Owner role, deadline and state for each item: done, open, blocked or unknown.
How unresolved items are handled
Anything not marked done stays on the unresolved list, including blocked, unknown and blank states. The checklist shows them all and a separate table repeats only the unresolved ones.
An item is overdue when its deadline is before the handover date and it is not done. Items with no owner role are flagged, because an unowned item usually gets dropped.
References, not copies
The manifest records where things are, not the things. Keep confidential documents, employer source files, personal data and credentials in the place that already holds them, with access controlled by their owner.
If an item mentions an attendee list, a password or an identity number, the tool flags it as a reminder to record only its location.
Using the pack
Walk through the checklist with the receiver, item by item, and agree the owner and date for every open line. File the manifest with your decision log.
After the handover, the receiver can run weekly updates with the status report builder.
Worked example · Fictional example
A fictional programme handover
Fictional roles and items, to show the pack.
An outgoing programme coordinator hands over to an incoming project lead. Five items are listed: an approved programme file, a registration page admin link held by the secretariat, a speaker decision, an AV scope task with no owner, and a registered attendee list held by the registrar.
Four items are unresolved and one is overdue. The attendee list is flagged so that only its location is recorded, and the AV task is flagged for having no owner.
Use this yourself
Handover checklist
Copy this table and complete one row per item. Agree an owner and date for every line that is not done.
| Done | Type | What | Where it is kept or link | Owner role | Deadline | State |
|---|---|---|---|---|---|---|
| File | ||||||
| Link | ||||||
| Outstanding decision | ||||||
| Task in progress |
Handle it in-house, or bring in help?
Your team can usually handle this when
- The handover is between two people who already know the event.
- Most items are done and the open list is short.
Outside planning help earns its fee when
- Status is unclear, files are scattered and decisions are unrecorded.
- The receiver is new to the event and needs a briefing as well as a list.
- Several people are handing over at once and the open items overlap.
Want the handover run for you?
A project lead can take over an event mid-stream: reconstruct the status, build the handover pack with your team, and agree who owns each open item. The work stays within a scope you set, and confidential material stays where it is held.
Questions organisers ask
Does the pack include my files?
No. It lists where files and links are kept. It does not read, copy or store them.
Will the tool ask for the attendee list?
No. If an item mentions one, the tool reminds you to record only where it is held.
What counts as unresolved?
Anything not marked done, including blocked, unknown and blank.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.