The contract lands on my desk already signed. Sales did their part months ago, negotiated the room block, the meeting space, the food and beverage minimum, and now the file is mine. From this point until the last pipe-and-drape rolls out the door, running the conference is my job, and the difference between a smooth one and a rough one is almost never talent on the show days. It is the work nobody sees in the weeks before.
People imagine event management as the visible part, the walkie-talkie in the ballroom, the fast decisions when a session runs long. That part is real, but by the time you are onsite, the outcome is mostly already decided. A conference is won or lost in the handoffs: sales to events, events to the operating departments, one day to the next, and finally the property back to a clean slate. Here is the full arc, the way I actually run it.
Reading the file the sales team hands over
The first thing I do is read the contract like it is going to be tested, because it will be. Every promise in it is now my problem to deliver. I want to know the room block and its cutoff, the meeting space and the hours it is held, the food and beverage minimum, the concessions sales agreed to, and any clause with a date attached. The handoff from sales to events is the first place a conference can quietly go wrong, because a promise made in the sales process that never reaches operations becomes a broken promise onsite.
If you want the full picture of what the selling team actually commits to, I laid it out in what sales and catering does. My job starts where theirs leaves off, and the cleaner that handoff, the fewer surprises later. I would rather spend an hour with the salesperson walking through the file than discover on day one that the client was promised a stage the contract never mentioned.
Out of that contract I build the document that runs everything: the banquet event order, or BEO. The BEO is the single source of truth for every function, every meal, every room set, every timing. It is what the kitchen cooks from, what the banquet team sets from, what audiovisual builds from. If it is not on the BEO, it does not happen, and if it is wrong on the BEO, it happens wrong. Getting the BEO right is most of the job.
The weeks before: turning a contract into a plan
With the file understood, the middle stretch is quiet, detailed, and where the conference is actually built. The block behaves like any group block, and the mechanics I described in how groups and room blocks work all apply here: I am watching pickup against the commitment, watching the cutoff, and staying in contact with the planner so nobody is surprised by attrition or a rooming list that shows up late.
Alongside the rooms, I am building the event itself with the client. That means locking the agenda, because the agenda drives everything downstream. Every session start and end sets a room turn. Every meal and break sets a kitchen timing. Once the agenda is firm, I can build the room sets, the meal counts, the audiovisual needs, and the flow of people through the space. A conference is really a choreography of moving hundreds of people between rooms, and it only works if the timings connect.
This is the phase where I chase the details that always slip if you let them:
- Guarantees. The client owes me final headcounts a few days out. I chase these early, because the kitchen orders and staffs against them, and a late guarantee forces a scramble.
- Rooming list. A clean list a week out lets the front desk pre-assign and pre-block. A vague one means arrival day gets improvised at the counter.
- Audiovisual. The most common day-of failure is a room that will not project. I confirm every session's technical needs against the BEO and make sure the AV team has walked the rooms.
- Special requests. Dietary needs, a green room, early access for a client's own vendor. Everything the client asks for goes on the BEO or it will not be there when they look for it.
- Vendor coordination. Outside decorators, entertainers, and production crews need load-in times, dock access, and a point of contact. I set those windows so vendors are not colliding with our own setup.
None of this is glamorous. All of it is the actual work. By the time I walk into the pre-con meeting, the conference should already be built on paper, and the meeting is where I prove it.
The pre-con: getting the whole building on the same page
The pre-conference meeting, the pre-con, is the hinge of the entire event. A week or so out, I get the client and every department that touches the conference in one room: front office, housekeeping, banquets, the kitchen, audiovisual, engineering, security if needed. We walk the BEO together, front to back.
The point of the pre-con is not to inform people. It is to catch the gap between what the client thinks is happening and what each department has planned. This is where you discover that the client expects the general session room flipped to a dinner set in ninety minutes and banquets budgeted three hours, or that the keynote needs a hard start the kitchen did not know locked their service window. Better to find it in a conference room a week out than in a ballroom on the day.
I run the pre-con so every department leaves knowing exactly what they own and when. The same principle drives the daily standup that sets the shift: a short, focused alignment beats a long document nobody reads. The pre-con is that standup scaled up to an entire event, and a good one means the show days are mostly execution, not discovery.
The show days: managing what you already built
Onsite, my job changes shape. The planning is done, and now I am the connective tissue, the person who makes sure each handoff lands and each department knows what is coming next. I am walking the space before the client is awake, checking that every room is set to the BEO, that the coffee is hot and out on time, that the general session is ready before the first attendee arrives. The first function of the day sets the client's confidence for the whole event, so I treat the opening like it matters most, because it does.
During sessions I am watching the seams. The break needs to be set before the session ends, not after, or three hundred people hit an empty foyer. The lunch room needs to be ready while the morning session is still running. The room that hosts a workshop at ten needs to be flipped and reset for a different group at two. Each of these is a handoff between departments, and my job is to see the next one coming and confirm it is ready before it is needed.
I also become the client's single point of contact, which matters more than any logistics. When the client has one calm person to bring every question and change to, the event feels controlled even when things move. The agenda will shift. A session will run long, a speaker will not show, the client will want to add a reception on day two. My job is to absorb those changes and translate them into the building without the client feeling the friction. That is the real skill onsite: staying calm, holding the whole picture, and making the next handoff land.
Between days: the overnight handoff
A multi-day conference has a hidden risk, which is the night. The team that runs day one is often not the team that opens day two, and everything I know about the client, the changes made, the room that needs to be reset differently tomorrow, has to survive the gap between shifts. This is exactly the problem I wrote about in running a clean shift handover: information that lives only in one person's head does not make it to the morning.
So I write it down. What changed today, what is different tomorrow, what the client cares about, what to watch. The overnight team resets the space for day two against tomorrow's BEO, and the morning team opens knowing exactly what happened while they were gone. A conference that runs beautifully on day one and falls apart on day two almost always failed at this handoff, not on the floor.
Teardown and the close: the part people forget
When the last session ends, the client is done, but I am not. Teardown is a real operation, and rushing it is how equipment gets lost and the next event's space is not ready. Vendors load out on their windows. Banquets breaks down the sets. Audiovisual strikes the gear. Anything the client is shipping gets staged and labeled. I walk the space to confirm it is returned to a clean slate, because tomorrow that ballroom belongs to someone else, and their event starts with how we left this one.
Then comes the close I never skip: the post-con review and the final bill. I reconcile what actually happened against the contract, the food and beverage minimum, the room pickup, the added charges, so the client's final invoice matches their experience and there are no surprises. A clean, accurate bill is the last handoff of the whole event, and a client who feels fairly billed is a client who rebooks. I also debrief my own team on what worked and what did not, while it is fresh, so the next conference is a little better than this one.
That is the full arc. Contract to teardown, one handoff at a time. The show days get the attention, but the conference is really built in the quiet weeks and held together at the seams. Get the handoffs right and the visible part looks easy, which is the whole idea.
The takeaway
A conference is not a performance you pull off on the day. It is a chain of handoffs you build over weeks and hold together at the seams. Read the contract like it will be tested, turn it into a BEO everyone trusts, align the building at the pre-con, and then onsite just make each handoff land. Do that and the show days feel calm, which is the surest sign the real work happened before anyone arrived.
Questions from the desk
What is a BEO in event planning?
The banquet event order is the master document for a function or event. It lists every meal, room set, timing, and requirement, and it is what the kitchen, banquets, and audiovisual teams execute from. If something is not on the BEO, it does not happen.
What is a pre-con meeting?
The pre-conference meeting brings the client and every department that touches the event together, usually about a week out, to walk the BEO front to back. Its purpose is to catch gaps between what the client expects and what each department has planned, before the event begins.
What is the hardest part of running a conference?
The handoffs, not the show days. Sales to events, events to operations, one day to the next, and the property back to a clean slate. Most conference problems trace back to a handoff that dropped, which is why the quiet planning weeks matter more than the visible ones.
How far in advance is a conference planned?
The contract is often signed months out, but detailed planning intensifies in the final weeks, when the agenda locks, guarantees come in, the rooming list arrives, and the pre-con aligns every department right before the event.