# Session-by-session booking preflight and test matrix

**English worksheet.** Copy one session row for every bookable date/time slot. Use authorized test records or a test environment. Do not enter attendee names or contact details here.

Event reference: __________  Provider/setup: __________  Version/date: __________

Registration owner: __________  Limit approver: __________  Exception owner: __________

## 1. Configure from an approved limit

| Session key and exact date/time | Room | Approved room/operational limit and owner | Places already committed outside public signup | Configured public signup ceiling | Eligible group and selection rule | Authoritative session roster location |
| --- | --- | --- | --- | --- | --- | --- |
| S1: | | | | | | |
| S2: | | | | | | |
| S3: | | | | | | |

The approved room limit, software signup ceiling, event-wide ticket cap, and live people-in-room count are different records. Record the basis for each number; do not let a software field decide room safety. For two time slots, make separate rows unless the provider actually shares their inventory.

## 2. Test the buyer path and the session record

For each scenario, note the *actual* form/preview or buyer-page result and the *actual* change in the specific session roster. Use sample labels such as **Test A**, not personal details. Mark unsupported cases **N/A**, with an owner for any alternate process.

| Session key | Controlled scenario | Starting session count / limit | Expected buyer result | Actual buyer result | Actual roster change and final count | Pass / owner |
| --- | --- | --- | --- | --- | --- | --- |
| | Eligible profile; place available | | | | | |
| | Last available place | | | | | |
| | One more attempt when full | | | | | |
| | Profile excluded by intended rule | | | | | |
| | Select a different session at the same event | | | | | |
| | Overlapping or multiple selection, if supported | | | | | |
| | Remove/cancel a selection, if supported | | | | | |

Check the confirmation or personal agenda: does it mean a **reserved session place**, a **saved preference**, or **another step required**? Record the provider's actual behavior. A session booking does not itself prove venue admission or attendance.

## 3. Sign off and restore the setup

- [ ] Correct title, date, time, room, eligibility and selection rule appear to the intended test profile.
- [ ] The session roster and count agree with every successful and rejected sample attempt.
- [ ] Event registration and session registration are checked as separate records.
- [ ] Any temporary test limit is restored to the approved ceiling; test records are handled through the authorized cleanup route.
- [ ] Buyer-facing wording agrees with what the organizer record proves.
- [ ] Exceptions have an owner; the registration owner approves the current buyer view and count before opening.

Change record: __________  Before limit/count: __________  After limit/count: __________  Approved by: __________

If a revised ceiling falls below existing bookings, stop the public change and resolve those commitments with the responsible organizer before making a new promise.