
Event Follow-Up
Post-event follow-up
Plan post-event follow-up around attendance, promised resources and agreed conversations, with clear owners and a review of what happened next.
Post-event follow-up should deliver what was promised, answer requests people made and give those who agreed to continue a clear next step. Start by reconciling event records, then fulfil commitments, assign each open task, check each message’s basis and review what remains. Registration or attendance alone does not mean someone wants a sales call.
Sort the records before sending
Bring together registrations, cancellations, attendance records, resource requests and conversation notes under the event identifier. Resolve duplicates where possible and leave uncertain attendance marked as uncertain. Keep speakers, staff and transferred tickets out of the attendee group unless their status has been checked.
What is known / Immediate job
- Attended, with no individual request
- Send the promised recap or materials, if appropriate.
- Registered but not observed attending
- Offer an accurate way to catch up, if one exists.
- Requested a resource or answer
- Deliver it or explain when it will be available.
- Agreed to a further conversation
- Give an owner the context and agreed contact route.
- Status or contact basis is unclear
- Check the record before assigning a message.
These groups can overlap. An attendee may need both the slides and an answer to a question. Track both tasks rather than treating a general email as completion.
Honour the event promise
Deliver resources promised at the event, and keep fulfilment distinct from sales follow-up.
For each promised item, record what is ready, who will send it, when it was sent and its delivery status. Keep queued or failed sends open, and assign an owner to resolve known delivery failures.
Respond to the request made
Someone who asked for a specification may need the document and a contact for clarification. Someone who requested a meeting needs an owner who can discuss the stated issue. Someone who attended a learning session without asking for individual contact may need only the general event material.
For an agreed conversation, retain the question, what was promised, the agreed contact method and timing, and the responsible person. Check existing account ownership before assigning a new task. A badge scan, public question or polite exchange does not establish buying intent. If notes are too thin to support a proposed approach, ask the staff member who recorded them to clarify.
Set priorities from commitments
An answer needed for an agreed meeting should reach its owner promptly. Send a promised resource when the checked version is ready, and update recipients if an expected delivery point cannot be met. Offer a no-show recap or replay only when it exists. Use agreed timing where it was recorded; these are priorities, not a fixed schedule for every event.
Use a task list that records the event, recipient or account, commitment, owner, due point, contact context and completion state. A queued email or unaccepted assignment remains pending. Record known delivery failures and give them an owner.
Check the basis for each message
Keep event fulfilment, individual responses and future promotion distinct. The Spam Act 2003 (Cth) governs commercial electronic messages, including marketing email and SMS. Before sending, check consent, identify the sender and provide a working unsubscribe method; honour unsubscribe requests.
For entities covered by the Privacy Act, the Australian Privacy Principles (APPs) provide privacy requirements for handling personal information. The OAIC (Office of the Australian Information Commissioner) publishes APP guidance. Assess the purpose and context before using event information for unrelated promotion.
APP 3 limits an organisation’s collection of solicited personal information to what is reasonably necessary for its functions or activities. Collection must use lawful and fair means. Sensitive information has stricter conditions: the individual’s consent is generally required unless an exception applies.
APP 5 requires reasonable steps to notify people about collection or ensure they are aware of it. Matters to address, as applicable, include the entity’s identity and contact details, the fact and circumstances of collection, and whether collection is required or authorised by law. They also include the purposes, consequences if information is not collected, usual disclosures and information about the entity’s APP Privacy Policy.
Further matters include whether the entity is likely to disclose information to overseas recipients and, if practicable, the countries where they are located. Take these steps before or when collecting information, or as soon as practicable afterwards if that is not practicable.
Under APP 6, personal information may generally be used or disclosed for the purpose for which it was collected. A different purpose may be allowed if an exception applies, such as the individual consenting, or the individual reasonably expecting the use and the new purpose being related to the original purpose.
APP 7 restricts an organisation’s use or disclosure of personal information for direct marketing unless an exception applies. Where an exception permits direct marketing, provide a simple way to opt out and comply with opt-out requests. If the person’s information was not collected from them, or they would not reasonably expect this use, additional opt-out information requirements apply.
APP 11 requires an APP entity to take reasonable steps to protect personal information it holds from misuse, interference, loss, and unauthorised access, modification or disclosure. Those steps include technical and organisational measures.
When an APP entity no longer needs personal information for a purpose permitted under the APPs, it must take reasonable steps to destroy or de-identify it. This does not apply where the information is part of a Commonwealth record or must be retained under Australian law or a court or tribunal order.
Key compliance and performance metrics
- APP 3: Collection limitationOnly collect personal information reasonably necessary for event functions
- APP 5: Notification requirementNotify individuals about collection purpose and contact details
- Spam Act 2003 (Cth)Requires consent, sender identification and working unsubscribe method
- APP 7: Direct marketing restrictionOpt-out must be simple and honoured; additional notices apply if info not collected directly
- APP 11: Security obligationTake reasonable steps to protect personal information from loss or unauthorised access
Review the next step
An early review should identify undelivered resources, unanswered questions, duplicates and tasks without an owner. Assign a review owner to maintain an event follow-up register showing open items, owners, due points and status.
Start the review after the event wraps up, then revisit open items at their recorded due points. A post-event debrief can gather staff feedback, express gratitude and discuss improvements.
Use the review to identify which routes helped people continue and one specific change for the next event.
In this guide
- Separating follow-up for attendees and no-showsBuild separate post-event messages for attendees, no-shows and uncertain records without assuming attendance or sales interest.
- Sending promised resources before a sales requestTrack event resource promises, deliver checked materials clearly and decide separately whether a sales request is appropriate.
- Routing high-interest conversations to the right ownerAssign event follow-up from the attendee's stated issue, check existing account ownership and confirm each promised action has an owner.
- Measuring whether follow-up helped the next buying stepDefine the next buying step, track eligible follow-up records and report outcomes without treating a later sale as proof an email caused it.



