Take readiness to the field — and bring back proof.
Run inspections, walkdowns, and trial checks on any device. Capture status, photos, and findings that become evidence candidates — and route failures straight into remediation.
A signed paper checklist proves a box was ticked. It doesn’t prove readiness.
Field work still runs on printouts, PDFs, and photos scattered across phones and inboxes — so findings get lost, re‑inspections aren’t tracked, and nothing traces back to the criterion it was meant to satisfy. CitiriOS executes the work in the field and captures proof candidates that flow into the readiness chain.
Paper & PDF checklists
- A tick with no photo, no reviewer, no trail.
- Failures noted on paper, then lost.
- Re‑inspections and remediation tracked in someone’s head.
- No link from the check to the criterion or gate it supports.
Executed & evidenced
- Every item carries status, photos, notes, and an assignee.
- A failure spawns a finding and a remediation loop automatically.
- Re‑inspection and closeout are recorded end to end.
- Results become evidence candidates against the right criterion.
From template to proof — with failures handled, not filed away.
One flow carries a check from a reusable template, through field execution and remediation, to a proof candidate ready to be accepted into the evidence chain.
Built for the people doing the walk.
Hierarchical checklists — groups, sections, and items — that a field team runs on a phone or tablet, with the structure and rigor an inspection actually needs.
Any device, in the field
Execute on phone or tablet. Mark each item Pass, Fail, or N/A, with assignee, due date, and notes.
Photos as evidence candidates
Capture photos and files against each item — persisted as proof candidates, not stranded in a camera roll.
Structured hierarchy
Groups, sections, and subsections keep large inspections organized and consistent across teams and sites.
Witness the test campaign — and turn each script into evidence.
Integrated systems testing (IST / Level 5 / integrated testing) is performed by your commissioning agent and integrators. CitiriOS governs the owner’s side: witnessing the campaign, capturing per‑script results, and accepting them as the evidence a gate relies on.
- I‑01Witness against the test scriptRun the witness checklist alongside the campaign — mark each script Pass, Fail, or N/A with witness, timestamp, and notes.
- I‑02A failed script spawns a findingFeed straight into the same remediation loop — re‑test and close, with the trail intact.
- I‑03Results become accepted evidenceWitnessed results are promoted through the evidence workflow — not accepted just because the test ran.
- I‑04An IST pass gates activationTie the campaign to the RFS / beneficial‑use / revenue‑service gate as a Go/No‑Go criterion.
Delivery runs the test. You own the evidence.
The integrator proves the systems work together; the owner witnesses it, accepts the results, and lets the gate turn on them. A passed IST is proof for a decision — not the decision itself.
A failure isn’t the end of a checklist — it’s the start of a loop.
- F‑01Fail spawns a findingA failed item captures the issue, severity, and location — no separate defect log to keep in sync.
- F‑02Route to the responsible partyOpen a remediation loop to the contractor or owner team accountable for the fix.
- F‑03Re‑inspect and closeVerify the fix on a follow‑up check; the finding closes only when re‑inspection passes.
- F‑04Keep the trailWho found it, who fixed it, what proved the fix — retained end to end.
Essential & Go/No‑Go items hold the gate
An item flagged Essential or Go/No‑Go, when tied to a gate, attestation, or transition, blocks it until the item is satisfied — or formally accepted. Readiness can’t quietly move past an open critical check.
Standardize the check. Control who can do what.
Build once, run everywhere — and keep field execution governed with role‑based access, so the right people execute, review, and manage.
Reusable templates
Standardized checklists for recurring inspections, trials, commissioning/IST, transition activities, and field validation — cloned into a live list in a click.
Role‑based execution keeps field work governed:
A finished checklist is not accepted evidence.
A completed item proves the check was executed. It becomes accepted readiness evidence only when it’s reviewed and accepted through the evidence workflow — so a ticked box never masquerades as readiness.
Execution produces candidates. People accept evidence.
Photos and results flow in as evidence candidates; they are promoted to accepted evidence — and can then satisfy a criterion or clear a gate — only through Evidence & Gate Governance.
Powered by CitiriOS. Connected to the launch.
Field execution is where readiness gets proven on the ground — feeding evidence, trials, and the requests that trigger inspections.
See a field inspection run end to end.
Book a demo built around your inspections, walkdowns, or trial checks — from template to finding to accepted evidence.
Activity Lists is a CitiriOS capability. A completed Activity List item is an evidence candidate, not accepted readiness evidence — proof is accepted through CitiriOS evidence and attestation workflows. Opti suggests and cites; people decide.