Encode the four-part board paper structure (decision, options, risk, recommendation) as a standing agent workflow, but have the accountable person write the decision, rejected option, risk owner and sign-off each time.
The Leadership and Governance playbook earlier in this series sorted governance work broadly into what is delegable and what never should be. Board papers sit in an interesting middle position. Whatever the topic, from a routine contract renewal to a merger proposal, almost every board paper an organisation produces follows the same underlying skeleton: the decision the board is being asked to make, the options genuinely considered, the risk attached to each, and a clear recommendation. That skeleton barely changes meeting to meeting even though the content inside it changes completely, which is exactly the property that makes it worth encoding once as a standing agent workflow rather than rebuilding from a blank page every time.
This piece is a mini playbook on which parts of that structure are safe to encode once, and which parts still have to be written fresh by a named, accountable person for every single paper.
Most organisations already write board papers in roughly this shape without ever naming it, which is why the structure is safe to formalise: it reflects how boards actually make decisions, not an invention imposed on top of governance practice. A fixed workflow that always asks for the decision, the options, the risk, and the recommendation, in that order, does not change what the board is asked to consider. It changes how much of the paper's structure a preparer has to reinvent each time, which for most papers is currently all of it.
A standing agent workflow for board papers is a fixed set of prompts, always in the same order: state the decision being asked in one sentence, list at least two genuinely considered options including one that was rejected and why, name the material risk of the recommended option, and state the recommendation together with who is accountable for it. The structure stays fixed across every paper the organisation produces. The content supplied into each section is written fresh, every time, by the person who actually owns that paper.
A standing structure only saves time on the parts that never change. It cannot write the parts that do.
A single four-part skeleton risks flattening genuinely different kinds of decisions into the same shape: a routine contract renewal and a merger proposal do not carry the same risk profile, and a rigid template applied mechanically can undersell or oversell risk depending on how much space each section is given. The honest answer is that the fixed structure is a scaffold for the writer, not a substitute for judgement about how much weight each section needs for this particular decision. A one-page paper on a routine renewal fills the risk section briefly. A merger proposal needs the risk section to be the longest part of the document, and the template has to flex that far rather than staying a uniform size regardless of the stakes.
Encode the four-part structure, decision, options, risk, recommendation, once as a standing agent workflow, but write the decision sentence, the rejected option, the named risk owner, and the final sign-off fresh for every paper; never let a template auto-fill those four load-bearing parts.
No external statistic cited; this article presents an internal mini playbook rather than third-party evidence.
If this is the question on your desk, a thirty-minute call tells you whether the service fits, or that you do not need us yet.