We frequently use TNEW custom fields to collect additional data needed from each ticket holder (for example name for nametag, pronouns, dietary requirements, accessibility needs, etc.) However, TNEW custom fields can only be tied to the individual performance line item, not to specific sublineitems/ticket holders. So if someone chooses to add three tickets to their cart, we may or may not get all the information we need for each ticket.
The result is a messy hybrid where, even with custom procedures, someone or something has to try to sort out which data went with which registrant, whether they filled out more or fewer forms than they bought tickets. This creates a huge amount of additional work for staff coordinating programs.
It should be possible to define a set of fields that must be filled in for each ticket sold, and the UI should dynamically add or remove these as tickets are selected on the performance page and ensure that required data is actually filled in for each ticket.
PS: I will also note strong support for Anne Robicheaux's point that native tool for saving these responses as structured data (rather than stashing them in the notes field of CSIs) would be a huge win. Tessitura should be at least as good at collecting and exporting usable form data as Google Forms, Microsoft Forms, etc.