Overview
Inspection templates define the form your inspectors fill out. Instead of one fixed report, you build forms that match your program — a detailed annual site inspection, a dental facility visit, or a quick field check. Every inspection you schedule uses one of your templates.
Where templates live
Go to Configurations > Templates. The Templates page lists your templates by category — inspection templates live under Oversight.
SwiftComply includes two inspection templates to start from:
Hard Copy Inspection Report Upload — mirrors the classic fixed inspection form. Your existing inspections were moved onto this template and work exactly as before.
Annual Facility Inspection — an example built from real customer inspection forms. Edit it, copy from it, or delete it if it doesn't fit your program.
Creating an inspection template
On the Templates page, click New Template.
Choose the Oversight category, then the Inspection document type.
Name the template. Template names must be unique — across every category, not just inspections.
Build the form (next section) and save.
The three kinds of fields
System fields fill in automatically from the Industrial User's records when the inspection is completed — things like Location Name, Account Number, Discharge POTW, SIC/NAICS codes, addresses, and permit information. Place them where you want them; inspectors never type them.
Data entry fields are the questions your inspector answers. Eight types:
Field type | What the inspector sees |
Short Text | A single-line answer |
Long Text | A paragraph answer |
Date | A date picker |
Time | A time picker |
Numeric | A number |
Checkbox | A checkbox |
Multiple Choice | Your options, shown as radio buttons or a dropdown — your choice when you configure the field |
Photo Upload | Inline photo upload — the photos render in the finished PDF |
Inspection fields are purpose-built for the inspection workflow:
Field | Notes |
Inspection Start | Date/time — required in every inspection template |
Inspection End | Date/time — required in every inspection template |
Inspection Due Date | The scheduled due date |
Inspection Result | Pass / Fail |
Inspection Type | Scheduled / Unannounced |
Inspection Reason | Annual / Violation / Complaint / New Facility / Other |
Authority Follow Up Required | Yes/No — adds a description field for the details when needed |
IU Corrective Actions | Yes/No plus a description — the pair inserts together |
Samples Taken | Yes/No |
IU Representative Signature | Name entry plus a signed-on date/time — the pair inserts together |
Nonconformances | The inspection's nonconformances table |
Required fields are marked with an asterisk in the editor's sidebar. Everything except Inspection Start and Inspection End is optional.
Editing and maintaining templates
Changing a template affects future inspections created from it. Completed inspections keep the form they were completed with.
The default templates are yours to change — edit or delete them like any other.
FAQ
Why is my template name rejected when I try to save?
Template names are unique across ALL categories. Pick a name not used by any other template, including permit templates.
Why won't a field delete from the form?
It's required. Inspection Start and Inspection End must stay in every inspection template.
Why does an inspection show old questions?
It was created before your template change. Template edits apply to inspections created after the change.
Related articles
Scheduling and Completing Inspections
Recording Nonconformances on an Inspection
Understanding Permit Templates and System Tables