Inspections

Overview

Inspections let you track when each device was last checked and when it is due next. Inspection schedules are driven by the device type's configured inspection types and their frequencies. When a device is created, Forz automatically sets initial due dates. Technicians record inspection results (Pass, Fail, or Bypass) during field visits, and Forz calculates the next due date based on the frequency.

Before You Begin

Prerequisites:

1. You have the Device Inspections: Create permission on your role.

2. At least one device exists in a system.

3. Inspection types are configured on the device type (these define the frequency and name of each inspection).

Understanding Inspection Frequencies

Forz supports the following inspection frequencies. The due date is calculated from the current date when the device is created or after an inspection is completed.

How Due Dates Work

When a device is created, Forz checks the device type's inspection types and sets an initial due date for each one. Due dates are stored as a JSON array on the device record, with each entry containing the inspection type name and due date.

A device can have multiple inspection types, each with its own frequency and due date. For example, a fire alarm pull station might have:

• Monthly visual inspection — due every 30 days

• Annual functional test — due every 365 days

Recording a Device Inspection

1. Open the device that needs inspection (navigate to the system, then click the device).

2. Click New Inspection or open the inspection form.

3. Select the inspection result:

• Pass (the device meets all requirements).

• Fail (the device did not pass inspection (requires follow-up).

• Bypass (the device was intentionally bypassed (document the reason).

1. Attach a Photo if required by your inspection protocol.

2. Click Save.

Expected result: The device inspection record is created and linked to both the device and the parent inspection. The due date for this inspection type advances to the next interval based on the configured frequency.

Tip: Attach photos to inspection records for documentation and compliance. Inspection photos are synced to the mobile app for field technicians to capture on-site.

Viewing Inspection History

1. Open the device from the system's device list.

2. The inspection records are listed chronologically, showing the inspection type, result (Pass/Fail/Bypass), date, and any attached photos.

Expected result: You see the full inspection history for this device, including all inspection types.

Identifying Overdue Inspections

Devices with overdue inspections have due dates in the past. Use the inspection view to identify which devices need attention.

1. Navigate to the system's device list.

2. Devices with overdue inspections are highlighted or flagged based on their due dates.

3. Open the device to see which specific inspection type is overdue.

Expected result: You can identify and prioritize overdue inspections across your device inventory.

What Happens After Recording an Inspection

When an inspection is saved, Forz automatically:

• Creates an inspection record — linked to the device and the parent inspection, with the result and optional photo.

• Updates the due date — the next due date for this inspection type is calculated based on the frequency.

• Syncs to mobile — the inspection record is available on the mobile app (via the Syncable concern).

Warning: Deleting a device removes all its inspection records permanently. Export or review inspection history before deleting a device if you need the records for compliance.

Common Scenarios

Monthly fire alarm pull station inspections

A fire protection company inspects all pull stations in a building every month.

1. Open the fire alarm system for the building.

2. For each pull station, open the device and click New Inspection.

3. Visually verify the pull station is in good condition and accessible.

4. Select Pass if the device meets requirements, or Fail if it needs repair.

5. Attach a photo of the device.

6. Save. The next monthly due date is set automatically (30 days from today).

Annual backflow preventer testing

A plumbing company performs annual backflow preventer certifications for commercial properties.

1. Open the plumbing system and locate the backflow preventer device.

2. Click New Inspection.

3. After running the test, record the result: Pass if the backflow preventer holds within tolerance, Fail if it needs repair or replacement.

4. Attach a photo of the test gauge readings.

5. Save. The next annual due date is set to 365 days from today.

Bypassing a device during construction

During a building renovation, a smoke detector must be temporarily bypassed.

1. Open the fire alarm system and locate the smoke detector.

2. Click New Inspection.

3. Select Bypass as the result.

4. Add a note or photo documenting the bypass reason (e.g., "Construction dust -- bypass until renovation complete").

5. Save.

Troubleshooting