How to organise a paid symposium around one specialist question

You have a question that keeps coming up in your field. Different specialists have pieces of the answer, the published evidence doesn't quite agree, and people would pay to spend a day working through it with the right people. That's a good starting point for a symposium. A long list of speakers is a much weaker one.

To organise a paid symposium, define the question first, then choose the evidence, contributors and discussion format needed to examine it properly. Build a ticket offer around what participants will understand or be able to decide afterwards, and cost the preparation and follow-up as carefully as the day itself.

The difference matters commercially. A specialist audience can watch presentations elsewhere. You're asking them to pay for a programme that connects those presentations, tests the conclusions and gives them access to a discussion they couldn't easily arrange themselves.

We'll work through an illustrative symposium for people deciding how to evaluate reusable food packaging in their organisations. The subject is an example, not technical guidance about packaging. It lets us connect the programme, the people in the room, the ticket price and the written outcome without pretending every symposium needs the same agenda.

Choose a question you can actually examine

"The future of sustainable packaging" gives you plenty of potential speakers. It gives a buyer little help deciding whether to come. Someone comparing procurement options needs a different discussion from someone researching materials or running a washing facility.

A more useful starting question is, "What evidence should a procurement team require before adopting reusable food packaging?" Now you can identify the participants, decide which evidence belongs in the programme and explain what the day is for. You can also say what it won't cover.

Write a short scope statement before approaching speakers. Identify the decision, the people making it, the settings you will discuss and the boundaries of the available evidence. For our example, you might focus on workplace catering rather than every possible food service setting. That keeps delegates with very different operating conditions from talking past each other.

Next, divide the main question into questions the programme can answer. What outcomes matter? Which comparisons are credible? Where do local conditions change the result? What would a buyer need to investigate before applying a finding? Each question should lead to a useful contribution or a genuine discussion, rather than another general introduction.

The UK Government Office for Science's roundtable planning guidance recommends agreeing what evidence or degree of agreement the meeting is intended to produce and testing the questions with relevant experts. Although written for policy teams, that advice is useful here. Your question needs testing before you sell a day devoted to it.

Show the scope to prospective delegates as well as specialists. Ask which decision they are trying to make and what currently stops them. If several describe a more urgent question, investigate that before announcing the programme. If they want individual consultancy on confidential projects, a public symposium may be the wrong offer.

A useful scope test is to complete this sentence: "This day helps this particular group decide what to investigate before doing this particular thing." If you can't complete it without listing several unrelated audiences, narrow the programme. You can still welcome observers, but don't let their interests quietly change what the main audience is buying.

For example, a materials researcher may want to compare measurement methods, while a catering buyer wants to know what those measurements mean for a purchasing decision. Both can contribute to our symposium if the programme explicitly connects the methods to that decision. If the connection requires an entirely separate introduction, you may need a different event for one of those audiences.

Make the paid offer specific

A symposium doesn't have to reach a final answer to be worth paying for. It can help participants understand why findings differ, recognise an unsuitable comparison or prepare better questions for a supplier. Those are credible outcomes when the underlying subject is unsettled.

What you should avoid is selling certainty the programme cannot deliver. "Find the best packaging system" overpromises if performance depends on local collection, transport and use. "Learn how to assess the evidence before selecting a system" makes a more defensible promise. It also tells you what the closing discussion needs to achieve.

Explain the required starting knowledge. A specialist meeting can lose both groups when experienced practitioners expect detailed scrutiny and newcomers need every term explained. Publish who the symposium is intended for, what participants should already understand and what preparation you will provide. Offer a separate introductory resource when that solves the problem without consuming the main discussion.

Then describe what the ticket includes. Be explicit about the live sessions, materials, catering and any promised summary. If participants will receive a discussion report rather than recordings, say so before purchase. If attendance doesn't confer a qualification or continuing education credit, don't let the language imply that it does.

For a buyer seeking employer approval, explain how the programme relates to their work. They should be able to point to a decision they face and the contribution the day could make. Our conference justification letter guide can help them present that case without inventing a financial return.

Decide whether participation is open to everyone who buys or subject to a clear eligibility process. A narrow discussion may need particular professional experience, but vague claims about an "exclusive audience" don't explain a restriction. Publish the criteria and approval arrangements before taking payment, and make the process usable for people outside your existing network.

Use the sales page as a preparation check too. Write the sentence that explains why each session belongs in the programme. If you can only describe a speaker's job title, ask for a clearer contribution before confirming the session. That conversation often reveals whether you have a useful session or merely a willing speaker.

Send potential delegates a draft offer during research, including an indicative price and the proposed time away from work. Ask what they would need to get it approved and whether the promised materials would help. A list of enthusiastic comments is less useful than learning that the intended buyers cannot attend on the proposed date or need a different level of detail.

Build the programme around the evidence

The first thing you want to do is identify what the audience needs to examine. For the packaging example, that might include a comparison method, an implementation case and evidence about the conditions under which results change. These are programme requirements. They aren't invitations yet.

Create a working record for each proposed contribution. Note the question it answers, the evidence available, its main limitations and the connection to the next session. A contributor who can explain a failed implementation may be more useful than another speaker presenting a successful project without its costs or assumptions.

Ask potential speakers what they can actually share. Can they discuss the method? Are the figures cleared for public use? Will they distinguish measured findings from estimates? Can they explain where their experience doesn't apply? A strong biography doesn't settle those questions.

Choose an organising lead with authority to challenge duplication and close gaps. If one person is both the commercial organiser and the subject lead, arrange another qualified person to review the programme. You need someone who can say that a popular proposed session doesn't help answer the question.

An invited programme is usually simpler when you already know the essential evidence. A call for contributions can reveal work you haven't found, but it adds selection, communication and review work. Set the scope, required submission information, evaluation criteria and decision dates before inviting proposals. Don't ask people to prepare full papers when a short structured proposal would support a fair decision.

ACM SIGPLAN's programme chair guidance provides a useful example of published evaluation criteria and independent handling of conflicts. It governs its own research events, rather than every commercial symposium. For your event, document who selects contributions and arrange for someone independent to assess a proposal when the selector has a relevant conflict.

Choose contributors who can disagree usefully

A focused question doesn't require everyone to share a conclusion. In fact, a programme becomes more useful when credible contributors explain why their conclusions differ. Your job is to make those differences understandable and relevant to the audience.

Consider what each person brings. A researcher might explain the comparison method, an operator might describe implementation constraints, and a procurement specialist might explain what evidence an organisation can realistically request. These roles aren't interchangeable, even if everyone has an impressive title.

Look beyond the contacts who usually speak at your events. Ask where experience is missing, whose operating conditions differ and whether the people affected by the decision are represented. Don't invite someone merely to stand for a whole profession or community. Explain the specific contribution you would like them to make.

Discuss commercial interests early. A supplier may have valuable evidence, but participants should know when a contribution concerns something the speaker sells. Decide how disclosures will appear in the programme and introductions. Sponsorship should not determine which conclusions the chair permits people to question.

Give speakers the shared question and each other's session outlines. Ask them to avoid repeating the same background material. Where accounts conflict, invite them to identify the difference before the day so the chair can prepare a fair comparison. You're looking for a substantive disagreement, not a surprise confrontation staged for entertainment.

If a contribution depends on unpublished findings, agree what can be discussed, recorded or circulated. Make those restrictions workable for the audience. A ticket buyer can't benefit from evidence that is repeatedly mentioned but never explained, and a contributor shouldn't discover your publication plans after the session ends.

Give the chair and discussant different jobs

The chair keeps the discussion understandable, fair and on time. They need enough subject knowledge to follow the argument and enough confidence to interrupt politely when a speaker avoids the question. Booking a well-known presenter doesn't automatically give you either skill.

A discussant has a different job. They read the contributions beforehand and connect them. They can point out that speakers measured different outcomes, used different assumptions or examined different settings. That helps the audience understand what a disagreement actually means.

For a small symposium, one person might perform both roles, provided the workload is realistic. If the subject is contentious or the programme is dense, separating them gives the chair more attention for the room. Agree payment and preparation time rather than treating these roles as unpaid introductions between talks.

Give the discussant access to materials before the event, with a clear deadline and permission arrangements. Ask for a short response that identifies the strongest connection, the most consequential difference and the question the audience should explore next. They don't need to deliver another full presentation.

Brief the chair on what to do when someone turns a question into a sales pitch or personal challenge. They should be able to restate the substantive issue, ask for evidence and move on when the exchange stops helping participants. Serious disagreement is compatible with respectful treatment.

Also agree what happens when the evidence remains inconclusive. The chair can identify the missing information, ask which next investigation would be useful and record the uncertainty. They don't need to manufacture a show of agreement just because the programme is ending.

Give the chair a working brief they can use during a difficult exchange. Include the main question, the purpose of each block, the speaker order and the point at which they should move to discussion. Add a contact for programme decisions and another for production problems. The chair shouldn't have to negotiate a replacement session while also keeping the room involved.

Write prompts against the actual material. For our example, a useful prompt might ask whether two studies count the same activities when comparing systems. Another might ask which assumption a procurement team can verify locally. These questions help participants inspect the reasoning. A generic "any final thoughts?" rarely does that work when everyone is watching the clock.

Protect time for the actual discussion

Build the agenda backwards from the work participants need to do together. If you fill the day with presentations first, discussion will get whatever time remains. Usually, that's the first thing lost when a speaker runs late.

For our illustrative single-room symposium, registration opens at 08:45 and the chair starts at 09:15. A short opening establishes the question and language everyone will use. The first evidence block runs from 09:30 to 10:30, followed by a break until 11:00. The next hour compares an implementation case with the earlier evidence.

Allow discussion before lunch, then return to application in the afternoon. In this example, lunch runs from 12:30 to 13:30. Participants work through a common assessment problem until 14:15, followed by a comparison of their reasoning. After a break at 15:00, the closing discussion begins at 15:30 and the programme ends at 16:30.

Those times are suggested planning choices, not a standard symposium template. Adjust them to the content, access arrangements and people attending. The important detail is that discussion has protected time and a defined purpose. It isn't an optimistic "questions if time allows" line.

Within an evidence block, tell speakers how long they have and what happens next. If a talk needs extensive methods discussion, give it that space explicitly. Don't promise several detailed presentations, an expert response and meaningful audience questions inside a slot that only accommodates the presentations.

For the application session, use the same hypothetical case throughout the room. Give people the assumptions and ask which evidence they would request before deciding. Comparing their reasoning can reveal confusion that wouldn't emerge from another panel. Our roundtable discussion guide covers the smaller-group facilitation in more detail.

Prepare the participants as well as the speakers. Send a concise reading note that explains the main question, defines necessary terms and identifies the evidence they will discuss. Distinguish essential preparation from optional background reading. If you require substantial preparation, disclose it before purchase so people can make a realistic commitment.

You can ask participants to bring one example of a decision they face, with confidential information removed. Explain whether they will share it publicly or use it privately during the application session. Have a prepared example available for anyone who cannot bring their own. That keeps the activity useful without pressuring someone to reveal information their organisation hasn't authorised them to discuss.

Plan for people joining with different levels of confidence. Begin the first discussion with a question participants can consider quietly before inviting contributions. The chair can then ask for different interpretations rather than rewarding whoever speaks first. This gives people time to think and makes it easier to hear a view that differs from the opening contribution.

At the same time, don't promise everyone an individual consultation. State how the discussion works, how questions are selected and what happens to questions the programme cannot address. If a particular case needs more evidence or private advice, the chair should say so. Participants can still leave with a better understanding of what to investigate.

Keep the question visible in the chair's notes throughout the day. When a conversation becomes interesting but unrelated, record it for later consideration and return to the agreed programme. People bought a specific experience, and the organiser is responsible for protecting the time needed to deliver it.

Cost the work before choosing the ticket price

A symposium's small audience doesn't guarantee a small workload. Programme research, speaker preparation and a careful written summary may take substantial time. Include those costs before deciding that the event can survive on a modest ticket price.

Separate fixed commitments from costs that rise with attendance. Fixed commitments might include the room, production, contributor fees, travel commitments, programme development, staffing and report preparation. Attendance-related costs might include catering and individual materials. Put access support into the budget too, with contingency for needs that require further arrangement.

Here's an illustrative calculation in USD, using planning assumptions rather than market prices. The approved layout allows 100 delegate places. You reserve 10 for contributors and invited participants, leaving 90 paid places. Fixed event costs, including a contingency allowance, are $12,000. Catering and materials cost $40 per delegate, including the non-paying participants.

Assume the organiser retains an average of $220 per paid ticket after applicable taxes and payment or ticketing charges. Each paid delegate therefore contributes $180 after their $40 attendance cost. The 10 non-paying places add $400 of costs. With no sponsorship in the forecast, the event needs 69 paid delegates to cover $12,400.

At 50 paid delegates, retained ticket receipts are $11,000 and total costs are $14,400, leaving a $3,400 loss. At 70 paid delegates, receipts are $15,400 and costs are $15,200, leaving $200. At all 90 paid places sold, receipts are $19,800 and costs are $16,000, leaving $3,800 before business expenses outside this budget.

This chart shows why a nearly full specialist room can still produce a thin result. The assumptions are ours, not observed symposium performance. Replace them with your quotes and expected retained ticket income. Our event break-even guide explains the calculation if your ticket mix or sponsorship changes.

Make the commercial decisions early

Look at how much room the budget leaves for error. In the example, 70 paid delegates barely cover event costs. If your audience research suggests that's the most you can sell, the current plan is fragile. Reduce commitments, test a higher price against the offer or choose a smaller format before signing.

Don't automatically add more seats to solve the problem. If the ticket promise includes detailed participation, a larger audience can change what people receive. You may need more facilitators, extra rooms or another session, which changes the cost again. Check the programme and the budget together.

Set aside the costs of any reduced-price places before announcing them. An early-career rate or supported place can make the audience more relevant and improve access, but the cost still needs funding. Count sponsor guests and contributor places honestly. They occupy space even when they don't produce ticket income.

If you seek sponsorship, sell benefits that fit the symposium without controlling its conclusions. Acknowledgement, an appropriate display or support for a published summary may be suitable. Agree editorial independence, branding and data arrangements in writing. Don't promise access to attendee contact information simply because a sponsor helps pay the bills.

Put payment dates beside commitments. Speaker travel, venue deposits and production balances may fall due before enough ticket money is available. A forecast surplus doesn't cover an earlier cash shortage. Use the broader paid conference planning guide for supplier, cash and operations planning rather than rebuilding those processes here.

Choose a review date before the next expensive commitment. At that point, compare paid bookings, confirmed funding, available cash and contractual options. Decide what would justify proceeding or changing the plan. Avoid waiting until every cancellation option has expired to acknowledge that the audience hasn't bought.

Make participation work in the room

Choose the room for the conversation. Participants need to hear an audience contribution as clearly as a presentation. Check microphones, sightlines and the route between seats before approving a layout. A beautiful lecture theatre can be awkward if the central promise is discussion.

Make materials available in accessible formats and give participants a clear way to request accommodations. The US federal government's accessible meetings guidance recommends advance materials, accessible participation tools and rehearsing relevant controls. Its legal requirements concern its stated federal context; use the practical planning advice alongside the obligations that apply to your event.

Ask speakers to explain charts and unfamiliar terminology aloud. Tell the chair to read written questions before responding, and discourage simultaneous conversations when someone is addressing the room. Arrange appropriate support with participants and providers rather than assuming the small audience makes access straightforward.

Offer more than one way to contribute. Someone may prefer to submit a question in writing or ask the chair privately during a break. Tell participants how those questions will enter the discussion and who monitors them. Don't collect questions in a channel nobody has time to read.

Be realistic about hybrid participation. A remote contributor needs reliable audio, a clear speaking process and someone watching the remote channel. A remote delegate who can only watch a camera at the back receives a different experience from someone discussing the case in the room. Describe the actual offer and price it honestly.

Rehearse the difficult transitions. Test a question from the rear, a speaker joining remotely and a change between slides and discussion. Confirm who deals with a missing microphone or absent contributor. Your programme lead should have a replacement activity that still advances the question if a planned contribution falls through.

Agree what can leave the room

Decide the recording and attribution rules before selling the symposium. Some subjects benefit from public presentations followed by a discussion with tighter sharing rules. Others are designed for full publication. Participants need to know which arrangement applies to each part.

If you use the Chatham House Rule, information can be used afterwards without identifying participants or their affiliations. That is different from promising that everything said remains secret. Chatham House also says photographs and video aren't allowed in a Rule meeting, so don't pair that promise with a replay offer for the same discussion.

Write down how your team will handle notes, audience questions and any proposed quotes. If someone shares information outside the agreed boundaries, the chair needs to stop and clarify whether it can be retained. Don't expect a recorder or summary writer to make that judgement later.

Contributor agreements should cover the intended uses of slides, recordings and written material. Check third-party material too. The UK government's copyright guidance explains that protected material generally needs permission or another valid basis for use. A speaking invitation doesn't automatically give you permission to publish everything shown.

Assign a named person to prepare the summary. Keep evidence, interpretation and suggested next steps distinguishable. Record substantive disagreements rather than smoothing them into an apparent collective recommendation. Someone who challenged a conclusion shouldn't discover that your report presents it as the room's agreed position.

Set a review and delivery timetable you can meet. Contributors can check factual accuracy and how their contributions are represented without acquiring an unrestricted right to remove criticism. Explain that process beforehand. If a promised publication needs permissions you haven't secured, resolve them before making the promise.

For the packaging example, the summary might record that participants identified a disputed assumption about return rates and proposed checking local collection data before applying a published comparison. That states what was discussed without claiming the symposium settled the technical question. Add the relevant references and identify any further work as a proposal, with an owner only when someone has actually agreed to take it on.

Sell the question, then deliver the outcome

Your event page should make it easy for the right person to recognise the decision they face. Lead with the question, explain why it matters now and show how the programme examines it. Use contributor names as evidence of the programme's substance rather than expecting their reputations to explain the offer.

Show a meaningful agenda, the starting knowledge expected, the ticket inclusions and the sharing rules. Distinguish confirmed contributors from invitations. If the programme changes, explain how the revised session still fulfils what buyers purchased. A vague right to change anything doesn't replace a useful explanation.

Once the offer is ready, Loopyah's ticketing lets you set ticket types and release prices. Use that to implement the allocations you've budgeted. You still decide which places to offer, what they include and whether the expected sales support the event.

After the symposium, send the materials you promised and ask whether the day helped participants examine the central question. Ask what remains unclear and which next decision they can now approach more confidently. Review those answers alongside the budget, preparation time and the commitments your team actually delivered.

Before booking another edition, read the closing notes with the programme lead. There may be a worthwhile follow-up question, or the next useful step may be a smaller working group or an independent investigation. Choose the format that serves that work. Another symposium makes sense when there is another question worth paying to examine together.