Build breakdown

A field inspection form where every Yes opens its own follow-up questions

Summary: A mobile friendly inspection form with a repeatable "Yes shows the details" pattern for each condition, equipment counts with a live total, and a sectioned PDF report generated from each submission.

A build I made for a posted project brief. I built this as a working sample with made-up questions. It is not a delivered engagement, and nothing here is a result from live use.

The problem, as a generic brief

A team wants a form for field inspectors. For each possible issue the inspector answers Yes or No. If Yes, the form should ask for severity, location, an estimate of the extent, photos and notes. If No, nothing else should appear. The form also needs counts of equipment, a summary, a signature and a printable report, and it has to be easy to use on a phone or tablet and easy for the team to extend later.

What I built

Two versions of one commercial roof inspection form (the topic is my example, not a claim about any company):

  • A rough demo with a few issue blocks and some counts, to show the pattern quickly.
  • A fuller build with four sections: inspection details, six issue blocks, equipment counts, and a summary and recommendations section.
    • Each issue block follows the same pattern: a required Yes or No question, then severity, location, extent, photos and notes that only appear on Yes. Severity and photos become required once they show.
    • Equipment counts (for example units, vents, drains, skylights, pipes, walkways) add up to a live total.
    • A damaged equipment follow-up and a follow-up inspection block use the same pattern.
    • A sectioned PDF report template built from every submission.
    • A theme (colors, fonts, rounded inputs), a custom thank you page and a submit button.
  • A one page logic map that shows the whole form as one repeated pattern, so a non-technical reader can sign off on the logic before the build.

How it works

  1. Write the logic map first. One page that shows the stages and the Yes/No pattern, agreed before building.
  2. Build section by section with consistent field names, so a form with dozens of branches stays predictable.
  3. Add the conditions as small blocks: show the follow-up fields on Yes, hide them on No, and require the important ones once visible.
  4. Add the calculation for the equipment total.
  5. Set up the PDF report from the submission fields, organized by section with photos attached.
  6. Test the Yes path and the No path on desktop, tablet and phone widths, and with required fields empty.
  7. Document the logic so the team can add questions later.

A practical note from the build: creating a form in bulk through the platform's API can silently drop fields, so I check the field list after any batch create and repair gaps.

Stack

Jotform (form builder, conditional logic, a calculation field, PDF report editor), the Jotform API for bulk creation and repair, custom CSS for the theme, and HTML and CSS for the logic map page.

What I'd do next

  • Agree the real question list and severity scale with the team, then rebuild the blocks from the logic map.
  • Send each submission to a spreadsheet or work order system through a webhook.
  • Add email copies of the PDF report.
  • Consider an app style wrapper for tablets. If offline use matters, plan a custom app as a later phase.
Figure placeholder

FREE CHECKLIST

Get the 10-minute lead leak check.

Seven quick tests you can run from your phone to see where calls, forms, and reviews are slipping away. Choose your business type and we will also send short tips that fit.