Embedded and remote working arrangements
Remote event lead communication rules
Your event lead works remotely, and decisions are now split across email, two chat groups and a call nobody minuted.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Remote communication rules fix one channel for each kind of message, a regular meeting rhythm, response windows and a written record of every decision. They replace habit with agreement.
The aim is a single place to look for the current answer, and a lead who is not interrupted all day.
One channel per purpose
| Purpose | Channel | Rule |
|---|---|---|
| Decisions and approvals | Email or the decision log | Written, with the decision, owner and date |
| Day-to-day questions | Team chat, one event channel | Short answers, no decisions left in chat |
| Weekly progress | Status report and call | Fixed day and time, agenda circulated before |
| Urgent matters | One named phone number | Only items on the urgent list, see the availability calendar |
| Documents | Shared folder | One current version, linked not attached |
A meeting rhythm that fits remote work
- A short weekly call with the sponsor: progress, risks and decisions needed.
- A fortnightly call with the committee chair, with the programme and budget view.
- Supplier calls scheduled by the lead, with notes sent the same day.
- No standing daily call unless the final fortnight needs it.
Written records
- After every call, the lead sends a note of decisions, actions, owners and dates.
- The sponsor corrects it within the agreed window, or it stands.
- Decisions go into the decision log, and the log is the reference if chat and email disagree.
- Meeting recordings, if any, are agreed in advance and kept per your own policy.
Confidentiality and data
Remote work raises practical questions: whether messages with attendee details may sit in chat, which tools your organisation permits, and where files may be stored. Ask your privacy or IT lead before choosing a channel.
Where the answer is unknown, avoid putting personal data in chat and refer to a record instead.
Worked example · Fictional example
A bar association's regional conference
Fictional organisation and figures, to show the level of detail that is useful.
A fictional bar association runs a two-day conference for about 450 delegates with a lead working remotely three days a week. It sets one event chat, a Tuesday progress call at 10 am and a Friday written status.
A speaker's substitution agreed in chat is moved to the decision log the same day, with the approver's reply. Disputed items are settled from the log. The urgent line is used twice in the final fortnight, both for venue access.
Use this yourself
Remote communication rules sheet
Copy into the engagement file and agree it at the first meeting.
- Channel for decisions and who keeps the log:
- Event chat channel and members:
- Weekly call: day, time, attendees, agenda owner:
- Committee call frequency:
- Routine and urgent response windows (see the availability calendar):
- Urgent contact and the list of what counts as urgent:
- Note-taker and window to correct notes:
- Where documents live and the naming rule:
- What may and may not be shared in chat (confirm with privacy or IT):
- Review date for these rules:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The team already uses one chat tool and a decision log.
- A few people need to be in the loop.
- Calls are short and the sponsor reads notes.
Outside planning help earns its fee when
- Several committees expect different channels.
- Decisions have been lost or reversed because they lived in chat.
- The lead works across time zones or alongside suppliers overseas.
Want communication rules your whole team will follow?
A remote embedded event project manager works in the hours and channels you agree, with decisions recorded in writing. A project lead can help you draft the rules, set up the log and run the weekly rhythm. Share how your team communicates today, including the awkward parts.
Questions organisers ask
How many channels are too many?
More than one for decisions is too many. Keep one for chat, one for records and one for urgent matters, and say which is which.
Should calls be recorded?
Only if everyone agrees in advance and your policy allows it. Written notes are usually enough and are easier to search.
Can the lead use their own tools?
Ask your IT and privacy leads first. Tools that hold attendee data or confidential files are your organisation's decision.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.