Start with recurring decisions
A useful decision register names decisions that recur: approve a new platform capability, accept a risk exception, retire a service, change a technical standard or commit portfolio investment. Avoid entries such as “governance” that do not state what is decided.
Separate final accountability from preparation, execution and contribution. Several functions may contribute, but one authority must own the final decision within a defined threshold.
Add the operating conditions
Record the forum, approval threshold, evidence required and escalation route. These fields turn a responsibility statement into an executable governance contract.
If decision authority changes by risk, cost or blast radius, encode the thresholds explicitly instead of listing multiple accountable owners.
Connect decisions to flow
A decision exists inside an interaction. Show who submits the proposal, which authority responds, what conditions are returned and where the approved outcome goes next. This exposes queues and missing handoffs early.