
Event Follow-Up
Part of Event email and reminder coordination
Distinguishing reminders from permission-based marketing
An event reminder tells a registered person what they need to attend.
A genuine event reminder serves an existing booking; permission-based marketing promotes a product, event or other action. Judge the message by its content and purpose, not its label in the sender’s system. Under the Spam Act 2003 (Cth), commercial marketing requires consent.
Review the whole email
Read the subject, body, images, links and footer. A factual change to the booked event’s start time or entry instructions serves the booking; a discount for the next event or an unrelated product offer promotes something else.
If an event reminder also offers a discount for the next event, that offer is marketing. Check the consent record for where consent came from and what the person agreed to; registration alone should not be treated as proof of agreement to future promotion.
For commercial text messages, identify the sender and include an easy opt-out. ACMA’s e-marketing guidance is a reference point when a message’s purpose or requirements are unclear. The Privacy Act 1988 and 13 Australian Privacy Principles also cover how personal information is collected, used and disclosed.
Event Reminder vs Permission-Based Marketing
- Purpose
- To inform about an existing booking (e.g. event time, entry instructions)
- Content Focus
- Operational details related to the booked event
- Consent Requirement
- Not required for operational reminders; only needed if promotional content is included
- Marketing Add-On
- Offering a discount on a future event or unrelated product
- Legal Basis
- Spam Act 2003 (Cth) – commercial marketing requires consent
Keep lists and journeys separate
Store event registration status apart from marketing consent. Keep a record of where and when consent was obtained and what the person agreed to. A person who opts out of promotion should still receive necessary information about a booked event, provided the message remains genuinely operational and applicable requirements permit it.
Do not add someone to a newsletter merely because they registered. Before sending, check what action the message asks for, why the recipient is receiving it and what consent record supports any promotional part. Keep a copy of the approved template and suppression logic.
Test the process with a realistic example before relying on it. Take one recent registration, trace which messages it received and mark each as operational or promotional. Where the answer is unclear, rewrite the message or remove the promotional part, and note the decision so reviewers can apply the same reasoning to later messages.



