Decision architecture
A risk decision charter
A report should alter a permitted choice
A risk report earns its place in a decision when a reader can identify the uncertain mechanism, the proposed intervention and the consequence of an adverse answer. A coloured cell cannot perform that work by itself. It may direct attention, but it leaves open whether the event is well defined, whether the control operates, which loss is being counted and who may accept what remains. This study treats those unanswered questions as the substance of risk governance. Its central proposition is conditional: exposing a mechanism can improve a choice when that exposure reveals a response tradeoff or a reason to stop that a summary score would conceal.
The proposition does not require every institution to abandon a risk matrix. It requires a matrix entry to retain a route to an inspectable decision. A terse board report can work well when its underlying record is accessible and its implications are specific. An elaborate register can work badly when every field is populated with an unsupported judgment. The difference lies in the decisions a reader can challenge, not the number of columns or the visual sophistication of the reporting system. A useful summary should compress established reasoning rather than substitute for it.
Consider the fictional dispatch safeguard that runs through the worked examples. Its prevention and consequence mitigation depend on the same operating support. When that support is unavailable, neither conditional protection is available. When it is available, the prevention and mitigation effects operate together under the supplied model. A reviewer who sees installed control descriptions may assume protection continuously applies. A reviewer who asks which operating state the decision depends on encounters a materially different claim. The distinction is deliberately numerical later in the study, but it begins as a question about how the safeguard works.
Evidence and scope
Management owns risk responses; internal audit contributes independent assurance and advice.
Evidence: The Role of the Internal Audit Function in Enterprise Risk Management
Protective improvement and the optional cost condition
Illustrative USDk/year. The two proposals use the same higher shared availability and conditional effects; their declared annual costs differ.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Protective improvement and the optional cost condition | ||||
|---|---|---|---|---|
| Configuration | Residual expected loss | Annual control cost | Net annual control value | Fictional disposition |
| Source mechanism | 92.00 | 30.00 | 78.00 | Baseline illustration only |
| Lower-cost availability proposal | 38.00 | 60.00 | 102.00 | Arithmetic eligible; evidence HOLD |
| Cost-heavy availability proposal | 38.00 | 180.00 | -18.00 | REJECT optional proposal under stated condition |
The first controlled comparison makes the decision advantage observable. The availability proposal reduces modeled residual loss and has positive net annual control value under its supplied inputs. The expensive proposal produces the same modeled residual loss but fails the fictional optional net-value condition. Their protective arithmetic is identical; their economic dispositions differ. Neither becomes implementation-ready because the evidence of real availability, resource delivery and institutional authority remains absent. The fiction deliberately ends with a bounded diligence decision rather than an invented installed success.
The completed decision is a result, not a blank form. The Chair has selected a capped information mandate and withheld implementation. The Operating Owner may prepare the safeguard proposal and identify practical installation conditions, but may not treat the annual calculation as permission to operate it. The Evidence Custodian must preserve the difference between the supplied availability assumption and operating evidence. The Assurance Reviewer challenges that distinction. A missing evidence object leaves the implementation branch held even when the model is numerically favourable.
The study's worked cases are authored counterexamples, not empirical case histories. Their probabilities, event losses, control performance and costs are stipulated to expose mechanisms. No incident database, operating facility, real audit opinion or actual committee is represented. Public primary guidance supplies bounded methodological context. It does not turn the stipulated inputs into measured forecasts. This separation makes the examples useful for learning without giving them a false evidentiary status. An actual decision would require an independently supported event definition, appropriate evidence and the institution's own authority framework.
Risk governance is often described as a reporting cycle. Here it is treated as a chain of permitted decisions. A sponsor may approve information work before approving a physical change. An operator may stop a task under a delegated safety condition before the board considers a long-term redesign. An assurance provider may report an evidence gap without owning the operating response. These are different acts. Combining them under a single label such as approval obscures exposure and can promote an analytical result into implementation authority. The fictional record below therefore states exactly which act has been authorised.
The recurring committee is an invented Model Risk Chair, supported by an Operating Owner, an Evidence Custodian, a Mechanism Analyst and an independent Assurance Reviewer. These role names do not claim a real organisational chart. They separate the person who proposes a control, the person who maintains its operating evidence, the person who checks the calculation and the person who accepts or stops the next exposure. In a smaller institution several functions might be performed by fewer people, but that practical constraint would require safeguards for conflicts and explicit limits on reliance.
The record also exposes a distinction between a good annual expected-loss result and a usable proposal. A control could reduce modeled loss while costing more than the stated benefit. It could improve annual expected loss while leaving an unacceptable severe consequence. It could be affordable but lack an accepted installation or maintenance plan. It could be technically plausible but be supported only by a supplier's description. The framework must preserve these adverse branches. If every proposed control emerges approved, the demonstration has tested arithmetic while avoiding the decision that the arithmetic was meant to inform.
Completed fictional dispatch decision: RISK-DISPATCH
D is an unresolved assumed implementation boundary. All statuses are part of an authored illustration; VERIFIED ARITHMETIC means exact reproducible computation only.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Completed fictional dispatch decision: RISK-DISPATCH | ||
|---|---|---|
| Field | Recorded decision | Evidence and authority |
| Permitted exposure | Diligence only, maximum USD20.00k | R-MANDATE: fictional policy; Chair accepts and stops |
| Permitted interval | D minus 10 to D minus 3 assumed business days | R-CALENDAR: fictional relative timing; actual D unknown |
| Current implementation | HOLD both favourable and unfavourable proposals | R-AVAILABILITY and R-DELIVERY: unresolved operating evidence |
| Optional analytical condition | Net annual control value at least USD0.00k | R-METHOD: authored policy; mandatory constraints checked separately |
| Adverse cost branch | REJECT cost-heavy optional proposal | R-COST: stipulated annual cost; no universal prohibition |
| Deadline consequence | STOP diligence at earlier cap or gate; no automatic renewal | Chair stops; fresh mandate required for more exposure |
| Assurance boundary | Reviewer reports evidence and method gaps | Reviewer does not own acceptance or operate the safeguard |
The bounded diligence cost is an information-purchase convention in the fictional mandate. It is not silently added to the app's annual control cost and is not counted as an avoided loss. To evaluate a complete investment, the institution would need to define implementation expenditure, operating cost, appraisal horizon and the treatment of information expenditure. The present mandate authorises only the next evidence step. Its narrowness is useful because the annual control-value comparison does not contain those broader economic inputs.
The adverse route is explicit. If the supplied cost-heavy proposal were offered as an optional improvement, it would fail the declared net-value condition and the Chair would reject that version. If a mandatory constraint required the safeguard despite this financial result, the proposal would return under a different stated mandate; the analyst would not change the sign of net value or label the requirement an economic benefit. If evidence showed the original safeguard unavailable, the Operating Owner would report that adverse state, and the implementation hold would remain. A positive result in a proposed future state cannot erase the current operating uncertainty.
An annual expected-loss model can support a narrow economic comparison. It cannot establish the total worst loss, the number of future events, a safety case or a legal acceptance standard. Those omitted dimensions are not decorative caveats. They determine which decisions the model may legitimately inform. For an optional low-consequence control, an expected-loss comparison might be sufficient for a limited screening decision. For an irreversible operation with severe effects on people, an aggregate financial expectation may be inadequate even if it is perfectly calculated. Method choice should follow the proposed commitment.
This study has a deliberately bounded original contribution. Scenario description, control assurance, risk appetite and board oversight are conventional subjects of institutional guidance. The contribution lies in arranging controlled examples so the reader can see precisely where a summary metric becomes insufficient, then routing that finding into a completed fictional authority record. The examples distinguish availability from conditional effect, arithmetic addition from valid loss incidence, and identical expectations from different consequences. These demonstrations make a challenge concrete. They do not prove that the arrangement improves outcomes across all institutions.
The paper's thesis could fail. A well designed score may already capture the distinctions needed for a reversible, low-cost decision; extra mechanism work could then consume attention without changing the choice. Evidence might be too weak to quantify the mechanism, making an ordinal triage more honest. A mandatory protective requirement could make a financial expected-loss ranking irrelevant. An institution might already have a mature assurance system in which the proposed record adds duplication. The later falsifiers address these cases directly, because useful synthesis must identify when its own method is unnecessary or insufficient.
Conventional guidance and the demonstrated synthesis
A contribution is judged by a decision difference, not by renaming established risk-management activities.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Conventional guidance and the demonstrated synthesis | |||
|---|---|---|---|
| Element | Origin | Demonstration in this study | Limit |
| Scenarios, appetite and role clarity | Conventional institutional guidance | Precise context for the decision | No new universal risk framework claimed |
| Shared availability and conditional controls | Explicit canonical app mechanism | Installed control can be unavailable or ineffective | Inputs remain stipulated |
| Economic and mandatory conditions | Author-owned routing of controlled cases | Same loss reduction, different optional cost disposition | No institution-wide optimal policy proved |
| Incidence and consequence challenges | Author-owned counterexample design | A correct sum or matching mean can still be unusable | No cross-risk tail distribution calculated |
| Bounded authority record | Original arrangement of case evidence and decisions | Arithmetic eligibility leaves implementation held | Fictional roles and relative dates need actual replacement |
Start with the act that could be authorised
Define the permitted exposure before selecting the reporting method. Treat a favourable calculation as support for its stated condition, then check the evidence and authority for the next act.
- Name the proposed action and who may accept or stop it.
- Separate a screening result, a diligence mandate and implementation authority.
- Route a material adverse answer to a specific hold, rejection or fresh appraisal.
The reader should therefore begin with a concrete decision rather than a general aspiration to improve risk culture. Name the action, the exposure it creates, the consequence that could defeat its objective and the authority that may accept that consequence. Then ask which uncertainty could change the action. A register becomes a decision system when the answer determines a permitted next step, an evidence requirement or a stop rule. That practical test is stricter than asking whether the report appears comprehensive.
A disciplined summary may already be enough
For a reversible action with modest consequences and well supported inputs, a concise score can correctly direct attention. Extra documentation is justified only when it changes the decision, preserves a material uncertainty or prevents unauthorised exposure.
The completed record remains fictional
No source commitment, measured safeguard availability, real committee delegation or implementation success is represented. The completed entries demonstrate a form of reasoning and routing, while their substantive assumptions remain open to challenge.