Decision summary
Proposed action, reason for review, key risks requiring sign-off, approval status.
Decision Packets
A Decision Packet is not a retrospective summary. It is assembled at the time the decision is made, locked to the data snapshot, and replayable at any future point. Thesis state. Evidence bundle. Portfolio impact. Risk context. Regime flags. What changed. Approval trail. Replay.
Packet anatomy
Proposed action, reason for review, key risks requiring sign-off, approval status.
Original thesis, current state, falsifiers and their status — strengthening, watching, triggered.
Policy, budget, market, price, analyst and internal evidence. Sources timestamped. Snapshot locked.
Current vs proposed exposure, concentration, factor impact, FX and liquidity context.
Risk team comment, sector concentration, liquidity flags, regime conditions at decision date.
Analyst → PM → Risk → CIO approval chain. Locked snapshot. Replayable at any future point.
When a packet is used
The packet arrives with thesis state, evidence, portfolio impact and risk context already assembled. The meeting is about judgment — not reconstruction.
Open the packet for that date. The thesis, the evidence, the regime context, the approval trail. Not a story — the actual state at the time.
Regime monitor flags a condition. The packet shows what the investment case was, what has changed, and whether the original falsifiers have triggered.
What QJ is not
A Decision Packet does not replace IC judgment. It does not enforce a decision process or produce investment advice. It captures the evidence that was available and the reasoning that was applied — so that review, replay and accountability are possible. The judgment remains with the investment team.
Next step
Walk through the EU Defense basket example — thesis, evidence, portfolio impact, regime flags, approval trail and replay.
Request Demo