Forms

A form is an ordered list of fields, published at a public link (oratora.live/f/<code>) that collects responses over time instead of during a live event. Forms move through draft → published → closed.

Fields, not activities

Forms are built from fields rather than session activities — a superset of the same primitives: text, choice, rating, NPS, contact details, email, number, phone, date, and file-free project submissions, plus presentational section and description blocks. Each field carries its own config and, where relevant, an optional visibility rule so later fields can show or hide based on an earlier answer.

Layout

The same ordered fields can be presented a few different ways, controlled by the form's layout setting:

• Single page — the classic scroll, every field at once (the default).
• Multistep — a wizard grouped into steps at each section field.
• Conversational — one field per screen, Typeform-style.
• Card — grouped slides with the multistep step boundaries.

Layout only changes how fields are chunked and revealed to the respondent — it doesn't change how responses are stored or validated.

Use cases

A form is tagged to the dashboard section it belongs to — plain forms, hackathon project submissions, retros, or HR pulse checks — so the same field engine powers several different surfaces in the product.