Capacity and staffing
Writing event role descriptions that work
Several people have agreed to help, and each has a slightly different idea of what they are responsible for.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A role description for an event is a single page that says what the role is for, what it decides, who it reports to, what it does in each time block, and what it hands to whom. It describes the work on the event, not an employment arrangement.
Write it from the post matrix in your staffing plan, then read it back to the person and change anything they cannot do.
What goes on the page
| Heading | What to write | Test |
|---|---|---|
| Purpose | One sentence: what the event gets from this role. | Could someone else read it and know when the role has done its job? |
| Reports to | One named supervisor, plus a deputy. | Is there exactly one person to ask? |
| Decisions it can make | What the role may decide alone, up to what limit. | Does it name something concrete, such as seat swaps or a refund request routing? |
| Escalate when | What must go to the supervisor. | Is the trigger a fact, not a feeling? |
| Tasks by time block | Before, setup, during, breaks, close, after. | Does each task have a time or a trigger? |
| Handover | What the role passes on, to whom, and in what form. | Can the next person start without a conversation? |
Keep roles about the event, not the person
Describe the post and its tasks, so the description still works when a different person fills it. This also makes it easy to brief a replacement (see coordinator replacement handover).
Avoid wording that reads as terms of work. How someone is engaged, what hours they work and what conditions apply are questions for your HR adviser or legal adviser, and sit outside this page.
Separate roles that are often blurred
- Supervisor versus post holder: a supervisor who also staffs a desk cannot supervise.
- Project owner versus committee chair: one decides programme, the other runs the delivery.
- Supplier lead versus your own liaison: the supplier runs their crew, your liaison confirms the agreed scope.
- Volunteer versus staff duties: volunteers should not be handed tasks that need specialist skill or sign-off (see competency checklist).
Review each description with its owner
- Send the draft with the staffing plan and the run-of-show.
- Ask the person to mark anything unclear, anything they cannot do, and anything missing.
- Resolve overlaps with neighbouring roles at the same time, not later.
- Freeze the version and give each person only their own page plus the contact sheet.
Pitfalls
- Descriptions so long nobody reads them on the day. Keep to one page.
- Verbs like support or assist with no object. Say what is supported, for whom.
- Two roles both holding the same decision.
- A decision limit with no number or example.
Worked example · Fictional example
Registration lead for a conference
Fictional organisation and details. Times and limits are hypothetical and show only the format.
A fictional association writes a role description for its registration lead, based on its staffing plan.
| Heading | Description |
|---|---|
| Purpose | Every registered delegate is checked in smoothly, and exceptions reach the right person quickly. |
| Reports to | Project owner. Deputy: secretariat officer. |
| Decisions it can make | Reprint a lost badge. Admit a delegate whose name appears on the list under a different spelling. |
| Escalate when | A delegate is not on the list; a payment query is raised; a badge needs a changed name or title. |
| Tasks by time block | Setup: lay out lists and badges. Doors open: check in. Break: handover to Volunteer 1. Close: reconcile the list, hand over to the project owner. |
| Handover | Final attendee list with no-shows marked, to the project owner, by end of day. |
Use this yourself
One-page role description template
Copy this into a document, one page per role. Complete every line; write Not applicable rather than leaving a heading blank.
- Role name and post location:
- Purpose, in one sentence:
- Reports to (name) and deputy (name):
- Decisions this role may make, and the limit:
- Escalate to supervisor when:
- Tasks before the event / setup / during / breaks / close / after:
- Skills or briefings needed before starting (link to competency checklist):
- What this role hands over, to whom and in what form:
- Contacts: supervisor, venue, supplier lead, emergency contact:
Handle it in-house, or bring in help?
Your team can usually handle this when
- A small team where everyone already knows the roles and decisions are rarely disputed.
- You have last year's descriptions and the posts have not changed.
- One person can review each page with its owner.
Outside planning help earns its fee when
- Roles overlap and decisions are being contested between committee members.
- Supplier crews, volunteers and your staff all work in the same area and need clear boundaries.
- You want an independent view of which role should hold which decision.
Want role descriptions written and agreed?
A conference project lead can draft the one-page role descriptions from your staffing plan, resolve overlaps with each owner, and keep the final set and contact sheet current. Questions on employment status or conditions stay with your own HR or legal advisers.
Questions organisers ask
How long should a role description be?
One page. If it is longer, people will not read it on the day. Put background and long procedures in separate documents and refer to them.
Do volunteers need a role description?
Yes. A short one helps volunteers know what they are responsible for, what they can decide and when to call someone. The volunteer briefing page covers how to deliver it.
Should the description include working hours and pay?
Event hours for a post belong in the staffing plan. Anything about pay, contract type or conditions is for your HR or legal adviser to advise on, not for this document.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.