Attendee journey map template for a paid event

You've sold someone a ticket. They arrive late because the entrance in the reminder email is closed, miss the opening session and spend the break asking where their included lunch is. Your sales report records a completed purchase. Their experience tells a different story, and it may affect whether they buy again.

An attendee journey map helps you connect those two views. It follows a defined attendee through discovering your event, deciding to pay, preparing, arriving, taking part and deciding what happens afterwards. At each stage, record what they're trying to do, what actually happens, the evidence behind that account and who can fix the problem. The useful result is a set of decisions your team can carry out.

This guide includes a reusable attendee journey map template and a worked example for a paid workshop. You'll see how to separate evidence from assumptions, include the people who didn't complete the journey and choose improvements that protect the experience without making promises your event can't deliver.

Start with one attendee and one reason to attend

The first thing you want to do is decide whose journey you're mapping. "Our attendees" is too broad when it includes someone buying for a group, a first-time visitor arriving alone and a regular who knows the venue. They may attend the same event, but the information and support they need can differ considerably.

Write a short description based on a real situation. For example, you're mapping a first-time attendee paying personally for a practical photography workshop. They want help using their camera and need to know whether the session suits their current ability. That description gives the team something concrete to investigate. It doesn't require an invented biography, favourite brands or assumptions about their personality.

Nielsen Norman Group's explanation of journey mapping identifies the person, scenario, stages, actions, thoughts and opportunities as core parts of the method. Apply that discipline to your event. Start with what this person wants to achieve and follow their experience over time, rather than arranging the map around your departments.

Choose a starting point that precedes the first contact you control. Someone might decide to learn photography before they see your announcement. Choose an ending that reflects the event's purpose too. For a practical workshop, receiving promised materials and trying the technique afterwards may matter more than the moment they leave the room.

Keep important differences visible. A companion receiving a ticket from the buyer might never see the purchase confirmation. An attendee who needs step-free access may need venue information before paying. When the route changes substantially, create a separate version or a clearly labelled branch. Don't combine incompatible experiences into an imaginary average attendee who never actually exists.

Copy this attendee journey map template

You can use the following template in a shared document or spreadsheet. Make a copy for the attendee group you've selected, then repeat the stage record for each meaningful part of their journey. Start with discovery, consideration, purchase, preparation, arrival, participation and follow-up. Adjust those stages when your evidence shows a different route.

For the map's introduction, write the event and edition, the attendee group, the reason they're attending, where the journey starts and ends, and the question your team wants to answer. Record when the map was last reviewed. State whether it describes the current experience or a proposed experience, because mixing those together makes an unresolved problem look like a completed improvement.

Use these fields for each stage:

• Attendee's task: What is the person trying to do or decide here?

• Actions and contact: What do they actually do, and which page, message, person or physical place do they encounter?

• Questions and expectations: What do they need to know, and what do they believe will happen?

• Evidence and confidence: Which observation, conversation or operational record supports this account? What remains an assumption?

• Difficulty and consequence: What prevents progress, and what happens to the attendee and event business?

• Owner and response: Who will investigate or change it, by when, and what should happen if the normal route fails?

• Outcome and review: What would demonstrate improvement, and when will you check it?

Write enough for someone outside your immediate team to understand the problem. "Better communication" won't help your door supervisor. "The reminder names the main entrance, but workshop attendees must use the courtyard door" tells them what needs checking. The response might involve the reminder, signage and the venue briefing, so identify the person coordinating those changes.

Leave unanswered fields visibly unanswered. You can write "unknown, ask recent first-time buyers" or "assumption, observe arrival at the next session". That is useful work. Filling every field with a confident guess creates a finished-looking map that may direct your team towards problems attendees don't have.

Gather evidence before filling in the story

You'll probably already have useful evidence in support conversations, refund reasons, attendee messages, order records and the questions staff hear repeatedly. Bring the original wording where possible, with identifying details removed from the shared map. A summary such as "people were confused" loses the detail that tells you whether the problem was price, timing or a missing instruction.

Compare those records with direct conversations and observation. A support inbox describes people who contacted you. It cannot explain everyone who quietly gave up. Speak with recent first-time attendees, returning attendees and people who considered coming but didn't buy, where you can appropriately reach them. Someone who bought and didn't attend can reveal a different problem again.

GOV.UK's guidance on in-depth interviews recommends open, neutral questions and real examples. Ask someone to walk you through their last decision. "What happened after you saw the workshop?" is more useful than asking whether a clearer page would have persuaded them. Follow their account before suggesting your own explanation.

For our workshop, ask how they checked the skill level, what they needed to bring and how they decided the price was reasonable. If they mention sending the page to a friend, explore what happened next. You might discover a joint decision that your current map treats as a solo purchase. That changes the information the page needs to explain.

Label each finding by its source and limits. An attendee saying they couldn't find the entrance supports that person's experience. Several similar messages strengthen the reason to investigate, but they still don't reveal how widespread the problem is. An email being delivered doesn't establish that its instructions were read or understood. Keep those distinctions in the evidence field.

Don't turn an interviewer's interpretation into an attendee quote. If someone described checking the cancellation terms, record that action. Calling them anxious adds an interpretation you may need to verify. You can include feelings when people report them, but a decorative emotional curve is a poor substitute for knowing which question they couldn't answer.

Discovery and consideration: connect the invitation to the decision

At discovery, your attendee is working out whether the event deserves attention. Record the invitation they actually encountered, including an announcement shared by a tutor or a friend's message. Your own social post may be the original source, but the person might first see a cropped screenshot with the date missing. Their experience begins with that incomplete invitation.

Much of that first contact happens in channels you don't control. In Loopyah's survey of 500 US event attendees, 65% said they rely on social media posts or ads to find out about upcoming events and 56% on word of mouth from friends, well ahead of event or venue newsletters at 27%.

Next, follow the questions they need answered before they can consider paying. For the photography workshop, those might concern experience level, equipment, location and what practical help the instructor provides. A returning attendee may know the format already. A newcomer has to establish all of it, including whether the description is credible enough to justify travelling and paying.

The map should show where each question gets answered and where it doesn't. If support keeps explaining that phone cameras aren't suitable, investigate whether the announcement and event page make the equipment requirement clear. A persuasive invitation that attracts unsuitable buyers can create refunds and disappointment later. More clicks won't resolve that mismatch.

You don't need to rebuild the event page inside the map. Link the relevant evidence and record the unresolved decision. Our event landing page guide explains how to present the offer and practical details. The journey map adds the connection between what attracted the attendee, what they expected to buy and what your team eventually delivers.

Include the decision to wait. Someone may be checking a work rota, coordinating transport or discussing the event with a friend. A pause isn't automatically a failure of persuasion. If your research shows buyers need a confirmed finish time to arrange travel, publishing that information is a more appropriate response than inventing urgency to push them through the decision.

Purchase: map the buyer and the people they book for

Once someone decides to pay, record the purchase they attempt and the confirmation they receive. Include the ticket type, what it includes, the total amount presented and any relevant terms. You aren't conducting a complete checkout audit here. You're checking whether the person can complete the decision they just made and whether the result matches their understanding.

Suppose a workshop buyer purchases places for themselves and a friend. Your sales record contains one buyer, but the event will receive two attendees. Follow what happens to the friend's ticket and preparation information. If the buyer must forward it, test what they actually forward. A confirmation intended for the purchaser may include information that doesn't help the second attendee prepare.

Write the failure route too. If a payment doesn't complete, how does the buyer know whether they have a booking? If the confirmation can't be found, where do they get help? The owner should know which records establish a valid order. Avoid telling buyers to try paying again while the status remains unclear, because the original attempt needs checking first.

For detailed website measurement, use the separate guide to understanding ticket buyer journeys in GA4. Analytics can show observed actions around purchase. The broader attendee map includes the conversations, shared decisions and physical experiences those reports don't describe. Keep the tools connected through a specific question, such as whether uncertainty about equipment interrupts an otherwise suitable booking.

Preparation: check whether paid attendees can act on your instructions

Buying a place creates a new task. The attendee now needs to get ready. For our workshop, they need their camera, a charged battery, the right arrival time and instructions for reaching the room. The preparation stage should show when they receive that information and whether they can retrieve it later without searching through unrelated promotional messages.

Separate information that affects the purchase from information that helps fulfil it. A required camera is relevant before payment. A detailed route through the building may be useful nearer the event. If a requirement first appears in the reminder, ask whether someone would reasonably have made a different buying decision had they known earlier. The fix may belong in the event description as well.

Accessibility needs deserve the same attention throughout the journey. W3C's accessible events checklist covers venue access, scheduling, materials and participant needs. For your map, identify when a person can check relevant arrangements, how they can ask a question and who confirms what will actually be available. Don't leave an unverified promise in the sales copy.

A pre-event question can help you prepare when the answer changes delivery. Our guide to pre-event survey questions explains that choice. Ask about something your team can respond to, then assign responsibility for reviewing the replies. Collecting requests without arranging the promised response creates another failure between the attendee's expectation and your delivery.

Test the preparation experience with someone unfamiliar with the venue. Ask them to find the arrival instructions on their phone and explain where they'd go. You may know that "studio entrance" means the courtyard door, but the attendee has never seen the building. Record what they can establish from the message itself, rather than helping them through the test.

Arrival and participation: follow the experience beyond the scan

A successful ticket scan establishes entry. It doesn't establish that arrival worked well. Follow the attendee from the point they approach the venue to the point they can begin participating. Include finding the entrance, understanding the queue, presenting the ticket and locating the room. Pay attention to changes of responsibility between your staff, venue staff and contractors.

For our workshop, the buyer may arrive with the friend whose ticket they hold. If the friend arrives separately, the normal route changes. The map should show how staff help without blocking other arrivals or exposing order details unnecessarily. This is a practical handover to resolve before the event, alongside the normal check-in process your platform already supports.

The UK Health and Safety Executive's crowd planning guidance considers entrances, movement, exits and the ways people may behave at a venue. Use your map to flag observed arrival difficulties to the people responsible for those arrangements. Safety concerns need the appropriate operational response; they shouldn't wait for a marketing experiment or a commercial ranking exercise.

During participation, compare the experience with the reason someone bought. Our workshop attendee wanted practical help using their camera. If they spend the session watching demonstrations without an opportunity to practise, an easy checkout and a friendly welcome haven't fulfilled that promise. Record the specific gap and discuss it with the person who controls the session format.

Also record how someone gets help while they're there. They might need a quieter explanation, assistance finding a facility or clarification about what's included. Staff need a usable response and a clear escalation route. A map that ends every problem with "ask staff" hides whether those staff can answer or arrange the help the attendee needs.

Follow-up and return: distinguish interest from another purchase

Afterwards, the attendee may be waiting for promised materials, a receipt or a reply about a problem. Complete those obligations before treating every follow-up as another sales opportunity. For our workshop, a practice exercise sent after the session can help people use what they learned, provided it was part of the offer and someone owns sending it.

Ask about the moments you're investigating. A broad satisfaction question can start a conversation, but it won't tell you why the arrival instructions failed. Ask what happened when they reached the venue, then compare the answer with the message and staff account. Let people describe something you haven't anticipated, including a problem that wasn't on your original map.

A person saying they'd return is useful feedback. A later purchase is different evidence. Don't treat survey intentions as future revenue or assume everyone who enjoyed the workshop needs the same session again. Their next suitable event might teach a more advanced skill. The return stage should reflect that change in need rather than defaulting to a discount for the identical offer.

When you review returning attendees, define the opportunity they actually had to return. Someone cannot rebook a workshop you haven't offered again. Compare suitable events and allow for their selling periods. Keep claims modest when the numbers are small. You can learn whether your follow-up helped people find a relevant next session without promising that every improvement will produce repeat sales.

A worked example: a first-time photography workshop attendee

Here's how the template might read when it's filled in. This is an illustrative scenario, not a customer case study or measured result. Imagine a paid photography workshop where newcomers bring their own cameras, practise with an instructor and receive an exercise afterwards. The team wants to investigate confusion about preparation and arrival before promoting another edition.

At discovery, the attendee sees a tutor's announcement and opens the event page. Their task is to decide whether the workshop suits a beginner. In this hypothetical map, the announcement says "get comfortable with your camera", while the page assumes knowledge of manual settings. The evidence field would contain the actual messages and attendee accounts. Until collected, the proposed mismatch remains a hypothesis.

At consideration, they check what to bring and whether a friend can join. The map records camera requirements and ticket availability as separate questions. The proposed response is to clarify the starting skill level and required equipment before payment. The event owner first confirms the instructor can deliver the revised description. Copy changes follow that decision, rather than making a broader promise to sell more places.

At purchase, the attendee buys both places and receives a confirmation. The friend's preparation route depends on what the buyer shares. The map assigns the ticketing owner to test the available delivery and forwarding process, while the event owner checks the wording. The desired outcome is that each attendee can find the instructions and their valid ticket when needed.

At preparation, both people need charged cameras and the correct entrance. The map proposes a reminder with one consistent arrival description, checked against the venue's actual arrangements. At arrival, the venue contact confirms the courtyard door will be available and staff know the workshop name. These connected actions prevent the email from describing a route nobody has arranged to open.

During the workshop, the instructor checks whether newcomers can attempt the exercise with their own equipment. Afterwards, the event owner checks that the promised practice material reaches attendees and investigates unresolved questions. The team then reviews the original preparation and arrival problems using comparable evidence. Nothing in this example guarantees a sales increase. It shows who must do what before the next edition.

Turn the map into a manageable set of changes

Once you've filled the stages, resist assigning every issue the same priority. Separate immediate safety concerns and failures to deliver agreed arrangements from improvements you want to test. Then consider how many people appear affected, how serious the consequence is and how strong the evidence is. An uncertain problem may deserve investigation before it deserves a redesign.

Bring the responsible people into the discussion. Marketing can change an announcement, but it cannot confirm the venue entrance or invent time for practical instruction. The event owner may need to coordinate several changes. Put one named owner against that coordination and record the other people involved, so the task doesn't disappear between departments after the meeting.

GOV.UK's experience mapping guidance describes building the map from users' experiences and reviewing it with the team. Keep that working approach. When a colleague disagrees, ask which experience or record supports their view. Sometimes the disagreement reveals different attendee routes that your initial version combined too loosely.

Write an expected outcome for each change before implementing it. For the courtyard entrance, you might expect attendees to identify the correct door without contacting support. Check this through a fresh preparation test and observations at arrival. Email opens alone wouldn't answer that question. Choose evidence close enough to the problem that the team can judge whether it improved.

Keep commercial consequences proportionate. Support time, refunds and repeat purchases can matter, but avoid assigning a lost ticket sale to every confused visitor. You don't know that each person would otherwise have bought. Start with confirmed operational costs and observed behaviour, then state what remains uncertain. That gives you a defensible reason to act without inflating the business case.

Adapt the template when the event is new

If you're launching an event, you won't have a completed attendee journey to examine yet. Start with a proposed map and identify the decisions you can test before selling. Ask likely attendees to review the invitation and explain what they think the ticket includes. Test whether they can find the practical details. Don't describe this as evidence that they will buy or enjoy the event.

You can also examine the delivery with your team. Walk through the venue using the instructions you plan to send. Have someone outside the production team attempt the booking route. Check how a person reaches support and what happens if the normal contact is unavailable. These checks can identify missing arrangements, although staff rehearsals won't reproduce every condition of a busy event.

Keep the proposed experience separate from confirmed arrangements. If you intend to offer individual feedback during the workshop, establish how the instructor will provide it within the session. If that doesn't fit, change the format or the promise before tickets go on sale. The map is useful here because it connects a sentence in the invitation to the time and people required to deliver it.

After your first edition, replace assumptions with observed accounts wherever possible. Keep unresolved questions open for further investigation. You don't need to defend the original map as if it were a forecast you promised to meet. Its purpose is to help you learn what happens and decide what to improve, including when your initial idea about the audience turns out to be wrong.

Keep personal information out of the shared map

The map should explain a problem without becoming a copy of your customer records. You can describe a missed preparation message without pasting in someone's email address, order details or private request. Keep supporting records in the appropriate restricted system and refer to them in a way the authorised owner can check. Wider sharing doesn't require wider access to those details.

Be particularly careful when a specific story could identify someone within a small event. Changing the name may not conceal a distinctive situation. Summarise the operational issue for the shared version and limit the original account to the people who need it. If you seek permission to use an attendee's words publicly, treat that as a separate decision from asking about their experience privately.

Also avoid collecting personal information just to make the map look complete. You need to understand which arrangement failed and how to respond. You may not need to know why a person requires that arrangement. Ask the person responsible for your information handling to confirm how research notes should be stored and reviewed, particularly when you invite staff or external suppliers into the discussion.

Use a short review that produces a decision

Before the meeting, send the selected attendee description, the current map and the evidence for the problems you want to discuss. Ask each responsible person to check the part they control. That gives the venue contact time to establish which entrance was available and the ticketing owner time to test the confirmation, instead of asking everyone to speculate together.

During the review, follow the attendee's sequence and stop at the first unresolved problem that affects later stages. If the equipment requirement is wrong before purchase, improving the reminder alone leaves unsuitable bookings possible. Agree the purchase information first, then follow that decision through confirmation and preparation. This helps you avoid solving a downstream symptom while leaving its cause in the invitation.

Finish by recording the action, owner, completion condition and review point. An action can be an investigation when the evidence isn't sufficient. "Ask recent first-time buyers how they checked equipment requirements" is a legitimate next step. After the action, record what you learned and whether it changed the proposed response. You should leave with fewer unresolved decisions, not simply a more polished description of them.

Make the shared version useful to the people working on the day. They don't need every interview note, but they do need confirmed instructions and the person to contact when an exception occurs. For the workshop, that means knowing how to help someone who arrives at the wrong door or whose friend holds the booking. Check that this information reaches temporary staff as well as the permanent team before the next person arrives at the venue. Otherwise, you can complete the research, agree the right change and still leave the attendee explaining the whole problem again to someone who hasn't heard about it.

Keep the next edition connected to what you learned

Save the current map with its review date and the changes you've agreed. When an action is completed, update the evidence rather than replacing the original problem with an unsupported success claim. A reminder being edited proves the wording changed. Whether people can follow it needs a separate check, especially if the next event uses another room or entrance.

Before the next selling period, revisit anything the new edition changes. A different venue, ticket inclusion or audience can alter several stages at once. Reuse what still applies and investigate the new conditions. Your team should be able to find the latest confirmed instructions without searching through old maps or guessing which version belongs to the upcoming event.

Start your first map with one attendee group and one question that crosses responsibilities. For the workshop, that question is whether a first-time buyer and their friend can arrive prepared and begin the session they expected. Bring the actual invitation, booking confirmation and arrival instructions to the review. Then agree who will resolve the first confirmed problem before the next attendee encounters it.