§5.3 · DECIDING · 4 MIN READ · EDITION 1.0
Approval evidence proportional to consequence
The depth of sign-off, testing and documentation should scale with the classified risk level, not with how interesting the technology is.
A Level A drafting aid needs a short intended-use note and a named owner. A Level C capability needs a qualification file, independent approval, and a monitoring plan before go-live.
Applying Level C rigor to every use case exhausts reviewer capacity and teaches teams to treat approval as a formality; applying Level A rigor to a Level C use case is a governance failure waiting to surface.
PUT THIS INTO PRACTICE
- 01Match documentation depth to the classified level, not habit.
- 02Reserve independent approval capacity for genuine Level C work.
- 03Revisit the level, not just the paperwork, when scope changes.
RELATED INSTRUMENTS
CITE THIS SECTION
§5.3 · Edition 1.0 · Approval evidence proportional to consequence