You opened your Call for Proposals three weeks ago and now you're staring at 247 submissions, 60 of which are genuinely good, and every single one of those 60 people thinks they should have the keynote slot. This is the speaker management problem, and nobody warns you about it because the people who write event planning guides have apparently never had to tell a well-known industry figure that they've been assigned to the 2:30 PM Tuesday slot in Room C.
The Call for Proposals Inbox Problem
The Call for Proposals is where optimism goes to die. You set it up thinking "we'll get some great submissions and carefully curate the best ones." What actually happens is a tsunami of proposals that range from brilliant to "did this person read our event description at all?" And they all need a response.
The volume isn't even the hard part. The hard part is that CFP submissions arrive in a format that makes comparison nearly impossible. One person writes three paragraphs of detailed session outline with learning objectives. The next person writes "I'll talk about AI" and includes a link to their Twitter profile. A third submits what appears to be their doctoral thesis abstract, complete with citations. You're supposed to evaluate these on a level playing field.
The move here — and I know this sounds obvious but almost nobody does it — is a structured submission form that forces consistency. Title. Abstract under 200 words. Three key takeaways. Target audience. Prior speaking experience (with links, not self-assessments). When everyone fills in the same boxes, comparison becomes possible. When you let people free-text their way through a submission, you're going to unconsciously favor the better writers, which is not the same thing as the better speakers.
Use blind review for at least the first pass. Strip names and affiliations. You'd be surprised how different your rankings look when you can't see that the submitter works at a company whose logo is on your sponsor banner. If blind review feels extreme, at minimum use a scoring rubric. "Vibes-based selection" is how you end up with seven talks about the same topic.
The Art of Saying No Without Making Enemies
You've selected your speakers. Now you have to reject 187 people, some of whom you'll see at industry events for the next decade. This is where most organizers either send a soul-crushingly generic form rejection ("Thank you for your submission. Unfortunately, due to the high volume of proposals...") or, worse, just never respond at all.
Both are bad. The form rejection is forgivable but forgettable. The ghosting is career-damaging — for you, not them. People talk. "I submitted to that conference and never heard back" is a sentence that will follow your event for years.
The right approach takes more effort but pays compound interest: send a personal rejection that includes one specific piece of feedback. "Your proposal on distributed caching was strong, but we had three submissions in that space and went with the one that included a live demo component." That's 30 seconds of writing per rejection, and it transforms a negative into a relationship. That rejected speaker comes back next year with an even better proposal, and they tell their colleagues your CFP is worth the effort.
Speaker Egos and the Keynote Hierarchy
Let's talk about something nobody puts in their event planning blog post: speaker egos. Most speakers are wonderful, professional, easy to work with. And then there are the roughly 15% who will make your life a negotiation exercise that would make a hostage mediator sweat.
The requests start reasonable. "Can I get a longer slot?" Sure, maybe. "Can I present in the main hall?" We'll see. "Can I have a different time slot? I don't do mornings." Okay, we're pushing it. "I need my own dressing room and a specific brand of sparkling water." Sir, this is a tech conference in a Marriott.
The trick is to set expectations early and in writing. Your speaker agreement — you do have a speaker agreement, right? — should spell out exactly what speakers get: their slot length, their room assignment process, what A/V is provided, the deadline for slides, and the fact that you reserve the right to make changes to the schedule. Don't leave room for "but I assumed I'd be on the main stage."
As for the keynote slot specifically: decide your keynotes before the CFP opens. Invite them directly. The CFP is for regular sessions. Mixing these two tracks is how you end up with someone who submitted a breakout session feeling slighted that they weren't "upgraded" to keynote. (This gets even more complicated when you're juggling multi-track conference scheduling.) Separate the processes entirely.
A/V Requirements That Contradict Each Other
Speaker A needs HDMI. Speaker B only has USB-C. Speaker C brings their own laptop but needs audio output for embedded video clips. Speaker D wants to do a live demo and needs hardwired ethernet. Speaker E is presenting from an iPad. Speaker F wants to use two screens. And all of these people are presenting in the same room, back to back, with 5 minutes between sessions for switchover.
This is a solvable problem, but only if you solve it in advance. Collect A/V requirements at least four weeks before the event. Not "what laptop do you use?" but a specific checklist: connector type, audio needs, internet requirements, slide aspect ratio preference, whether they need a confidence monitor. Then hand this list to your A/V team (or your friend who's "good with tech" if you're running lean) and let them tell you what's actually possible.
Buy a $40 adapter kit that covers HDMI, USB-C, Mini DisplayPort, and VGA. Yes, VGA. Someone will need it. Keep it at the A/V desk at all times. This single purchase will prevent more mid-session crises than any amount of advance planning.
Speaker Prep That Actually Helps
Most conferences send speakers a "speaker kit" that contains: a logo file, the WiFi password, and a request to promote the event on social media. This is not speaker prep. This is marketing collateral with a different name.
Real speaker prep means telling people things they actually need to know. What's the room layout? How many people typically attend sessions in their track? Is there a moderator or Q&A mic runner? What's the signal for "you have 5 minutes left"? Can they arrive early to test their setup? Is there a speaker-ready room where they can do a final run-through?
For first-time speakers — and you should absolutely be including first-time speakers in your conference lineup — consider offering a practice session via video call two weeks before the event. Twenty minutes where they can run through their opening, get feedback on pacing, and ask questions they're too embarrassed to ask in an email. This costs you almost nothing and dramatically improves session quality.
The No-Show Contingency You Need
It will happen. A speaker will cancel. Maybe they get sick. Maybe their flight gets cancelled. Maybe they just... don't show up. (It's rare but it happens, and the awkwardness is nuclear.) At 60 speakers, the probability of at least one cancellation approaches certainty. Plan for it.
The simplest approach: identify 3-4 speakers on your roster who you trust and who have flexible material. Talk to them before the event. "If someone drops out, could you do an extended version of your talk, or a bonus session on [topic]?" Most experienced speakers will say yes immediately — more stage time is rarely turned down.
The backup plan for your backup plan: unconference-style sessions. "This slot is now an open discussion on [cancelled speaker's topic]." Attendees often rate these improvised sessions higher than the planned ones, because the format naturally produces more engagement than a one-way presentation.
Speaker management at scale is exactly the kind of problem that outgrows spreadsheets fast. Kagibag handles the full speaker pipeline: structured CFP intake, review workflows, acceptance and rejection communications, A/V requirement collection, schedule assignment, and speaker profile pages that feed directly into your event program. When a speaker cancels at 11 PM the night before, you're updating one record instead of five spreadsheets and a website.
The best conferences aren't the ones with the most famous speakers. They're the ones where the speakers feel supported, prepared, and respected — and where the organizer has systems in place so that a single cancellation doesn't turn into a five-alarm fire. (And once you've survived the event itself, the post-conference followup is where you lock in the value.) Build the infrastructure before you need it. Because the morning of, when your keynote texts you from the airport saying their flight is delayed, you will not have time to improvise a system.