How to prevent competition-law problems at an industry conference

You've booked a room full of people who understand the same market. That's why delegates are paying to attend. Then a speaker suggests comparing next year's prices, a sponsor asks for a live poll about discount plans, and someone wants the group to agree which customers deserve better terms. Your conference now has a problem that good networking etiquette won't solve.

To reduce competition-law risks, review what you're inviting competitors to discuss, remove prompts that seek sensitive commercial information, and give moderators the authority and instructions to stop inappropriate exchanges. Have a competition lawyer familiar with the relevant markets review uncertain sessions and agree how your team will respond to an incident. A reminder on the opening slide helps only when the programme and the people delivering it follow the same rules.

You can still run a useful, commercially valuable industry conference. Delegates can examine technical problems, customer experiences and published research without being asked to coordinate their businesses. The work is in choosing questions that produce useful learning while keeping independent commercial decisions with each business.

This guide develops that approach through an invented paid event, Service Industry Forum. Its session plans, staffing choices and costs are illustrations, not legal standards or evidence of a real event's results. Competition law depends on the conduct and jurisdictions involved. Use the guide to prepare your event brief and questions for a qualified adviser, rather than treating it as legal clearance for a particular discussion.

Start with the decision your conference should help people make

The first thing you want to do is write down why delegates are buying a ticket. "Meet senior industry leaders" describes the audience. It doesn't explain what a session needs to achieve. A stronger purpose might be to help managers diagnose service delays, compare public technical guidance or assess how customers experience a handover between suppliers.

At Service Industry Forum, the proposed session is about reducing failures during customer onboarding. Delegates should leave knowing how to spot missing information, assign responsibility and test whether a customer understands the next step. They don't need to disclose their company's planned prices, customer allocation or future output to learn those things.

That distinction improves the product you're selling. A vague promise of unrestricted commercial discussion gives your moderator little basis for an intervention. A defined learning outcome lets them say why a question belongs elsewhere and offer a useful alternative. The session can continue to deliver value without extracting information that participants shouldn't share.

Write the intended output as well. Will delegates receive a fictional exercise, a reading list or a summary of technical questions? If the advertised takeaway is a shared pricing recommendation, changing the opening disclaimer won't repair the underlying session. Change the promise before it appears on the sales page.

Your broader paid conference plan should account for these choices alongside speakers, production and ticket sales. Programme review needs time before bookings become commitments. It's much harder to replace a headline session after sponsors have sold it internally and buyers have made travel arrangements around it.

I would rather sell a well-defined discussion with a useful outcome than promise that delegates can ask absolutely anything. Explain what the room is for, select speakers who can deliver that learning, and make the limits part of preparation. Buyers should be able to judge the value of the learning you will actually provide.

Get advice for the markets and activities involved

Competition law and antitrust law are names used in different places for rules protecting competition. For an international industry event, don't assume that the venue's address settles every legal question. Give your adviser a practical account of who is participating, where their businesses operate and what the proposed activity would involve. Let them identify the relevant law.

The UK's Competition and Markets Authority, or CMA, warns in its guidance for trade associations that an association and its members can face consequences when the association encourages an infringement. Its advice includes keeping members' commercial decisions independent and avoiding sensitive discussions around association events, including social occasions. This is UK guidance, not a universal legal test for every conference.

For your own review, prepare a short description of the event, the industry and the relationships between participants. Include businesses that may compete for employees or suppliers as well as customers. Add the draft agenda, prompts, proposed polls, sponsor activities, planned recordings and any research you want to distribute. A lawyer can review a specific proposal more usefully than a session title alone.

Ask what needs to change before you confirm the programme. You want an answer about the actual questions, materials and format, plus clear instructions for the people delivering them. A general presentation about competition law won't tell your chair what to do when the first audience question names a forthcoming tender.

Agree when another review is needed. A new sponsor might change a technical session into a discussion of commercial terms. A speaker might replace a published report with an unpublished company forecast. Those changes affect what was assessed. Your production process should bring them back to the adviser rather than treating approval of an earlier version as approval of whatever appears on the day.

Keep the advice and resulting decisions with the people who need them. Your moderator needs practical instructions; they don't necessarily need every confidential document given to counsel. Ask your lawyer how their advice should be stored and shared. Don't assume that adding "privileged" to an ordinary event document creates legal protection.

Recognise questions that need to be stopped or reviewed

The problem often begins with an ordinary-sounding invitation to be helpful. "What are you all planning to charge next year?" asks competitors to reveal future commercial decisions. "Could we agree to stop discounting?" asks for coordination. Train your team to hear the proposed action, even when the speaker describes it as protecting quality or helping the industry.

The CMA's guidance on sensitive commercial information identifies non-public strategic information, including future pricing and output plans, as competitively sensitive. It also warns about sharing current or historical cost or pricing information and discussing projected industry pricing trends. Its advice distinguishes some historical, aggregated information, but that doesn't give your conference a general permission to exchange company figures.

For preparation, give moderators examples tied to the actual audience. A session for service suppliers might drift into next year's fee increases, minimum discounts, plans to withdraw capacity or intentions about particular customers. A procurement session might drift into coordinating bids. Make these examples recognisable without collecting real participants' plans to illustrate them.

Keep employment discussions in view. The US Federal Trade Commission and Department of Justice explain in their guidelines on business activities affecting workers that agreements to fix wages or avoid recruiting workers can raise antitrust concerns, as can exchanges of sensitive employment information. The guidance also addresses independent contractors. For your programme, send proposed compensation surveys or recruitment agreements to counsel rather than assuming a human resources session sits outside competition law.

A delegate can ask about improving an interview process without asking the room to agree what employees should be paid. A technical speaker can explain a testing method without polling competitors about future production. Use the learning objective to find the useful question you can actually deliver, then have uncertain alternatives reviewed.

Don't turn this into a list of words that nobody may utter. A published price in a historical case study is different from asking rivals to announce their next increase. Context matters. Your team's job is to recognise a concern, stop an exchange when necessary and involve the right adviser. They shouldn't improvise a legal ruling because a word appeared on a slide.

Rewrite the agenda before inviting contributions

Start with the title, then read every question beneath it. "The future of our industry" may sound harmless while its discussion notes ask participants to reveal which territories they intend to enter. Your review needs the planned conversation, including the follow-up questions a moderator would naturally ask.

At our fictional forum, the first draft says, "How should suppliers respond together to falling margins?" The organiser changes it to, "Where does customer onboarding fail, and how can a manager investigate the cause?" The revised session uses an invented service handover with missing information. Participants explain the checks they would make without describing actual pricing plans or agreeing a collective response.

Develop the exercise properly. The fictional customer has signed a service order, the delivery team hasn't received the agreed specification, and the customer expects work to begin on Monday. The group must identify who should verify the promise, what information is missing and how the customer should be updated. There is enough detail for a substantive discussion without asking anyone to bring a live contract.

The moderator can explore disagreement. One participant wants to contact the customer immediately; another wants to establish the facts first. Ask what each response assumes and how they would handle a deadline. The discussion becomes valuable because people explain their reasoning. It doesn't need confidential business data to become interesting.

Use the roundtable discussion guide for turn-taking and facilitation, then add the reviewed subject limits. An open format still needs a defined purpose. Asking everyone to contribute doesn't mean requiring everyone to reveal a commercial figure or explain their company's future strategy.

Review audience participation as carefully as prepared slides. If you collect questions in advance, explain which subjects the session covers and which it cannot take. Have a person screen submissions before they appear on a public display. Don't make a technician responsible for recognising legal concerns while also running sound and slides.

Give speakers a deadline for the materials you actually need to assess. Specify whether that includes handouts, polls, prompts and proposed exercises. If a presentation changes late, identify what changed and review it before use. A generic promise that the speaker will comply with the law doesn't tell your producer whether the replacement file matches the approved session.

Your speaker agreement can describe the preparation and review process, delivery requirements and authority to interrupt. Have the relevant terms reviewed for your event. The practical aim is for a speaker to know, before accepting the booking, that programme approval includes the proposed audience interaction.

Treat live polls and benchmarking as separate proposals

A live poll can distribute information faster than a discussion. One question appears, everyone submits a response and the result goes onto a screen. Before adding one, ask what information is being requested, who can see it and what the audience could infer from the result.

At Service Industry Forum, a sponsor proposes asking suppliers to select their planned price increase for the next year. The organiser removes the poll and sends the proposal for legal review. Hiding the company names wouldn't resolve the underlying concern about collecting and sharing competitors' future intentions. The room doesn't need that result to examine onboarding failures.

A different poll asks which part of the fictional handover participants would investigate first. Its answers concern the exercise, not their companies' commercial plans. The moderator can use disagreement to develop the case. That's a better fit for the advertised outcome, though the full session still follows the review process.

If you want to publish genuine industry benchmarking, define it as a research project before advertising it as a conference benefit. Specify the purpose, fields, contributors, collection method, who receives raw data and what the intended report contains. Get advice on the actual design. An event producer shouldn't invent a threshold and call everything above it anonymous.

Canada's Competition Bureau recommends care with association information sharing, including third-party collection and distributing aggregate information that can't be attributed to competitors. Its trade association guidance also recommends agendas, accurate minutes and a response when improper discussion arises. These are Canadian recommendations; the design still needs assessment under the law relevant to your activity.

An independent research supplier can help administer a project. That doesn't make every question suitable. Ask whether a reader could identify a contributor through a small subgroup, a distinctive product or a combination of details. Define what happens when there aren't enough appropriate responses to publish the promised breakdown.

Be particularly careful with old internet checklists. In December 2024, the FTC and Department of Justice withdrew their 2000 competitor collaboration guidelines, saying they no longer provided reliable guidance. Their statement also referred to reliance on outdated, withdrawn policies. The agencies opened a public inquiry about new collaboration guidance in February 2026. Check the current position with your adviser before using an old numerical information-sharing formula in a conference brief; an old checklist isn't current legal clearance.

If your report can't be prepared appropriately in time, change the deliverable. A reading list and a well-developed fictional exercise can still support a worthwhile session. Buyers should know what they will receive before they pay, especially if a supposedly exclusive dataset is a main reason to attend.

Give moderators authority they can actually use

A moderator can't manage a sensitive discussion if their only instruction is to keep an influential sponsor happy. Tell them who approved the agenda, what requires an immediate stop and how to contact the named event lead. Confirm that they can interrupt a speaker regardless of the speaker's status or commercial relationship with the conference.

Rehearse the words out loud. For a request about future prices, an illustrative response is, "I'm stopping that question. We won't ask participants to share their future pricing plans. Please don't answer it. We're pausing the session and contacting the event lead." Have counsel review the intervention and next steps for your event. A confident, specific interruption is easier to follow than an embarrassed joke.

Don't repeat the sensitive question in full to explain why it was a problem. The audience may not all have heard it. State the category of concern and the instruction to stop. If a poll has already appeared, the operator should stop receiving answers and showing results according to the agreed response plan, while preserving the relevant record for restricted review.

The chair needs a handoff that works in the room. Identify the event lead by name and provide a direct contact method. Agree how a host signals a pause to the technician and how remote participants receive the same instruction. Test it during the production rehearsal rather than assuming that everyone monitors the same messaging channel.

Late arrivals need the same participation rules. A person entering midway through an open discussion may have missed the opening reminder. Put a concise explanation in the advance participant information and have the host direct late arrivals to it. The moderator can restate the relevant boundary when necessary without reading a long policy every time the door opens.

Choose a moderator who understands the subject and can resist pressure to keep talking. Familiarity with the industry helps them recognise why a seemingly casual question is sensitive. Still, subject expertise doesn't replace specialist legal advice. Their responsibility is to follow the agreed plan and escalate uncertainty, not negotiate a legal exception in front of the audience.

Prepare a genuinely useful fallback. If the live discussion can't continue, the producer might have an approved technical presentation or a prepared exercise available. The fallback should have its own materials and instructions. "We'll just talk generally" can recreate the same problem if nobody has decided what that conversation contains.

Agree what happens when the discussion crosses a line

Your incident plan starts with stopping the exchange. It then needs a clear decision about who takes charge, what gets preserved and whether the session can continue. These decisions belong in preparation with counsel. Don't leave the event manager to work them out while the room waits.

At the fictional forum, a participant begins asking other suppliers whether they will avoid bidding for a particular customer's next contract. The moderator interrupts immediately, tells people not to respond and pauses the session. The host contacts the designated lead. This example illustrates an operational response to a concern; it doesn't make a legal finding about the participant's conduct.

The producer stops the current discussion and any live distribution according to the agreed technical plan. The incident lead arranges restricted preservation of the relevant recording, chat, poll or notes and seeks prompt legal advice. They don't send the material to every speaker asking for comments, and they don't tell staff to delete it to make the problem disappear.

Keep a factual record. Note the session, approximate time, people involved, what was observed and the actions taken. Distinguish an exact quotation you can verify from somebody's recollection. If you correct an error later, preserve a clear record of the correction. Ask counsel what further evidence and records are needed and how they should be handled.

Participants also need instructions for their own position. The organiser's pause doesn't decide what obligations a delegate or their employer may have. Your advance rules should explain how to object clearly and leave an improper discussion, with the departure recorded. The Canadian guidance above specifically recommends leaving and recording departures when improper discussions arise. Give people the reporting route, and make clear they can seek their own legal advice and contact authorities where appropriate. Don't promise that the organiser will resolve everybody's legal exposure.

Agree beforehand who decides about resuming. A sponsor's request to continue isn't enough. If the right advice or responsible decision-maker is unavailable, end the affected session. You can explain the programme change briefly without accusing someone publicly or distributing the detail you're trying to contain.

Seek prompt specialist advice about reporting to a regulator, responding to an authority or applying for any available immunity or reduced penalty. People must remain free to make lawful reports directly. Avoid writing a ticket condition that requires people to obtain the organiser's permission before making a lawful report. Also avoid suggesting that a private apology, confidentiality promise or later correction automatically resolves what happened.

For the follow-up, separate communication with affected people from publicity. A factual operational update may be necessary. A marketing recap usually doesn't need an account of the incident. Have the incident lead and counsel decide what can be shared and with whom before a team member posts an explanation from the conference account.

Include sponsors and informal activities in the review

A sponsored breakfast can invite the same competitors as the main stage. Review its purpose and proposed discussion before selling it. Calling the session a networking benefit doesn't explain what the host plans to ask, what data they want to collect or what they will distribute afterwards.

At our fictional forum, a sponsor offers to host a breakfast about common service challenges. The organiser asks for the actual prompts. One asks businesses to compare future commercial terms; another asks them to work through a fictional customer journey. The organiser rejects the first proposal and develops the second through the normal review route. Sponsor funding doesn't change the process.

Put the relevant programme requirements into the sponsorship agreement. Define which sessions you control, the materials and prompts that need review, and how changes or cancellations are handled. Have counsel check the specific wording. Your sponsor manager should know what they can promise without selling an exemption from the event's rules.

Informal time still deserves a brief. Hosts should know how to respond if an organised networking table moves into sensitive commercial discussion. That doesn't mean attempting to supervise every private conversation. It means avoiding organised prompts that invite coordination, making the event's expectations clear and giving staff a practical response when a concern comes to their attention.

Don't solve a competition concern by moving the conversation into a smaller room or removing the recording. Our guide to confidential conference discussions deals with permission, capture and disclosure boundaries. Those arrangements address different questions. A non-disclosure agreement doesn't authorise a discussion that the applicable competition law prohibits.

If participants want to pursue a genuine collaboration after the conference, don't casually convert the event session into its planning meeting. The CMA's advice on joint ventures asks businesses to define the actual purpose and limits of a collaboration and avoid unnecessary restrictions or unrelated sensitive information sharing. For your event, refer a specific proposal for separate advice before offering to host or administer it.

Be equally clear about independently organised gatherings. Decide what use of your branding implies, what approval you require and what you are actually managing. Describe those responsibilities accurately. A small-print label won't repair an arrangement in which your team is designing the agenda, recruiting participants and directing the activity while claiming no involvement.

Check digital spaces and the material you send afterwards

A conference discussion can start before anyone reaches the venue. Review the introduction prompts in your event community, any pre-event survey and the questions attached to a session invitation. Don't ask people to upload a confidential commercial plan as preparation for a discussion that has been approved only as a fictional exercise.

Assign a person to moderate organised online spaces during the relevant periods. Give them the same escalation route as the room host. They need to know what to do with a concerning message, how to restrict further distribution where appropriate and how to preserve a record under the agreed incident process. "The platform handles it" isn't an instruction.

Test the audience-question setup. Can somebody publish directly to the screen, or does the host review a submission first? Can the producer stop a poll quickly? Who can access exports? These are operational questions for the actual tools you use. Work through them before a speaker discovers an unreviewed feature during their presentation.

Check what automated summaries will do. A transcript, meeting assistant or post-event recap can reproduce a sensitive exchange even after the room has moved on. Decide what you will record and how outputs are reviewed before release. If an incident occurs, stop routine publication and follow the restricted preservation and advice process rather than letting the usual marketing schedule continue.

Approved educational material still needs ordinary editorial checking. Compare the recap with the session's agreed learning outcome and source material. Don't turn an individual remark into a recommendation that the industry should follow a common price, hiring policy or commercial response. If the writer is uncertain, get the passage assessed before distributing it.

Use your attendee communications for practical preparation. Loopyah's attendee email tools support building and sending messages to event audiences. Your team can use that communication channel to explain the session purpose, preparation and contact route. The content and legal review remain your responsibility; sending a message doesn't establish that every delegate has understood or accepted it.

Provide a route for corrections and concerns after the event. Someone may notice a problem while reviewing their notes or a recording. Name the contact and explain how to share a concern privately without forwarding sensitive material to a broad group. Keep that route available for the period your reviewed event process requires.

Budget for the preparation you have promised

A carefully designed session takes staff time. Include review, rehearsal and technical preparation in the event budget before deciding whether a sponsor fee or premium ticket makes it worthwhile. Don't treat those tasks as free because your team already has salaries.

Here is an invented USD example for one discussion block. The producer assigns eight hours to preparation at an internal cost of $40 an hour, giving $320. The moderator receives $450 for preparation and delivery. A host costs $160, and a technical rehearsal costs $120. Those selected costs total $1,050. They are fictional planning assumptions, not market rates or a complete compliance budget.

Legal advice is an additional cost to obtain from your adviser for the actual work. Include it explicitly, together with any extra access support, production changes and wider conference costs. A fixed legal allowance invented in a blog would tell you nothing about the cost of reviewing your industry, countries and proposed activity.

If a sponsor pays $1,500 retained after relevant transaction charges and sales taxes, the amount left after those selected $1,050 costs is $450 before legal advice and other omitted costs. That isn't a profit forecast. It tells you how little room the example leaves for work that hasn't yet been priced. Staff time also isn't necessarily a new cash payment, so keep the cost calculation separate from your payment schedule.

Now consider an unsuitable session. Rewriting the offer, reducing its scope or replacing it before sale may be the better commercial decision. Don't calculate a supposed saving by dropping the moderator or review process while continuing to promise the same discussion. You would be changing the conditions under which the event was planned.

Check cancellation and replacement terms before confirming the booking. Who bears the cost if a speaker won't supply suitable materials? What can a sponsor expect if its proposed poll can't be used? Resolve those questions in the actual agreements, with appropriate advice. A producer should be able to make a programme decision without discovering an unrelated commercial promise that prevents it.

Test a late sponsor change against the actual offer

Suppose the fictional forum's sponsor accepts the onboarding exercise, then sends a different deck shortly before the event. It includes a slide inviting delegates to submit their expected price increases through a QR code. The sponsor says the answers will be anonymous and that the result is the most valuable part of the breakfast. Your producer spots it while checking the final presentation.

The first action is to hold the changed material out of production and send the proposal through the agreed review route. Don't let the deadline decide the answer. Tell the sponsor which part of the session was approved and explain that the replacement question changes what participants would be asked to disclose. Your team can describe the concern without asserting that it has completed a legal analysis.

Next, check the promise already made to buyers. In this example, the event page promises a facilitated fictional exercise and practical preparation notes. The sponsor's new poll isn't part of that offer. Returning to the approved exercise preserves the planned experience, provided the speaker and moderator are ready to deliver it. You don't need to invent a replacement dataset to make the original session worthwhile.

If the sponsor has independently advertised the poll, involve the commercial lead and counsel in resolving the conflicting message. Establish what was sent, to whom and under what approval. Agree the necessary corrections and any contractual consequences. Don't ask the technician to hide the slide while the sponsor continues inviting people to scan the same code from a printed handout.

Check every route by which the changed activity could reach delegates. The presentation may be one copy, while the speaker has a personal laptop, a handout or a scheduled community post. Your producer needs confirmation of the actual materials being used. Hold the unapproved activity out of the event, while retaining the relevant proposal and review record according to your document-handling process.

Now rehearse the approved version with the speaker. Can they explain the fictional case and develop its questions without referring delegates to the rejected poll? If they won't deliver the reviewed session, use the replacement or cancellation process in the actual agreements. A sponsor manager's confidence that the speaker will probably cooperate isn't enough to brief the room host.

Finally, record the decision and update the people delivering it. The moderator should know which case is approved, the technician should have the correct file, and the host should know how to respond if a delegate asks about the promised poll. The incident lead should also know whether anyone reports that responses have already been collected, so they can seek advice on that separate concern.

This example is why approval needs to follow the activity through to delivery. Reviewing an early outline is useful, but the audience experiences the final questions and materials. Give one producer responsibility for checking that those match the decision made, with time to escalate differences before the session begins.

Give the team a completed session brief

Pull the decisions into a record that somebody else can use. A general policy is useful background, but the team delivering a particular session needs its approved subject, materials, people and response plan. Keep confidential legal advice separately as counsel directs, while making the operational instructions easy to find.

For Service Industry Forum, the completed brief could contain the following. This is an example of production information to prepare, not a legal policy or a ready-to-sign agreement.

• Purpose: help service managers investigate an incomplete customer handover using the supplied fictional case.

• Audience: delegates from the industry, including businesses that may compete with one another. The relevant jurisdictions and participant relationships have been supplied to counsel for assessment.

• Materials: the reviewed case, moderator prompts and reading list. No live company data, future-price poll or shared commercial recommendation is part of the session.

• People: a named moderator, room host, producer and incident lead, with direct contact details and an identified route to legal advice.

• Opening: explain the learning outcome, participation boundaries, recording arrangement and concern-reporting route in the agreed wording.

• Interventions: stop a concerning exchange, tell participants not to continue and contact the incident lead. Follow the reviewed response rather than inviting the room to vote on whether a question is acceptable.

• Production: screen audience questions, test the pause signal and confirm how live distribution can be stopped while relevant records are preserved appropriately.

• Follow-up: distribute only the prepared case and checked educational notes. Hold any affected material for restricted review if a concern arises.

Add the final file names or version references used in production. If the moderator has an older deck than the technician, the review process hasn't reached the actual room. Ask the producer to open the files during rehearsal and show the host where the approved prompts and contact details are stored.

Keep the brief usable under pressure. A host shouldn't have to search a long sponsorship contract to find whom to call. Put the immediate operational instructions where the delivery team can reach them, and retain the fuller agreements in their proper place. Confirm that replacements receive the same briefing when a staff member becomes unavailable.

Rehearse the awkward moment before opening the doors

A rehearsal should test a decision, not merely confirm that the microphone works. Ask a colleague to introduce a question about future prices while the moderator is speaking. Watch whether the chair interrupts, the host responds and the producer can pause distribution. Then check whether the incident lead receives enough factual information to act without asking the group to repeat the exchange.

Run a different version in which the sponsor asks to keep talking privately after the pause. Your team should know that changing the room doesn't resolve the concern. Test another in which the event lead doesn't answer. The fallback contact and decision to end the affected session need to work without an improvised chain of messages.

Check that ordinary participation still works, too. A delegate should be able to challenge the fictional exercise, disagree with a proposed management decision and ask for clarification. You want thoughtful discussion within the reviewed scope. A moderator who interrupts every technical disagreement can damage the learning experience just as surely as one who ignores the agreed limits.

Ask a colleague outside the planning team to read the sales description and session brief together. What do they think a buyer will receive? Who do they think can stop the discussion? What would they do if a poll asks for a company's future plans? Any conflicting answers identify something you still need to settle.

Before approving delivery, confirm the actual materials, responsible people and available advice route. If the useful session can run within those arrangements, brief the team and proceed. If it still depends on competitors revealing plans or agreeing a shared commercial response that hasn't been cleared, change the session before you sell it.