How do you plan conference sessions for different experience levels?

You've booked a speaker who knows the subject inside out. The session description says "advanced", the room fills up, and the first questions are about the basic terms on the opening slide. Now the speaker has a choice. Explain the foundations and disappoint the people who came for detail, or keep going and leave part of the room behind.

You can prevent a lot of that confusion before anyone buys a ticket. Plan conference sessions around what attendees already need to know and what they'll be able to do afterwards. Then make those requirements visible in the programme, check that speakers actually teach at the stated level, and provide a useful alternative when a session isn't the right fit.

The level label helps people find their options. The explanation underneath lets them choose. Someone can be an experienced business owner and a complete beginner in the subject of your next session. If your programme treats those things as the same, you're asking the buyer to guess.

This guide works through the decisions using an invented paid retail conference, Stockroom Forum. The examples are planning suggestions, with invented sessions and timings. We'll build session descriptions, test the prerequisites, brief speakers and handle the people who arrive in the wrong room. The aim is a conference buyers can use, with commitments your team can afford to deliver.

Start with the task, then decide how much knowledge it needs

The first thing you want to do is choose a task an attendee would pay to get better at. "Inventory management" is a subject. "Decide what to reorder when cash is limited" gives your programming team something to develop.

That task can support several sessions, but they won't necessarily be a neat ladder. One person needs to understand a stock report. Another can already use the report and wants to question the assumptions behind a reorder. A third needs to deal with irregular demand across several shops. Those people need different explanations, examples and time to work.

For Stockroom Forum, suppose you're considering a foundation session about making a first reorder decision, an application workshop about improving an existing routine, and a specialist discussion about exceptions. Before accepting the titles, ask what someone must already be able to do in each room. Reading the same report could be a prerequisite for all three, or it could be something you teach in the foundation session.

Write the intended result in everyday language. Carnegie Mellon University's Eberly Center recommends learning objectives that describe observable actions, with teaching and assessment organised around them. We're adapting that course-design principle to a short conference session. It doesn't make the session an accredited course or establish that a single exercise proves lasting competence.

For your first reorder session, the result might be choosing an order from a supplied example and explaining the reason. For the application workshop, it might be identifying which assumption to investigate before changing an existing process. A specialist session could compare two defensible responses to uncertain demand, with attendees explaining what evidence would change their decision.

These results make editorial decisions easier. A speaker who wants to cover the history of retail software may have interesting material. It doesn't automatically help someone make the promised decision. Ask how that material supports the task, and shorten or remove it when the connection is weak.

Keep the scope realistic for the available time. If buyers need an entire afternoon of guided practice to perform the task, don't promise mastery in a short talk. Offer an introduction, a demonstration or a bounded exercise and describe that honestly.

Define session levels by starting knowledge, not seniority

You can use beginner, intermediate and advanced if those are familiar to your audience. You could also use foundation, application and specialist. Pick a small set your team can explain consistently. You don't need a clever new classification system.

The important work is defining what each label means within your programme. Our suggested foundation session teaches the essential terms and works through a first example. The application workshop assumes attendees can already complete that example and spends its time on adapting the process. The specialist discussion assumes familiarity with the process and examines cases where the usual answer is uncertain.

Those are editorial definitions for this hypothetical conference. They aren't a universal standard for event education. An advanced technical tutorial and an advanced business discussion may require very different kinds of preparation.

PyCon US's 2026 talk proposal guidance provides a useful real example. It distinguishes audiences by their existing context and knowledge, while acknowledging that people interpret experience levels differently. It also asks what attendees will gain. That combination is more useful than a difficulty label on its own.

Avoid using years in a job as the only test. A retailer who has worked for a decade may have delegated buying throughout that time. A newer employee may manage orders every week. Likewise, being a director doesn't tell you whether someone can use a spreadsheet, interpret a stock report or participate in a technical exercise.

Don't use difficulty as a ranking of personal worth. "For serious professionals" makes the foundation session sound like a consolation prize. "For people making their first reorder decision" names the work and lets a senior attendee recognise that it applies to them.

Allow topic-specific choices. Someone might choose specialist content on merchandising and foundation content on cash planning during the same conference. A single experience category attached to their whole booking would hide that difference. Recommend suitable sessions without assigning a permanent level to the person.

Also separate format from difficulty. A keynote can be technically demanding. A hands-on workshop can begin with the basics. If the programme uses "workshop" as shorthand for advanced, buyers still won't know what preparation is required.

Find out what your intended buyers can already do

Before you promise several levels, check whether the audience needs them. Start with people who fit the conference you're selling, including prospective buyers and returning attendees. Ask about their work on the specific subject, rather than whether they consider themselves experienced.

For Stockroom Forum, you might ask which description fits their current involvement. They could be preparing to place their first order, following an established buying routine, or reviewing decisions across several locations. Add an option for people whose work doesn't fit those descriptions. Their answer tells you more than their job title, but it still doesn't prove what they can do.

Use a short example to explore the difference. Show a simple fictional stock report and ask which information they'd check before placing another order. Let them explain in words. You aren't conducting a hiring test or collecting a performance score. You're finding out what your proposed session can reasonably assume.

The Eberly Center's guidance on assessing prior knowledge distinguishes direct evidence of a task from indirect evidence such as self-reports. It describes using the results to adjust teaching or offer preparation. For a conference, a small relevant task and an explanation of its purpose can inform your programme without turning registration into an exam.

Tell people whether their answer affects admission to a session. If it's only programming research, say so. Don't let a voluntary question become an undisclosed entry requirement later. If a genuinely restricted practical session needs verified preparation, explain that separate process before someone pays.

Look at who answers. Existing customers may know your subject terminology already, while first-time buyers use different words. Your most enthusiastic respondents may also be the people looking for specialist content. Their interest is useful, but it doesn't establish that the rest of your likely buyers want the same programme.

Keep questions short enough that you can act on the answers. A long survey containing every possible topic creates more information than a small team can sensibly interpret. Ask about the decisions you're still able to change, then use follow-up conversations where an answer needs explanation.

When evidence is weak, make a smaller commitment. You could run one clearly defined foundation session and one application workshop, rather than selling a full specialist track. More labels won't fix uncertainty about who the event serves.

Write prerequisites that a buyer can check

A prerequisite is something someone needs to know, have or do before the session begins. Write it so an attendee can check it without asking your speaker for permission.

"Basic industry knowledge" doesn't help much. "You should be able to read the supplied stock report and explain the difference between units sold and units still available" is clearer. It identifies a task. You can also supply a sample report so the reader knows what kind of information you mean.

Distinguish essential preparation from material that would merely help. Someone who needs a short glossary can read it before arrival. Someone who cannot perform the central task may need a different session. If both appear under one vague preparation heading, buyers won't know which matters.

For the application workshop, list the report-reading requirement as essential. Describe familiarity with a weekly buying meeting as useful context. If the workshop uses only the supplied example, say that attendees won't need to bring their own business records. That avoids unnecessary preparation and keeps confidential information out of an exercise that doesn't require it.

Be equally specific about equipment. If participants need a laptop, a particular file format or access to a tool, identify the requirement and give them a way to check it. Don't announce software setup in an arrival email after selling a workshop that sounded self-contained.

Where your event includes a technical exercise, test setup instructions on the equipment and connection attendees will actually use. Provide a workable alternative if someone cannot use the expected method, and describe any limit that changes what they can participate in. The teaching plan and the access plan need to agree.

You can give buyers a brief readiness example. "Can you find opening stock, sales and closing stock in this sample?" helps them judge fit. Provide the explanation as well as the question. Making people guess whether they passed simply replaces one unclear label with another.

Be careful with prerequisites that depend on another conference session. If you require attendance at the morning foundation session, you also need to make a place available and schedule it first. If equivalent experience or a preparation resource is acceptable, say that clearly. An optional recommendation should remain optional.

Publish session descriptions that let people choose

A useful session description tells buyers what they'll work on, what you expect them to know and what the format will let them practise. It also states the important exclusions. You can write all of that without making the listing read like a contract.

Here are three illustrative descriptions for Stockroom Forum. The titles and durations are invented examples. They show how the level changes the starting point and activity, rather than just adding a more impressive adjective to the same talk.

Foundation: make your first reorder decision

This session is for people who haven't yet made an independent stock reorder. We'll explain the terms in a simple stock report, work through one example together and let you choose an order from the supplied options. You'll leave with a completed example and the questions to ask before applying the method to your own shop.

You don't need buying experience or a laptop. We supply the fictional report and a readable worksheet in advance. This is a foundation explanation and guided exercise. It doesn't cover supplier negotiations, software setup or decisions across multiple locations. The session lasts 50 minutes and includes time for questions.

Notice that the description doesn't apologise for teaching the basics. It names the first decision the attendee needs to make. An owner who has never placed an order can choose it without having to decide whether "beginner" describes their career.

Application: improve an existing reorder routine

Choose this workshop if you already use a stock report to place orders and want to examine the assumptions behind your routine. Using a supplied fictional example, you'll identify a weak assumption, propose a change and explain what you would check before using it. You can work on paper or with the accessible digital worksheet.

You should already be able to identify sales and available stock in the sample report supplied with the listing. The foundation session or the preparation explanation can help you check that starting point. This workshop lasts 50 minutes. It won't teach the report terminology from scratch or review confidential data from individual businesses.

This description gives an attendee a reason to choose the workshop over the foundation session. It also gives the facilitator permission to maintain the agreed starting point, because buyers have been told what it is.

Specialist: review a reorder when the usual assumptions fail

This facilitated discussion is for people who already review stock decisions and can explain the assumptions in an existing reorder process. You'll compare possible responses to an uncertain demand scenario and identify the evidence you would want before committing. Expect discussion of tradeoffs, with more than one defensible response.

Read the short fictional case in advance. You won't need to disclose your own company's figures. This 50-minute discussion doesn't include individual business advice, an introduction to stock reporting or a step-by-step software demonstration. If you want to practise a standard routine first, choose the application workshop.

Read the descriptions together. Each offers something useful. The specialist discussion isn't the reward for completing the others, and it shouldn't be sold as the best choice for everyone. The best session is the one that addresses the buyer's current work at a starting point they can use.

Keep one session record your team can use

Before publishing the programme, put the agreed choices into a short record for each session. Keep it with the speaker brief and the current description. A spreadsheet row with links to the materials is enough if your team can find and update it.

Use these prompts to make the record reusable:

• Who is the attendee, and what decision are they working on?

• What must they already be able to do, and how can they check that?

• What preparation or equipment is essential, and what is optional?

• What will they practise, discuss or produce during the session?

• What does the session deliberately leave out?

• What alternative can staff actually offer if the starting point doesn't fit?

• Who approves a change to the level, activity or public description?

For our application workshop, the completed record would name someone already placing stock orders. It would require reading sales and available stock in the supplied report, with the sample and explanation available before booking. Familiarity with a buying meeting would be helpful. No private business data would be required, and participants could use the paper or accessible digital worksheet.

The activity would be reviewing an assumption in the fictional reorder routine. The intended result would be a proposed change with an explanation of what to check before using it. Report terminology, software installation and individual business advice would remain outside the session. The programme lead would approve any change that affected those commitments.

For the alternative, record something deliverable. If the foundation session has already happened, staff could point to its preparation explanation, while checking whether the attendee wants to observe or choose another available session. Don't list a repeat workshop unless you've booked the person and space to run it.

Date the record and review it after the speaker rehearsal. If the rehearsal exposes a new prerequisite, fix the session or update the buyer information and contact affected attendees. Keeping the internal record accurate matters because it determines what staff will tell someone who needs help.

Check speakers against the level you've promised

A speaker can choose the wrong level in good faith. They may underestimate how much background their example requires, or use "advanced" to mean that the subject is new. Your programme lead needs to check the actual session, not simply accept the category on the proposal form.

Ask for the opening explanation, the main example and the activity attendees will complete. You don't necessarily need a finished slide deck before accepting a proposal. You do need enough detail to see whether the promised result fits the time and starting knowledge.

For the foundation session, listen for unexplained terms. Does the speaker explain the report before asking people to use it? For the application workshop, check how much time goes into recap and how much into applying the method. For the specialist discussion, ask what makes the case difficult and how the facilitator will keep the conversation useful when attendees disagree.

Have someone with the intended starting knowledge try the central activity. Ask them to describe what they understand and where they get stuck. This is a rehearsal check, not proof that every attendee will have the same experience. Its value is finding hidden assumptions while you can still change the session.

Agree what to do with questions outside the scope. A foundation question in a specialist session deserves a respectful answer, but it may need a short clarification and a named follow-up resource. If the speaker repeatedly stops to rebuild the whole introduction, the session no longer matches the description experienced buyers used to choose it.

The conference speaker briefing guide covers the broader preparation process. Add the session's essential starting knowledge, its promised result and the topics the speaker can leave out. Make those choices part of the same brief the host and facilitator receive.

Sponsored sessions need the same review. A sponsor's expert may know the product well without knowing how to teach the underlying task. Check whether the session assumes access to a paid tool, and disclose that before buyers choose it. A useful commercial relationship doesn't remove your responsibility for the programme you've sold.

When you change a session's level during preparation, update the description and tell people who have already selected it. Renaming it in the internal schedule alone leaves the original buyer promise in place.

Decide when to separate levels and when to keep people together

Separate sessions work well when the starting knowledge changes what the speaker can explain or what attendees can practise. If beginners need substantial guided explanation and experienced attendees need time on exceptions, putting everyone in one short workshop can make both groups wait for the material they need.

But a shared session can work when people face the same decision and different experience adds to the discussion. A conference opening about a new market condition might be useful to everyone, provided it explains necessary terms and doesn't require specialist preparation. You can then offer more focused sessions afterwards.

Don't force every subject into every level. You may have a strong foundation session on one topic and no useful specialist treatment to offer. Leaving that part of the programme smaller is better than commissioning another speaker to repeat the material under a new label.

A shared exercise with optional extensions is another possibility. Everyone works on a core case, and people who finish can examine an additional complication. That requires a core task people can actually complete with the support available. It won't work if half the room needs an explanation the other half already knows and the facilitator cannot provide both.

Avoid making experienced attendees responsible for teaching everyone else. Pair work can be useful when participation and expectations are clear. An attendee who bought specialist instruction shouldn't discover that their role is unpaid assistance for another table. If peer exchange is the point of the session, explain that before people choose it.

There is also a delivery cost. Another level can mean another room, facilitator, rehearsal, set of materials and access provision. Compare the full additional commitment with the specific audience need. Don't count an existing ticket holder's interest in a specialist session as a new sale that pays for it.

For a small conference, I would usually start with fewer, well-defined options. Add a separate level when you can explain what the combined session cannot deliver and identify buyers who need the additional option. That gives you a stronger decision than splitting the programme because the venue has a spare room.

Build routes that don't depend on impossible choices

Once the session boundaries are clear, test the day from the attendee's point of view. Someone choosing the foundation session may want to continue into application. Someone arriving with experience may want to skip the introduction and join directly. Both routes should be described accurately.

In our invented programme, the foundation session runs before the application workshop. The specialist discussion happens later. That sequence permits progression, but attendance at the first session doesn't automatically establish readiness for the next. Give people the sample task and let them check what they can now do.

If you run foundation and application sessions at the same time, treat them as alternatives. Don't recommend that newcomers attend both. If the application workshop requires knowledge taught only in the foundation session, the timetable prevents that route entirely. A recommendation in an email cannot solve the clash.

You also need enough time to change rooms and use the access arrangements each attendee requires. A path that works only for someone who can hurry up the stairs isn't a usable programme path. Check the full journey with the delivery team, including breaks and any preparation expected between sessions.

Our guide to building conference tracks without splitting the same audience develops the timetable decisions. Use it once you've defined who each session is for. Here, the extra check is whether a suggested sequence provides the knowledge the later session assumes.

Make reservations clear as well. A pass to the conference doesn't necessarily guarantee a place in every workshop. If the foundation session leads to an application workshop with fewer places, explain the booking arrangements before recommending that route. Otherwise you may help someone prepare for a session they cannot enter.

Keep the distinction between an expression of interest and a confirmed booking visible. Our conference session registration guide covers allocating places and communicating what a pass includes. Experience-level guidance helps people choose; reservations determine whether a place is available.

When a route depends on a specific session, confirm its delivery before promoting the route. An unconfirmed speaker or room is a risk to everything you recommend afterwards. Assign someone to check the whole affected sequence whenever the timetable changes.

Keep accessibility separate from the knowledge requirement

A person who needs more time to read a worksheet may understand the subject very well. Someone who asks for captions or an accessible document hasn't identified themselves as a beginner. Keep those questions separate in your planning and in the language your team uses.

W3C's accessible events checklist recommends accessible materials, advance sharing where needed, support for interpreters and captioners, and care with participant activities. Apply that guidance across your session levels. Specialist content still needs to be perceivable and usable by the people it serves.

For Stockroom Forum, make the fictional report available in a format attendees can adjust and navigate. If a diagram matters to the exercise, provide a usable text explanation. Have the speaker describe the relevant information rather than asking everyone to read a projected chart silently.

Give people a way to ask for support without disclosing personal details to the whole room. The programme team may need to coordinate an arrangement, but other attendees don't need an explanation of why someone is using it. Check the practical arrangements with the person concerned and the colleagues responsible for providing them.

Don't use speed as a hidden prerequisite. If the specialist exercise genuinely depends on making a timed operational decision, describe why and plan appropriate support. If fast reading has nothing to do with the promised skill, racing through the case makes the session harder without making it more advanced.

Also distinguish unfamiliar language from unfamiliar subject matter. An attendee may know the work but use different terminology or be participating in a second language. A glossary, clear delivery and a written version of the case can help them participate without sending them to a lower-level session.

Test any alternative activity before advertising it. Observing a demonstration may be useful, but it doesn't necessarily provide the practice promised by a hands-on workshop. Explain what the alternative includes and work with the attendee on a suitable option. Don't quietly replace participation with watching and call the commitment fulfilled.

Prepare people without adding a second course before the event

Preparation should make the promised session possible. It shouldn't compensate for a description that attracted the wrong audience or a speaker who has packed too much into the slot.

For the application workshop, a short sample report with an explanation may be enough for someone to check the entry requirement. If an attendee needs extensive tuition to reach that starting point, recommend the foundation session or another suitable resource. A large compulsory reading pack sent late doesn't turn an advanced workshop into an accessible choice for beginners.

State the preparation commitment in the public description, including any required tool or material. Test the task yourself and use that experience to give an honest estimate of the time required. An estimate should help attendees plan, while recognising that reading and setup times differ.

Send the preparation when people can still act on it. Link to one current version, identify what is essential and include a contact for questions. If you revise the case, explain which version the speaker will use. People shouldn't waste time comparing slightly different attachments to work out what changed.

With Loopyah attendee email, you can send event updates to ticket holders and use purchase information to organise relevant audiences. Keep any session choices you've collected separate unless they're actually reflected in your ticket or audience setup. Your programme team still decides what each session requires and who needs that preparation.

For group purchases, check that the information reaches the person attending. The accounts contact who paid may not be the delegate doing the preparation. Explain how participants can access the materials and ask questions without relying on the buyer to interpret the session for them.

Give the room team a plan for unprepared attendees. Spare copies can solve a missing worksheet. A worked example can sometimes support observation. Neither solves missing essential knowledge in a short practical session. Agree a respectful alternative before staff have to invent one at the door.

Plan a session that maintains its promised starting point

The description and the actual delivery need to match. For the application workshop, decide how the facilitator will establish the starting point quickly, support the activity and keep enough time for the promised result.

Here's an illustrative 50-minute plan. It's a design example for our fictional conference, not a recommended duration for every workshop. Allow five minutes for the purpose and readiness example, ten for a worked case, fifteen for individual or paired work, ten for discussion, five for questions and five for attendees to write a final explanation of their decision. Those allocations total 50 minutes.

The readiness example checks whether the room can use the material as planned. It shouldn't publicly identify people as weak or capable. Show the explanation, offer the preparation resource and let attendees privately choose whether to continue with the activity or use the agreed alternative.

During the main exercise, the facilitator needs a way to distinguish a confusing instruction from missing background knowledge. If several people ask what the worksheet means, stop and clarify it. If one attendee needs the full foundation explanation, arrange the planned support without using everyone's practice time to deliver another session.

For a more demanding practical format, our conference skills lab guide covers equipment, assistance and delivery. The same principle applies here. A level label does not remove the need to provide enough teaching support for the activity you've advertised.

Give the facilitator language they can use naturally. "This part assumes you're already reading the stock report. The foundation explanation is available here, and my colleague can help you choose an alternative" respects the attendee and protects the agreed scope. It also gives them an actual next step.

If the whole room is struggling, reconsider the plan. A widespread problem could mean the description, preparation or session design was wrong. The facilitator should contact the programme lead and adjust openly. Tell attendees what can still be delivered, rather than pretending the original outcome remains achievable while removing the practice it required.

Handle the wrong choice without blaming the attendee

Someone will choose a session that doesn't suit them. They may have misunderstood the description, followed a colleague or discovered an unfamiliar topic within a field they usually know well. Your response matters because they have paid for a useful day.

Ask what they were hoping to work on and what is making participation difficult. That conversation can reveal a missing explanation, an access problem or a genuine mismatch in starting knowledge. Each needs a different response. Moving everyone who asks a basic question to another room would be a poor substitute for finding out.

If another session is suitable and has space, explain the option and help with the move. Check reservations and access support first. Don't send someone to a foundation workshop that has finished or a room that cannot admit them. Staff need current information about workable alternatives.

For someone who finds the session too basic, check the promise before recommending an upgrade. If the speaker is delivering what was advertised, another available session may be a better choice. If the talk was sold as specialist content and has become an introduction, your programme lead needs to address the delivery problem.

Use a clear process for complaints or requests for a remedy. Record what was advertised, what changed and what option the attendee received. Your response should follow the terms and obligations that apply to your event. A generic warning that schedules may change shouldn't become an excuse to ignore a substantial difference in the experience sold.

Don't promise private coaching or a replacement workshop simply to end an uncomfortable conversation. Confirm the teacher, time, budget and access arrangements first. A useful immediate response is better than an impressive follow-up your team cannot deliver.

Brief hosts to keep the language ordinary. "Let's find the session that helps with the decision you're working on" is more helpful than telling a business owner that they're in the wrong ability group. You can maintain a session's requirements without turning them into a judgment about the person.

Review whether the descriptions led to useful choices

After the conference, ask attendees whether the starting knowledge matched what the description led them to expect. Ask separately whether the activity helped with the promised task. A session can be enjoyable and still be the wrong level, or appropriately demanding without being a favourite.

The Eberly Center's guidance on matching assessment to learning objectives explains why evidence should relate to the skill being taught. For our conference example, an explanation of a reorder decision is more relevant to the stated task than a satisfaction rating. Keep any exercise modest in its claims. Completing one fictional case doesn't prove reliable performance at work.

Look at specific points of confusion. Did buyers understand "application"? Did they read the sample report? Did the speaker introduce terms the description never mentioned? Did an inaccessible activity make someone appear unprepared? Record these as different problems so next year's team changes the right thing.

Review people who moved or left as well as those who stayed. Their reasons may be missing from the room's feedback form. Invite comments without assuming that leaving means the teaching failed. A timetable clash, work call or change of interest could explain the same behaviour.

For the wider event budget, ticket options and commercial decisions, return to the guide to organising a paid conference. Judge the extra session levels against the specific audience commitment they served and the cost of delivering them. Attendance alone won't show whether an additional specialist room justified that commitment.

Before approving your next programme, choose one session and have someone outside the programming team use its public description to make a decision. Ask them who it suits, what they need to know, what they'll do and where they'd go if it isn't suitable. If they have to ask you to interpret the label, revise the description before you sell the place.