# Planning an event and where Happenee helps

> A map of event planning from the first intent to the next edition, and the points where it turns into setup and evaluation in Happenee.

- Canonical article (Help Center): https://help.happenee.com/en/articles/100-planning-an-event-and-where-happenee-helps
- Česká verze: https://aidocs.happenee.com/cs/planovani-udalosti-a-kde-pomuze-happenee.md
- Collection: Event Sherpa
- Updated: 2026-11-05

---

> **Overview**
> This article is a map of event planning from the first intent to the next edition. It shows which decisions stay with you and your suppliers and which of them turn into setup and evaluation in Happenee. It is not a planning guide. You can start the setup even when half of the answers are still missing; keep what you do not know as an open question.

## Getting started

1. **Name the goal for each side.** What the organizer should get from the event, what the attendee should get, and at an external event what the partner or sponsor should get. Also settle whether the event is mainly about people meeting, about content, or about business with partners; everything else is ordered by that answer. Add how you will recognize success and where you will read it afterward: attendee feedback needs a **Survey**, while the number and outcome of meetings need an agreed source other than scans.
2. **Decide who you will answer to for the result.** At an internal event, leadership, HR, internal communications, sales, finance, and IT all sit behind you as internal stakeholders, and each of them measures something different. The recipient of the report decides what is worth collecting during registration.
3. **Settle the relationship between the audience and the organizer.** Employees, external guests, or both. That answer decides the admission price, consents, groups, and content visibility.
4. **List what is already running and what stays with you.** Registration, ticketing, a CRM, e-mailing, or your own website each have an administrator and an authoritative list of people. The venue, catering, production, and suppliers stay with you; Happenee only needs whatever affects the setup.
5. **Write down what you still do not know.** A missing date, an unapproved budget, or an unfinished agenda are working assumptions. Mark them as assumptions and come back to them once they are settled.

## Details

### Start from the goal, not from the features

The goal is usually in someone's head and rarely on paper. During preparation, operational tasks surface first: handle workshop registration, check guests in without a queue, get invitations to everyone. From each of them you reach the goal by asking what each side gets out of it.

Break the goal down by side, because each side wants something different and each one shows up somewhere else in the setup:

- **The organizer** wants the event to run without a mistake and to be defensible afterward. In Happenee that turns into what you watch in **Statistics** as you go, and what you pass on as an export.
- **The attendee** wants to choose a workshop or a table, receive the right information about transport, accommodation, and the agenda for their group, and easily find where to go. Part of their goal is the impression they should leave with. Ask what they expect from the event in the Registration form and ask the same in the **Survey** afterward; that gives you a comparison of expectation and result.
- **The partner or sponsor** wants conversations instead of scans, visibility in the Agenda and the app, and measurable interaction. Give them a place in the **Agenda** and a profile in the app, and agree on what they receive in the export afterward.
- **The exhibitor** also deals with their own invitations and quotas and with working on contacts after the event. A representative at the booth and a company profile are two different things. A profile without a person present does not produce a meeting.
- **The speaker** has goals derived from the organizer's, and the surest route is to ask them directly. At a conference with a call for papers, the author of a submitted paper is not an approved speaker or a registered attendee; only the approved result belongs in **Speakers**.

### From the goal to the setup and to the evaluation

Each side's goal has a place in the Happenee setup and, after the event, a place it can be read from. The most common pairs:

- **The attendee wants to meet relevant people and arrange meetings.** Set up **Networking** with profiles and meeting reservations; customer support sets up the meeting locations, so agree on them in advance. After the event you export the meetings (who booked a meeting with whom and when) and the list of saved contacts from administration; a badge scan is not a meeting that took place.
- **The attendee wants to choose a workshop or a table.** Set up workshops with a capacity and session registration in the **Agenda**; assigning a group on registration lets you target communication. After the event you see the occupancy and who signed up for what.
- **The attendee wants the right information for their group.** Set up groups and content visibility and target campaigns and Notifications by group and status. After each campaign you read the delivery status: delivered, read, undelivered.
- **The internal stakeholder wants people to understand the message and take part.** Set up **Polls** and **Questions** alongside the agenda. After the event you have the poll results in Excel and the queue of questions that came in.
- **The partner or sponsor wants to be visible and to have conversations instead of scans.** Give them a category in **Sponsors** shown on the home page and with sessions in the **Agenda**. Their people take part in Networking as ordinary attendees. After the event you prepare the agreed extract for their people from the meetings and saved-contacts exports.
- **The exhibitor wants visitors to reach the booth and wants someone to follow up with.** Set up **Exhibitors** with representatives and the booth as a meeting location. After the event the scan statistics export (who scanned whom and when) and the booth meetings are available.
- **The organizer wants feedback.** Prepare a **Survey** before the event and send a Notification or a campaign pointing to it at the right moment. After the event you download the answers in Excel.
- **The organizer has to show who came.** Read the statuses from invitation through registration to attendance in **Statistics**, and send colleagues without access an export.

Where a side's goal is missing from this list, the place to read it from after the event is usually missing too. That is the reason to agree on it before registration opens.

### Internal, external, or both audiences

The relationship between the audience and the organizer runs through every event type. With an **internal audience**, meaning employees or your own sales network, you do not deal with an admission price or return on sales as long as no third party pays for attendance. You deal with the internal stakeholder who commissioned the event and with what people should do differently after the meeting. Expect part of the audience to be out of the office or on a shift, possibly without a company mailbox or device. An invitation cannot rest on that, and the route to the content has to work from a browser.

With an **external audience**, meaning clients, partners, and the public, you add price, admission types, consent to share a contact, and the question of who takes over contacts afterward. Partners and sponsors are parties with their own goal and their own commercial next step; account for them when you design the agenda and the outputs, not on the day itself.

When **both audiences** come together, both branches apply at once and do not merge into one. Groups and content visibility tell them apart, so neither side needs to be left out of the setup.

### What is decided outside Happenee

The venue, the budget, and any tender stay with you. Of these decisions, Happenee needs only what affects the setup:

- **Who pays for the event.** Does the attendee pay, the company, or a partner? This decides whether you set up **Tickets** and orders at all.
- **The date and venue.** Is the date known, what is the capacity, how many entrances, halls, and zones the space has, and what connectivity is available on site? That shapes your check-in places and the fallback for a network outage.
- **The agenda and content.** When does the agenda close, who approves it, is there one stream or several, and do workshops, tables, and slots have their own capacity? This decides when it makes sense to open session registration.
- **Accommodation and transport.** Are people told by group who stays where and how they travel? Then you need groups and visibility before you start sending anything. You contract accommodation and transport with your suppliers; you prepare the handover for the accommodation provider manually from an export.
- **Suppliers and systems.** Is an agency involved, and which tools are already running: registration, ticketing, a CRM, e-mailing, your own app? Do not replace a working tool before the data and access handover is ready.

The same holds for the event day: staff at the entrance, catering, technology in the hall, and decisions about exceptions stay with you. How these answers turn into a specific setup is covered by the recommended setups for each event type.

### What can be read afterward, and what cannot

You usually have to show the result to someone else, and soon. Without an agreed measure you reach for whatever is at hand, meaning the number of registrations or the impression from the room. That is why it pays to agree on the criterion at the start. The data that would support it can only be collected in advance.

The two most common criteria are attendee feedback after the event, and the number and success of meetings together with commercial indicators. The first needs a **Survey** prepared before the event; the second needs a source agreed with the partner, such as their record of the meetings that took place.

When you read the numbers, keep the quantities apart. An order, a registration, a check-in, a reservation, and recorded engagement in the app are different things, and a missing record is not zero attendance. With registration with additional information, for example, the order is created before the registration, and the gap between tickets sold and attendees registered is a work queue, not an error.

A report therefore needs a scope, a unit, a period, a denominator, excluded test records, and a recipient. Only then can it be compared with what you promised. Colleagues and partners without admin access get an export from **Statistics** → **Exports**. **Agree on the report format with your partner before the event.** Once it is clear what will be sent and to whom, everyone knows what has to be collected, and no argument about the denominator comes up afterward.

### The next edition or a follow-up event

After the last day, people return to materials, recordings, and contacts, and they continue with another event in the same environment as long as their access lasts. Keep the promised materials available for the agreed access period and tell attendees before that period ends.

For a repeat event, how many invitees are new and how many are returning usually matters more than what type of event it is. Treat a copy of last year's setup as the start of a check. Before you use it, verify dates, contacts, permissions, and the scope of your license. Last year's guests are not this year's confirmed attendees.

### How to tell which moment you are in

Where you stand in planning shows in what you already have and what is still missing. It changes what to start with, not whether you can start:

- **Intent only:** there is no date and no venue. Clarify the goal for each side and sketch the setup only in outline; the specific configuration follows once the date and venue exist.
- **A known date or venue:** the agenda is still coming together. You can plan the setup in full and keep open items as assumptions.
- **Preparation is under way:** invitations went out and registration or communication is being handled. Start from what is already running instead of building it again from scratch.
- **Shortly before the event:** the date is weeks away. Concentrate on check-in and operations, and note the rest for next time.
- **After the event:** concentrate on evaluation, bringing people back to the content, and the next event.

## Common pitfalls

### An operational task is mistaken for the event goal

"Handle workshop registration" says what must not break, not what the event should achieve. For each operational task, ask what the attendee and the internal stakeholder get out of it. Otherwise you set up features with nothing to evaluate them against after the event.

### The success criterion is looked for after the event

Nobody defines it afterward, and the data that would support it is collected in advance. When no criterion was named, that is the first thing to clarify, not a reason to postpone the setup. The target number has to come from the internal stakeholder; do not estimate it for them or promise a guaranteed benefit.

### The report promises more than the recorded data shows

Neither a badge scan nor a reservation proves that a meeting took place, and a missing record does not mean zero attendance. Before you promise results to anyone, define the quantities, their source, and the period.

### The plan gets filled in with things nobody decided

Leave what you do not know yet empty and mark it as open. Mark a working assumption as an assumption so that nobody reads it as a decision. Add to the registration form only the details someone will actually use after the event.

## Related articles

- [Must-have, optional, and advanced features and modules by event type](https://aidocs.happenee.com/en/must-have-optional-and-advanced-features-and-modules-by-event-type.md)
- [Minimum recommended setup for small, medium, and larger events](https://aidocs.happenee.com/en/minimum-recommended-setup-for-small-medium-and-larger-events.md)
- [Recommended order for setting up an event step by step](https://aidocs.happenee.com/en/recommended-order-for-setting-up-an-event-step-by-step.md)
- [Recommended setup for an internal corporate event](https://aidocs.happenee.com/en/recommended-setup-for-an-internal-corporate-event.md)
- [Recommended setup for an external client event](https://aidocs.happenee.com/en/recommended-setup-for-an-external-client-event.md)
- [Recommended setup for a conference](https://aidocs.happenee.com/en/recommended-setup-for-a-conference.md)
- [Interpreting attendee statistics](https://aidocs.happenee.com/en/interpreting-attendee-statistics.md)