Ask for what you need.
A useful question tells the respondent what kind of answer would help. A label provides the question; a short description can explain the context, expected detail or reason for asking. Avoid collecting information just because another form did.
Brio offers five types: short answer, long answer, email, dropdown and a single checkbox. Use a dropdown when the choices are meaningful and limited. Use a long answer when a person needs room to explain. A required checkbox should make the choice explicit rather than hide an agreement in small text.
Give the form a shape.
Add a field from the library, select it in the canvas and edit its properties. Labels are required. Dropdowns need at least two distinct nonempty choices. Fields can be moved up or down, removed and restored with Undo last edit. The demo supports up to twelve fields and keeps a bounded configuration history.
Form settings change the title, introduction and colour theme. Every successful configuration edit increments the revision and saves locally. A template replaces the current configuration while keeping previous response snapshots. It can be undone.
Try it from the other side.
The preview renders the current configuration as an actual form. Required text must contain something beyond whitespace. Required checkboxes must be checked. Email answers are checked for a basic address shape, and dropdown answers must match an available choice.
Errors appear beside their questions and in a short summary. A valid submission saves only a local response and shows an explicit confirmation. No email address is contacted and no hosted endpoint receives the data. Use fictional sample answers to explore the flow.
An answer needs its question.
Each response stores the form title, revision and a snapshot of field identifiers, labels and types. This means an older answer remains understandable after you rename or remove a question in the builder. The response list does not pretend that every record was collected with today's form.
New and Reviewed are local review states. They do not send a notification or trigger a workflow elsewhere. A response can be inspected, marked reviewed, returned to New or removed from this browser's collection.
Take a useful copy.
The builder exports its configuration as JSON. Responses export as JSON with their full question snapshots, or CSV with columns for the questions represented across the selected records. Different versions of a label remain distinct where necessary.
CSV cells are quoted, embedded quotation marks are escaped, and text that could be interpreted as a spreadsheet formula is neutralized. Exports are local downloads. They are not synced to a spreadsheet, database or external service.
Keep the demo in perspective.
Brio is an original form-product concept. Configuration, undo history and responses are stored in local browser storage when available. Clearing browser storage removes them. Corrupt saved data falls back to a safe starter configuration and sample responses.
There is no account, public form link, hosting, automation delivery, payment collection, file upload or external submission. The product demonstrates a complete local build–preview–review workflow without claiming those services exist.
Make a form worth trying ↗