Configuring Inspections
What is Inspection Configuration?
Inspection configuration is the process of defining what gets checked, how often, and on which assets. An inspection has two parts that must both exist before an operator sees anything: an inspection form (the questions) and an inspection schedule (the assignment to a specific item with a due date and frequency).
Key point: The form defines the questions for an inspection type; the schedule assigns that form to a specific asset on a specific interval. You can create one inspection form and assign it to hundreds of assets — or configure unique forms per asset type.
What Can Be Inspected
Inspections can be assigned to the following item types:
- Tanks
- Field Locations (Wells)
- Plants
- Vessels
- Pipelines (sender to receiver — right-of-way inspections)
- Misc Items
- Gas Flow Measurements
- Liquid Meters
Setup Overview
Step 1: Create an Inspection Form (Admin → Form Config)
Step 2: Assign Inspection Schedules
Option A — Bulk: assign to multiple assets from the Form Config page
Option B — 1x1: assign directly on each asset's config page
Navigate to Admin → Form Config and create a new form with type Inspection.
Inspection forms use the same question engine as all other forms, with these important differences:
Pass Values Are Critical
Pass values define which answers are acceptable on Radio and Select questions. The EZOPS system compares each submitted answer against its pass value to determine whether the inspection passes or fails:
- If a question has a pass value set — answering with anything other than the pass value fails that question, automatically generating a task
- If a question has no pass value set — any answer will fail the question and generate a task
- Pass Required — forces the operator to select the passing value before they can submit the form (useful for mandatory compliance checkpoints)
Always set pass values on every Radio and Select question in an inspection form. Leaving them blank will cause every submission to fail every unanswered question.
Sections Are Not Available
Inspection forms cannot use sections. Inspections are designed to be completed in a single offline session by one operator. All questions are presented at once.
Workflows Are Available
Inspection forms support workflows (email notifications and corrective action tasks). Note that failed questions already generate tasks automatically — workflows are additional, configurable actions on top of that.
Departments Are Available
Assign a department to control which supervisors are notified via workflows.
Replacement Questions
The Replacement answer type is unique to inspection forms. Use it on questions where an operator may be replacing a physical item (e.g., a gasket, filter, or valve component) during the inspection.
Previous Value Visible
Enabling Previous Value Visible on a question displays the answer from the last completed inspection alongside the current question. This helps operators identify whether a condition has changed since the last check.
Step 2A — Assign Inspection Schedules in Bulk (Form Config Page)
The Form Config page allows assigning a single inspection form to many assets at once — the most efficient path when setting up inspections for a new asset class or rolling out a new inspection type across multiple locations.
- Open the inspection form on the Form Config page
- Go to the Schedules tab
- Select the asset type to assign to (Tank, Well, Plant, Vessel, Pipeline, etc.)
- Select the specific assets to assign this inspection to
- Set the schedule parameters (applies to all selected assets):
- Due Date — when the first inspection is due
- Frequency — how often the inspection repeats (interval + unit: days, weeks, months, years)
- Repetition Type — Dynamic, Static, or Window
- Warning Period — number of days before the due date that the inspection becomes visible to operators as upcoming
- Save — schedules are created on all selected assets
Use bulk assignment when deploying a standard inspection across many similar assets (e.g., assigning a Tank Visual Inspection to all tanks at all plants).
Step 2B — Assign an Inspection Schedule on an Asset's Config Page (1x1)
Individual inspection schedules can be created directly on each asset's configuration page. This is the path for:
- Adding a new inspection to a single asset
- Assigning a different inspection form to one specific asset that differs from the rest
- Making per-asset schedule adjustments (different frequency, warning period, etc.)
For Tanks:
- Navigate to Admin → Tanks and open the tank
- Go to the Inspections tab
- Click Add Inspection Schedule
- Select the Inspection Form to assign
- Set the schedule parameters (due date, frequency, repetition type, warning period)
- Save
For Wells (Field Locations):
- Navigate to Admin → Field Locations and open the well
- Go to the Inspections tab, add and configure as above
For Plants:
- Navigate to Admin → Plants and open the plant
- Go to the Inspections tab, add and configure as above
For Pipelines:
- Navigate to Admin → Pipelines and open the pipeline group
- Go to the Inspections tab on the relevant line group
- Add and configure the inspection schedule as above
The process is the same across all asset types — open the asset, find the Inspections tab, add the schedule.
Schedule Parameters Reference
| Field | Description |
|---|---|
| Inspection Form | The form (question set) to use for this inspection |
| Due Date | The date the first inspection is due |
| Frequency | How often the inspection recurs (e.g., every 30 days, every 1 year) |
| Repetition Type | Dynamic (from last completion), Static (fixed calendar), or Window (open period) |
| Warning Period | Days before due date that the inspection appears as upcoming to operators. Applies to Dynamic and Static; Window inspections appear when their window opens instead |
How Inspections Work for Operators
Once a schedule is assigned:
- The inspection appears on the asset's page and on the dashboard as upcoming. For Dynamic and Static schedules this happens once the inspection is within its warning period or is overdue; for Window schedules it happens as soon as the window opens, which may be well before the due date
- The operator opens the inspection, answers all questions, and submits
- On sync, EZ Ops evaluates each answer against pass values:
- All answers pass → inspection status: Completed
- One or more answers fail → inspection status: Failed; tasks auto-generated for each failed question
- Once all auto-generated tasks are completed → inspection status changes to Rectified automatically
- A new inspection schedule is created for the next interval
If the previous inspection failed, the operator sees a warning at the top of the new form listing what failed — prompting them to pay close attention to those items.
Common Issues
"Operators aren't seeing the inspection"
- Confirm the inspection schedule is active on the asset
- Confirm the warning period is set — on a Dynamic or Static schedule, if the inspection is not yet within its warning window it won't appear as upcoming
- Operators must sync to receive new schedules
"An inspection is showing as upcoming years before it is due"
- Check the repetition type. Window schedules become visible when their window opens and stay visible for the whole period, so a multi-year window is legitimately in the Upcoming list for years. This is by design, not a misconfiguration
- On a Dynamic or Static schedule, check the warning period — visibility for those types is driven entirely by that value, so an oversized warning period will surface the inspection far earlier than intended
"Every question is failing even when operators answer correctly"
- Pass values are not set on the questions — any answer without a configured pass value fails automatically
- Open the inspection form and set pass values on all Radio and Select questions
"The inspection passed but tasks were still created"
- Workflows on the inspection may be configured to create tasks on form completion regardless of pass/fail status — review the form's workflows and add validations if needed
Tips & Recommendations
- Set pass values on every question — inspect your inspection form before deploying to ensure no question is missing a pass value
- Use bulk assignment for standard inspection types — create one form and assign it to all relevant assets at once from the Form Config page, then use 1x1 only for exceptions
- Set warning periods generously, but not excessively — a 7–14 day warning gives operators time to schedule and complete inspections without them becoming overdue. Very large warning periods are the usual cause of "why is this in my list already?" questions on Dynamic and Static schedules
- Use Dynamic repetition for most inspections — Static scheduling is better for regulatory inspections with fixed calendar deadlines; Dynamic is simpler for routine condition checks
- Remember that a Static schedule only rolls forward from its warning period onward — an operator who completes a Static inspection earlier than the warning period will find the due date unchanged. If a team consistently works well ahead of schedule, Dynamic is the better fit
- Review previous failure warnings with operators — train operators to use the previous failure warning as a targeted checklist, not just a notice to dismiss
Remember: An inspection form without a schedule is never seen by operators, and a schedule without an inspection form cannot exist. Both must be configured, and pass values must be set for the auto-fail and auto-task system to work correctly.