How to build an attendee research panel for a recurring event

You ask your regulars what they want next year. They want longer sessions, more networking and an evening reception. Then you speak to someone who came once and didn't return. They liked the sessions, but leaving work early and getting home late made the whole day difficult. If you only keep asking the people who keep coming, you'll miss part of the explanation for who stops buying.

An attendee research panel gives you a group you can return to as you plan and improve a recurring event. Recruit people with different relationships to the event, explain the commitment, pay fairly for their time and make it easy to decline. Keep enough returning participants to understand their changing experience, while bringing in fresh people so your research doesn't depend entirely on your most familiar customers.

The panel helps you understand decisions and test proposed changes. It doesn't give a small group authority to speak for everyone who might buy a ticket. Here's how to set one up, keep participation manageable and use the findings without confusing thoughtful feedback with a sales forecast.

Start with the decisions you keep having to make

The first thing you want to do is look beyond the next survey. What do you need to understand repeatedly across your event series? Perhaps first-time visitors struggle to choose sessions, returning customers question whether the programme offers enough new material, or people stop attending when their employer changes its training budget.

A panel makes sense when continuity helps answer the question. You can ask someone what they expected before an edition, speak to them afterwards and revisit the decision when the next event goes on sale. Their earlier explanation gives you context that a fresh satisfaction score wouldn't provide. You still have to check what happened between those conversations.

Imagine a business running a paid professional conference twice a year. Its team is considering a later start, shorter talks and an optional evening activity. These changes affect different people differently. A local attendee may welcome an evening reception. Someone travelling home may prefer an earlier finish. An employer paying for a ticket may care most about the practical learning available during working hours.

Those are useful panel questions because the team has choices to make across several editions. Write the choices down, with the person responsible and the deadline. If the venue contract fixes the opening time before your first discussion, be honest about that. Explore the next edition rather than suggesting participants can change an agreement you've already signed.

Also decide what would be enough to act. Confusion about a session description might justify a wording change after a few clear examples. A proposal to add an expensive evening programme needs delivery costs and evidence about bookings as well. The amount of research should fit the commitment you're considering.

If you only need preferences from people already booked for next week, a panel may create unnecessary administration. Our guide to pre-event survey questions covers that immediate task. Use a panel when returning to the same people will help you understand a continuing problem, and when someone in the business has time to maintain the relationship.

Be clear about what membership means

A research panel is a group of people who have agreed that you may invite them to research over a stated period. Membership doesn't mean they must complete every activity. It also doesn't mean all members meet together. You might use private interviews, short questionnaires or individual tests of a proposed programme page, depending on the question.

For the fictional conference, suppose you recruit twenty-four adults for a six-month pilot. You expect to invite each person to two short activities, with some invited to an additional interview. These numbers are a proposed working arrangement for this example, not a standard panel size. Choose your own scale from the questions, participant availability, analysis time and budget.

Explain the difference between joining and taking part. Someone may agree to receive invitations but decline a call during a busy week. That's compatible with membership. If you require a specific repeated activity for one study, explain that commitment separately and give the person a genuine choice about it.

Keep research separate from event governance. Panel members can explain why a timetable works poorly for them. They don't approve your safety plan, direct staff or promise attendance on behalf of their employer. Your team remains responsible for the programme and the commercial decision. Avoid titles that imply powers you don't intend to give.

The distinction matters when participants ask what happened to a suggestion. You should be able to explain the decision and acknowledge their contribution without implying that every request will be implemented. A panel whose members expect to control the programme will become frustrating for everyone when suggestions conflict.

Write a short membership agreement in ordinary language. State the pilot period, likely activities, expected contact frequency, payment arrangements, privacy information, contact person and exit route. Say whether members will ever meet one another. Don't launch a public discussion group by default when private participation would answer your questions with fewer demands on members.

Recruit across customer circumstances

Start with the people whose experience you need to understand. Purchase history is useful, but it isn't the whole picture. A person who buys a team booking may never attend. Someone attending on a colleague's ticket may know your event well without appearing as a repeat buyer. Check which role matters to each research question.

For our conference pilot, you could recruit eight repeat attendees at the latest edition, eight people who attended for the first time at that edition and eight previous attendees who didn't return for that edition. These are mutually exclusive recruitment groups for the example. The equal allocation makes room to investigate each experience; it doesn't claim the event's audience is divided equally between them.

Within those groups, look for relevant differences. Include people travelling different distances, people paying personally and people needing employer approval, and people attending alone or with colleagues. You won't cover every combination in twenty-four places. Record the gaps so the programme team can see whose circumstances remain unexplored.

GOV.UK's guidance on finding research participants recommends recruiting actual or likely users and varying recruitment approaches to reduce exclusions. For an event business, that means checking whether your invitation only reaches the people most comfortable with your current format. An evening video call can exclude someone whose difficulty with the event is already lack of time outside work.

Recruit through suitable routes rather than relying only on an enthusiastic social post. Where contact is permitted, invite people from relevant past-attendee groups. You could also ask a professional association to circulate an invitation. Keep track of the route, because several names supplied by one well-connected member may share experiences you haven't recognised.

People who considered your event but never attended can help explain a different problem. Recruit them for relevant studies as a clearly identified group, rather than quietly counting them as attendees. If you want to learn about a new city or an unfamiliar profession, you may need research beyond the panel entirely. Existing customers can't explain every audience you're hoping to reach.

Screen for relevance without recruiting approval

Keep the screening questions short and tied to the study. Ask which edition someone attended, whether they chose or paid for their ticket, how they travelled and what happened when they considered returning. Use the answer only where it helps selection or planning. You don't need their entire professional history to understand a conference booking.

Avoid questions that advertise the opinion you want. "Would you like to help us create an even better conference?" makes enthusiasm sound like the entry requirement. "We're researching how people decide whether to attend our conference again" gives someone more room to describe disappointment, indifference or a practical barrier.

Ask about connections that could affect the discussion. Staff, speakers, sponsors and close friends of the organising team may have useful views, but their incentives differ from an ordinary attendee's. Keep those roles visible. If a sponsor employee joins as a ticket buyer, decide whether that relationship makes them suitable for the particular activity.

Set selection rules before reading the most flattering applications. Otherwise, articulate regulars can crowd out quieter people whose answers take more effort to understand. Choose for the experience the person can explain. Being good at writing an application is rarely the quality you're researching.

Allow more than one way to express interest if the audience needs it. A short phone conversation or an accessible form may reach someone who can't comfortably complete your default process. Confirm practical adjustments privately. Asking what would help a person participate is more useful than requiring a diagnosis as a condition of joining.

Verify eligibility proportionately. If the person says they attended an edition, a permitted check against the relevant record may resolve it. Don't demand identity documents or publish the screening rules in a way that encourages invented answers. If a response is inconsistent, ask a neutral clarification before deciding it is dishonest.

Tell unsuccessful applicants what happens to their information. You might ask whether they want to hear about a future opening, but don't keep them indefinitely because recruitment was difficult. A waiting list needs a purpose, an explained retention period and someone responsible for it. Joining that list should remain a choice.

Write an invitation people can judge

The invitation should let someone understand the actual commitment before they accept. Describe who is running the panel, why you're forming it and the kinds of activities you may offer. Give the pilot period, likely frequency, expected duration, compensation and the arrangements for declining or leaving. Provide privacy information and a real contact route.

Here's wording you could adapt for the fictional conference. "We're inviting adults who have attended our conference to help us understand decisions about returning. During a six-month pilot, we'd like to invite you to two activities of about fifteen minutes each. Some members will also be invited to a forty-five-minute interview. Each invitation will explain the activity and payment before you decide."

Continue with the conditions that matter. "You can decline an activity or leave the panel. Your decision won't affect your event booking, customer support or future invitations to buy tickets. We welcome critical feedback, and payment doesn't depend on agreeing with our plans." Add your actual payment amounts, payment timing and participant-information link before sending it.

GOV.UK's informed-consent guidance for research explains the importance of telling people what will happen, what will be collected and how the results will be used. Treat this as research practice. Your organisation must also establish the privacy arrangements and legal basis that apply where you and the participants operate. Joining the research does not, by itself, authorise every use of a participant's personal data.

Get agreement for each activity as well as membership. A person who accepted short written tasks hasn't necessarily agreed to a recorded interview with observers. Explain recording separately, say who can see it and offer an appropriate alternative where possible. Don't describe identifiable repeated research as anonymous just because you use participant numbers in the report.

Keep permission to publish quotes separate too. A useful private comment isn't automatically an endorsement you can put in a sales email. If you later ask to publish it, show the wording, attribution and intended use so the participant can judge that request. A refusal should not jeopardise a payment they have earned.

A pilot brief your team can adapt

Before opening applications, put the working arrangement in one brief that the researcher and event owner can both approve. It doesn't need to be a long document. It needs to settle the decisions that otherwise get improvised when someone asks for another interview or a participant wants to know when they'll be paid.

For the fictional conference, the research purpose could read, "Understand how recent first-time, returning and lapsed attendees decide whether to attend another edition, and test programme information while we can still change it." That statement keeps the work focused. A request to review a sponsor's unrelated product would need a separate justification and participant agreement.

Describe recruitment next. "Recruit twenty-four adult past attendees, with eight in each stated attendance group. Record relevant travel and payment circumstances, recruit through more than one appropriate route and flag gaps before filling places." Add the event editions that define eligibility in your actual brief. Otherwise two colleagues may use different meanings of a lapsed attendee.

State the activity allowance. "Offer two activities of about fifteen minutes to each member during the six-month pilot. Invite twelve members to an additional forty-five-minute interview where their experience fits the question. Explain each activity before acceptance. Check the burden before adding further contact." The twelve interviews are additional to the short activities, so both the budget and invitation must say so.

Name the people doing the work. One person manages recruitment, scheduling and payments. A researcher prepares activities and reviews findings. The programme owner decides what can change and approves any resulting spend. One employee may hold several roles in a small business, but those responsibilities still require time in the plan.

Give each activity a decision deadline and an output. The first task might produce a summary of returning-attendance barriers for the programme owner before the next edition is specified. A session-description test might produce the misunderstandings to correct before descriptions go live. Specify the material participants will see so an enthusiastic colleague doesn't add an unplanned sales presentation.

Finally, record the budget, permission process, approved tools and review date. Include what happens if recruitment leaves a group missing, support costs exceed the allowance or the relevant decision closes early. The sensible response may be to narrow the study or delay it. Filling empty places with easy-to-reach regulars changes the research question and should be an explicit decision.

Pay for time and make the budget honest

For a commercial recurring panel, budget to compensate people for the work you're asking them to do. A busy attendee shouldn't have to provide repeated unpaid consulting because they like your conference. Choose an amount and payment method appropriate to the task and audience, and check any restrictions affecting the people you recruit.

The Department for Education's guidance on research incentives discusses repeated effort, participation costs and risks that incentives can introduce. It governs its own research setting, rather than setting commercial event rates. The practical question for you is whether the arrangement recognises the burden while leaving people comfortable declining and disagreeing.

A discount on a future ticket is a poor default for this panel. It requires someone to remain a customer to receive its value, which is especially awkward when you're asking why people stopped attending. A suitable payment that doesn't require another purchase gives lapsed attendees a clearer reason to participate on equal terms.

Use a published schedule based on activity and effort. Agree any reasonable travel or access costs separately. Tell people when they'll be paid, what happens if you cancel and how partial participation is handled. Don't make the final payment depend on completing every activity across the whole membership period. That creates unnecessary pressure to continue.

For our fictional pilot, all the following amounts are illustrative USD planning figures, not research market rates. Twenty-four members completing two short activities at $20 per activity would cost $960. Twelve additional interviews at $35 each would cost $420. The planned participant-payment allowance is therefore $1,380 if all those activities take place.

Allow another $960 for twenty-four staff hours at an internal rate of $40 an hour that includes pay and associated employment costs. Twelve forty-five-minute interviews use nine of those hours, leaving fifteen for recruitment, preparation, administration and analysis. Check that your own team can do the work within the time you allow. Add a separate $360 allowance for the recruitment, access support and payment-processing costs assumed in this example. That makes a total planned resource cost of $2,700. Confirm actual support needs and supplier quotes before treating that allowance as sufficient.

The $960 staff allocation may already be covered by salaries. In that case, distinguish it from new cash leaving the bank account and don't add the same salary expense twice in your event accounts. It still represents work you need capacity to do. Record actual payments, staff time and other costs separately so you can decide whether to continue after the pilot.

Plan the research around the event calendar

Work backwards from decisions and supplier commitments. If you want feedback on a proposed timetable, collect it before the programme is approved and the room bookings become difficult to change. If you want to understand the arrival experience, ask while people can still recall what happened, then use the findings before the next edition's instructions are written.

Avoid turning membership into a constant stream of small requests. A programme colleague may see twenty-four helpful contacts and ask for a quick opinion on every draft. Those interruptions still consume time and can exceed the commitment people accepted. Have one panel owner approve invitations and track the total burden across the business.

For the conference pilot, the first short activity might ask members to describe their most recent decision about returning. A later activity could test how they interpret two proposed session descriptions. Twelve members could be invited to separate interviews where their circumstances need more exploration. Each activity needs its own reason; you aren't obliged to fill the calendar just because you recruited a panel.

When you do need repeated measurement, design it deliberately. Keep the core question and answer options consistent if you want to compare answers over time. Record what participants saw and when. If you change the question halfway through, you may learn something useful, but you can no longer assume the answers measure the same thing.

Select members for interviews based on the question. If you're studying employer approval, recruit people who have recently navigated that process. Don't automatically interview whoever replies fastest. Rotate invitations where several members are equally relevant so a small enthusiastic subset doesn't complete all the work and dominate the evidence.

Give people a clear deadline and reasonable ways to respond. If you can't accommodate their schedule, note the missing circumstance in the findings. Don't silently replace a travelling attendee with a local regular and then report that all the relevant perspectives were covered. Recruitment convenience needs to stay visible when you interpret the result.

Keep the contact list and research records useful

You'll need a small amount of information to manage the panel reliably. A membership record can hold the participant code, contact route, recruitment group, permission status, activities offered, activities completed, payments and review date. Keep notes about what the person said in an appropriate research record rather than spreading them across informal team messages.

GOV.UK's guidance on research data and participant privacy recommends collecting only what is needed, limiting access and deleting details when they are no longer required. For this panel, decide who handles contact details and payments, who reads identifiable notes and what the programming team actually needs to see. Confirm the applicable privacy requirements with the person responsible in your business.

Using codes can help reduce unnecessary exposure, but it doesn't make linked records anonymous. If a code connects an interview to a named member, someone with access to the key can identify them. Store that key with suitable restrictions and explain the setup accurately. Don't promise anonymity that your own follow-up process makes impossible.

Set retention dates by record type and purpose. A payment record may need different handling from a recording or recruitment application. Explain what happens when someone leaves, including how you handle future contact, material already used and any request concerning their data. Have a process you can actually carry out rather than promising that every trace can disappear instantly.

For invitations to eligible contacts, Loopyah's attendee email tools let you select audiences using purchase information and include a link to your external panel sign-up form. Check that the proposed contact is appropriate and permitted. Your separate research process still needs to manage membership, participation agreement, responses and payments. Don't assume a ticket buyer represents everyone on their booking.

Keep general promotions separate from panel administration. A member leaving the panel is asking you to stop the relevant research contact; a person opting out of marketing has made a different choice that also needs respect. Record the choices accurately in the systems handling each type of communication. Don't classify a recruitment pitch as an essential booking update to reach people who wouldn't otherwise receive it.

Listen without teaching members the answers

Continuity is useful because you can return to an earlier explanation. It also means members may learn your terminology and become familiar with the team's preferred ideas. A person who has reviewed the programme several times may understand a vague session title that a new customer would find confusing. Keep track of what you've already shown them.

Before testing new wording, decide whether you need a first impression or an informed reaction. For a first impression, use people who haven't seen the draft, including fresh participants outside the panel where necessary. For an informed reaction, earlier exposure may be useful. The important thing is knowing which question the activity answers.

Ask people to describe a recent decision before showing a long list of possible explanations. For example, "Tell me what happened when you considered booking the latest edition" leaves space for a reason you didn't anticipate. A question asking whether the programme was too expensive, too long or too advanced may confine the answer to your own assumptions.

When members suggest a change, explore the problem it would solve. Someone asking for more networking may have struggled to start a conversation at the last edition. Adding another hour could make their journey home worse without improving introductions. Ask about the actual moment, who was involved and what would have helped them participate.

A group activity requires care because members may begin to recognise and defer to each other. Let people record an initial response privately before discussion. Offer individual participation for subjects they may not want to discuss together. You don't need every panel member in a shared chat to benefit from having an ongoing panel.

Don't reward agreement through your reactions. If criticism gets a defensive explanation and praise gets an enthusiastic thank-you, people can learn which answer makes the conversation easier. A facilitator should be able to ask a genuine follow-up without protecting the programme team's favourite idea. Your aim is to understand the response before deciding what to do about it.

Handle missed activities and disagreement consistently

Decide your reminder approach before the first activity. For this pilot, you could send the invitation and one reminder, then close the activity on the stated date. That's a proposed contact rule, not a research standard. Choose a pattern appropriate to your audience and tell members what to expect. A personal chase from several colleagues defeats the purpose of having one panel owner.

If someone misses an interview, contact them privately to check whether they want to reschedule. Don't infer that their event feedback will be unreliable or threaten their customer benefits. Repeated scheduling problems may justify pausing invitations after a clear conversation, but the record should describe what happened rather than label the person difficult.

Apply the agreed payment rules when the problem is yours. If the interviewer fails to attend or the test materials don't work, participants shouldn't have to negotiate from scratch to have their time recognised. Record the incident, resolve the payment and fix the process before issuing the next invitation. Keep a route for a member to raise a concern with someone other than the person conducting their interview.

Distinguish critical feedback from harmful conduct. A member saying your conference was poor value is providing relevant research, even if the wording is blunt. Sharing another member's personal information or harassing someone requires a response under clearly explained participation rules. If you end membership for conduct, document the reason and settle outstanding payments according to the agreement. Don't use conduct rules to remove people whose views are inconvenient.

Some requests need a different route immediately. An unresolved refund or access complaint should reach the responsible service team rather than wait for the next research report. Ask before transferring identifying details, explain the next step and keep the research decision separate. Participation mustn't become the only way a dissatisfied attendee can get ordinary customer support.

Compare the same people before claiming a change

Suppose all twenty-four members answer a question before an edition, but only eighteen answer it afterwards. An overall shift might reflect changed opinions, different people responding or both. Start by checking who answered each time. A new total alone can't tell you which explanation fits.

For a separate repeated-question example, imagine asking about a later finishing time in both rounds. In the first round, twelve of twenty-four respondents prefer the later finish. In the second, ten of eighteen prefer it. You might see the second result and think support has grown as a share of replies. But the six missing respondents all preferred the later finish in the first round.

Among the eighteen people who answered both times, the count preferring the later finish therefore changed from six to ten. That is a change within those eighteen respondents. It still doesn't establish what the six absent members now think, or what the wider audience would choose. Keep the matched comparison and the full-round counts distinguishable.

Look at the individual explanations as well. Did someone change because the event overran, because their work schedule changed or because they interpreted the question differently? A count can help locate the change. The explanation tells you what you might do about it. Don't assume that every movement came from an improvement or mistake your team made.

Record missing answers as missing. Declining an activity doesn't mean someone dislikes the proposed programme, and continuing to answer doesn't prove satisfaction with the event. If you ask why someone stopped participating, keep that follow-up optional and limited. Repeatedly chasing a departing member would contradict the low-pressure arrangement you offered.

When you write up the results, the American Association for Public Opinion Research's disclosure standards provide a useful reference. They ask researchers to explain how participants were selected, including whether they volunteered, and to state methods, sample sizes and limitations. Describe your panel as the voluntary, deliberately recruited group it is. Don't add a survey margin of error that assumes a randomly selected sample, or present equal recruitment groups as a representative audience sample.

Our guide to event survey sample size explains why counting more replies doesn't automatically solve a recruitment problem. Use the panel's continuity to understand these members' experience. Use an appropriate separate research design when your decision requires a population estimate.

Refresh membership without losing the history

Give membership a planned review date. At the end of the pilot, ask whether the group still helps answer the questions your event business faces. Some members may want to continue. Others may no longer be relevant to the studies or may need a break. Neither outcome needs to be treated as a problem with the person.

Refresh for a reason. You might need first-time perspectives after everyone in the original group has attended again. You may need more people paying personally after recruiting heavily through employers. Or the event may have changed enough that new audience groups matter. Write down the gap before deciding whom to recruit next.

Keep membership history rather than relabelling people to preserve neat categories. A first-time attendee becomes a returning attendee after another edition. A lapsed attendee may buy again. That change can be valuable to understand, so retain the original recruitment group and record the current relationship separately where appropriate. Don't overwrite the past and then wonder why your comparison no longer makes sense.

New members need a clear introduction without being told what earlier members think. Explain the research arrangement, event context and activity they are joining. If you send them a report containing the previous group's favourite solution before asking their first reaction, you've changed what that reaction can tell you.

When reporting a new round, state how many participants are continuing members and how many are new. Analyse changes among continuing respondents separately from differences involving replacements. A fresh participant cannot supply a missing before-and-after answer for someone who left. They contribute a different perspective, which has value on its own terms.

Don't promise a permanent place merely to make recruitment easier. A pilot with a defined end is easier to explain honestly, budget and improve. If the panel continues, offer a new term with the relevant commitments and privacy information. People should be able to finish the original agreement without feeling they've abandoned your event.

Turn findings into an event decision

After each activity, write what happened, what you think it means and what action you're proposing. Keep those statements distinguishable. "Several interviewed members could not explain the workshop level" records an observation. "The description needs a clearer statement of prior knowledge" is a proposed response that the programming team can check.

Use participant explanations to understand differences. A frequent attendee asking for advanced material and a first-time attendee asking for simpler descriptions may both be reasonable. You might need clearer session levels or separate sessions, rather than an average programme that satisfies neither. Our guide to analysing open-ended event feedback covers how to group comments while preserving the exceptions that affect a decision.

For the fictional conference, imagine the research suggests that people want introductions earlier in the day because they struggle to approach strangers during an unstructured evening. The team could test a short hosted introduction within the existing programme before committing to a longer reception. Cost the staff time and check the effect on sessions already advertised.

Be careful about how you evaluate the test. If you change the welcome, programme, ticket price and marketing at once, a different booking result won't isolate the effect of introductions. You can still learn whether the delivery worked and what attendees experienced. Just describe the uncertainty honestly when deciding which changes to keep.

A panel can also help explain an apparent sales problem. Members may reveal that an employer approval deadline comes before you release enough programme detail. That suggests an earlier information schedule worth testing. It doesn't prove the revised schedule will sell a particular number of tickets. Our guide to researching willingness to pay for an event covers the separate evidence needed for pricing decisions.

Close the loop with participants using a short account of what you considered and what happens next. Say which change you plan to test, which suggestion isn't feasible and what remains undecided. Avoid naming members or revealing personal circumstances in a group update. People can see that you listened without receiving one another's private explanations.

Before renewing the panel, review its own usefulness. Which decisions changed, what did you learn that existing sales records couldn't explain, and how much work did participation require? Review actual participant payments, staff time and other costs against your approved budget, including any work that exceeded the original allowance. Stop or simplify activities whose answers never reach a decision.

For your first panel, choose one recurring uncertainty, a responsible researcher and a funded pilot period. Write the membership invitation and recruitment groups before you contact anyone. Once you can explain who you need to hear from, what you'll ask and how the answer could change the next edition, you're ready to recruit.