Permanent control, shipped on the engine
Your network's permanent-control plan — by process, risk and frequency — executed and proven on the same engine as your inspections and compliance. This domain runs end to end today.
In the free trial, this domain's screens start empty: the shared demo pre-fills inspections only.
The business problem
Permanent control usually lives in three places at once: an annual plan in a spreadsheet, level-1 controls filled in by branches, level-2 controls run by head office. The plan's real coverage — what was done, by whom, on which sample, with which result — is rebuilt by hand, when it is rebuilt at all.
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 control plan
By process, risk, scope and frequency: the plan is versioned, not copied from one spreadsheet to the next.
L1 and L2 controls
Level-2 controls are generated from level-1 results.
Reproducible sampling
Method, rate and seed documented: the sample replays identically.
Coverage and completion
Plan coverage and completion rate computed separately — one never hides the other.
Automatic escalation
Late or critical controls escalate in three tiers, with no manual chasing.
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 |
|---|---|---|---|
| CP-01 | Define a control plan by process, risk, entity and frequency. | P1 | Covered |
| CP-02 | Schedule level-1 and level-2 controls. | P1 | Covered |
| CP-03 | Manage sampling and document the method used. | P1 | Covered |
| CP-04 | Record result, anomaly, incident, proof and comment. | P1 | Covered |
| CP-05 | Compute control coverage and completion rate. | P1 | Covered |
| CP-06 | Automatically escalate critical or late controls. | P1 | Covered |
Codes and priorities: functional and technical requirements specification, §4.3 and §7.