FESTALUNEUnlock Your Next Adventure.
Home / Building a Confirmed-Only Play Roster from an Invitation List
GuestWeave · Fictional worked scenario

Building a Confirmed-Only Play Roster from an Invitation List

This is an invented planning exercise, not a customer event or testimonial.

Background and constraints

A fictional organizer has an invitation register with six names, including one decline and one unanswered invitation. The final paper-strategy game should allocate only the four confirmed participants.

Exact tool inputs

names
Ari | | confirmed
Bea | | confirmed
Cleo | | confirmed
Dev | | confirmed
roles
Reader
Mapper
Recorder
Timekeeper
teams
2

Actual generated result

Planning process

The host makes a separate saved project for confirmed play and enters the four records shown here. The original invitation register remains intact. Random roles and two teams are generated from the confirmed set, so no printed seat or essential responsibility is assigned to an absent guest.

Result explanation

Filtering the source list before generation changes the actual allocation, rather than merely hiding a row in a printout. The two-project approach preserves invitation history while giving the activity host a clean operational roster.

Alternative

Wait for the final response deadline before drawing teams if attendance is still uncertain. Use a flexible observer role for a last-minute addition.

Execution notes

Name the saved projects clearly, such as “Invitation register” and “Confirmed play roster,” so helpers do not use the wrong version.

Continue planning

Open GuestWeave

How to Organize Guests, Roles and Seating

Reviewing a Random Role Draw Before Sharing It

FAQ

Are these real event records?

No. All people, dates, constraints and planning amounts in this scenario are fictional inputs supplied to demonstrate a workflow.

How can I try this plan?

Open the linked tool, enter the exact inputs above, review the result and save it locally. Export a backup if you want a separate copy.