Skip to main content

Understanding Reports and Inspection Forms

How report templates work — field types, prepopulated data, composite fields, and the report status lifecycle.

Overview

Reports are the primary way inspections and observations are documented in SwiftComply Stormwater. A form defines the fields, layout, and PDF output. A report is a single completed inspection an inspector creates and fills out from a form. Reports are created at the site level and progress through a status workflow.


Key concepts

Forms

💡 Organizations with Form Builder access can create and edit their own forms and PDF outputs. If your organization doesn't yet have access, forms are managed by the SwiftComply team — contact your SwiftComply representative.

The form's fields and structure are built in the Input Builder — see Building Forms with the Input Builder.

Each form defines:

  • The form fields (text, dropdown, date, checkbox, signature, GPS coordinates, photos, etc.).

  • Prepopulation rules: which fields auto-fill with site data, user data, weather data, or previous-report data.

  • Composite fields: complex elements like deficiency logging, BMP entries, enforcement actions, and monitoring data.

  • Output settings: PDF orientation, weather forecast attachment, and other rendering options. The PDF layout itself can be fully customized with the PDF Builder — see Designing PDF Outputs with the PDF Builder.

Form field types

A form can include any of these field types:

  • Text / String: free-form text input.

  • Date: date picker.

  • Time: time picker.

  • Select / Dropdown: choose from a list of options.

  • Boolean / Checkbox: yes/no toggle.

  • Signature: digital signature capture.

  • Geocoordinates: GPS coordinate capture.

  • Images / Photos: photo uploads.

  • Multi-value: multiple values in one field.

  • Groups: sections that organize related fields together.

Prepopulated fields

Forms can be configured so that some fields auto-fill with data the system already knows. Common sources include:

  • Site data: site name, address, owner contact info, coordinates, status, notes.

  • User data: inspector name, email, phone, title, certificate ID.

  • Date data: today's date, tomorrow's date, dates from a previous report.

  • Weather data: last storm start/end dates, latest storm since the previous report, ongoing storm data.

  • Instance data: organization name, Site Profile title.

  • Previous report: any field value from the most recent previous report can be carried forward.

Whether a prepopulated field is editable or locked depends on how the form is configured. Some prepopulated fields are meant as a starting point and can be changed in the report; others are locked. There is no visual color difference between prepopulated and non-prepopulated fields, all editable fields look the same in the report.

Composite fields

Composite fields integrate other parts of SwiftComply directly into the report:

  • Deficiencies: log and manage deficiencies inside the report. Can prepopulate with currently open deficiencies or deficiencies from the previous report.

  • BMP Implementation: document BMP conditions and tie them to deficiencies.

  • Enforcement Action: record enforcement actions within the report.

  • Monitoring Sites: enter monitoring data for designated sampling points.

  • Education Interaction: log education outreach interactions.


Report lifecycle

Reports move through a status workflow:

  1. Draft: the report has been created and is being filled out. It shows as [DRAFT] in lists. Use Save Draft to save your progress, including photos and other attachments.

  2. Published / Submitted: the report has been finalized and submitted. The publisher's user and timestamp are recorded.

  3. Approved: if your workflow has approval enabled, an administrator reviews and approves the report. Approver and approval date are tracked.

  4. Emailed (optional): the report can be emailed to stakeholders.

Not all instances use the approval workflow. If approval is not configured, reports go directly from Published to their final status.


FAQ

Q: Why are some fields already filled in when I open a report?

A: Forms can be configured to prepopulate certain fields automatically (for example, today's date, your name, the site address). Whether you can edit a prepopulated value depends on how the form was set up; some can be changed and some are locked.

Q: How do I save my progress on a report so I can come back later?

A: Click Save Draft while filling out the report. Your draft, including any uploaded photos, is preserved and you can return to it later from the site's report list.

Q: Can I use the same form across multiple programs?

A: Forms are created per program. Similar forms can be set up for different programs by SwiftComply, but they are separate form records.

Q: Who can change forms?

A: Administrators in organizations with Form Builder access can create and edit forms and PDF outputs directly — see Getting Started with the Form Builder. If your organization doesn't have Form Builder access, contact your SwiftComply representative.

Did this answer your question?