GroundOS / evidence
Reconstruct incidents, trace materials and review recorded work with the context and history attached.
Inside an incident record
Select a moment to inspect its location, source and response. The linked camera frame stays tied to its capture time.
A position sample places the steel fixer’s tag near CRN-04. Inspect the next event to follow the warning and response.
The supervisor acknowledged the event and requested an access check. The HSE lead must confirm the site conditions, review the location history and record the follow-up. A warning record alone does not establish a collision, fault or completed corrective action.
Inside a material record
Open the receipt, follow the revisions and distinguish material arrival from accepted work.
12 t received
Report #042 rev 1 identifies the next steel requirement and crane-access constraint.
DR-018 records procurement approval of the morning slot. Delivery plan v4 supersedes v3.
RCV-024 records 12 t against batch ST-0917. The certificate and receipt photo stay linked to the delivery.
A reviewable evidence package
A record index connects each source to its version, date and review state. Take the example with you to inspect the structure.
| Record | Linked sources | History / state |
|---|---|---|
| INC-016 | Location samples, Camera 04, response | Review open · HSE lead |
| DR-018 | Report #042 rev 1, delivery plan | v3 → v4 · approved 16 Sep, 17:10 |
| ST-0917 | DEL-024, RCV-024, certificate reference | 12 t received · acceptance pending |
| SC-03 | Steel team, recorded reinforcement work | Activity context · work review required |
A two-page project review with incident history, decisions and material traceability. The JSON index is available for technical review. Both describe this product example; original source files are not included.
For North bridge, subcontractor SC-03’s steel team is associated with deck reinforcement in Zone B. Team activity, field observations and recorded quantities appear alongside inspection and approval records.
Presence alone does not establish completed work. The receipt of batch ST-0917 also does not prove installation or acceptance. Work acceptance remains pending until the responsible reviewer records it.
Prepare daily reporting, incident reviews and handover records with references to the underlying observations, images, revisions and decisions. Review the draft before sharing.
An export package brings together a readable report, a record index and associated source files. Agree formats, date ranges, access and retention around the people receiving the package.
DR-018 starts as a proposed delivery change on 16 September. The procurement lead checks stock and supplier availability. Approval updates delivery plan v3 to v4; DEL-024 and RCV-024 then record the 17 September delivery and receipt.
Keep earlier revisions visible so a reviewer can distinguish what was known at the time from what was added later.
Preserve timestamped history and cryptographic fingerprints so a reviewer can check whether retained records have changed. Independent verification keeps that check useful beyond the original workspace.
Integrity supports provenance. It does not establish that an observation is true; source quality, missing information and human review still matter. We’ll define the verification and export format around your review process.
GroundOS