Risk Revisions
A risk is re-assessed by opening a revision — a new record that keeps the chain's code, with the revision number raised by one. It is not an edit of the previous round.
Editing a closed assessment would destroy what the module exists to produce: a record of what was known, decided and accepted at a point in time. A revision keeps that and adds the next round beside it.
What carries over
| Carried over | Starts fresh |
|---|---|
| The definition, the scope, the owners | The residual pass |
| The threat and the vulnerability | The attachments |
| The existing and selected controls | The measures |
| The asset link | |
| The treatment option, and the measure not required switch decided with it |
The authorization matrix is not copied and never was. It lives on the main form and is read live, so a revision inherits it by belonging to the same register.
The measure-not-required switch carries over deliberately. Left behind, every revision of a risk that needs no measures would read as needing them and would park on a wait it can never leave.
Where a new round's scores start
The new round opens with the scores where the previous round ended — its residual pass where it has one, its initial pass otherwise.
Not blank, and not the previous round's opening scores either. The risk as it stands today is what a new assessment is measured against.
On a measure-free treatment the revision's residual pass is not empty either: the rule that gives such a risk a residual pass equal to its current one applies to a revision exactly as it applies to a first round.
The previous round stands down when the revision is opened
The round being revised is stood down the moment the revision is opened, not when the new round takes effect.
The reason is the register. One code means one row: leaving the previous round in force until the new one was approved would show the same risk twice — once as the assessment in effect and once as the one being prepared. That was tried and rejected on sight during manual testing.
Giving a revision up puts the previous round back in force, and the abandoned round is removed rather than parked in a state the register has to hide.
This is not tidying. The previous round was stood down when the revision was opened, so without the restore the chain would be left with a code nobody holds.
Guards on opening a revision
Three conditions, all checked:
- The revise operation on the main form's authorization matrix — a per-register right, not a system-wide permission.
- The source round must be in force. Revising a draft, a round mid-flow, or one already stood down would fork a chain with no agreed starting point.
- No other revision may be open in the chain, or there would be two candidates for "the risk".
Reading the earlier rounds needs view past revisions.
The history is a list
Past revisions is a list like any other: paging, sorting, column selection, export, and filters for round number, state and date.
Two things distinguish it:
- The chain is pinned by the record you opened it from, not by a filter the page sends. This is the whole history of one risk, and a filter the client controls is one the client could widen.
- It applies no revision filter. Showing the rounds the register hides is the entire point of it.
A round opens read-only from this list. Finished rounds are only ever read.
Where the buttons are
Both revision actions — start revision and past revisions — are available from the record itself and from the register's row menu. Somebody scanning the register can open the next round without walking into the form first.
Three absences are deliberate:
- No past-revisions button on a round that is itself superseded.
- No start-revision button anywhere but on the round in force.
- No eye on a screen that already renders the whole record.
Revisions and the Statement of Applicability
The Statement of Applicability's suggestion reads only the round in force. A control that a superseded round selected and the current round dropped is no longer a reason for the control to be applicable.
Open a revision when something changed — the threat landscape, the asset, a control that failed, an incident. Re-assessing annually with nothing to re-assess produces a chain of near-identical rounds, and the register's usefulness comes from the rounds where something actually moved.