Embedded and remote working arrangements
How to onboard an embedded event lead
A temporary event lead starts on Monday, and your team has not yet decided what they can see, decide or ask for.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Onboard an embedded event lead around five things: the scope and event list they will cover, who they report to and who decides, which files and systems they may use, agreed working hours and how to reach them, and where their work will be recorded. Settle these before day one, then use the first two weeks to introduce people, review live decisions and set a regular check-in.
Authority, access and task limits are covered in more detail in embedded event lead authority agreement, access checklist and task boundaries. This page is the order in which to do them.
Settle five things before day one
| Item | What to decide | Who decides |
|---|---|---|
| Scope | Which events, which workstreams and what is excluded. | Event owner |
| Reporting and decisions | One named person to report to. Which decisions the lead prepares and which they may take. | Event owner |
| Access | Which files, systems and mailboxes they will use, and who grants each. | Event owner with the person who administers the systems |
| Hours and availability | Agreed days, times and response expectations, in writing, with out-of-hours stated separately. | Event owner and lead |
| Record keeping | Where status, decisions and open items are written so someone else can pick them up. | Lead, agreed with event owner |
A two-week plan
- Day 1: welcome, scope walk-through, introduction to the reporting person and the key internal contacts. Confirm access has been granted and works.
- Days 2 to 3: review live events with the owner, listing decisions already made, decisions pending and promises given to suppliers or speakers.
- Days 4 to 5: introduce the lead to suppliers by short message from your team, naming them as a contact for the agreed scope.
- Week 2: first status note and decision log, a first check-in with the event owner and a review of what is unclear.
- End of week 2: confirm scope, hours and boundaries are working. Adjust in writing.
What to hand over on day one
- A one-page summary of each event: purpose, audience, date, status and the three most urgent items.
- The decision log and any open supplier or speaker commitments.
- A list of who is who: committee members, approvers, supplier contacts and their roles.
- Read-only access to the budget view, unless the scope includes budget tracking and finance has approved it.
- Where to ask, and how quickly to expect an answer from the reporting person.
Common onboarding mistakes
- Starting the lead before access exists, so the first week is spent waiting for logins.
- Leaving suppliers unaware that a new contact is coming, so messages are ignored.
- Assuming the lead is available every hour. Agree hours and say what happens outside them.
- No place to record decisions, so knowledge leaves with the lead at the end.
- Treating employment or contract questions as part of onboarding. Questions about status, terms or obligations go to your HR or legal adviser.
Worked example · Fictional example
Onboarding a lead for a three-event season
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Pegawai Kewangan Korporat engages a temporary event lead for 12 weeks to cover its annual forum and two regional briefings. The honorary secretary is the single reporting person.
Before day one the secretary writes a one-page scope, grants access to the shared event folder, and tells the hotel and AV supplier that the lead will be a contact for those two events. Hours are set as three agreed days a week, with replies expected on those days.
| When | Action | Owner | Evidence |
|---|---|---|---|
| Before day 1 | Scope note and access list agreed | Honorary secretary | Signed-off note |
| Day 1 | Walk-through and introductions | Honorary secretary | Attendee list |
| Days 2 to 3 | Decision log reviewed | Lead and secretary | Log with open items |
| Week 2 | First status note and check-in | Lead | Dated note |
Use this yourself
Embedded lead onboarding checklist
Complete before day one where possible. The handover pack builder can turn the filled-in items into a manifest the lead can pick up and update.
- Events and workstreams in scope, and what is excluded:
- Reporting person and who decides on budget, programme, speakers and suppliers:
- Access granted and tested: files, mailboxes, systems, and who administers each:
- Agreed days and hours, response expectations and how out-of-hours matters are handled:
- Introductions made to committee, internal contacts and suppliers:
- One-page summary and decision log for each live event:
- Open commitments to suppliers, speakers and members:
- Where status notes and decisions will be recorded:
- First check-in date and review of scope at end of week 2:
- Questions for HR or legal advisers about the engagement terms, kept separate from this plan:
Handle it in-house, or bring in help?
Your team can usually handle this when
- You already know which tasks the lead will cover and who reports to whom.
- Access can be granted quickly by a person on your side.
- The engagement is short and the events are well documented.
Outside planning help earns its fee when
- Several events are live and nobody can summarise their status in one page.
- Authority and access are unclear and the lead's first week would be spent waiting.
- You want temporary dedicated capacity and a project lead to set up the onboarding with you.
Want dedicated temporary capacity?
An embedded event project manager can join your team for the hours and scope you agree, using this onboarding plan as the starting point and recording decisions as they go. Availability is agreed in advance rather than assumed, and your committee keeps programme, budget and supplier decisions. If an embedded arrangement does not fit, a conference project lead can take the coordination of agreed events.
Questions organisers ask
How early should access be arranged?
Before the first day, if the person who administers the systems can act. Ask what lead time they need and start the request when the start date is agreed.
Can the lead contact suppliers on day one?
Only after the supplier has been told by your team who the lead is and what they may discuss. Until then, messages from a new name are easily ignored.
Does the lead need access to member or attendee lists?
Only if the scope requires it. Ask your data protection owner what may be shared, and give the narrowest access that lets the work happen.
Who should answer questions about the engagement terms?
Your HR or legal adviser. This plan covers the working arrangements, not employment status or contract terms.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.