Test whether the control fits
For each risk, name the exposure before choosing the control. Then ask what the control actually changes:- Probability: does it make the event less likely?
- Exposure: does it reduce the money, inventory, workload, or dependency present when it happens?
- Detection: does it reveal the event or mismatch sooner?
- Recovery: does it make the response faster, cheaper, or more reliable?
Build the register around real dependencies
Use a small number of material risks. The examples below show the required logic; replace every trigger and scope with the operation’s own evidence.
For transaction risk, a questionnaire, photograph, sample, or prior history can inform a written
check; none proves that a counterparty or whole lot is safe. Name the mismatch that stops work and
the evidence that releases it.
Measure concentration on one basis
Concentration becomes usable when the denominator is explicit: Dependency share = exposure tied to one dependency ÷ total relevant exposure Choose one basis whose parts can be added cleanly—completed orders, inventory acquisition cost, open payments, sourcing spend, or critical workflow hours—and one period or measurement date. The amount tied to one dependency must be part of the total and cannot exceed it. The total must be positive; if it is zero, the share is not applicable, not zero. Suppose an invented shop completed 90 orders in eight weeks and 72 used one venue. Its dependency share on the completed-order basis is72 ÷ 90 = 80%. That describes the concentration; it does
not make 80% a course limit or prove that the venue is unsafe. Choose the maximum and response from
the continuity your operation needs.
Faster sale or a smaller position belongs in the inventory row because it can reduce the amount or
time exposed. Cash can absorb a loss but does not prevent the event. Use neither as a substitute
for the other controls in the register.