The compliance board: the full concept
The compliance board is the first surface in goiso that works by a different rule than the ones you're used to. In assets, locations and inspections you create and edit the data by hand. The compliance board you never edit — it is a mirror that reflects your work, not a form you fill in. That difference is what confuses the first visit, and grasping it opens everything.
A mirror, not a form
Each standard clause's state — its color and percentage — is a derived value: computed at read time from your operational tables (inspections, locations, evidence…), never stored as a field you edit. That is why there is no "edit" button on a clause: there is nothing to edit here; the color is a result, not an input.
Start by seeding
The first time you open the board you'll find it empty — no plan yet. Don't look for a form to fill in — click "Seed". The seeding wizard turns the standard's clauses into tasks spread across your operational surfaces and your team, in one click. That lays the plan where you'll actually work.
The real work is in operations
After seeding, move to the operational world — the task board and inspections — because that's where the real work happens: you complete tasks, run inspections, and upload evidence. None of this happens on the compliance board; the board only watches and reflects.
Automatic reflection
The moment you upload evidence or close an item in operations, it reflects instantly on the board: the clause greens and the readiness KPIs rise. The Living Compliance Index (LCI) is recomputed in a nightly batch. You wrote nothing on compliance — you worked in operations, and it reflected.
Why evidence specifically? Because the color measures the claim's credibility, not its existence: closing a task is not evidence; the uploaded document is. This blocks "compliance theater."
The colors and what they mean
- Red = the entity is absent.
- Amber = present but without evidence (claimed).
- Green = present and documented with evidence.
- Excluded with justification = out of the calculation.
Details in How to track standard clauses.
The bridges between board and work
The board is no island; it connects to operations through several bridges:
- The seeding wizard: from clauses to distributed tasks (details).
- Request evidence: from a missing clause to a task assigned to a colleague who uploads the evidence on it, which reflects (how to green a clause).
- A nonconforming inspection item opens a corrective action.
All of them feed the same rule: work in operations, and the result reflects on the board.
How to read it and act
Read the board like a dashboard: where is the red and amber? To fix a red clause don't touch the clause — go to its operational surface and work (upload the evidence, close the inspection, complete the task). When you come back, it will have greened.
The rule to carry with you: seed → work in operations → it reflects; and don't touch the reflection.