Workshop add-ons and multi-day conference passes

What pass structure should a multi-day conference use?

Here is a pass matrix for a two-day conference with a workshop day in front of it. Copy the shape, change the prices.

Two details do a lot of work here. The workshop is cheaper as an add-on ($199) than as a standalone day ($249), which pushes workshop buyers toward the full pass. And the day passes do not include recordings, which is a real difference the full pass can point at.

What should a single-day pass cost relative to the full pass?

At half the two-day price, two day passes cost the same as a full pass before fees. At 60 percent, buying both days separately costs more. That gives the full pass a price advantage; the schedule, included benefits and buyer's availability still determine which option they choose.

For a three-day conference, another scenario to model is 40 to 45 percent for one day and 70 to 75 percent for two. The table applies those illustrative percentages and rounds to the nearest dollar.

Plan catering separately for Thursday and Friday when day-pass attendance differs. If you also offer early bird tiers, compare the day-pass price with the currently available full pass; decide whether a day-pass discount or a later launch makes the choices clearer.

Should a workshop be its own ticket or an add-on at checkout?

Separate ticket types still make sense in two situations: when the workshop can be bought without a conference pass at all, as with a public training day, and when a workshop has its own audience that would never buy the main event.

For other add-ons, an order bump keeps the purchase in one checkout. This site has no reliable benchmark for workshop attach rate or evidence that a checkbox will double it. Measure the percentage of eligible pass buyers who add the workshop, compare placement or price changes, and keep enough inventory data to interpret the result.

How do you cap the number of seats in each workshop?

Illustrative operating assumptions to test in a rehearsal:

• Hands-on technical workshops: 20 to 30 seats. Above 30 the facilitator cannot get round the room.
• Discussion or roundtable format: 12 to 20 seats.
• Lecture-style masterclass: whatever the room holds, minus a row.
• Anything with equipment: count the equipment, not the chairs.

If you show remaining places, use the actual available inventory and explain any reservation holds. You can try displaying the count only near capacity, but measure its effect rather than assuming a particular threshold changes purchase timing.

When a workshop sells out, the ticket page should show it immediately. Keeping workshop inventory in the same system as the pass can reduce reconciliation work compared with a separate signup form, but the workflow still needs an end-to-end capacity test before launch.

How do you sell dinners, tours and social events?

Set an end date on each add-on so it disappears from checkout on its own. Chasing a caterer for a late addition is a worse use of your last week than almost anything else.

How do you keep a ten-option ticket page readable?

A long flat list can make similar ticket options hard to distinguish. Group by attendance mode or access level, then test the purchase path with people who did not design it and record where they choose the wrong option.

On Checkout Page, ticket groups do exactly this: they hold several ticket types, carry their own group-level capacity, and display as a quantity dropdown, a multi-select or a single-select. Single-select is the right choice for day passes, because it stops someone buying a Day 1 pass and a Day 2 pass instead of the full pass.

How does check-in work across multiple days?

Decide which of these two you are before you build the ticket types, because it changes the structure:

Checkout Page records one check-in per ticket. Invited staff can scan concurrently on Launch or above, with activity synchronized online and attributed to the staff member. The scanner requires an internet connection, so test connectivity at the registration desk. The conference check-in guide covers fallback planning.

What does a finished lineup look like for a 600-person conference?

Worked example, a 600-capacity two-day tech conference:

The in-person allocations total 600, including the 60 comp places. Enforce a hard shared capacity of 600 across all in-person ticket types and reserve places within it for any additional staff or guests. Day passes grant access only on their named day. Workshop and dinner add-ons use separate capacities and belong to existing pass holders; virtual attendees do not occupy the venue. Do not rely on unsold tickets or no-shows to stay within the room limit.

For how the sales windows in that table should be spaced, see conference ticket tiers, and for the underlying price, how to price conference tickets. The ticket tier template has three ready-made versions of this table by conference size.