Compliance-grade rig inspections and environmental reporting that work offline at remote sites.

Equipment integrity checks, BOP tests, and pre-tour safety briefings captured against asset and well identifiers.
Structured reporting with severity classification, root-cause workflows, and automated regulatory notifications.
Emissions, spill, and flare readings with GPS and photo evidence, exportable for regulator submission.
Digital JSA, hot work permits, and confined-space sign-offs with multi-step approval chains and expiry tracking.
Right-of-way patrols, corrosion logging, and integrity assessments tied to GIS coordinates and asset registers.
No. The mobile app downloads the form definition, its reference data and its compiled rule logic before the crew leaves coverage. Inspections, permits, photographs and audio notes are captured and stored on the device, and everything uploads when the device reconnects. There is no partial-submission state and no dependency on a live server call during capture.
Yes. The platform is designed for on-premise deployment, and air-gapped installations are supported. In that mode no vendor code runs inside your install, licence and configuration updates are applied through signed offline bundles rather than a live channel, and all data stays within your network boundary.
It enforces sequencing. Permits are modelled as a workflow: rules control which questions appear and which are mandatory, wait-for-approval nodes hold the permit at each authority in the defined order, e-signatures are verified server-side rather than trusted from the client, and timer nodes escalate as validity approaches expiry. A permit cannot reach the issued state with a step skipped.
An approval step can be configured to require either a password re-entry or a drawn signature. Verification happens on the server, which issues a single-use token that is consumed by the approval and recorded against the workflow task alongside the approver identity and timestamp. The signature cannot be reused, and the same enforcement applies whether the approver acts from the web app or the mobile app.
Yes. Role-based access control governs what any account can see and do, so contractor accounts can be limited to receiving dispatched forms and submitting their own. Forms can also be broadcast to a group, where the first crew member to accept claims the task and the rest are released, which suits shared contractor pools better than assigning by name.
Submissions export as XLSX or CSV, with an option to include one column per question, and individual records render as PDF. Exports can be run on demand or scheduled and emailed. Because every submission carries its form version, submitter, approval history and, where enabled, per-field timestamps and geostamps, the export is an evidence package rather than a data dump.