A UST workflow in Stratum
An annual visit, from site record to report.
One customer. One site. The equipment, forms and people behind the job stay connected through the field work, office review and the record kept for next time.
Canyon Field Services
Juniper Station
Juniper Fuel Group
- Job
- WO-104 · In progress
- Configured scope
- Annual
- Equipment records
- 16 connected assets
- Required forms
- 4 form types
Fictional company, site and records. This Annual scope illustrates a configured workflow; it is not a complete compliance program or a test procedure.
The job starts with the whole site.
Each tank, line and device has its own identity. Their connections give a form its context: which line a detector serves, which tank a probe sits in, and which ATG monitors a sensor.
Tanks
3- Tank #1
Tank field · Position 1
- Tank #2
Tank field · Position 2
- Tank #3
Tank field · Position 3
Lines
3- Line #1
Tank #1 to dispensing area
- Line #2
Tank #2 to dispensing area
- Line #3
Tank #3 to dispensing area
Leak Detectors
3Automatic tank gauge
1- ATG #1
Office · Monitoring console
Probes
3- Probe #1
Tank #1
- Probe #2
Tank #2
- Probe #3
Tank #3
Sensors
3This example uses three sensors. Equipment, relationships and required work are configured for the actual site.
Define the work before the crew arrives.
The office assigns the site’s Annual scope to WO-104. The job brings the equipment, required forms and crew together, with the due date and visit window shown separately.
- Scope
- Annual
- Requirement due
- October 14, 2026
- Scheduled visit
- October 14, 2026 · 09:00–12:00
- Office
- Prepares the site, scope, assignment and required output.
- Tech #1
- Records the field work against the assigned equipment.
- Helper #2
- Supports the visit as assigned by the team.
- Reviewer
- Checks the returned records and routes questions back.
The right form, tied to the right equipment.
The technician opens the job’s assigned forms. Each record retains the equipment references the office needs to understand and review the return.
RP C-9
Line leak detector performance
These are simplified record summaries. A reviewed record does not mean the equipment passed its technical test. C-9 documents line leak detector performance; line tightness is a separate form.
RP C-8 · Sensor #2
One open question. A clear next step.
The submitted location says “Sump.” The reviewer needs the specific location before the report is prepared.
Current example: in progress. 3 forms reviewed; 1 still needs correction. The final report has not been prepared.
Keep the record useful after the visit.
Once the required review is complete, the office can prepare the report from the configured forms. The site keeps its work history; authorized customers see the reports published to them.
Previous closed visit · WO-052
Annual report · 2025
Juniper Station · October 14, 2025
- RP C-7
- RP C-8
- RP C-9
- Line Tightness Form
ClosedPublished to customer
One history. Different access.
- Compliance Vault
- Keep internal source documents with the customer, site and linked equipment.
- Customer reports
- Give authorized customers access to the reports your team publishes. Internal field records stay separate.
- Next required work
- After the prior job closed, its configured cycle supplied the next due date: October 14, 2026. A due date still needs a scheduled visit.
The previous packet illustrates the completed cycle. The current WO-104 still has an open correction. Report publication does not confirm an email was delivered, a regulator accepted it or remedial work was completed.
Walk through a job like yours.
Bring a typical site, a form and the report your customer needs. We’ll show you how the records connect in Stratum.