Testing never changes your scores by itself. When a test shows something's wrong, it makes proposals for the assessor and flags the unit, so the next assessment takes it into account.
What a proposal can be
The tester said | Proposal | On |
|---|---|---|
The control is poor in practice | Lower its confirmed effectiveness | the control |
The control is weak by design | Lower its strength, or add a new or changed control | the control |
The inherent risk is wrong | Raise the unit's likelihood | the unit |
Where you see them
A banner at the top of the unit screen, for example "Since the last assessment: 1 test Not effective (PTO guards, 22%), finding FND-0014 still open."
On the control's card, which opens its Testing by itself when a proposal is waiting.
A flag on the unit's Back-Log and board cards.
The Proposals tab of the unit's history.
Apply one
Click Apply on the proposal. The usual dialog opens (confirm the control, edit the control or override the score) with the suggested values filled in. Check them, give a reason and save.
If a control change and a likelihood change come from the same test, Conform warns you about counting it twice. Only raise the likelihood if the exposure itself has changed.
Re-cycle now
Usually a flagged unit is dealt with at its next cycle. For serious cases (a life-threatening failure, say) use Re-cycle now on the Controls panel to bring the unit back for assessment straight away.