How to prioritise event workload when time runs short
There is more to do than your team has hours for, and everything feels urgent.
The short answer
Prioritise by three questions: does it have a date that cannot move, does something else depend on it, and what happens if it is done late or not at all? Then sort each task into do now, schedule, hand off or drop.
Do this with the event owner, because dropping or delaying a task is a decision about scope, not a scheduling detail.
Urgent is not the same as important
Loud requests feel urgent. A task is truly time-critical only if a date is fixed outside your control, such as a printer deadline or a venue cut-off, or if other tasks are waiting on it.
Importance is about the outcome: what does the event lose if the task is late, reduced or dropped?
The decision sequence
- List every open task in one place. Use your workload estimate if you have one.
- Add the hours each takes and who is doing it, using the committee workload planner to see overlapping commitments.
- Mark fixed dates: supplier cut-offs, venue deadlines, speaker and printing dates, member communications.
- Mark dependencies: which tasks cannot start or finish until another is done.
- Rate the effect of lateness or omission for each: stops the event, harms the guest experience, internal only, or none.
- Sort into four groups: do now, schedule with a date, hand off to someone with capacity, drop or defer after the event.
- Take dropped and deferred items to the event owner for a recorded decision. Update the decision log.
- Recheck weekly. Priorities change when suppliers, speakers or approvals move.
A simple sorting grid
| Group | Test | Typical example |
|---|---|---|
| Do now | Fixed date soon, others depend on it, or event cannot run without it. | Confirming final numbers to the venue. |
| Schedule | Matters, but no date forces it today. | Speaker biographies for the programme. |
| Hand off | Someone else has the skill or time to do it. | Printing proofs checked by the designer. |
| Drop or defer | Low effect if late or absent, or can wait until after the event. | Redesign of the website footer. |
Dealing with the cost of saying no
Every deferred task has a cost, such as a member who was promised something and does not get it. Name the cost when you take the item to the event owner.
If the list is still longer than the hours, the problem is capacity, not prioritisation. Use the capacity gap estimator and look at options in the internal capacity assessment.
Common pitfalls
- Priorities set by whoever asked last.
- Items dropped silently, so a committee member finds out at the event.
- Fixed dates not checked, so a supplier cut-off is missed.
- Dependencies ignored, so a task done early sits waiting for something else.
- No weekly recheck, so the list becomes outdated.
Worked example · Fictional example
Ten weeks out, 60 hours short
Fictional organisation and figures, for illustration only.
A fictional association secretariat has 14 open tasks and about 60 hours fewer than needed in the next three weeks. Four tasks have fixed dates: final venue numbers, printer artwork, speaker travel booking and the early-bird closing notice.
Those four go into do now. Two are handed to a volunteer who has the skill and time: reviewing the printed proofs and drafting speaker biographies. Three are scheduled for later with named dates. Two are deferred until after the event: redesigning the website footer and a new survey layout. The secretariat head takes the deferred items to the chair for approval and records the decision, which brings the list back within the hours that exist.
Use this yourself
Workload prioritisation table
Copy into a sheet and fill one row per open task. Review weekly with the event owner.
| Task | Owner | Hours | Fixed date? | Others depend on it? | Effect if late or dropped | Group | Decision recorded |
|---|---|---|---|---|---|---|---|
| Yes (date) / No | Yes (which) / No | Stops event / Guest experience / Internal / None | Do now / Schedule / Hand off / Drop or defer | Yes / No | |||
Handle it in-house, or bring in help?
Your team can usually handle this when
- The overload is short and the event owner is available to make the scope decisions.
- Most tasks have clear owners and dates already.
- Someone can chase the weekly review.
Outside planning help earns its fee when
- Several committees or departments each place requests on the same people.
- The overload is every week, which suggests a capacity gap, not a sorting problem.
- Nobody has the standing to defer or drop tasks.
Want help sorting the list and keeping it sorted?
A conference project lead can run the weekly prioritisation with your team, hold the dependencies and fixed dates, take deferral decisions to the event owner and keep the decision log current. Which tasks matter most remains your call; the project lead coordinates the list and the follow-up for the agreed scope.
Questions organisers ask
How often should we reprioritise?
Weekly in the last two months, and any time a fixed date, supplier or approval changes.
Who decides what gets dropped?
The event owner or committee, on the project team's recommendation. Record the decision and the reason.
What if everything has a fixed date?
Check each date. Many are preferences rather than hard limits. If they are all real, the problem is capacity, and the answer is more people or less scope.
Does the workload planner decide priority?
No. It shows allocated hours against available hours and overlapping commitments. You still rank the tasks.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.