Guide5 min readUpdated Jun 4, 2026
Build better smart forms for site teams
Good smart forms reduce noise. Great smart forms remove it entirely, showing only the questions that matter for the actual work in front of the crew.
BYBy Team BYLT
Start from the inspection logic
The field form should branch based on the substrate, penetration type, fire class, and completion state. Avoid one static form for every scenario.
- Gate photo requirements behind actual completion states
- Ask for substrate-specific details only when they matter
- Hide certificate-only fields from field crews if office review owns them
Keep the crew moving
The right form is one a field lead can finish without hunting for the next input. Keep blocks short, labels direct, and follow-up questions conditional.
Field rule
If a question does not change the outcome, the report quality, or the certificate trail, do not show it on site.