A conference is a content product
with a hard date.

The call for papers and the invitation list are two different pipelines: Open submissions give you volume, range, and a fairness story. Direct invitations give you the names that sell tickets. Most conferences run both at once and then discover the reviewed track and the invited track were never compared against each other, so the programme has three talks on the same subject and nothing on the one people asked for.

Review needs a rubric written before the first submission arrives: Without one, review becomes a taste contest that different reviewers score on different axes. Agree what you are scoring: relevance, originality, the speaker's ability to deliver it, and whether it fills a gap in the grid. Put the scores on the board next to the sessions so the shape of the programme is visible while you can still change it.

Scheduling is where the real damage happens: Two strong talks opposite each other means half the room misses one and both speakers feel undervalued. So does putting the deep technical session immediately after lunch, or scheduling the beginner track opposite the only other beginner talk. Lay the grid out visually and the clashes become obvious in a way a spreadsheet never makes them.

Leave a hole on purpose: Someone will drop out. Keeping one reserve session ready, and one flexible slot in the grid, turns a cancellation from a crisis into a swap. Note the standby speakers on the board beside the grid rather than in a private message thread nobody else can find.

Every speaker owes you six things and will send them in random order: A bio, a headshot, a session title, an abstract, a slide deck, and their AV requirements. Some arrive the day they confirm, some arrive after four reminders, and one arrives during the coffee break before their talk. A single view of who owes what is the difference between three chases and thirty.

Tone matters because they are not employees: Most speakers are unpaid, busy, and doing this partly as a favour. Chasing works best when the ask is specific, the deadline is real and explained, and the reason is obvious: the programme goes to print on this date, the website needs the headshot for the reveal post. Keep the reason attached to the request so whoever sends the reminder can say it.

AV requirements are collected late and then cost you an hour: Whether they need audio from the laptop, a clicker, a confidence monitor, a specific adapter, a live demo with internet, or their own machine on stage. Ask at confirmation, not the week before, and put the answer on the speaker card where the AV crew can read it without an email chain.

Deck deadlines exist to protect the transitions: A slide deck that arrives on the morning cannot be loaded onto the house machine, which means a laptop swap, which means the changeover that was supposed to take four minutes takes eleven. Set a deck deadline, state why, and track it on the board so the AV plan is not a guess.

The promise was made months before the plan existed: Logo placement, a stage mention, a workshop slot, a booth position, an attendee list, a scanned lead count, a slide in the holding loop. Each was sold by someone in a conversation, and each has to be true on the day. Write every deliverable on the board attached to the moment it happens, not in the contract PDF only the salesperson has read.

Sponsor content is content, so it belongs in the calendar: A sponsored session needs promoting like any other session. A logo needs to be on the right assets before they ship. Keeping sponsor obligations inside the marketing calendar rather than beside it is what stops the awkward post-event email asking why their name was not on the agenda page.

Booth logistics have their own lead times: Access times, power, wifi credentials, shipping addresses for their materials, furniture, and who lets them in on the morning. None of it is complicated and all of it is a phone call at seven in the morning if it was never written down where the venue team can see it.

Photograph what you promised, on the day: The renewal conversation happens with evidence. A shot of their branding in the room, their stage mention, their busy booth, and the session they sponsored is worth more than a spreadsheet of numbers. Put a capture list on the run of show so somebody is actually assigned to take them.

Write a run of show per room, not one for the event: Each room has its own chair, its own AV operator, and its own sequence. One combined document forces everybody to read past the parts that are not theirs, which is exactly how a cue gets missed. One page per room, with the doors, the intro, the talk, the questions, and the changeover, each with a name beside it.

The transitions are the part that breaks: Mic handover, laptop swap, the next speaker being found, the chair's introduction, the room being reset, the overrunning question that eats the changeover. Budget real minutes for each of these and the day holds. Assume they are instant and every room drifts by twenty minutes before lunch.

Decide the recording plan before the day, not during it: Whether every room is recorded or only the main stage, whether you capture a clean feed of the slides, whether speakers have consented, whether questions from the floor are picked up on a mic, and who holds the files afterwards. This single set of decisions determines whether you have a year of content or a folder of unusable footage.

Plan the on-site and post-event content while you can still staff it: Photography, social clips, quote cards, and the recap post all need somebody assigned in advance, because on the day everyone is busy. Put the capture list on the run of show so it competes for attention at the same time as everything else rather than after everything else.