Panel Submissions and Convention Programming: From Open Call to Published Schedule

Last updated: April 2026. This article is for informational purposes only. Statistics and third-party features referenced may have changed since publication. Terms apply.

Programming is the heartbeat of any convention. The panels, workshops, presentations, and Q&A sessions that fill your schedule rooms are often the primary reason attendees buy tickets. Yet most convention organizers still build their programming lineup the same way they did twenty years ago: the programming director and a small inner circle brainstorm ideas, reach out to people they already know, and cobble together a schedule over email threads and spreadsheets.

There is a better way. An open panel submission process -- where anyone in your community can propose a session -- produces a richer, more diverse, and more relevant schedule. It surfaces voices you would never have found on your own, creates community investment in the event before a single badge is scanned, and gives you the structured data you need to evaluate proposals fairly and build your schedule efficiently.

This guide walks through the entire panel submission lifecycle, from designing your submission form through review, approval, schedule integration, and post-event feedback. If you have ever tried to manage this process with Google Forms and email, you know the pain. Convention-specific platforms like Confanum have purpose-built submission workflows that eliminate most of that manual overhead -- something generic ticketing tools like Eventbrite simply do not offer at all.

Why Open Panel Submissions Improve Your Programming

The case for open submissions goes beyond convenience. It fundamentally changes the quality and character of your programming.

Diversity of voices

When a small team brainstorms programming ideas internally, they draw from their own networks, interests, and blind spots. The result is a schedule that reflects a narrow slice of your community. Open submissions bring in proposals from people with different backgrounds, expertise, and perspectives. A first-time panelist with deep knowledge of a niche topic will never appear on your radar unless you give them a way to raise their hand.

This is especially important for conventions that serve broad fandoms or industries. Your attendees are not a monolith. A pop culture convention might have attendees who are passionate about anime, horror, tabletop gaming, indie comics, accessibility in media, cosplay construction techniques, or the business side of creative work. No programming director can be an expert in all of these areas. Open submissions let the community tell you what they want to talk about.

Community buy-in and ownership

When someone submits a panel proposal, they become invested in your event months before it happens. They tell their friends about the panel they proposed. If accepted, they promote it on social media. They buy tickets early. They recruit co-panelists. This organic marketing is invaluable -- and it costs you nothing beyond the effort of running the submission process.

There is a psychological dimension too. Attendees who see that your programming came from community proposals -- rather than being handed down by organizers -- feel a stronger sense of belonging. The convention becomes something they helped build, not just something they attended.

Better data for better decisions

A structured submission form gives you consistent, comparable data across every proposal. Instead of parsing free-form emails to figure out what someone is actually proposing, you have standardized fields for format, duration, audience level, content rating, and technical requirements. This structured data makes review faster, scoring more objective, and schedule building dramatically easier.

Designing Your Submission Form: What to Ask For

The design of your submission form is critical. Ask too little and you will not have enough information to evaluate proposals or build your schedule. Ask too much and you will scare away potential submitters, especially first-timers who are already nervous about proposing a panel. Aim for a form that takes 15-20 minutes to complete thoughtfully.

Panel title and description

The title should be concise and descriptive -- something that works in a schedule listing and on the mobile app. Set a character limit (80-100 characters is reasonable) to prevent unwieldy titles. The description should explain what the session covers and why attendees should care. This is the copy that will appear in your published schedule, so encourage submitters to write for an audience, not for reviewers. A 150-300 word range works well.

Session format

Not every session is a panel discussion. Give submitters a dropdown or radio button selection:

• Panel discussion -- multiple speakers, moderated conversation, audience Q&A
• Workshop -- hands-on, interactive, often with limited seating
• Presentation or lecture -- single speaker, slide-based, educational
• Q&A / AMA -- audience-driven questions with a featured guest or expert
• Screening or watch party -- viewing content together with discussion
• Performance or demonstration -- live demo, reading, or showcase

The format directly affects room assignment (workshops need tables, presentations need a projector and screen), capacity planning (workshops are often capped at 20-30 people), and scheduling (performances may need sound checks or setup time).

Panelist names and bios

Collect the name, a short bio (100-150 words), and contact email for every proposed panelist. If the submitter is organizing a panel with multiple speakers, they should list all of them at submission time. This prevents the awkward situation where you approve a panel only to discover the submitter has not actually confirmed their co-panelists.

Consider also asking for each panelist's pronouns and any accessibility needs. This information helps your panel room moderators make proper introductions and ensures you can accommodate everyone.

AV and technical requirements

Ask what equipment the session needs. Provide checkboxes for common items:

• Projector and screen
• Laptop (provided by panelist or by convention)
• Microphones (how many, handheld vs. lavalier)
• Audio playback capability
• Whiteboard or flip chart
• Internet access (specify wired or Wi-Fi)
• Special setup (tables for workshop materials, demo equipment, etc.)

This field is often overlooked, but it has a direct impact on room assignment. A panel that needs a projector cannot go in a room without one. A workshop that requires tables for 25 participants needs a different layout than a standard theater-seating panel room. Capturing this at submission time prevents last-minute scrambles.

Time slot preferences and conflicts

Ask submitters when they are available and when they are not. The simplest approach is to provide your convention's time blocks (e.g., Friday evening, Saturday morning, Saturday afternoon, Saturday evening, Sunday morning) and let submitters check all that apply for availability and flag any hard conflicts.

If your panelists are also attending specific events -- a cosplay contest, a celebrity photo op, another panel they want to see -- knowing this upfront avoids the painful process of publishing a schedule and then fielding a wave of "I can't actually do that time slot" emails.

Target audience and content rating

Ask submitters to identify who their session is for:

• Experience level: Beginner, intermediate, advanced, or all levels
• Age appropriateness: All ages, teens and up (13+), adults only (18+)
• Content warnings: Does the session discuss mature themes, graphic content, or potentially sensitive topics?

This data feeds directly into your schedule. You can filter sessions by audience level in your app, ensure 18+ panels are scheduled in appropriate rooms (ideally with badge-check at the door), and flag sessions that need content warnings in the program listing.

Setting Submission Windows and Deadlines

Open your submission window 4-6 months before the event. This gives submitters time to develop their proposals thoughtfully and gives your review team time to evaluate them without rushing.

A typical timeline looks like this:

• 6 months before event: Announce that panel submissions are coming. Tease it on social media. Let people start thinking about ideas.
• 5 months before: Open submissions. Promote heavily for the first two weeks.
• 3.5 months before: Submission deadline. Send reminders in the final week. Consider a short grace period (2-3 days) for late submissions, but be firm after that.
• 3 months before: Review period. Your committee evaluates all submissions.
• 2.5 months before: Send acceptance, waitlist, and rejection notifications.
• 2 months before: Publish the schedule. Announce programming lineup publicly.

The most common mistake is opening submissions too late. If you open submissions only 8 weeks before the event, you are compressing every subsequent step -- review, notification, schedule building, promotion -- into an impossibly tight window. Give yourself breathing room.

The Review and Approval Workflow

This is where most organizers struggle, because the review process is inherently subjective and often politically sensitive. A clear, documented workflow makes it fairer and more efficient.

Review criteria and scoring rubrics

Define your evaluation criteria before a single submission arrives. Common criteria include:

• Relevance -- Does this topic fit your convention's focus and audience?
• Originality -- Is this a fresh take, or has this exact panel been done at every convention for the past five years?
• Speaker qualifications -- Do the proposed panelists have credible knowledge or experience on this topic?
• Description quality -- Is the proposal well-written and clearly articulated? A poorly written submission often signals a poorly prepared panel.
• Audience demand -- Does this fill a gap in your programming, or do you already have three panels covering similar ground?
• Feasibility -- Can you actually deliver what this session requires (equipment, room size, time slot)?

Use a simple scoring rubric: rate each criterion on a 1-5 scale. This makes it easy to compare submissions and resolve disagreements with data rather than opinions.

Committee review vs. single-curator model

Small conventions often have a single programming director who reviews everything personally. This works when you have 30-50 submissions. At scale -- 100, 200, or more submissions -- a review committee is essential.

A committee of 3-5 reviewers, each scoring independently, produces more balanced results. Average the scores to create a ranked list, then meet to discuss borderline cases. This approach reduces the risk of personal bias driving the entire schedule and distributes the workload.

If using a committee, assign submissions by track or topic area. Your tabletop gaming expert should review the gaming panels. Your cosplay coordinator should review the crafting workshops. Domain expertise makes reviews faster and more accurate.

Communicating acceptance, waitlist, and rejection

Every submitter deserves a response, even if it is a rejection. Radio silence is the fastest way to damage your convention's reputation in the community.

For accepted panels, send a congratulatory email that includes: the confirmed session title, assigned time slot (if available), room details, any logistical information (arrival time, green room access, AV setup), and a deadline to confirm participation.

For waitlisted panels, be honest about the situation. "We received more strong proposals than we have schedule slots. Your panel is on our waitlist and we will notify you by [date] if a slot opens up." Set a date after which waitlisted submitters can assume they are not on the schedule.

For rejected panels, be respectful and constructive. A brief reason helps: "We received multiple proposals on this topic and selected the one that best fit our schedule," or "This topic fell outside the scope of our programming this year." Encourage them to submit again next year. Many of your best panelists will be people who were rejected the first time and came back with a stronger proposal.

Converting Approved Submissions into Schedule Items

This is the step where convention-specific tools pay for themselves. In a manual process, you are copying data from a submission spreadsheet into a separate schedule spreadsheet, then manually entering it into your app or website. Every copy-paste is an opportunity for errors -- wrong room, wrong time, misspelled panelist name.

With a purpose-built panel submission system, approved submissions convert to schedule items with a single action. The title, description, panelist names, format, and technical requirements flow directly into your schedule. No retyping. No copy errors. The panelist who submitted the proposal sees their session appear in the published schedule exactly as they wrote it.

This is a capability that generic event platforms simply do not have. Eventbrite, for example, has no concept of a panel submission. There is no way for a community member to propose a session, no review workflow, no approval pipeline, and no conversion to a schedule item. You would need to bolt together multiple third-party tools -- a form builder, a spreadsheet, a review system, a schedule builder -- and manually bridge the gaps between them. For conventions with 50 or more panel submissions, that manual bridging becomes a significant time sink and error source.

Handling Schedule Conflicts and Room Assignments

With approved panels in hand, you now face the puzzle of fitting them into your available rooms and time slots. This is part art, part science.

Room assignment considerations

• Capacity matching. Put your highest-demand panels in your largest rooms. A celebrity Q&A in a 50-seat room will create overflow crowds and frustrated attendees. A niche workshop in a 500-seat ballroom will feel empty and awkward.
• Technical requirements. Match panels to rooms that have the equipment they need. This is where capturing AV requirements at submission time pays off -- you can filter and sort by requirements rather than guessing.
• Content segregation. 18+ panels should be in rooms away from the kids' programming area. Loud performances should not be next door to quiet discussion panels.
• Traffic flow. Spread popular sessions across different areas of your venue to distribute foot traffic. If your three most popular panels are all in adjacent rooms, the hallway becomes impassable.

Avoiding panelist conflicts

If a person is speaking on multiple panels, those panels obviously cannot overlap. This sounds simple, but it becomes complex quickly. Panelist A is on Panel 1 and Panel 3. Panelist B is on Panel 2 and Panel 3. Now Panels 1, 2, and 3 all need different time slots, even though A and B are never on the same panel together.

Build your schedule in passes. First, place your largest and most constrained sessions (celebrity panels, events tied to specific times, sessions requiring unique equipment). Then layer in the medium-demand panels. Finally, fill remaining slots with smaller sessions. At each step, check for panelist conflicts before locking in the time.

Attendee experience conflicts

Beyond panelist availability, consider what your attendees want to see. If your two most popular panels are at the same time, you are forcing attendees to choose -- and they will be unhappy about it regardless of which one they pick. Look at topic clustering: try not to schedule all of your cosplay panels in the same time block, or all of your gaming panels on the same morning. Spread related content across the schedule so attendees with specific interests can attend multiple sessions.

Managing Last-Minute Changes and Cancellations

No matter how carefully you plan, things will change. A panelist gets sick. A speaker's flight is canceled. A room develops an AV problem. Your ability to handle these disruptions gracefully is what separates a professional convention from an amateur one.

Build in buffer

Do not schedule your rooms at 100% capacity with no gaps. Leave at least one open slot per room per day. This gives you somewhere to move a panel if its original room has a problem, and it provides breathing room for attendees between sessions.

Maintain a waitlist of ready-to-go panels

Your waitlisted submissions are not just rejections -- they are your backup bench. Keep 5-10 waitlisted panels "warm" by communicating with those submitters that they might be called up. If a scheduled panel cancels two weeks before the event, you can slot in a waitlisted panel with minimal disruption.

Real-time schedule updates

When changes happen during the convention itself, you need to communicate them instantly. A mobile app with push notification capability is essential here. When Panel Room B's 2:00 PM session moves to Panel Room D, every attendee who bookmarked that session gets notified immediately. Printed schedules cannot do this. A website that attendees have to manually refresh cannot do this reliably. Push notifications can.

Also update your physical signage. Assign a volunteer specifically to signage updates during the event. Nothing is more frustrating for an attendee than following a printed sign to Room 204 only to find a completely different panel in progress.

Panelist Communication and Logistics

Your panelists are essentially unpaid contributors to your event. Treat them well, and they will come back year after year with increasingly polished presentations. Treat them poorly, and word spreads fast in convention communities.

Pre-event communication

Send a detailed logistics email at least two weeks before the event covering:

• Their confirmed session title, time, room, and duration
• Where to check in when they arrive at the convention
• Whether they receive a complimentary badge (most conventions offer at least a day pass to panelists)
• Green room or speaker lounge location and hours
• AV setup instructions (how to connect their laptop, when they can test equipment)
• Who to contact if they have a problem or need to cancel

Day-of support

Assign a volunteer panel room monitor to each room. This person introduces the panelists, keeps time, manages the Q&A microphone, and handles any problems. A good room monitor makes panelists feel supported and keeps sessions running on time.

Provide water in every panel room. This costs almost nothing and is appreciated more than you might expect. If your budget allows, provide a speaker lounge with snacks, coffee, and a quiet space for panelists to prepare.

Post-event acknowledgment

Send a thank-you email within a week of the event. If you have session feedback data, share the highlights with each panelist -- "Your session was rated 4.6 out of 5 by attendees" is enormously motivating. Invite them to submit again next year. Building a returning cadre of experienced panelists is one of the best things you can do for your programming quality over time.

Promoting Your Programming Lineup

Your programming schedule is a marketing asset. Use it.

Once the schedule is finalized, promote it in phases:

• Headline panels first. Announce your biggest, most exciting sessions individually with dedicated social media posts. Give each one a moment in the spotlight.
• Track highlights. "Check out our gaming programming this year" with a curated list of the best gaming panels. This targets specific audience segments and gives people a reason to buy tickets even if the headliners alone did not convince them.
• Full schedule release. Publish the complete schedule on your website and in your mobile app. Make it filterable by track, day, and room. Encourage attendees to build their personal schedules in the app.
• Panelist amplification. Give your panelists social media graphics they can share. "I'm presenting at [Convention Name]!" posts from 50+ panelists create a ripple effect that no amount of paid advertising can match.

Every programming announcement is an opportunity to link back to ticket sales. Do not be shy about including a "Get your tickets" call to action alongside schedule announcements.

Post-Event: Collecting Session Feedback and Planning Next Year

The submission cycle does not end when the convention is over. Post-event feedback closes the loop and makes next year's programming even stronger.

Attendee session ratings

Collect feedback on individual sessions, not just the convention as a whole. A simple 1-5 star rating with an optional comment field gives you actionable data. Which sessions were the highest rated? Which had low attendance despite an interesting topic (indicating a scheduling or promotion problem)? Which topics generated the most demand for follow-up sessions next year?

In-app ratings collected immediately after a session ends produce much higher response rates than post-event email surveys. Attendees are willing to tap a star rating on their phone while walking to the next panel. They are much less likely to fill out a survey three days later.

Panelist self-assessment

Ask panelists how their session went from their perspective. Did they have enough time? Was the room appropriate? Did the AV equipment work? Was the audience the right size? Panelists see things that attendees and organizers miss, and their feedback improves your logistics for next year.

Review team retrospective

After the event, convene your review committee for a brief retrospective. Which types of submissions produced the best sessions? Were there topics you wish you had received more proposals for? Did your scoring rubric accurately predict session quality? Refine your criteria and process based on real results, not just assumptions.

Building your submission pipeline for next year

The best time to recruit next year's panel submissions is immediately after this year's convention. Attendees are energized. Panelists are thinking about what they would do differently. First-time attendees who were inspired by a session are thinking, "I could do something like that."

Announce next year's dates and tease the submission window before attendees leave the building. Collect email addresses specifically for "programming updates" so you can notify them when submissions open. The conventions with the strongest programming are the ones that treat the submission pipeline as a year-round effort, not a one-time task.