How to manage speaker conflicts of interest at a paid conference

Your speaker has agreed to explain how businesses should choose a new supplier. Then you discover that one of the suppliers pays them for referrals. Their advice might still be useful. But your ticket buyers deserve to know about that connection, and your programme team needs to decide whether this person should be making the recommendation at all.

Ask speakers about relevant interests before you confirm their contribution, review those interests against the actual session, and agree what must change before it goes ahead. A disclosure can help attendees judge a speaker's perspective. It doesn't make an unsuitable presentation suitable, establish that a claim is true, or remove your responsibility for the programme you're selling.

The practical question is what to do with the information. Sometimes the answer is a clear declaration and an otherwise unchanged talk. Sometimes you need a different example, an independent reviewer or a narrower role. Occasionally, the right decision is to replace the speaker. You need a process that makes those choices possible while there's still time to act.

This guide walks through that process for paid conferences, including a declaration form, disclosure wording and worked decisions. The general recommendations are an editorial approach you can adapt. If your event offers accredited education, start with the relevant body's requirements, which can be more restrictive than the approach suitable for an ordinary business conference.

Start with the session people are paying to attend

A speaker conflict of interest arises when another interest could influence the contribution they're supposed to make to your audience. The connection might involve money, a professional relationship or a personal relationship. What matters for your programme is how that interest relates to the subject, the proposed advice and the decisions the speaker controls.

Imagine a conference for independent hotel operators. You're commissioning a session about choosing housekeeping software. A hotel manager describing their own implementation has a particular experience to explain. A consultant comparing suppliers may also have referral arrangements. A software company's employee has an employer's commercial interest. Those people can contribute useful knowledge, but they aren't offering the same perspective.

Write the session's purpose before deciding what interests matter. Are attendees expecting an account of one project, a comparison of buying options or a demonstration of a particular product? The more the presentation promises an independent recommendation, the more carefully you need to examine relationships that could affect that recommendation.

The International Committee of Medical Journal Editors explains in its recommendations on financial and non-financial relationships that relationships don't always establish problematic influence, while transparent disclosure helps readers assess relevance. That guidance concerns medical publishing. The useful principle for your conference is to examine the connection and the contribution, rather than assume every relationship proves wrongdoing.

Don't turn the review into a search for people who have never worked with anyone in their industry. You probably invited the speaker because they've done relevant work. Instead, establish what they can explain honestly, which interests attendees need to understand and whether your proposed format gives them inappropriate influence over someone else's decision.

Your own description matters here. Calling a supplier's founder an independent adviser creates a problem that an accurate biography could have avoided. If the talk is the founder's account of building and operating their product, say so. If the programme needs an independent buying comparison, commission someone who can provide that contribution under your editorial requirements.

Separate personal interests from paid programme placement

A speaker can have a relevant interest even when nobody paid your conference for the session. The consultant might receive commissions from a supplier, hold shares in the business being discussed or sell a course based on the method they're recommending. Those arrangements don't disappear because you selected the talk through an open call for proposals.

Conversely, a sponsor can fund a session without choosing the speaker or approving the conclusions. In that arrangement, you need to explain the funding and preserve the editorial separation you promised. You still need declarations from the people shaping the content. The event's funding arrangement and an individual's relationships answer different questions.

Our guide to sponsored conference sessions covers selling and delivering a clearly described commercial contribution. This article deals with the interests of speakers and decision makers across the programme, including sessions that your conference commissions and pays for itself. Don't move every difficult declaration into sponsorship simply to make the review easier.

A label also needs to describe the whole relevant connection. Saying that a speaker's company supports the event doesn't tell attendees that the speaker personally receives money when someone buys the recommended software. An employer name in the biography may explain employment while leaving a separate referral arrangement unclear.

Keep those facts separate in your records. Note who funds the session, who employs or pays the speaker, and who controls the topic and conclusions. Then decide which facts need to appear together in the public explanation. You can be concise without collapsing several different arrangements into a reassuring word such as "partner".

Ask specific questions before making the commitment

Send the declaration request with your proposed brief, rather than after you've announced the headline speaker. Explain that the information helps your team agree a suitable contribution. A person should understand why you're asking and what will be made public before they provide information that may be sensitive.

Ask about relationships connected to the subject and organisations likely to be discussed. Include employment, consulting, advisory work, ownership interests, referral payments, royalties and support for the work being presented. Give examples in the language of your audience. A practitioner may recognise a commission arrangement more readily than a question about "pecuniary interests".

Ask about relevant unpaid roles too. Someone can chair a supplier's advisory group without receiving a fee, or help lead a campaign whose position they intend to present as an impartial industry conclusion. Your review should establish the role and its effect on the contribution, without requiring a list of every association the person has ever joined.

Choose and state a review period for your own policy. You might ask about current relationships, relevant recent relationships and already agreed future work. Explain what you mean by recent, and allow speakers to flag an older connection if it still affects the subject. This is your editorial choice unless a professional or legal requirement sets the period.

Don't copy an accreditation body's time limit into a general conference form and present it as a universal standard. Different programmes have different requirements. You need a period that your team can explain and apply consistently, alongside an instruction to update the declaration when a relevant connection changes.

Make unresolved review conditions visible before you commit to fees, travel or promotional production. If a speaker needs to clarify a referral arrangement, agree when you will decide and which commitments remain on hold under the booking terms. Otherwise, the cost of replacing the session can start influencing a decision that should have been made before those costs arose.

A speaker may reasonably decline to share information you don't need. Explain the purpose and narrow the request where possible. If you still lack the facts needed to approve the proposed role, keep it unapproved and consider another contribution. Don't quietly treat refusal or silence as a declaration of no relevant interests.

A blank form should trigger a follow-up. It doesn't tell you that the person has nothing to declare. Ask for an explicit response, including an explicit statement when they report no relevant interests under your policy. If someone is unsure whether a connection matters, invite a private explanation so your reviewer can decide with them.

Use a declaration form your team can act on

The form below is a starting point for a general business conference. Set the scope, review period and privacy information for your event before sending it. It isn't an accredited education form, and it doesn't replace any declaration required by a professional body.

• Speaker and session: give your name, proposed role and the session title or reference.

• Subject: name the organisations, products, services or decisions you expect to discuss or recommend.

• Relevant relationships: identify the organisation or person involved and describe the relationship in plain words.

• Timing: explain whether the relationship is current, ended within our stated review period, or relates to future work already agreed.

• Financial connection: tell us whether you receive payment, referral income, ownership benefits, royalties, funded travel or other relevant support.

• Other relevant connection: describe an unpaid role or personal or professional relationship that could affect this contribution.

• Content involvement: tell us who suggested, funded, prepared or approved the examples, research, slides or demonstration.

• Limits: identify any restriction that prevents you from discussing alternatives, limitations or relevant evidence.

• Uncertainty: tell us anything you're unsure whether to declare and request a private review if needed.

• Confirmation: confirm that your response is complete to the best of your knowledge and that you'll report relevant changes before the session and agreed recording release.

Add a short explanation of who reviews the response, who can access it, how the public statement will be agreed and how long you expect to retain the private record. Give a real contact for corrections or sensitive questions. Don't imply that every field will be published unchanged.

You usually need the nature of a payment to make an initial editorial decision, rather than the speaker's full financial records. Ask for more detail only when a specific unresolved issue requires it. If a rule requires an amount or another particular detail, collect it for that stated purpose and limit access appropriately.

Keep the form connected to the session. Someone might be suitable for an implementation interview but have a conflict when judging proposals from suppliers. One declaration can contain the relevant facts, while your decision record explains what those facts mean for each role. Don't let approval of one contribution silently approve everything the person does at your event.

Decide whether the relationship affects the contribution

When a declaration arrives, ask what the person can influence. A speaker may choose examples, recommend products, select research or answer buying questions. A programme chair may choose the entire shortlist. The same financial connection can require different action depending on which of those decisions the person controls.

For the hotel conference, suppose a consultant receives referral payments from one housekeeping software supplier. An interview about a project they helped deliver could still be useful if the arrangement is clear and the account is evidence based. Asking that person to produce your supposedly independent ranking of suppliers creates a much harder problem.

Check the link between the interest and the content. Which conclusion could benefit the connected organisation? Can the speaker explain the limits of their example? Is the session's value dependent on a claim your team cannot assess? Write the answers in ordinary language so a colleague can understand why you chose the outcome.

I would use four possible outcomes for a general conference: proceed with the agreed disclosure, proceed after specified changes, hold the contribution pending further information, or decline the proposed contribution. These are decisions for your programme, not a numerical risk score. Each should come with a reason, an owner and any conditions that must be satisfied.

Don't approve a vague promise to "be balanced". Ask for the actual change. That might mean removing a ranking, showing the basis of a recommendation, replacing a sales link with a neutral resource or changing a solo presentation into a moderated account of one implementation. The revised contribution should still deliver something your audience wants.

A disclosure on its own can be reasonable when it gives attendees the context needed to understand a suitable contribution. It becomes insufficient when the format promises independence the speaker cannot provide, when evidence remains unsupported or when a controlling organisation won't allow necessary editorial changes. In those cases, change the contribution or choose another speaker.

Give the decision to someone able to disagree

A declaration process becomes weak when the person who wants the booking also decides that every connection is harmless. Name a programme owner who can ask for changes, delay an announcement or decline a proposed contribution. They need authority over the decision, not just responsibility for collecting completed forms.

At a small event, you may hold several roles yourself. Ask another suitable person to review a decision when you have a relevant connection, such as a financial relationship with the speaker's business. You don't need a standing committee for every ordinary declaration. You do need a credible way to avoid approving your own interest without scrutiny.

Apply this to proposal reviewers and chairs as well as speakers. A reviewer shouldn't privately reject a competitor's proposal while their own company's speaker is under consideration. Ask them to declare the connection, arrange another reviewer for that decision and record who made the assessment instead.

Nature's competing interests policy includes financial and non-financial interests and requires editors with relevant conflicts to step away from handling affected manuscripts. That's a publishing policy, not a rule for your event. It offers a useful example of why disclosure and responsibility for the decision need to be considered together.

Tell commercial colleagues what the review can change before they promise a speaking place. They can explain a sponsor's objectives and the consequences of changing a package, but a revenue target shouldn't quietly become the programme's approval criterion. Resolve a disagreement with the named event decision maker while the offer remains open.

Consider a second fictional case. Your programme chair has an unpaid advisory role with a professional association. The association nominates a speaker for a session your chair would normally approve. Ask what the advisory role involves and whether the chair helped prepare the nomination. Another suitable reviewer can make the acceptance decision, with the chair providing factual information through the ordinary route rather than deciding the outcome.

The nominated speaker might be excellent. Moving the decision to someone else doesn't require rejecting the nomination, inventing a competing speaker or suggesting that the chair acted improperly. It lets your team assess the contribution against the same criteria it uses for other candidates, while recording who made the decision and why the chair stepped aside.

Now suppose the chair also moderates the accepted session. Review that role separately. A routine introduction might need no further change, while an interview evaluating the association's own work may need another moderator. The point is to follow the actual influence the person has at each stage, instead of treating one declaration as a permanent ban or a complete approval.

Give the speaker a fair route to correct facts or suggest another format. Your message should identify the connection, the concern and the change needed. "You have a conflict" doesn't explain why the proposed supplier comparison is unsuitable or why a project interview could still work. A concrete explanation lets a capable speaker respond constructively.

Work through a declaration before announcing the session

Let's develop the fictional hotel conference example. The proposed speaker, Morgan, runs an operations consultancy. Your programme team invited Morgan to explain how hotels should compare housekeeping software. The provisional title promises an independent buying guide, and marketing wants to announce it as a reason to buy the conference ticket.

Morgan declares an ongoing referral agreement with the fictional supplier Alder Systems. Morgan receives payment when an introduced hotel signs an eligible contract. Alder has also provided demonstration access and suggested a customer example. The company hasn't paid your event for the session, and your team originally selected Morgan for their implementation experience.

Those facts don't establish that Morgan's advice is false. They do establish that the original promise needs review. Attendees considering a purchase would reasonably want to understand the referral arrangement. Your programme owner also needs to know whether Morgan can discuss other approaches and explain when Alder's product was unsuitable.

The owner asks for the outline and the evidence behind the proposed comparison. Morgan can provide a detailed account of an Alder implementation, including what the hotel changed in its processes. However, Morgan hasn't evaluated the other systems under comparable conditions. The current deck ranks them anyway and ends with a referral link.

You decide against the independent buying guide in that form. Instead, you propose a moderated implementation interview. It will explain the hotel's original problem, the selection process as Morgan observed it, the changes made and the limits of the account. The unsupported ranking and referral link will be removed. Morgan can identify the product because the implementation would be confusing without it.

Your reviewer then checks whether the revised outline actually delivers that account. They ask for support for a claimed operational improvement and remove it when Morgan cannot provide enough evidence. The case can still explain decisions and difficulties without a dramatic performance claim. Declaring the referral relationship wouldn't have made that unsupported result publishable.

Morgan agrees to the narrower contribution and confirms that Alder won't control the questions or approve the conclusions. Your team agrees a public statement naming the referral arrangement and provided demonstration access. The programme description changes before announcement, and the moderator receives the approved scope and questions.

If Morgan had refused to remove the ranking or allow questions about limitations, your programme owner would decline that contribution. You might separately consider a clearly advertised commercial demonstration if it suits the event. That would be a new offer with its own terms, not a way to preserve the original independence claim.

This is the distinction worth discussing with your team before the first difficult booking. A declared interest starts a decision. The result depends on the promised session, the available evidence and the speaker's willingness to work within an honest description. Collecting the form is only the first part of that work.

Write down what was approved and why

Keep a short decision record alongside the declaration. It should let someone covering for the programme owner see the concern, the agreed action and what remains unfinished. Avoid a status that simply says "conflict cleared". That can conceal conditions that production and marketing still need to carry out.

For the fictional Morgan session, a completed record could read as follows. The names are fictional, and this record shows how your programme team could document its decision.

• Contribution requested: an independent comparison of housekeeping software for hotel operators.

• Interest declared: Morgan receives referral payments from Alder Systems, which also supplied demonstration access and suggested a customer example.

• Concern: the proposed ranking isn't supported by comparable evaluation, and the speaker benefits from purchases of one recommended product.

• Decision: approve a moderated account of a specific implementation after the revised outline is reviewed.

• Required changes: remove the ranking, unsupported improvement claim and referral link; explain the limits of the account; allow questions about alternatives and difficulties.

• Public explanation: name the referral arrangement and supplied access on the session page, in the introduction and in the recording.

• Responsibility: the programme owner approves content, marketing updates the description, and the moderator confirms the delivery brief.

• Remaining condition: do not announce the contribution until the revised outline and disclosure wording are approved.

Notice that the record contains decisions another person can verify. Marketing can check the description, the reviewer can inspect the revised outline and the moderator can explain the questions they will ask. Nobody has to guess whether receiving the declaration automatically authorised the announcement.

Connect this record to your wider conference speaker management process. Use the same session reference and approved version so a replacement deck doesn't escape the agreed conditions. Keep the private declaration restricted while giving each colleague the information needed to perform their part.

If the decision changes, record the new reason and replace the affected instructions. For example, a newly agreed commission for a different supplier may change the disclosure and the scope of a buying discussion. Keep enough history to understand the earlier decision without leaving two competing versions in active use.

Tell attendees what the connection actually is

A useful disclosure names the person, the organisation and the nature of the relevant connection. Use ordinary words. "Morgan receives referral payments from Alder Systems" communicates more than "Morgan has industry partnerships". If the supplied software access also matters to understanding the session, explain that as well.

For an employment relationship, name the role and company. For paid consulting connected to the subject, describe it as paid consulting. For a relevant ownership interest, say that the speaker holds an ownership interest. Avoid making readers work out the relationship from a logo, job title abbreviation or list of organisations without explanation.

The US Federal Trade Commission's endorsement guidance explains that a material connection can affect how people judge an advertising endorsement and that necessary disclosures should be clear. Its application depends on the advertising arrangement and the facts. It isn't a general law requiring the same wording in every conference talk; check the relevant rules when a contribution is promotional.

For your editorial policy, place the explanation where people choose the session and repeat it when the contribution begins. A declaration first shown after a product recommendation gives attendees the context too late. Someone choosing between simultaneous sessions should be able to understand the connection before committing their time.

For the fictional session, you could write: "Morgan receives referral payments from Alder Systems and was given access to its software. This interview examines one implementation. The conference team sets the questions and has reviewed the session for the stated programme purpose." Use that last sentence only when it accurately describes your process.

Don't add "all conflicts resolved" because someone approved the text. The financial relationship may continue. Your team has changed the contribution and explained the connection; it hasn't removed the underlying interest or guaranteed that every opinion is impartial. A specific statement is both more honest and more useful.

For someone reporting no relevant interests under your policy, a possible statement is "The speaker has reported no relevant interests under the conference's disclosure policy." That describes the information you received. It doesn't claim your team has independently investigated every financial or personal relationship in the speaker's life.

Review the presentation as well as the declaration

The declaration tells you what interests the speaker reports. It doesn't tell you whether the proposed talk is accurate, useful or consistent with the approved contribution. Read the outline and presentation against the session promise, including any conditions you set after reviewing the declaration.

Check where evidence comes from and what it actually supports. A case study supplied by the connected company can be relevant, but attendees should understand the source and its limits. Don't present the supplier's selected customer account as an independent comparison of the whole market. Ask the speaker to explain how the example was chosen.

Look at the practical advice too. A session can avoid naming a product while teaching a buying checklist that only one supplier could satisfy. Ask why each criterion matters to the audience and whether the explanation acknowledges realistic alternatives. The issue is the substance of the advice, not how many logos appear in the deck.

Avoid demanding an artificial balance of every possible view. A specialist can make a strong argument supported by evidence without presenting all approaches as equally good. Your reviewer needs to distinguish a defensible opinion from concealed promotion, an unsupported comparison or a conclusion dictated by a commercial relationship.

Put the disclosure in the approved presentation and moderator brief. Check that it is readable, explained in speech where appropriate and connected to the right contribution. A page of tiny company names shown during a hurried introduction doesn't help delegates understand which relationship affects the talk they're about to hear.

Use the conference speaker briefing guide for the wider delivery instructions, then add the specific editorial conditions. Tell the speaker what to do if a question touches a restricted subject and who can approve a late change. The moderator should know the boundary without having to read private declaration details.

Give accredited education its own review

If you're offering professional credit, confirm the relevant accreditor's requirements before applying a general conference policy. The body may define which relationships matter, who is eligible to control content, what action is required and when learners must receive information. An ordinary declaration and moderator briefing may be insufficient.

For example, the Accreditation Council for Continuing Medical Education's Standard 3 requires covered providers to collect financial relationships with ineligible companies, a defined category of healthcare product businesses, over the preceding 24 months, without a minimum amount. Providers assess relevance, take appropriate steps before people assume their roles and disclose relevant relationships to learners before education begins. The standard also excludes certain owners and employees from controlling content, subject to specified exceptions, and includes activity exceptions.

That is a particular accreditation framework, not a worldwide conference rule. Have the responsible provider apply the full current requirements to the actual contribution. Don't assume the moderated interview in our fictional business example would qualify as accredited healthcare education simply because the connection is declared and the questions are independently selected.

Keep commercial sessions and accredited learning clearly identified in the programme. If a proposed change alters eligibility, stop and resolve that with the provider before retaining a credit claim. Selling a ticket that promises recognised learning creates an expectation your general editorial approval cannot establish by itself.

Handle new information without making a public accusation

A speaker may report a new role after approval, or an attendee may raise a connection your team hasn't seen. Start by establishing the facts and the effect on the session. A public profile might be outdated, and an allegation might confuse two people. Don't publish a conclusion before checking what the evidence shows.

Ask the speaker about the specific information through your established contact route. Explain what needs clarification and when a decision is required. If the uncertainty affects an essential part of the session, pause the announcement, distribution or contribution while the responsible owner reviews it. Record the temporary decision without presenting an unresolved allegation as fact.

If a relevant connection is confirmed, revisit the original approval. Can you update the disclosure and still deliver the promised contribution, or does the new fact require a change in scope? Consider what people have already bought or selected. A major change may require direct communication and advice on the event's contractual obligations.

Agree the event-day response in advance. A moderator can ask for a clarification, remind the speaker of the agreed scope or move to another question. They shouldn't improvise a public investigation into private finances. If the contribution cannot continue within the approved conditions, the named programme lead should decide the next action under your event arrangements.

For example, suppose Morgan begins recommending Alder through a new commission link despite the agreed interview format. The moderator can state the relevant referral relationship and redirect to the implementation account. If Morgan persists, the programme lead can move to prepared audience questions within the approved scope, or close the interview under the agreed event arrangements. That response addresses observable behaviour without inventing an allegation about motives.

Treat the commercial consequences separately. Ending a contribution doesn't automatically establish a right to withhold a speaker fee or avoid a refund obligation. Follow the agreement and applicable requirements, with qualified advice where needed. Your declaration policy should support an editorial decision rather than promise powers your event doesn't have.

Keep the disclosure with recordings and corrections

When you publish the replay, preserve the explanation of relevant interests. An editor may naturally trim introductions to get to the content sooner. If the disclosure disappears with that introduction, someone watching the recording receives a different account of the speaker's relationship from someone in the room.

Review excerpts individually. A clip containing a product recommendation may be shared without the original programme page or opening statement. Decide what context needs to travel with it before release, including any applicable advertising disclosure. Don't assume a link to the full conference recording will give every viewer the missing information.

If new information affects a released session, assess the correction with the programme owner. Identify the missing or inaccurate statement, its effect on the contribution and the people who received it. You might need a corrected session page, an amended recording or a direct message to affected ticket holders. Choose the remedy for the actual problem.

State what changed clearly. "We have added Morgan's referral relationship with Alder Systems, which was missing from the published session description" is more informative than "We have updated our records". If you're still checking facts, say what is being reviewed without implying that an unverified concern has been established.

Loopyah's attendee email tools let you build and test a message and communicate event updates to ticket holders. That helps when a programme correction needs to reach the people attending your event. Your team still has to decide what to explain, check the message and update the session information and recording wherever necessary.

Keep the correction proportionate without hiding it. A spelling correction in a company name may only need an accurate replacement. A missing financial relationship relevant to a buying recommendation deserves a clearer explanation. Decide whether the original advice also needs review, rather than treating every problem as a missing line of disclosure.

Keep private information out of the public handover

Your declaration record may contain details that help a reviewer but don't belong in the programme. Decide what you need for assessment, what attendees need to understand and who needs access to each. Those are related decisions, but the answer isn't automatically to publish the whole form.

For a relevant personal connection, the public explanation may only need enough information to explain why another person made the editorial decision. You don't necessarily need to identify a family member or describe private circumstances. Work through the wording with the responsible person, while preserving whatever information the audience or applicable rules require.

The UK's Information Commissioner's Office explains in its data minimisation guidance that personal data should be sufficient for the stated purpose, relevant and limited to what is necessary. The guidance is under review following UK legislation. For a UK programme, check the current requirements when designing the process; don't collect private details merely because they might become useful.

Give marketing the approved public statement. Give the moderator the disclosure and contribution boundaries. Keep supporting private correspondence with the people making the decision. Avoid circulating an entire declaration spreadsheet to every room producer or asking a speaker to upload sensitive information into a folder shared with other presenters.

Choose a retention period for the actual purpose and applicable obligations, including any accreditation or dispute requirements. Explain it to speakers and review the records when that period ends. Don't assume you need all private supporting documents indefinitely because the recording remains online. An approved public statement and a private checking record serve different purposes.

Test the policy before the next invitation

Before using the policy across a programme, take a small set of realistic contributions through it. Try an employed specialist, a consultant with referral income and a reviewer assessing a former colleague. Ask your team what information it would request, who would decide and what the attendee would read.

Include a case where your commercial lead wants the contribution to proceed but the programme reviewer requires a change. Can the named decision maker settle it before a promise is made? If everyone expects someone else to take responsibility, fix that now. A form cannot compensate for an approval process your team cannot explain.

Then test a late change. Ask production to find the approved disclosure and confirm what happens if a replacement presentation omits it. Ask marketing which session description is current. Ask the moderator what they would say if the speaker starts promoting an arrangement that wasn't part of the approved contribution.

For your next speaker invitation, start with the session promise and send the declaration request alongside it. Name the person who will review the response and leave enough time to change the contribution before announcement. The useful result is a session you can describe honestly, with a speaker who understands the conditions and attendees who can judge the perspective they're hearing.