Platform / The governance core
Committee reporting
In most of the risk functions we have worked in, the committee pack is rebuilt by hand the weekend before the meeting, and nobody can say afterwards which version of which number went into it.
Drawn from the platform.
What changes
The pack assembles from live data, and every figure traces back to source.
Sections are chosen, ordered and filtered once and saved as a template. The pack then moves through a recorded approval chain with segregation of duties at every gate.
In detail
Packs assemble from live data, so nobody writes one by hand. There are eight sections, each of which can be switched on or off, reordered, filtered to a band, capped to a top few and given its own commentary. A configuration saves as a named, reusable template, and editing a template never changes a pack already produced: what the committee saw in March stays as it saw it.
Packs then move through a recorded approval chain with segregation of duties enforced at every gate. Each step records who approved, when and in what role, and no one person takes a pack through two steps.
Export is to PDF or PowerPoint, watermarked DRAFT until approved, and every page carries the data-as-at and export instants, so there is no doubt which version of which number a page shows. A group pack and a unit's pack come from the same engine, and the unit's pack ranks, bands and counts on the unit's own figures.
The evidence it leaves behind
Each approval step is an audit entry with a name, a role and a time, so the chain that took a pack to the board can be read back later. Segregation of duties, enforced rather than asserted