Collect the details.
Put them to work.

Yes. Write labels and guidance in your studio's voice. A label such as Uniform # can still map to the shared Jersey Number meaning used by your templates.

The editor supports text, numbers, choices, checkboxes, longer answers, dates, and an event-team selector. You can mark answers required. Semantic meanings are available for compatible input types; the example above shows a selection of them.

A page groups related questions into one screen. Parents use Next and Back to move through the same form. Each row can hold one full-width field or two half-width fields.

It tells Batch Relay what an answer means. Print Name, for example, identifies the name to use in a connected template, even if you label the question differently. Choose the meaning for the field; simply renaming a question does not change its mapping.

Yes. Use an existing form as the starting point for a new draft. Keep last season’s questions, add a Jersey Number field for this season, and review the parent preview before publishing the new version.

No. Work in a draft and publish a new event-form revision when it is ready. Published revisions are immutable. The editor's publication review explains the changes and their registration consequences.

Parent-facing personalized print previews are coming soon. The form editor already has a parent-form preview for reviewing questions, pages, and validation. The artwork on this page illustrates how mapped answers personalize a template.

Yes. Read reusable definitions and event-form revisions, create and update drafts, and publish revisions with the appropriate permissions. Write and publish operations require live credentials; test keys can read forms. Explore developer tools