
Event Strategy
Part of Marketing recurring events
Keeping a recurring event's audience promise consistent
Define what every edition promises, separate it from date-specific details and check the invitation against the programme.
Keep a recurring event’s audience promise consistent by stating what every edition is for and testing each proposed date against it. The topic and speaker can change. People should still recognise who the series serves, what kind of work they will do and the limits of what it offers.
Set a boundary the team can apply
Write the promise as a short test: This series helps [audience] work through [kind of problem] by [kind of activity]. Add the expected knowledge level and an important exclusion if either affects who should book.
For a hypothetical series: Process owners compare practical responses to supplier-approval delays using worked cases. One edition might examine an initial route; another might examine exceptions. A product demonstration could be useful, but it needs an honest description if the series has been promoted as peer comparison.
Check several planned editions against the statement. If one cannot provide the promised activity, change its program or description. If it serves a substantially different purpose, consider placing it outside the series.
Ensure consistent audience promise across recurring events
- Define the series promise using*This series helps [audience] work through [kind of problem] by [kind of activity]*
- Include expected knowledge level and key exclusions if relevant
- Test each planned edition against the promise statement
- Adjust program or description if an edition cannot deliver the promise
- Consider placing substantially different editions outside the series
Keep the right things stable
| Recognisable series promise | Reconfirm for each edition |
|---|---|
| Intended audience and recurring problem | Particular question, case and outcome |
| Usual kind of participation | Speaker, agenda and contribution route |
| Meaning and limits of the series name | Date, time zone, venue or joining method, fee and access arrangements |
This is an editorial check, not a demand for identical logistics. A workshop replacing a briefing should be labelled as a workshop. If beginners are welcome only at certain dates, identify those dates. A reusable page or email must not carry an earlier edition’s claims into the next.
Stable vs. variable elements in a recurring event series
- Recognisable series promise
- Must remain consistent across editions
- Intended audience and recurring problem
- Remain unchanged
- Usual kind of participation (e.g., speaker-led, peer discussion)
- Consistent format unless clearly rebranded
- Meaning and limits of the series name
- Clarify date, time zone, venue, fee, access method
- Logistics (e.g., format, location, timing)
- Can vary without breaking consistency
Check what the invitation promises
Put the edition invitation beside its page and running order. For each outcome claim, point to the part of the session that delivers it.
‘Compare two approaches’ requires two approaches and useful criteria. ‘Practise’ requires a task and time to try it. Narrow any claim the program cannot support before inviting people to book.
Approve one current outcome statement for the edition. If the program changes after registration opens, update affected descriptions and tell booked attendees about a material change to what they chose. Keep the approved wording dated so partners and colleagues can use the current version.
Validate invitation promises against actual programme delivery
- Align the edition invitation with the event page and running order
- For each outcome claim, identify the session component that delivers it
- Ensure claims like 'compare two approaches' are supported by two clear approaches and criteria
- Verify 'practise' includes a task and dedicated time for hands-on work
- Approve one current outcome statement per edition; update if changes occur post-registration
- Communicate material changes to registered attendees promptly
Look for drift across dates
After each edition, compare the advertised activity with what attendees could actually do. Use the running order, delivery notes, specific questions and feedback to locate any gap. A broad satisfaction score will not identify which promise failed. Distinguish one delivery problem from a pattern in which the series now serves a different audience or expects different prior knowledge.
When the pattern changes, revise the series description before promoting another date. The name should help a prospective attendee judge the next edition, even if they have never attended before.
Post-event review: Detecting drift in audience promise
- Use feedback, running orders, and delivery notes to assess gap between promise and delivery
- Avoid relying solely on broad satisfaction scores
- Distinguish isolated issues from patterns of change in audience or knowledge expectations
- Revise series description if a pattern of drift is confirmed
- Ensure the series name remains useful for first-time attendees to judge suitability



