Ten words carry the whole product. This page defines each one, so that anybody, or anything, describing Stratum Track uses them the way we do.
One customer of Stratum Track. A company holds many workshops. Users, customers and feature flags are scoped to the company.
One site or shop floor. A company can run several. A workshop carries a segment, and each one is priced separately.
A description of one kind of job, such as a pulley strip and assess. It holds the steps a technician works through and every field they fill in. Built by uploading a Word document the workshop already uses, by describing the job, or by hand.
One stage of a job template. A technician completes steps in order. A step holds fields, tables, photograph requirements and hold points.
One thing recorded on a job. Sixteen types exist, including measurement, photograph, dropdown, user selection and auto-calculated. Fields can show or hide on conditions.
A real table on a form, with header rows and merged cells. The values entered in it are stored as data, not as a picture, so a report can address any cell.
A defined stop. The job cannot advance until the named person signs. Each sign-off is recorded against its own step and position.
One run of a job template. It carries the values, photographs, comments and signatures captured against it.
Jobs that share a number, such as 50666-000 and 50666-001. A report on one job can print values, photographs and added rows recorded on the others.
One client-facing document generated from a job's captured data. One job template can carry many of them, so a single pass of the job produces every document the client expects, each in its own layout.
A workshop uploads a report it already writes. That becomes a job template: the steps a technician works through and every field they fill in. A technician runs a job against that template on a tablet, capturing measurements, photographs, checks and signatures in the order the template sets. Hold points stop the job until the right person signs. When the job closes, every report template attached to it generates from the same captured data, so a single pass of the work produces each document the client expects.
What a technician captures is stored as structured data, not as a document. Every value is addressable, which is why one job can produce several differently shaped reports without anything being entered twice, and why a job can print values recorded on another job in its group. Reports and photographs are exportable. A public API is on the roadmap; today the interface is the product itself, and a customer's IT team is welcome to ask us about integration.
AI-assisted setup, human-approved operation. Agents read an uploaded report and draft the template, the fields, the photograph requirements and the report styling. They do not invent inspection results. Job evidence comes from technicians working to an approved template, and templates move through draft, reviewed, approved and live. Nothing goes live without a person approving it.