The system of record for regulated field work.

Give field and office teams one place to work from. Stratum connects customers, sites and equipment with the forms, review and reports behind each job, so the next person can pick up with the context intact.

Customers

Keep account contacts, sites and work history together.

Sites & assets

Know what is installed and how the equipment connects.

Work & forms

Give the crew the required work and the office a clear return.

Reports & records

Keep reviewed output and history useful beyond the visit.

Customers, sites and installed assets

Know the site before the work begins.

Bring the customer, equipment and work history into view before the crew arrives. Each site keeps its own installed assets, requirements, jobs and reports, so the next assignment starts with the context already on record.

Asset types that fit your work
Define the fields your team needs, from identifiers and locations to equipment-specific details.
Connections that mean something
Link related equipment. A probe can belong to a tank and connect to the ATG that monitors it.
One place to look back
Open the site’s equipment, requirements, jobs, reports and history from the same record.
How the records connect
CustomerJuniper Fuel Group
SiteJuniper Station
Tank #1Installed asset
Probe #1Installed in Tank #1
ATG #1Monitors Probe #1

Illustrative records. Each asset keeps its own identity and connections.

Scopes, requirements and forms

Your requirements. Your forms. One workflow.

Put your operating knowledge into the work your team performs. A configured scope connects the applicable requirements, forms and evidence expectations to the right site and assets.

Define where the work applies
Use site and asset conditions to shape the scope. Your team confirms the rules for the equipment, jurisdiction and program.
Give each task the right form
Build the inputs and required records around how the work is performed, including rows tied to individual assets.
Configure the output once
Connect your forms to PDF mappings and packet templates for the reports your operation uses.
Configured scope

Annual

Juniper Station

Equipment context
ATG, probes, sensors, lines and leak detectors
Required forms
RP C-7RP C-8RP C-9Line Tightness Form
Cadence
Annual · Configured for this example
Report structure
Configured forms and packet

Illustrative configuration. “Annual” is the chosen scope, not a determination of every legal requirement.

Jobs, scheduling and field records

Turn required work into a job the crew can use.

Give the crew a clear assignment and the office a return it can follow. The customer, site, equipment and configured forms stay with the job as the work moves from scheduling to review.

Plan the visit
See upcoming work, schedule the visit and assign the crew. Keep the requirement’s due date separate from the scheduled appointment.
Complete the assigned forms
Record answers, notes and supporting files against the job and its assets. Each form keeps its own progress.
Keep the office in context
See which records are reviewed and which need attention. A correction stays with the form that needs it.
Explore the interactive workspace
One job. Individual form records.

WO-104 · Annual site visit

Juniper Station · In progress

Scheduled visit
October 14, 2026 · 09:00–12:00
Requirement due
October 14, 2026
Assigned crew
Tech #1 · Helper #2
  • RP C-7Automatic tank gauge operation inspection
    Reviewed
  • RP C-8Liquid sensor functionality
    Needs correction
  • RP C-9Line leak detector performance
    Reviewed
  • Line Tightness FormLine tightness
    Reviewed

Illustrative job. Review status describes the record, not the equipment’s test result.

Office review and reporting

Review the record. Then prepare the report.

Give the reviewer the form, its equipment context and its history. Resolve a specific correction, check the revised record and prepare the customer’s output from the configured sources.

Review each record
One form may be reviewed while another needs a correction. The original return and review history give the next person context.
Prepare connected reports
Use configured PDF mappings and packet templates to bring reviewed records into the agreed output.
Know what happened next
A generated report, published customer access and a delivery receipt are different states.
Follow a UST job from preparation to report
A correction stays with the record

RP C-8 · Liquid sensor functionality

WO-104 · Juniper Station

  1. Field return

    Sensor #2 is recorded against the job.

  2. Reviewer’s question

    Identify which sump Sensor #2 belongs to before the report is prepared.

  3. Correction requested

    The record returns to the field team. The job is still in progress.

Illustrative record review. A correction request is separate from the technical test result.

Compliance Vault and customer access

Keep the source. Share the result.

Keep the material behind the work available to your team, and the published result available to your customer. Source documents and reports stay connected to the customer, site and assets with separate access.

Your team’s document Vault

Organize source documents with their customer, site and linked assets. Keep the material behind the work available in context.

Internal source records

Your customer’s report access

Give authorized recipients read-only reports published for them. Their view contains the shared result, not every internal working document.

Contractor-published reports

Recurring work and operating history

The next visit starts with the history.

The work your team finishes becomes context for the next job. Keep earlier forms, corrections and reports beside the equipment and its next requirement. Configured recurrence carries the cycle forward when the job closes; the next appointment is scheduled separately.

See how we set up your first workflow
The record carries into the next cycle.

Juniper Station

Annual scope

  1. Previous visit

    WO-052 · Closed

    October 14, 2025

    Report
    Prepared
    Access
    Published to customer
  2. Next requirement

    Annual · October 14, 2026

    Requirement due date. The visit is scheduled separately.

Illustrative recurrence. Preparing a report alone does not close the job.

Configured around the work you do.

Start with a normal job, the forms you use and the report your customer expects. Confirm the equipment, scope, devices and outputs together before first use.

Your expertise stays at the center.

Your organization defines and reviews its requirements. Stratum carries that configuration through the work; it does not determine the technical test result or guarantee compliance. Assistance follows the agreed Order.

See your operation in Stratum.

Bring one job, its forms and the report you need. We’ll show how the records connect and talk through the fit for your team.