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 recordsGive 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.
Keep account contacts, sites and work history together.
Know what is installed and how the equipment connects.
Give the crew the required work and the office a clear return.
Keep reviewed output and history useful beyond the visit.
Customers, sites and installed assets
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.
Illustrative records. Each asset keeps its own identity and connections.
Scopes, requirements and forms
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.
Juniper Station
Illustrative configuration. “Annual” is the chosen scope, not a determination of every legal requirement.
Jobs, scheduling and field records
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.
Juniper Station · In progress
Illustrative job. Review status describes the record, not the equipment’s test result.
Office review and reporting
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.
WO-104 · Juniper Station
Sensor #2 is recorded against the job.
Identify which sump Sensor #2 belongs to before the report is prepared.
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 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.
Organize source documents with their customer, site and linked assets. Keep the material behind the work available in context.
Internal source recordsGive authorized recipients read-only reports published for them. Their view contains the shared result, not every internal working document.
Contractor-published reportsRecurring work and operating 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 workflowAnnual scope
October 14, 2025
Requirement due date. The visit is scheduled separately.
Illustrative recurrence. Preparing a report alone does not close the job.
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 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.
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.