Pass, fail and what happens next
An inspection is only useful if a failure goes somewhere. This is how to wire that up.
Pass / fail / N/A
Use a dropdown or a toggle for the verdict on each line. Mark the field so a fail is distinguishable from an unanswered question — "not checked" and "checked and bad" are different facts, and a blank cannot tell them apart.
Ask for evidence only on a fail
Put the photo field, the severity and the notes behind conditional logic on the verdict. They appear when someone selects fail, and stay out of the way the rest of the time. This is the single biggest difference between a form crews fill in properly and one they rush.
Making something happen
On-submit rules let a failure do something rather than sit in a document:
- Email the PDF to a customer, a manager or a fixed address
- Notify a role
- Raise a corrective action when a specific answer is chosen
Set these on the form, under its settings. A rule that fires on "any Fail" means nobody has to read the whole report to notice.
Approvals
If the form needs a second pair of eyes, add an Approval chain. The submission goes to whoever you nominate and is held until they approve or reject it, with their decision recorded on the record.
Still need help?
Email Support@gofieldwizard.com and a person will answer — include your company name and, if it's about a particular form or job, its name.