RAMS. Quality. Safety. Plant.
Proof that survives the question.
Site teams, supervisors, H&S managers and quality managers need controlled forms on site and evidence that survives being asked about six months later. XO Field covers the RAMS cycle, quality and safety inspections, corrective actions and plant checks, and seals the result into evidence packs the database itself refuses to alter.
Four things you get asked to prove
All four run on the same controlled forms, and all four land in the same sealed evidence pack.
RAMS
The method statement everyone signed up to, in one place.
The RAMS cycle runs on versioned form templates, and subcontractors can submit into it from outside your tenant. Approval is recorded with who did it and when.
Quality
Inspections that cannot be half-filled.
Quality checks run as forms with built-in logic, so the form itself refuses an incomplete answer instead of leaving the gap for somebody to catch later.
Safety
What was raised, and what was actually done about it.
Safety observations become corrective actions with a history that cannot be rewritten and a discussion thread opened automatically, so the fix stays attached to the finding.
Plant
Proof the person was actually standing at the machine.
Plant checks start from a single-use QR scan tied to that session. A photo of somebody else's sticker will not work twice, so the check that happened was a real one.
Site evidence is assembled long after the fact
By the time anyone asks, nobody can prove what was true on the day. These are the three ways it goes wrong.
"We assemble the pack by hand and hope nothing changed"
When the auditor asks, the evidence is a folder put together after the fact, with no way to show that nothing was added or swapped since.
"Every project uses a slightly different form"
The form set drifts into a folder of near-identical PDFs, and the same check gets captured a dozen slightly different ways.
"Defects get raised and then disappear"
The raise sits in one inbox, the fix in another, and when closeout is questioned nobody can put the steps back in order.
What changes with XO Field
One controlled form set
One controlled, versioned form set instead of a folder of near-identical PDFs.
Issues that carry their own history
From raise to verified closeout, every step is on the issue itself.
Evidence fixed at seal
Evidence packs are fixed at the moment you seal them, and provably so.
From the form on site to proof you can hand over
Schema-driven forms, corrective actions, offline capture, plant scans and evidence packs, each recording what happened as it happens.
Site inspection forms from one controlled template set
Build the form set once, as versioned templates with schema and logic validation. Publishing a template needs two people, so the form a site fills in is one that has been reviewed.
- Versioned, not overwrittenA template change becomes a new version, keeping one controlled form set
- The form refuses a gapTemplates are validated before they can be published
- Two people, or it does not publishA publish needs a second person to review it, not one admin on a Friday
Corrective action tracking with an append-only history
Raise the issue and assign it, and a discussion thread opens automatically. The corrective action carries its closeout evidence, and closing then verifying are separate steps. Every one of them is appended to the issue's own event log.
- Nothing quietly disappearsRaised, assigned, closed and verified, all on the issue, not in someone's inbox
- An automatic discussion threadThe conversation stays attached to the defect instead of scattering
- Closeout evidence, then verificationThe corrective action carries its evidence, and verification is its own recorded step
Evidence packs sealed with a SHA-256 manifest
Build the pack while the work happens, version it as evidence accumulates, render it and seal it. A sealed evidence pack version carries a SHA-256 manifest of its contents and is protected against modification at the database level.
- Sealed means sealedA sealed version cannot be altered or deleted; the write is rejected by the database, not by a convention
- Tampering shows upThe SHA-256 manifest records what the sealed version contains
- Versioned as evidence accumulatesBuild and version the pack as work proceeds, then seal the version you will be asked about
Form capture that works offline
In a basement plant room, forms keep being completed. Work is saved on the device, shown in Saved Work To Send, and sent when signal returns, with duplicate protection on the replay.
- Saved Work To SendQueued work is visible on the device, not silently pending
- Duplicate protection on replayEach queued action carries an idempotency key, so a retry does not become a second submission
- Create, update and submitCompleting, changing and submitting form instances all queue for replay
Plant QR scanning that cannot be replayed
Scanning plant starts a signed, single-use session. A screenshot of someone else's code does not work twice, so the scan on the record is a scan that happened.
- The scan cannot be fakedEach scan starts a signed session, not just a link to a form
- One scan, one useA session works once; a second attempt with the same code is refused
- The scan has to be realA copied or reshared code cannot be used to fake a scan record
One position instead of five chases
XO Field aggregates readiness across five domains: Directory, Federation, Comp, Field and Time. And external parties can submit RAMS forms through the federation surface.
Straight answers
Does XO Field work offline?
Form capture works offline. Creating, updating and submitting forms is saved on the device, shown in Saved Work To Send, and replayed with duplicate protection when signal returns. Photos and file uploads are not queued and need a connection, and XO Field must be open to send.
Can a sealed evidence pack be edited?
No. A sealed evidence pack version carries a SHA-256 manifest of its contents and is protected against modification at the database level. The database rejects any attempt to alter or delete a sealed version.
Can we sign a RAMS in XO Field?
No. There is no signature step on a RAMS in XO Field. External parties can submit RAMS forms through the federation surface, and the submission is recorded, but it is not signed.
Does XO Field check competency before letting work proceed?
No. Readiness reads competency records and shows them as part of the project position. XO Field does not gate work on competency.
Ready for evidence that holds up?
See the form set, an issue's event log and a sealed evidence pack running against a project of your own.