How to check a conference speaker's credentials before booking

You've found a speaker with the right subject, a convincing biography and a well-edited showreel. Now you need to decide whether to put your event's name behind theirs. What have they actually done, can they explain it to your audience, and which parts of the pitch can you safely repeat when you sell tickets?

Start by checking the claims that make this person suitable for the session. Confirm their relevant work with the organisation, publication or professional body behind it. Then assess their ability to deliver the session through a sustained recording, a focused conversation and references from people who commissioned similar work. Keep the booking and public announcement on hold while any essential claim remains unresolved.

That doesn't mean investigating every line of someone's career. It means being clear about what your buyers are relying on. Someone sharing lessons from a project needs a different review from someone teaching a regulated professional technique. Both deserve a fair process, and your team needs a useful answer before it commits money or makes promises.

This guide walks through conference speaker due diligence, the checks you make before booking. You'll get a practical way to verify experience and qualifications, questions for reference calls, an example of a booking decision, and a checking record you can adapt. The aim is to book people you can describe accurately and whose contribution fits the event you're charging people to attend.

Decide what you need this person to establish

The first thing you want to do is write down why you're considering the speaker. Be specific. "A respected business leader" doesn't tell a researcher what to check. "Someone who personally managed a difficult software change across independent hotels" points towards work, responsibility and a useful subject for a session.

Our guide to finding keynote speakers covers building the candidate list. At this stage, you have someone in mind and need to decide whether the proposed booking stands up. You're checking the evidence behind the invitation, including any gaps that a discovery search left open.

Describe the intended audience and what they will be able to understand after the session. A hotel owner deciding whether to replace a booking system needs different experience from a software developer deciding how to build one. The speaker may understand both subjects, but you need evidence for the contribution you're actually buying.

Next, separate essential claims from details that would simply look good in the announcement. If the session depends on having led an implementation, that involvement needs confirming. You can remove an unrelated award without holding up a strong booking. Missing experience that the session depends on needs a different decision.

Include the format in that decision. A practitioner who can explain a project clearly in conversation might be excellent in a moderated interview. A technical workshop requires the ability to teach, respond to mistakes and manage the promised exercise. You can't infer those abilities from a senior role alone.

Write the requirement before reviewing the candidate's evidence. Otherwise, it's easy to keep changing what counts as sufficient because you already like the name. Your team should be able to explain why the same evidence would satisfy it for another candidate with a less familiar employer or fewer followers.

Ask for a focused evidence pack

Send a short request explaining the proposed session and the information you need. Ask for the speaker's current role, the work that relates to the subject, their responsibility for it, and the original sources behind claims they want you to publish. Include a relevant recording and references where those are available.

Tell them what happens next. For example, you might review the material, have a programme conversation, confirm anything essential with the relevant organisation, and agree the public wording before announcement. This makes checking an ordinary part of booking rather than an unexpected interrogation after you've already negotiated a fee.

Ask which details are confidential. A speaker may be allowed to discuss a method without naming the client or revealing results. That can still make a useful session, but it changes what you can verify and promise. Find that boundary before your marketing team writes a dramatic case-study headline.

Don't request a passport, full academic transcript or private client contract as your standard first step. Often an official profile, a qualification verification route or an authorised confirmation will answer the actual question. Collect more only where the proposed work requires it and you can handle it appropriately.

Use a real deadline tied to your own booking decision. Explain that missing material may mean delaying the announcement or considering a different format. A candidate can then tell you early if a former employer is slow to respond or a reference is unavailable. Silence should never quietly become approval.

Keep the request manageable enough for good candidates to complete. You're commissioning a contribution, and the checking work should serve that contribution. If your pack asks everyone for the same long career history regardless of subject, review what each field helps you decide. Remove the fields that nobody will use.

Confirm identity and the organisation behind the pitch

Start with the basics before reading a stack of impressive material. Make sure the person you're speaking to is the person named in the sources, and that anyone negotiating for them is authorised to do so. Similar names, outdated profiles and agency introductions can all create confusion without anybody intending to mislead.

Compare the candidate's supplied details with an official employer or institution page where one exists. Check dates and role descriptions. If the person has moved on, ask how the earlier experience should be described. "Former operations director" can be completely relevant; presenting that role as current creates a different impression.

Use contact details obtained independently when a confirmation matters. A telephone number on the organisation's own website gives you a better starting point than a number supplied in an unexplained message. If you need to verify a representative's authority, ask the speaker through a previously established channel or an official enquiry route.

You don't need an identity document for every speaking enquiry. Decide what uncertainty you're resolving and use the least intrusive reliable method. A brief conversation through a recognised organisation may settle an ordinary booking. A suspicious change in representative or payment instructions needs its own pause and verification.

Keep your identity check separate from bank details and payment approval. Confirming that a person works at an organisation doesn't verify an invoice or a newly supplied bank account. Follow your normal supplier-payment process when the booking reaches that stage, even if the programme team is excited to announce the speaker.

Record what you confirmed, where and when. "Current employer profile checked" is useful only if the next person can find the profile and understand which claim it supports. A screenshot can preserve what you saw, but it doesn't turn an unofficial source into an official one.

Check experience at the level of responsibility you will advertise

The useful question is often smaller than "Has this person worked there?" You want to know what they did. Someone can have worked for a successful company without designing the project in your session title. They can also have done important work that a short public biography barely mentions.

Ask the speaker to describe the starting problem, their own responsibility, the decisions they made and the people involved. Listen for a clear account of what belonged to them and what belonged to colleagues, suppliers or clients. A detailed answer gives you specific points to verify without demanding that one person claim every success.

For a project account, look for a source close to the work. That might be an organisation's published report, a named project account or confirmation from someone authorised to describe the candidate's role. An interview can help, but check whether it adds information or simply repeats the same biography.

Several websites carrying identical wording still lead back to one claim. Don't count a bureau profile, an event listing and a personal website as independent confirmation if all three use the candidate's supplied text. Follow the claim to its origin and decide what remains unverified.

Be precise about the wording you approve. "Helped design staff training" and "led the entire implementation" describe different responsibilities. If only the first is supported, use the first. The session might become stronger when it concentrates on the training decisions the person actually understands.

Ask about recency where it changes the subject. Experience with an older system may explain a useful principle while offering little authority on its current features. You can still book a retrospective session. Make the period and scope visible so buyers aren't promised current operational advice based on historical work.

Verify qualifications through the body that issued or regulates them

A qualification matters when it supports the work you're asking the speaker to do or a title you're planning to use. Start with the exact name of the award, the issuing body and its date. "Certified expert" is too vague to verify and too vague to help a ticket buyer.

Check what the credential actually establishes. Course attendance, passing an assessment, professional membership and permission to practise are different things. A person can accurately hold one without holding the others. Ask the issuing body how verification works, including whether it needs the holder's permission or a reference number.

The UK government's guide to regulated professions explains that some activities and titles have qualification or experience requirements, with regulators listed for the relevant professions. That is UK guidance, not a worldwide rule for who may give a conference talk. Check the profession and jurisdiction relevant to your event.

For a concrete example, the UK's General Medical Council provides searchable professional registers with registration status and related information. If a medical speaker's current professional status matters to your programme, use the relevant regulator's live record. A historic certificate or a photograph in clinical clothing doesn't answer the same question.

Avoid deciding the legal effect of a restriction by guessing. If the record contains conditions you don't understand, ask the regulator or an appropriately qualified adviser what they mean for the proposed contribution. Speaking about personal experience and providing professional instruction may raise different questions. Describe the actual session when seeking advice.

Don't require a degree simply because checking one is convenient. An experienced operator can be highly suitable for a practical business session without an academic credential. Your standard should follow the subject and the claims, while preserving any qualification or authorisation that the proposed activity genuinely requires.

Read research claims beyond the profile page

For an academic or research-led session, confirm that the candidate is connected to the work you're discussing. Open the publication, read the author information and identify what the study actually examined. A paper's title can sound relevant while its setting or research question differs substantially from your audience's problem.

Ask the speaker to explain their contribution in plain language. Being an author doesn't automatically mean they led every element of the research. Equally, someone who did a specialised part may be the right person for your session. Your programme should describe that contribution accurately instead of upgrading everyone to the project leader.

ORCID's guide to research record summaries explains how to see who added affiliations and other information. Some entries come from member organisations and others from the researcher. ORCID also warns that missing information doesn't, by itself, mean a record is problematic. Use the record to investigate a connection, rather than treating it as a quality certificate.

Check the publication's current status through its publisher. Look for corrections, notices or an updated version that affects the proposed claim. If you find a notice, establish what it changes before drawing conclusions about the individual. The existence of a correction and deliberate misconduct are not interchangeable findings.

You don't need to become a peer reviewer. You do need someone able to assess a technical claim when the promise of the session depends on it. Ask an independent subject specialist to review the relevant material if your programme team cannot judge the methods, limitations or practical conclusions.

Keep the advertised outcome within what the evidence supports. Research identifying an association is different from evidence that a particular intervention caused an improvement. A useful speaker can explain those limits. If your sales headline removes them, the problem is now in your event's copy even if the speaker's research is sound.

Test whether results support the story being sold

Measurable business results need more than an impressive number. Ask what changed, how it was measured, over what period and against which comparison. Establish whether the result belongs to one site, a group of businesses, a trial or the organisation as a whole. Those details can change the meaning of the story.

Suppose a candidate says a project "cut operating costs". Ask which costs and what happened to the rest of the operation. A saving in one department may have required additional work elsewhere. You can discuss that trade-off, but a session promising a general method should not hide the conditions under which the example worked.

Also ask who measured the result and whether the candidate can authorise its publication. A confidential presentation shared for your review is not automatically material you can place on a ticket page. Get agreement on the exact public statement or remove the number while keeping any supported description of the work.

The US Federal Trade Commission's advertising and marketing guidance says advertising claims must be truthful, non-deceptive and evidence-based. That is US guidance, and specialised subjects can have additional rules. For your event, review the objective claims you publish rather than assuming a speaker's supplied biography settles your responsibilities.

Ask what buyers might reasonably infer. "Learn the system that doubled sales" can suggest a repeatable result even if the supporting example came from an unusual situation. A more accurate session description might promise an examination of the decisions, evidence and limitations. You can be commercially compelling without promising the audience somebody else's result.

If the result can't be substantiated, decide whether the whole session depends on it. Sometimes removing an unsupported number leaves a strong practical talk. Sometimes the number was the entire reason for the booking. In that case, changing the adjective in the biography won't resolve the underlying decision.

Watch a complete explanation, including the difficult questions

A showreel helps you see presentation style. To assess delivery, watch a sustained section of a relevant talk or interview. You need enough context to understand the argument, how the speaker explains it and what happens when they move beyond the polished opening.

Look for the ability your format requires. Can the speaker explain an unfamiliar term before relying on it? Do examples make sense without knowledge of their employer? Can they distinguish an observation from a recommendation? For a commercial audience, practical relevance matters more than how loudly the room applauds at the end.

Watch audience questions where available. A useful answer may include uncertainty, a request for context or a clear limit on what the speaker can advise. That can be more reassuring than an immediate answer to everything. You're looking for judgement as well as fluency.

Treat the recording's context fairly. A technical lecture for specialists may use language your audience won't know. A remote interview may reveal little about managing a workshop. Ask whether the candidate can adapt, then test the relevant part rather than rejecting them because an unrelated recording serves a different audience.

For a first-time speaker, use a short rehearsal or programme conversation instead. Ask them to explain one important idea and respond to a realistic audience question. Don't ask for a complete unpaid version of a new workshop. Agree a proportionate sample that helps both sides decide whether the format will work.

Record your assessment as an assessment. "Explained the implementation decision clearly in our call" is more useful than "excellent communicator". Include the evidence and any support required, such as a moderator, rehearsal or narrower brief. Strong subject knowledge can justify changing the format rather than abandoning the candidate.

Run the programme conversation around a real audience problem

Come to the call with a situation your buyers recognise. For a hotel-operations conference, you might describe a small business replacing a system while keeping reception open. Ask the candidate which decisions matter first, where the common mistakes occur and what they would need to know before recommending an approach.

Then explore the limits. "When would your method be unsuitable?" often tells you more than another question about achievements. A candidate who understands the work should be able to describe conditions, alternatives and uncertainty. They don't have to solve the entire business problem during a booking call.

Ask which parts they can demonstrate or explain from direct experience. If their strongest contribution is staff training, build around that. If they mainly observed the project as an executive sponsor, discuss whether an interview about governance would be more honest and useful than a technical implementation workshop.

Discuss the proposed audience's knowledge and resources. Advice that assumes a dedicated data team may be unhelpful to an independent operator. Ask how the explanation changes for that reader. Specific adaptation gives you more confidence than a general assurance that every presentation is tailored.

Leave time for the candidate's questions. Good questions about your audience, the session objective and adjacent programme can reveal whether they understand the assignment. They may also identify a mismatch your team missed. A thoughtful decision not to proceed is better than forcing a booking neither side can deliver well.

Finish with a clear record of what remains unresolved. That might be a reference, permission to discuss a client, an updated professional status or a revised session outline. Name who will provide it and the date you need it. Don't let an enjoyable call turn conditional interest into a confirmed announcement.

Ask references about the work you are commissioning

Choose references with relevant first-hand knowledge. A previous organiser can discuss preparation and delivery. A project colleague may confirm responsibility for the work. A client may be able to explain what the speaker actually contributed. One enthusiastic contact rarely answers all those questions.

Ask permission to make appropriate enquiries and confirm each referee's relationship to the candidate. Locate their professional contact route independently where practical. A reference from the speaker's business partner can still contain useful facts, but record that relationship rather than describing it as an independent customer review.

Keep the questions connected to your event. You could ask:

• What did you commission the speaker to deliver, and who was the audience?

• What did they do to understand the brief before the event?

• How closely did the delivered session match the agreed description?

• What happened when the audience asked difficult or unexpected questions?

• Were there any material changes, missed deadlines or corrections, and how were they handled?

• Would you commission them for this proposed format, and what support would you arrange?

Let the referee describe a specific experience before asking for an overall recommendation. "We loved them" tells you less than an account of how they adapted an unsuitable draft or handled a challenging question. Ask what they observed directly and what they heard from someone else.

If the reference concerns project expertise, ask about role and scope instead of stage performance. You may need a separate conversation for delivery. Don't pressure a former colleague to disclose confidential information or offer views on subjects they cannot fairly assess.

A missing reference is an unresolved point, not automatic evidence of dishonesty. Offer another appropriate route where one exists. That could be a different organiser, a relevant recording or an authorised confirmation of work. If an essential requirement still cannot be established, keep the booking unapproved rather than pretending the uncertainty has disappeared.

Check commercial interests before finalising the format

Ask whether the speaker, their employer or a connected business sells something relevant to the proposed advice. Also ask about relationships that could affect the choice of examples, recommendations or products discussed. You need to understand those interests before deciding whether the session is independent education, a practitioner account or a clearly sponsored presentation.

A commercial connection doesn't automatically make the speaker unsuitable. A supplier may know a technical problem extremely well. The issue is whether the format and public description let attendees understand what they are hearing, and whether your programme can maintain the boundaries you've promised.

Agree how the session handles product demonstrations, customer examples and invitations to follow up. If the speaker wants attendee details, resolve that separately. A speaking invitation doesn't establish permission to receive the audience's contact list. Keep the booking conversation focused on the actual rights and responsibilities involved.

Don't let a sponsor's recommendation replace your checks. Ask the same essential questions about expertise and delivery, and record who controls the final programme decision. A fee contribution or a promise to promote the event doesn't verify a qualification or make an unsupported claim publishable.

For sessions sold as sponsorship, our guide to sponsored conference sessions explains how to define the contribution and audience promise. Use the appropriate format openly. Trying to make a commercial presentation look independent creates expectations your team will then have to manage in the room.

Keep disclosure and competence separate in your decision. An accurate disclosure can explain a commercial interest. It cannot supply missing expertise. Likewise, a highly qualified speaker can still have an interest that needs managing. Your record should show how you dealt with each question instead of combining them into one vague approval.

Make a decision without hiding essential gaps in a score

Use a short written decision that says whether the person is suitable for the specific contribution. You can organise observations consistently, but avoid letting a high overall score compensate for an essential claim you haven't verified. Strong delivery cannot establish a qualification, and an impressive credential cannot guarantee useful teaching.

A practical decision can be to proceed, proceed after named conditions are met, change the proposed contribution, or decline. Explain what each means for the booking. If the condition is essential, don't sign an unconditional agreement or publish the original promise while you wait for it.

Changing the contribution can be the best outcome. You might replace a workshop with an interview, narrow a broad claim to one documented project, or pair a first-time practitioner with an experienced moderator. Confirm that the revised format still serves paying attendees and that the candidate agrees to it.

Decide who has authority to approve. The programme lead can own the editorial decision while finance approves expenditure and a specialist advises on a technical issue. Make those roles visible. Otherwise, one person's "looks good" can be mistaken for everybody's approval.

Keep a brief reason for declining. "Cannot establish direct responsibility for the implementation the workshop depends on" is specific and reviewable. "Something feels off" may justify further questions, but it is a poor final record. Give the candidate an opportunity to correct a factual misunderstanding before you close the decision.

Your record should also make the limits of approval clear. Approving a moderated account of one project doesn't approve future claims about every aspect of the subject. If the proposed session changes substantially, review what the new promise requires rather than carrying over an old decision automatically.

A worked example: change the booking before making the announcement

Imagine you're producing a paid conference for independent hotel operators. Everything in this example is fictional. You are considering Alex, whose biography describes them as the leader of a successful hotel-system replacement and an expert in changing operations without disruption. The proposed session is a practical implementation workshop.

Your essential requirement is direct responsibility for planning and delivering that kind of change. You request relevant work, a sustained recording, references and permission to use the project description. Alex supplies a company project account, a presentation and contacts who can discuss the work.

The project account confirms Alex managed staff training. An authorised former colleague explains that another manager selected the system, controlled the budget and led the implementation. Alex confirms this distinction when you ask. The original biography was broad enough to suggest responsibilities they didn't hold.

That finding gives you a reason to reconsider the format. During your call, they explain how reception staff practised unfamiliar tasks, how training changed after problems appeared, and what managers misunderstood about shift coverage. Their strongest material concerns preparing staff. They cannot substantiate the broader implementation claim.

You watch the full presentation and ask a previous organiser about delivery. The recording shows a clear explanation of training choices, and the organiser describes effective preparation for a similar audience. You now have support for a different contribution. You still don't have support for advertising Alex as the leader of the whole system replacement.

The programme lead proposes a moderated session about preparing hotel teams for a software change. Alex agrees. You replace the broad biography, remove the unsupported claim about avoiding disruption and approve a description focused on the training decisions. The agreement records the revised contribution and required preparation.

If Alex insisted on keeping the original claim without evidence, you would decline that booking. If the event genuinely needed an implementation workshop, you would continue searching for someone with the required responsibility. The right decision depends on the programme need, not on rescuing the time already spent evaluating a candidate.

Use a checking record your team can act on

Keep one record for the candidate and proposed contribution. It should be short enough for the approver to read, with links or controlled attachments for the supporting material. The purpose is to show what you established and what decision follows, rather than preserve every page anyone opened.

You can copy these fields and adapt them:

• Candidate, preferred public name and proposed role in the programme.

• Audience, session question, format and the reason this person is being considered.

• Essential claims, including the responsibility, credential or experience required for this contribution.

• Evidence for each claim, the original source, date checked and any limitations.

• Delivery assessment, the material reviewed and any rehearsal or moderation required.

• Reference findings, the referee's relationship and what they observed directly.

• Relevant commercial interests and the agreed treatment in this session.

• Unresolved points, responsible person, deadline and effect on approval.

• Decision, approver, date and conditions that must be completed before contracting or announcement.

• Approved public wording and the changes that require a fresh review.

For the fictional Alex booking, an essential-claim entry would say that direct leadership of the full implementation was not established. It would name the company account and authorised confirmation, then record that Alex led staff training. The decision would approve only the revised moderated session after its outline and public wording were agreed.

A usable decision entry could read: "Candidate: Alex. Contribution: moderated discussion of staff training during a hotel software change. Approved experience: responsibility for training, confirmed in the company account and by the former project colleague. Not approved: leadership of the full implementation or claims of avoiding disruption. Status: pending revised outline and biography. Owner: programme lead. Marketing instruction: hold announcement until the owner confirms both documents are agreed." This is sample wording for the fictional case. In your own record, add the actual source links, check dates and deadline so another person can complete the outstanding work.

Don't replace that explanation with a tick labelled "experience checked". Someone reviewing the record later needs to understand why the original workshop changed. A tick can show a step was completed, but it doesn't communicate what the step found or how the finding affected the event.

Keep opinion visibly separate from verified facts. "The reference confirmed delivery of the agreed workshop" describes a reported fact. "We think the speaker needs a moderator for this audience" is your assessment. Both can be useful if their basis and author are clear.

If another person takes over the booking, have them read the decision and find the essential sources. Ask what they believe is approved. This simple handover can reveal an ambiguous condition before the marketing team or contract owner acts on the wrong interpretation.

Protect the information you collect

Your checking record contains personal information, including opinions and references. Decide why you need each item, who may see it and how long you need to retain it. A public profile being accessible online doesn't mean every private comment about the person belongs in a shared marketing folder.

The UK's Information Commissioner's Office explains data minimisation as keeping personal data adequate, relevant and limited to what is necessary. Its guidance also says records should distinguish opinions and give enough context to interpret them. The page is under review following UK legislative changes, so check current requirements where that law applies.

In practice, your programme team may need the approval decision and conditions, while marketing needs only the approved public facts. Finance needs the contractual and payment information. Those groups don't automatically need every reference note or document used during review. Share the information each job requires.

Tell candidates how you use the information and handle enquiries in a way that respects the rules applying to your business. Avoid collecting sensitive personal history or running broad background checks just because a search service offers them. If the proposed activity requires specialist screening, use the appropriate process with professional advice.

Set a retention decision that fits the booking and applicable obligations. There is no universal number of days that makes every speaker file appropriate. Record your reason, limit access and remove material you no longer need. Correct errors when you establish them rather than preserving an inaccurate note because it appeared in an early draft.

Carry the decision into the agreement and ticket copy

Once the essential checks are complete, make the agreement describe the contribution you approved. That includes the session's scope, preparation, publicity permissions and any agreed boundaries around commercial material. Our speaker agreement template covers the booking terms that need separate attention.

Don't assume a clause saying "the speaker warrants accuracy" replaces the checking you decided was necessary. A contract can define responsibilities and remedies, but it doesn't make an unsupported claim true. If the main reason for the booking is still unresolved, fix that decision before relying on contractual wording.

Approve the actual public biography and session description with the speaker. Our speaker bio template helps turn the checked facts into useful copy. Keep the evidence record private and send marketing the wording it is authorised to use. Otherwise, an old supplied biography can reintroduce the claim you removed.

Check the ticket page as a buyer would. Does the session title promise a method the speaker can actually teach? Does a shortened caption change a contributor into a project leader? Does an employer logo imply involvement beyond the permission you've received? Review those meanings across the places people encounter the booking.

Agree what happens if relevant facts change before the event. A new role, a revised professional status, lost permission to discuss a client or a substantial change of topic can affect the approval. Ask the speaker to tell your named owner, and make that person responsible for deciding which checks and public statements need updating.

Deal with new concerns before they become public confusion

If new information challenges an approved claim, pause the affected promotion and establish what the information actually says. Check the source and identity, ask the speaker for a response, and involve a qualified specialist where the subject requires it. Treat an allegation, a documented finding and a corrected factual error differently.

Don't publish a speculative explanation while you investigate. Keep the people making the decision informed of the specific uncertainty and the next step. If the original promise is no longer supportable, decide whether to correct the description, change the session, replace the speaker or take another action appropriate to your agreement and obligations.

A change that materially affects what buyers purchased may require direct communication and consideration of remedies. Assess that against your terms and applicable consumer law. Quietly removing the disputed sentence from the website doesn't tell existing buyers what changed or resolve every consequence of the original representation.

When an attendee message is needed, Loopyah's attendee email tools let you build a message and select its audience. Use the appropriate ticket-buyer audience for the update and check the message before sending. Your team still decides the facts, the affected group and the response the change requires.

Be clear about the difference between correcting a biography and changing the booking itself. An outdated job title may need an accurate update while the speaker remains fully suitable. A missing essential qualification or an unsupported central claim may require a different decision. Match your response to what you have established.

After the event, add a short delivery note while the details are fresh. Record whether the contribution matched the agreement and what you would change before rebooking. For the next edition, recheck the facts that can change and revisit the proposed session. A successful appearance is useful evidence, but approval should always relate to the contribution you plan to sell next.