Back to guides
Platform-neutral remote workshop runbookUpdated July 22, 20264 min read

How to assign breakout rooms for online workshops

Choose a room shape that fits the activity, generate all rounds against one encounter history, and give the producer a plan that still works when someone arrives late or does not attend.

A remote workshop host organizes floating video call tiles into tidy breakout room clusters.

Guide visual

Breakout room planning

Room assignments for repeated online sessions.

6 rooms3 roundsroom hosts

Set the operating constraints first

  • Choose room count when the platform, venue, or facilitator count is fixed; choose people per room when conversation size matters most.
  • If every room needs a facilitator, do not create more staffed rooms than available facilitators.
  • Budget instructions, room movement, a warning, return time, and debrief—not only discussion time.
  • Ask about accessibility needs privately and give everyone an accessible route to request help.
  • For hybrid sessions, verify room audio and participation rather than assuming one laptop makes a physical table accessible to remote attendees.

Prepare all breakout rounds

  1. Clean the planned roster

    Use one stable participant name or ID. Add only attributes and rules that affect this activity.

  2. Choose rooms and rounds

    Set the complete rotation. In the preloaded example, 36 people and six rooms produce six planned people per room.

  3. Add operational rules

    Fix one host in each room, add genuine separation requirements, and balance at most one useful field.

  4. Generate the full rotation

    Keep repeat minimization enabled so later rooms are evaluated against earlier conversations.

  5. Prepare two views

    Give the producer one detailed roster per round. Give participants only the assignment information they need, without private attributes or rule explanations.

  6. Run and adapt visibly

    Announce the round, destination, task, return time, and help route. Keep late arrivals in the main room until a producer assigns them.

  7. Regenerate when attendance changes materially

    A single absence may justify one deliberate move. Several absences should trigger a new plan for the remaining rounds and a fresh repeat review.

Turn the result into a producer-ready room plan

  • Your groups carries the operational detail: room assignments, assigned count, capacity, and whether each named host appears in the intended room.
  • Fixed-host and required-apart rules are invariants. Their cards report “No violations” in a valid result; a violation is a solver defect, not an imperfection the producer is expected to absorb.
  • The Pair Meeting Histogram summarizes repeat distribution across the event; repeated cells in the matrix identify the people and sessions involved.
  • When an experience mix was requested, its Attribute Balance card shows the desired and actual category counts for each room that missed the target.
  • Roster, plain-text, CSV, and visualization views support different producer workflows. After material no-shows, all of them—and the contact diagnostics—describe a stale plan until the remaining rounds are regenerated.

Worked example: six hosted rooms

The preloaded example has 36 people, six rooms, three rounds, and one fixed host per room. Its 12 New, 12 Practiced, and 12 Advanced values make two of each experience level per room arithmetically possible before the fixed-host and apart rules are considered.

Setup facts

  • 36 participants
  • 6 rooms with 1 fixed host each
  • 3 rounds
  • one experience field and one apart rule

Review the result

  • Confirm every room has its host and stays within capacity.
  • Compare the actual experience mix with the possible 2/2/2 target.
  • Inspect repeats and regenerate remaining sessions after material attendance changes.

Try this setup in GroupMixer

This tool is preloaded with the example from this guide. You can edit the participants, constraints, sessions, and balance settings before generating groups.

Enter one person per line in the first column. Optionally, add attribute columns such as gender, role, or skill-level on the right. Those attributes can then be used to balance groups and set additional rules.
Name
Use 1 session for a single round of groups. Increase sessions when you want multiple rounds with new group assignments for the same people.
People
36
Groups
6
Approx size
6
Force specific people into the same group in every session. Write one "clique" per line, with names separated by commas. Example: "Alex, Sam" keeps Alex and Sam together.
Prevent selected people from being placed in the same group. Write one set per line; everyone on a line is kept mutually apart. Example: "Alex, Sam, Jordan" keeps all three separated.
Pin specific people to a specific group across all sessions. Enter one name and one group number per row. This is useful for leaders, presenters, or anyone who must stay in a known group.
Name
Group
Set target counts for each attribute value inside each group. Keep auto distribute enabled for fair automatic targets, or edit the counts manually when you need exact control.
Experience
Automatic targets · All sessions
Groups 1-6Drag the handles in the bar to adjust the distribution, or edit the numbers next to the labels manually. A 0-target attribute is still active: the solver tries to keep that value out of the group. A non-allocated attribute is ignored by this balance target. Toggle an attribute on or off by clicking its label in the legend or bar.
Drag the handles in the bar to adjust the distribution, or edit the numbers next to the labels manually. A 0-target attribute is still active: the solver tries to keep that value out of the group. A non-allocated attribute is ignored by this balance target. Toggle an attribute on or off by clicking its label in the legend or bar.
Need even more control?
  • Partial attendanceSet which participants attend which sessions instead of assuming everyone is present every round.
  • Custom group capacitiesGive each group its own capacity and override those capacities for specific sessions when room sizes or staffing change.
  • Session-specific constraintsApply scoped rules only where they matter, then use global objectives such as Avoid Repeats for whole-schedule quality.
  • Weighted preferencesAdd preferences that can be violated when needed, then tune their weights relative to other goals.
  • Encounter targetsTarget how often selected people should all meet across the schedule, including exact, minimum, or maximum encounter counts.
  • Group visit targetsControl how often selected people visit selected groups across sessions for station rotations, task exposure, or visit caps.
  • Advanced constraint tuningFine-tune repeat limits, attribute-balance modes, penalties, and other constraint details beyond the landing-page controls.
  • Solver settingsAdjust runtime limits, deterministic seeds, solver family, and other optimization settings.
  • Result analysisInspect score breakdowns, constraint compliance, penalties, and saved results in more detail.
Quick Setup and the scenario editor use the same saved scenario. Settings hidden here remain intact.

Related guides