From vaults, a file in the seed packEverything on this sheet is the source site's own text; the newsroom's chrome is outside it.
Running an acceptance meeting
The meeting where a holder accepts, funds or fixes. Thirty minutes, one holder, their material risks.
Before
- For each risk: the statement, the facts that establish it with sources, the facts that would end it, the controls and their states, and the chain above the holder.
- The ladder on one page.
- Any rung the holder cannot honour struck off in advance. An interval nobody can deliver is a finding, not an option.
During
- Read the risk and its facts. If the holder disputes a fact, the risk does not change; the fact is checked. Disagreement resolves into which fact is wrong, not whose view wins.
- Offer the three doors: accept for a rung, fund, or fix.
- For an acceptance: the rung, and the action before it ends. Written down in the holder's words.
- For funding: the project, its cost and its duration, which becomes the interval.
After
- The decision is written to the risk's record the same day.
- The GRC platform's row is updated with the interval, the expiry date and a link to the vault.
- The holder's boss sees the decision arrive through the chain.
When the holder will not decide
Record that. Unaccepted is critical, and the risk escalates at the next expiry check. The meeting's job is not to force a signature; it is to make the absence of one visible.