Organisation Portal
Exceptions Register
The Exceptions Register shows, in one place, where your organisation’s controls were set aside: every waived checklist item and every override of the reviewer agents on a gate in your studios, with who granted it, under which authority, why, and when it runs out.
What it lists
Open Organisation → Exceptions Register. Each row is one exception on one work package’s gate, in one of three states:
In force — the item counts as waived.
Expired — its time ran out. The item is unmet, and the work package cannot take its next step or be released until the exception is renewed in its studio or the item is met.
Voided — a material change to the work package, a new decision on the item or a renewal cut it short.
An exception that expired and was since renewed or decided is history, not a problem; the register counts those separately, so the Expired count is what still needs someone.
What each row tells you
Organisation item — the item came from your guardrail policy, so the policy’s exception rules applied.
Expiry — an exception to one of your own items always expires, within the days the policy allows — counted in all, from the first exception to that item on the work package. The register shows when that time started. A studio’s own item may have no expiry.
Time limit restarted — shown when an item was under exception under an earlier version of the policy and the count began again under a newer one. It is a prompt to look, not a finding: where the register could not match the item itself, the label may sit on a different item of the same gate.
Granted by — the person, and how they were entitled: a studio owner or reviewer, or — where the policy names approver roles — a member of one of them, and only a member. Where the studio’s own owner holds the role the register says so, because the owner also decides who holds roles in their studio. Also approved the other side means one person granted the exception and approved the item’s other side.
It lists studios’ own items too. The register shows exceptions on a studio’s own checklist items as well as on yours, with the name of the person who granted each and their justification. Studios are told this in their own documentation.
Reading a large organisation
The register is read from each studio’s gates a part at a time, so it cannot drift from them. The page keeps reading until it has every studio and says how far it has got; Read the rest of the register carries on when it stops.
A studio that has left the organisation, or whose owner is not a member of it, is listed but not read: its gates are not the organisation’s to see.
Acting on it
The register is read-only. An exception is renewed, or its item met, in the studio that owns the work package. Whether exceptions are allowed at all, how long an item may stay under exception in all, and who may grant one are set on the guardrail policy. Reading the register needs no Enterprise contract.
