# Multi-day pass access and scan matrix

Event: ______  Local time zone: ______  Ticket provider/setup: ______  Gate owner: ______  Revision/date: ______

## Product rights — one row per product
| Pass product | Friday dates/times/zones | Saturday dates/times/zones | Sunday dates/times/zones | Workshop/parking/camping add-ons | Same-day re-entry | Transfer rule | Support owner |
|---|---|---|---|---|---|---|---|
| Full-event pass | | | | | | | |
| Weekend pass | | | | | | | |
| Single-day pass | | | | | | | |

If your event has different dates, replace the column headings. Do not use the word “all-access” unless every included area and session is actually covered.

## Provider behavior to verify
- How is the valid day attached to a ticket or package? ______
- Does the same credential allow separate check-in on each valid day? ______
- Is a daily rule switch, checkout or reset needed? By whom and when? ______
- What happens if a scanner is offline during an overnight status change? ______
- How do refunds, transfers and add-ons alter access? ______
- Where are per-day attendance records visible? ______

## Gate rehearsal
| Scenario | Expected display and action | Actual result | Owner / correction |
|---|---|---|---|
| Valid pass on first authorized day | | | |
| Same pass on next authorized day | | | |
| Pass on wrong day or zone | | | |
| Duplicate scan within one day | | | |
| Authorized same-day re-entry | | | |
| Canceled or transferred pass | | | |
| Offline device then sync | | | |

Buyer-facing dates and gate rules reviewed by: ______  Gate team briefed by/date: ______