Conditional logic & required fields

Show a field only when it is relevant

The walkthrough builds the classic case: a check comes back as a fail, and only then does the form ask for the corrective action, the severity and the photo. Answer pass and none of it appears. The person filling it in never scrolls past questions that do not apply to them, which is most of why paper checklists get rushed.

• Trigger — Any earlier answer — a choice, a checkbox, a number crossing a threshold.
• Effect — Reveal a field or a whole section, or branch down a different path.
• Stacking — Several conditions can gate the same field.

Enforce what cannot be missing

The required toggle blocks submission until a field is answered. Combined with logic it becomes precise rather than blunt: the photo is only mandatory on the path where a photo actually matters, so you are not forcing every clean inspection to attach an image of nothing.

Why it matters

Long forms get abandoned, and forms that let anything through produce records you cannot rely on later. Logic and required fields pull in opposite directions on purpose — shorter to fill in, harder to submit incomplete — and that combination is what makes the data trustworthy when it reaches a dashboard or an auditor.