How to add a registration question after ticket sales begin

Define the new question and its use

Download the answer-backfill decision worksheet (Markdown, English)

Write the question, choices and purpose before changing the live form. For a non-sensitive example, ask, “Would you like a printed programme?” with Yes and No choices for print planning. Decide whether a blank answer is acceptable and when the aggregate count is needed. Do not make a field required merely to fill a report. Record the owner role and intended action in the worksheet.

Separate future buyers from existing tickets

Map the cohorts separately. New buyers encounter the question at your platform's actual stage; existing holders need a ticket-edit or assisted-answer route. Decide whether the buyer or each attendee answers and which ticket types are affected. Eventbrite offers buyer-level or per-attendee questions and ticket-type targeting. Tito documents adding a question after tickets are issued. These are provider examples, not universal behavior.[1][2]

Configure and test the future flow

Add the question in the supported editor, then run an approved test order for each relevant ticket type. Check wording, options, required setting and ticket issuance. Eventbrite says its order-form questions come after an order is placed and tickets are issued once required information is provided. Tito has its own question and ticket settings. Record the observed result; do not transfer one provider's rule to another.[1][2]

Audit the already-issued cohort

Count applicable issued tickets before the change, then inspect how the new field appears. Tito says an existing ticket lacking a newly required answer can show “Details missing,” but that requirement does not retroactively stop the ticket; it applies to a later order or claim. Do not call the cohort unregistered. If the platform cannot identify the exact unanswered question, note that before selecting a follow-up audience.[1]

Verify how existing holders can answer

Confirm whether existing holders can edit details and where the answer appears. In Tito, holders can answer from their ticket page while the setting that stops attendee changes is off; organizers can also edit attendee records. Test the path with an approved test ticket without exposing another person's record. If self-service is unavailable, assign an owner to the approved support route.[1]

Request only the missing answer

Request only the new answer from affected holders: explain its purpose, any real deadline and the verified answer route. Describe the ticket's current status accurately; a new question alone does not cancel an issued ticket. Tito's message flow can target missing details, but its broad “Not filled in” group includes other omissions. Review recipients before sending and suppress resolved cases.[1]

Reconcile responses and close the change

Compare applicable, answered, unanswered and not-applicable counts for this question. Tito's question page shows answer totals and a No answer group; its broad missing-details segment is not the same count. Eventbrite documents a custom-question responses report for roles with Basic reports permission. Use your provider's actual report. Give each remaining aggregate difference an owner and close only after both cohorts' routes are verified.[1][3]