# Add a registration question after sales begin: answer-backfill card

Use aggregate counts and role names only. Do not place attendee names, contact details or individual answers in this card. Apply the actual rules of your ticketing provider.

| Event / session | Change version / date | Change owner role | Answer needed by (if real) |
|---|---|---|---|
| [ ] | [ ] | [ ] | [ ] |

## Define the change

- Question and answer choices: [ ]
- Why the answer will be used: [ ]
- Who answers: [ ] buyer / [ ] each attendee
- Applicable ticket types or sessions: [ ]
- Is the answer required for a later task? [ ] no / [ ] yes — task: [ ]
- If the answer is optional, what happens when it is blank? [ ]

**Example without personal data:** “Would you like a printed programme?” Choices: Yes / No. Use the aggregate response count to plan printing; do not treat no answer as Yes.

## Check the two cohorts

| Cohort | What changes | Verified path | Owner role / evidence |
|---|---|---|---|
| Future buyers | New question appears at the provider's actual question stage | [ ] Test order [ ] ticket status checked | [ ] |
| Existing ticket holders | Existing ticket and answer state remain as the provider reports | [ ] Self-edit or approved reply path [ ] no unintended admission change | [ ] |

## Backfill existing answers

- [ ] Record the applicable existing-ticket count before changing the form.
- [ ] Check whether the platform identifies missing answers to this question specifically, or only a broader missing-details group.
- [ ] Verify the link or route by which existing holders can answer; test it without exposing another person's record.
- [ ] Prepare a concise request stating the question, reason, real deadline if any, and support route. Send only through an approved audience workflow.
- [ ] Recheck status before follow-up so completed answers are not requested again.

| Applicable existing tickets | Answered | No answer | Not applicable | Difference to resolve / owner role |
|---|---|---|---|---|
| [ ] | [ ] | [ ] | [ ] | [ ] |

Close the change when future checkout has been checked, the existing cohort has an answer route, and the unresolved aggregate count has an owner. Do not infer that making a question required changes tickets already issued.