# Ticket dependency buyer-path card

This worksheet is in English. Use fictional ticket labels and a supported preview or authorized test route. Do not make a paid purchase merely to test a rule.

| Rule field | Record |
| --- | --- |
| Event / occurrence |  |
| Required parent ticket type(s) |  |
| Dependent ticket type |  |
| Why the combination is needed |  |
| Customer-facing error or locked-state explanation |  |
| Rule owner and date |  |

## Controlled basket checks

| Basket | Expected outcome | Observed outcome | Follow-up owner |
| --- | --- | --- | --- |
| Dependent ticket alone | Blocked or locked by the configured rule |  |  |
| Approved parent plus dependent ticket | Can advance through the checked checkout step |  |  |
| Unapproved ticket plus dependent ticket | Does not satisfy the prerequisite |  |  |
| Parent for another date or occurrence | Test whether it qualifies; accept only the intended result |  |  |
| Parent alone | Allowed if that is the intended offer |  |  |
| Required parent sold out or hidden | Record the actual dependent-ticket display and stock view |  |  |

## Final review

- [ ] The exact eligible parent types and occurrences are recorded.
- [ ] The buyer can understand what additional ticket is needed.
- [ ] The dependency was tested in the basket, beyond a disabled-looking listing.
- [ ] Ticket capacity and admission rights were checked separately.
- [ ] Someone owns a recheck if the parent ticket changes or sells out.

Approved by: ____________________  Date: ____________________