Compliance: shipped end to end
Your network's regulatory and internal requirements, versioned then executed in the field — every result sealed by a proof, every finding tracked to resolution. This domain runs today on the BranchCheck engine.
In the free trial, this domain's screens start empty: the shared demo pre-fills inspections only.
The business problem
A risk or compliance department runs a branch network without being able to inspect everything in person: it delegates controls, aggregates results, and must show — control by control, year after year — that every conclusion holds. Between the procedure binder and the tracking spreadsheet, it is the proof that gets lost; and the proof is exactly what a regulator asks for.
What runs today
Shipped and executable end to end on the common engine in v1.5 — every brick below exists in the product, not on a roadmap.
Versioned with an effective date
Regulatory and internal requirements published and versioned with an effective date, never hard-coded; the history of versions and decisions is kept.
Control campaigns
Goal, scope, period, population, success criteria: your compliance control scheduling is a recurring campaign on the engine — one-off or automatic.
Four-state evaluations
Compliant, non-compliant, not applicable, missing data: four distinct states, never conflated in aggregation — the score says what it measures.
Score and cartography
Compliance score and cartography by scope — branch, zone, process — explainable down to the source data and the proof carrying it.
Findings and corrective actions
A non-compliant point becomes a finding, then an action: owner, deadline, resolution proof, a validation distinct from the execution.
Proof files
Every submission is sealed — geolocated photos, signatures, timestamps, integrity hash — and exports as a readable evidentiary file, shareable in a controlled way.
The requirements specification, requirement by requirement
The specification's requirements for this domain — and, facing each, its real status in the product.
| Code | Requirement | Priority | Status |
|---|---|---|---|
| CON-01 | Manage versioned regulatory and internal requirements. | P1 | Covered |
| CON-02 | Tie each requirement to controls, a frequency, a criticality and an expected proof.Frequency, criticality and expected proof are in the API, not yet in the admin form; no link to a control-plan line. | P1 | Partial |
| CON-03 | Produce a compliance score and cartography by scope. | P1 | Covered |
| CON-04 | Manage findings, remediation plans, validations and closures. | P1 | Covered |
| CON-05 | Keep the history of versions and decisions. | P1 | Covered |
| CON-06 | Generate proof files that export and share in a controlled way. | P1 | Covered |
Codes and priorities: functional and technical requirements specification, §4.3 and §7.