How to analyse event date conflicts
A date looks free on the committee diary, and then someone notices the same week already holds another event.
The short answer
Check every candidate date against four things: your own people, shared suppliers and venues, your audience's calendar, and the days either side for setup and recovery. A clash on people or venue is a hard conflict that must be resolved. A clash on audience or adjacent days is a soft conflict that needs a decision and a written reason.
Run the check before any date is announced. If the clash is between events competing for the same people, continue with event portfolio resource allocation.
Four kinds of clash
| Type | Question | Hard or soft |
|---|---|---|
| People | Is the programme owner, finance approver or on-site lead already committed to another event that week? | Hard |
| Venue and suppliers | Is the venue, AV supplier or caterer already booked, or booked for your setup day? | Hard |
| Audience | Do your members, speakers or sponsors have a known peak, conference or reporting deadline in that week? | Soft |
| Adjacent days | Is there enough setup before and recovery after, including the days that other events need? | Soft |
Check the calendars that are easy to miss
- Public and state holidays: confirm the official calendar for the state where the event is held, because dates and observances differ and some are announced late.
- School holidays and examination periods that affect speakers, members with children or student audiences. Confirm the current official calendar rather than relying on last year's.
- Your own members' peak periods, such as financial year-end, audit season or tax filing, depending on who they are.
- Other organisations' major events in the same field in Kuala Lumpur or Selangor, which may draw the same speakers and attendees.
How to decide what to do with a conflict
- Write each clash in the log with the type, the weeks affected and the event that was there first.
- Mark it hard or soft. Do not announce a date that carries an open hard conflict.
- For each hard conflict, choose to move, split the task, add capacity or drop the event, and name who decided.
- For each soft conflict, either accept it with a reason, such as a lower expected turnout that the committee has accepted, or mitigate it, for example by moving registration close earlier.
- Re-run the check whenever a date, venue or key person changes.
Common mistakes
- Checking only the event day. Setup, speaker travel and pack-down can use the days either side.
- Treating a soft conflict as no conflict because nobody complained yet.
- Relying on the venue's availability alone. The venue being free does not mean your people or your audience are.
- Several one-day roadshow stops on consecutive days with unchecked travel between them. The briefing circuit planner lets you enter your own travel ranges and shows which transitions are impossible.
Worked example · Fictional example
A conflict found before the notice went out
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Perunding Kejuruteraan wants its half-day seminar on Thursday 12 November. The programme owner is also the on-site lead for an annual dinner on Friday 13 November, and the venue for the dinner needs its setup the day before.
The log records one hard conflict on people and one soft conflict on adjacent days. The secretariat moves the seminar to the Tuesday of the following week, accepts that two speakers will be confirmed later, and records the reason in the log.
| Candidate date | Clash | Type | Hard or soft | Decision and owner |
|---|---|---|---|---|
| Thu 12 Nov | Programme owner on setup for dinner | People | Hard | Move seminar. Honorary secretary |
| Thu 12 Nov | Setup day for dinner at the same venue | Venue | Hard | Resolved by moving |
| Tue 17 Nov | Two speakers away that week | Audience | Soft | Accept, confirm replacements. Chair |
Use this yourself
Date conflict log
Add one row per candidate date. Keep rejected dates in the log so the reason is not lost.
| Candidate date | Clash found | Type | Hard or soft | Weeks affected | Decision | Decided by and date |
|---|---|---|---|---|---|---|
| People / venue / audience / adjacent | Move / split / add capacity / accept / drop | |||||
Handle it in-house, or bring in help?
Your team can usually handle this when
- You have a small number of events and a single shared diary.
- Venue and supplier bookings are made by one person who sees all of them.
- Soft conflicts are accepted by a committee that meets regularly.
Outside planning help earns its fee when
- Dates are announced from several committees without a single check.
- Several events share suppliers or venues in the same weeks.
- A multi-stop schedule across Kuala Lumpur, Selangor and Seremban depends on travel nobody has measured.
Want clashes checked before dates go out?
A recurring programme manager can keep one conflict log across all your events, run each candidate date through the checks above and bring hard conflicts to the decision owner with options. Dates, venue choices and the final decisions stay with your committee. For multi-stop schedules, the event recurring calendar capacity planner is a first look at where the weeks collide.
Questions organisers ask
Who should own the date conflict log?
One person, usually the secretariat head or portfolio coordinator, so there is a single place to check before any date is announced. Event owners add their dates to it.
Are public holidays a hard conflict?
Treat them as a question to confirm for the state and the audience. Check the official calendar for the date and place. Whether it is hard or soft depends on your audience and venue.
How far ahead should dates be checked?
Before the date is announced and again before contracts are signed. Re-check when any key person, venue or supplier changes.
Can a soft conflict be left as it is?
Yes, if someone with authority accepts it and the reason is written in the log. The problem is leaving it unrecorded, so nobody knows it was chosen.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.