Field notes
How to Host a Side Event at a Big Conference
A small, approval-only room with a clear guest list will do more than a loud party you cannot remember the next morning.
A side event is a gathering that happens around a larger conference or a citywide week, but is not the main stage of that program. It might be a breakfast, a dinner, a working session, or a short salon. The host, not the conference organizer, usually chooses the room and the list.
If you want the room to be useful, start with who should be in it, and why. Then keep the list small enough that you can follow up. Logistics matter, but they are not the product. The guest list is.
Official rules change by program. For SF Tech Week, including how to get a listing on the official calendar, use our live SF Tech Week side events guide. This article is the general playbook I would use around any large conference week.
What a side event is for
A citable definition, before the checklist.
A side event is a hosted gathering held during, or next to, a larger conference or week, created so a defined group can meet with a purpose. It is not a substitute for the official program, and a listing on someone else's calendar is not the same thing as a full room.
Name the room around a buyer and a question, not around "networking." "A dinner for security founders who are hiring their first marketers" is a room. "Drinks during the conference" is a calendar block.
Choose a size you can actually run
A tight list, one clear question, and a plan for no-shows.
I trust small rooms during a loud week: a breakfast, dinner, or working session for about 30 people. That size gives people a chance to speak, and it gives you a chance to remember what was said. If the format needs to be smaller, make it smaller. Do not grow the list to make the invite look impressive.
Co-host the room with someone the guests already trust, if you can. Invite-only or approval-only is usually the right default. Ask one screening question that tells you whether someone belongs there. Approve the people you want, and reject the rest quickly so they can go elsewhere.
Plan for no-shows, especially if the event is free. Official programs sometimes publish their own guidance. For SF Tech Week, the official host guide says free events regularly see 50% to 70% or more no-shows, and it tells hosts to approve about 2.5 to 3 times their target attendance (Tech Week, How to Host; also summarized in our SF Tech Week side events guide). That is official guidance for that week, not a universal law. For any other conference, ask the organizer if they publish a rule, and otherwise plan as if a free event will lose a large share of approvals.
Build the list with a reason next to each name
The invite should say why this person belongs in this room.
Write down the accounts and roles the room is for. Then shortlist people the way you would for any other event: why they fit, and whether someone on your team already has a relationship with them. If you cannot write the reason, they wait or come off the list.
A purchased or predicted conference lead list can be an input. It is not the guest list. How to turn a file into a shortlist is in how to use a conference lead list. The operating companions are how to invite the right people to an industry event and how to build an activation guest list from your CRM.
Draft a short invitation around that reason, then have a named person approve it. Your team approves every invite. Personal notes and posts from co-hosts will usually do more than a company page.
Follow the official listing rules when you want to be on a calendar
A listing gets you on the calendar. Filling the room is still your job.
Each program has its own path. Some want a specific ticketing tool, a title format, a neighborhood instead of a street address, or a cap on how many events one host can submit. Those rules belong to the organizer, and they change.
Do not copy another week's process onto a different conference. For SF Tech Week 2027, the official path (including the current Partiful requirement, title tag, and submission cap) is in our SF Tech Week side events guide, which follows the official How to Host guide. Submissions for that week were not open as of the guide's publication, and 2027 deadlines had not been announced.
If you want a simple place to write your own plan down first, use the free Tech Week Pipeline Planner. It starts with the buyer and the room you are considering. It does not fetch listings, and it does not promise admission.
Write the next step while you still remember it
The room is only useful if the follow-up happens.
Right after each conversation, write three things in one place: what you talked about, what you promised, and who owns the next step. Send that follow-up the next morning, after a named person has approved it.
Swapcard's study of 2,000 events and 2.5 million attendees found that fewer than 15% of exhibitors downloaded their final lead reports within 10 days of the show (PCMA, sponsored by Swapcard, December 2024). In Bizzabo's 2026 benchmarks, only 15% of organizers rated their own networking as very effective, down sharply from the year before (Bizzabo, event marketing statistics 2026). A well-hosted room still needs a written next step.
For measuring the work later, see How to Measure Event Marketing ROI. The operating companion is our guide on how to measure pipeline from field events.
How Marvelous can help
The software prepares the work. Your team approves every invite.
Marvelous is B2B event-focused GTM software plus services. It helps you start from the room's goal, shortlist the people who belong there with a visible reason, and draft invites and follow-up for review. People make every decision. Pricing is proposal-based, scoped to your launch or event plan, with no public price list (Marvelous pricing).
If you are considering a side event this season, bring the accounts that matter and the room you have in mind. We will walk through the shortlist and what your team would approve before anything goes out.
Related: how to choose SF Tech Week side events, and the event outreach playbook for a small GTM team.
Related: Sponsorship, Booth, or Dinner: How to Spend a Conference Budget.
FAQ
What is a side event?
It is a hosted gathering held during, or next to, a larger conference or week, created so a defined group can meet with a purpose. It is not the official main program.
How do I host a side event at a big conference?
Name the room around a buyer and a question. Keep the list small enough to run, usually around 30 people for a dinner or breakfast. Invite or approve with a visible reason, plan for no-shows, follow the official listing rules if you want to appear on a calendar, and write the follow-up the next morning.
How many people should I invite?
Invite for the room you can actually host, not the largest list you can build. I would start around 30 confirmed guests for a conversation-heavy breakfast or dinner, and approve more than that if the event is free and no-shows are likely. Official programs may publish their own ratios.
How do I get my side event listed on an official calendar?
Follow that program's current rules. For SF Tech Week, see the live side events guide. Do not assume another conference uses the same tool or the same deadline.
Does Marvelous send the invitations for me?
No. Marvelous can prepare drafts. Someone on your team approves every invite and every follow-up before it goes out.
How is Marvelous priced?
Pricing is proposal-based. Every program is scoped to your launch or event plan. There is no public price list. Details are on the Marvelous pricing page.