Top view of an open planner on a blue background with 'Vote Yes' text. Ideal for election or voting concepts.
Photo by Tara Winstead on Pexels

Event Strategy

Event campaign operations and review

Coordinate approved event details, campaign release decisions, changes and post-event review.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Event Strategy Desk.

Run an event campaign from a single approved set of event details. Give each public placement an owner, agree its release point, and decide before launch which records will support the review. That lets the team correct conflicting information and assess the event beyond registrations alone.

Keep one campaign record

Record the event name, intended audience, attendee promise, program, date, start and finish times with a named time zone, format, venue or joining method, registration conditions and help contact. Name the change approver; the campaign calendar and individual assets should refer to this record.

List where those facts appear: invitations, partner materials, listings, the registration page, confirmations, calendar items and attendee instructions. For each placement, record its owner, approval point and correction route. A partner-controlled placement may take longer to change than one the organiser controls.

Agree on release decisions

PointDecision before proceeding
Before promotionDoes the programme support the advertised promise, and do booking routes show the approved practical details?
Before the eventDo registrants have current instructions, and does someone own unresolved joining or access requests?
At campaign closeAre attendee commitments assigned, and are the records ready for review?

A release decision needs an owner and something they can inspect, such as approved venue instructions or a booking-route check. Detailed tasks belong in the promotion checklist; the campaign record shows who can authorise each stage.

Handle material changes

When a detail changes, approve the replacement, identify affected placements and people, and assign corrections. Update the booking route and public descriptions, then tell affected registrants what changed. Check that partner assets and queued messages will not restore the old detail.

For a venue change, confirm the arrival route and available access information before describing them. If a detail is still being confirmed, provide a contact route rather than guessing.

Keep essential booking information separate from optional promotion. Check ACMA guidance before sending campaign messages, especially when promotional content is included.

Review the decisions made

Before launch, identify the records needed for review: released placements, valid bookings, cancellations, observed attendance, delivery issues, feedback and fulfilled commitments. Give each a source, definition, extract date and owner. If the team uses Google Analytics, URL builders can collect campaign data with custom URLs.

Review delivery records while staff can still resolve errors and fulfil promises. Review longer-term outcomes at a later stated point. Record what happened, what remains uncertain and which campaign decision should change next time. Close the campaign with outstanding attendee commitments and next actions assigned.

Key Records for Post-Event Campaign Review

Released placements
Required
Valid bookings
Tracked via registration system
Cancellations
Recorded by date and reason
Observed attendance
Verified at event
Feedback collected
From post-event survey
Fulfilled commitments
Confirmed by team lead

Further reading: How to Use Microsoft Dynamics for Campaign Performance Tracking (wolfesystems.com.au).

In this guide

  1. Building an event promotion checklistBuild an event promotion checklist with owners, release points and evidence for each campaign task.
  2. Updating event invitations after a venue or date changeCorrect event invitations after a venue or date change, including saved copies, partner assets and recipient instructions.
  3. Reviewing the gap between registration and attendanceInvestigate the gap between event bookings and observed attendance without guessing why people were absent.

More in Event Strategy