Choices: radio and checkboxes
Configure single- and multi-select fields with labels, values, layout, and ops marking.
Video coming soon
Choices: radio and checkboxes
id: academy-selection-fields · ~2–4 min
Describe the follow-up
Audience: Admin
Radio buttons and checkboxes let field users pick from a fixed set of answers. Use Radio Buttons when exactly one option applies. Use Checkboxes when one or more options can be selected. Both field types share the same option editor in Form Builder.
Add and edit options
Open the field on the canvas and expand Options. Each row has:
- Display label — what the user sees on mobile and in reports.
- Value — the stored answer key sent with the submission. Keep values short, stable, and free of spaces when possible (for example
yes,needs_followup,tier_a).
You can reorder options by dragging. Add rows with Add option and remove ones you no longer need.
Horizontal vs vertical layout
In the field panel, turn on Display horizontally to render options in a single row. Leave it off for a vertical stack—the default on narrow phone screens.
Use horizontal layout for short yes/no or 2–3 option sets. Prefer vertical layout for longer labels or many choices so text stays readable on mobile.
Radio vs checkboxes
| Field type | User picks | Stored value |
|---|---|---|
| Radio Buttons | One option | Single value |
| Checkboxes | One or more | Multiple values |
You can convert between radio and checkboxes in Form Builder; options are kept. Existing submissions may look different after conversion because radio stores one value and checkboxes store several.
The "Correct" flag
Each option can be marked Correct. This flag is for operational marking—for example highlighting the expected answer during review or QA—not for automatic quiz scoring.
Chekku does not add up scores, pass/fail totals, or certificate UI based on this flag. Use it when supervisors need a visual hint of what "good" looks like, or when exporting data for offline grading in another system.
When to use each type
- Radio — severity level, single root cause, compliance yes/no, one product variant.
- Checkboxes — symptoms observed, services performed, equipment checked, multi-select from a checklist.
For long catalogs (hundreds of SKUs or customers), prefer a List field bound to a Data Source instead of hand-typed options.
Tips
- Keep option labels parallel ("Good / Fair / Poor" rather than mixed phrasing).
- Set explicit values before go-live; changing values later breaks historical report filters.
- Test both layout directions on a phone—horizontal rows can wrap awkwardly with long Spanish labels.
- Mark Correct only when your review process actually uses it; otherwise leave options unmarked to avoid noise.