Conference recovery: readiness, scope and accountability
The event depends on one unavailable person
The one person who knows the registration system and supplier contacts is on leave, and the conference is two weeks away.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Treat it as a continuity question: find out what only that person knows, who can legitimately take each task, and what can be paused. Do not contact the person for work if they are on sick leave unless your organisation's policy and the person agree.
Use the handover pack builder to capture what is known and the decision log to name temporary owners. The unknowns are listed first, then decided.
What is known and what is not
| Known | Not yet known |
|---|---|
| The person holds the registration system login, the supplier contact list and the run sheet draft. | Whether those items are also stored on a shared drive, and who else has access. |
| The leave is expected to cover the next ten working days. | Whether the person may be available for a short call, which is a matter for the person and their employer. |
| Two suppliers are awaiting confirmations from this person. | Which other confirmations are pending and which deadlines are due this week. |
| The deputy has attended all meetings but has never used the registration system. | What the deputy can learn in a day and what needs the system owner. |
Who has authority to decide
The person's line manager or the committee chair decides who covers. Access to systems and data is for the system owner and the data protection contact to approve, not the event team. Contacting someone on leave is a matter for the organisation's policy and the person's own wishes.
Record the cover owner for each task in the decision log and set a date for review.
The realistic options
| Option | What it involves | Consequence to weigh |
|---|---|---|
| Assign a temporary owner per task | Name a cover person for registration, suppliers and the run sheet, with a short handover from whatever documents exist. | Keeps work moving. Slower at first, and gaps appear where nothing was written down. |
| Appoint a temporary lead for the remaining weeks | Ask the organisation to assign a person, or a project lead, to coordinate the agreed tasks. | Adds capacity, needs a briefing and access approval. Costs time to set up. |
| Pause non-critical tasks | Postpone non-urgent items, such as the post-event survey, and focus on critical tasks. | Reduces load. Needs the chair to agree what counts as critical. |
| Postpone or scale down | Move the date or reduce the programme if coverage is not credible. | Affects deposits and delegates. Check contract terms with the competent party first. |
Communications: who says what to whom
Tell the committee the facts and the proposed cover owners. Tell suppliers who their new contact is and what stays the same. Do not share the reason for the absence beyond what the person and the organisation have agreed to.
Tell delegates nothing unless a date or programme item changes.
- Short message template: [Name] is the contact for [task] from [date]. Earlier confirmations remain valid. Please send any questions to [name] at [contact]. We will confirm any change to dates or the programme in writing.
Follow-up and preventing a repeat
- Record what was missing and write it down now: logins, contacts and decisions.
- Keep a shared drive with the current run sheet and supplier list.
- Name a deputy for every critical task before the event.
- Review how access is granted so that cover does not depend on one person's login.
Worked example · Fictional example
Persatuan Fiktif Arkitek: registration lead on leave
Fictional organisation and figures, written to show the level of detail that is useful.
Two weeks before a fictional architects' association conference, the registration lead goes on medical leave. The deputy finds the supplier list and run sheet in the lead's personal folder and no one has the registration system login.
The chair names the deputy as supplier contact and asks the system owner for access through the association's own approval route. The secretariat writes down every pending confirmation and sets a daily ten-minute check. Suppliers receive the new contact in one message.
Use this yourself
Key person cover sheet
List every task that depends on the person. Add a cover owner, access needed and a review date for each.
- Task and why it depends on this person:
- What is documented and where:
- What is not documented:
- Cover owner and approver:
- Access needed and who may approve it:
- Suppliers to be told and the new contact:
- Deadlines this week and next:
- What can be paused:
- Review date:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Most work is documented and a deputy already knows the system.
- The absence is short and the event date is not close.
- One person can approve cover and access.
Outside planning help earns its fee when
- Critical knowledge sits in one person's head or inbox.
- Nobody can decide who may access the registration data.
- The remaining team is already full.
Need cover arranged without losing control?
A planning diagnostic can identify tasks that depend on one person and list the decisions needed to cover them, with owners and dates. A conference project lead or an embedded manager can then coordinate the agreed tasks for a temporary period. Access approvals and personal matters stay with your own organisation.
Questions organisers ask
Can we contact the person on leave?
That is a matter for your organisation's policy and the person's own wishes. Plan as if they are unavailable and treat any contact as a favour, not a method.
Who may approve access to the registration data?
The system owner and your data protection contact. Ask them before the deputy logs in or the password is shared.
How do we avoid this next time?
Name a deputy for each critical task, keep documents on a shared drive and review access before the event, not during it.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.