Skip to main content

Overview

Form templates are the foundation of the PDF Form Parser system. They define the structure and fields that will be filled out during inspections. Once uploaded and configured, templates can be reused across multiple inspections for consistent reporting.

What You’ll Need

  • A PDF form file (the original inspection form)
  • System category assignment (e.g., Sprinkler, Standpipe, Fire Alarm)
  • Interval categories (e.g., Monthly, Quarterly, Annual)

Upload a New Template

1

Navigate to Form Templates

From the main navigation, go to Form Templates and click New Template.
2

Enter Template Details

Fill in the following information:
  • Name: Give your template a descriptive name (e.g., “Monthly Sprinkler Inspection”)
  • System Category: Select the fire safety system this template applies to
  • Interval Categories: Choose one or more inspection intervals (monthly, quarterly, etc.)
3

Upload the PDF File

Click Choose File and select your PDF form template from your computer. The system accepts standard PDF files.
The uploaded PDF will serve as the base template that gets filled with inspection data.
4

Save the Template

Click Create Form Template to upload and save your template. The system will process the PDF and make it available for inspections.

Configure Field Structure

After uploading your template, you can define the form fields using the Form Builder.
1

Open Form Builder

Navigate to your template’s detail page and click Form Builder.
2

Define Form Fields

The Form Builder allows you to specify:
  • Field names: Unique identifiers for each form field
  • Field types: Text, checkbox, date, photo, signature, deficiency, etc.
  • Section names: Group fields by section for better organization
  • Label names: User-friendly display names
Use consistent naming conventions across templates to make data analysis easier later.
3

Save Field Structure

Click Update Form Structure to save your field configuration.

Field Types Reference

The system supports various field types to capture different kinds of inspection data:
Field TypeDescriptionUse Case
TextFree-form text inputNotes, equipment IDs, locations
CheckboxPass/Fail/N/A optionsCompliance check items
DateDate pickerInspection dates, next due dates
PhotoImage uploadVisual documentation of equipment or deficiencies
SignatureDigital signature captureTechnician and client sign-offs
DeficiencyStructured deficiency recordingTrack failures with item, riser, and severity
System CategorySystem type selectorAuto-populated from inspection settings
Interval CategoryInspection frequencyAuto-populated from inspection settings
Field structure updates will automatically sync to all form fills based on this template (see form_template.rb:11 and form_template.rb:25-29).

Assign to System and Interval Categories

Templates must be assigned to at least one system category and interval category combination. This ensures the right template is used when creating inspections. Example Assignments:
  • Sprinkler System + Monthly = Monthly Sprinkler Inspection Form
  • Sprinkler System + Annual = Annual Sprinkler Inspection Form
  • Fire Alarm + Quarterly = Quarterly Fire Alarm Inspection Form
You cannot delete a template that has been used in existing inspections (see form_template.rb:2). Create a new version instead.

Special Templates

The system automatically creates several standard templates for every inspection:

Deficiencies Template

Captured automatically when deficiencies are found during the main inspection. This template compiles all “Fail” items for follow-up.

Additional Risers Template

Used to document extra risers or systems beyond the primary inspection form.

Corrected Deficiencies Template

Tracks resolution of previously identified deficiencies during follow-up visits.
These templates are automatically instantiated when you create a new inspection (see inspections_controller.rb:109-149).

Best Practices

  • Use clear field names: Avoid special characters or spaces in field names
  • Group related fields: Use section names to organize fields logically
  • Test before deploying: Create a test inspection to verify your template works correctly
  • Document your structure: Keep notes on custom fields for training purposes

Next Steps

Once your template is created and configured:
  1. Create inspections using the template
  2. Fill out forms during field inspections
  3. Generate reports with completed data

Build docs developers (and LLMs) love