Platform / One committee pack, end to end

One committee pack, end to end

The committee pack is the document the board reads, and in most risk functions we have worked in it is the document that takes the most weekends. What follows is one pack, from choosing its sections to the committee receiving it, with nothing retyped on the way.

The same pack the platform page describes, one step at a time. A companion walk follows one risk.

A committee pack being configured and taken through its approval chain A drawn view of the platform. On the left, the eight sections of a pack with a switch beside each, one switched off. On the right, a preview page of the pack watermarked draft, and beneath it the approval chain: compiled and reviewed done, signed off in progress, released to come. Connected risk intelligence All entities (Group) Dashboard Risk register Risk assessments Controls Control assessments KRI register KRI collection Breaches Risk events Remediation Committee packs Audit log MODULES TPRM & Supplier DD Obligations Management ICARA Operational Resilience Customer Oversight Portal RMRisk manager Committee pack Group audit and risk committee · this quarter · assembled from live data Export PDF Sections Template: standard Executive summary Indicator early warning Risk appetite Principal riskstop 10 · outside appetite Risk events Path to green Indicator performance Control effectiveness Drag to reorder · filter to a band · cap · add commentary Preview data as at 30 Sep · page 1 of 14 Executive summary DRAFT Every figure traces back to source · exported 3 Oct 09:12 Commentary by the risk manager, dated APPROVAL CHAIN Compiledrisk manager Reviewedcompliance officer Signed offboard, awaiting Releasednot yet

Drawn from the platform.


The walk

  1. The sections are chosen once, and saved

    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. The risk manager sets the committee's pack up once and saves it as a named template, so next quarter the pack is generated from the template and nothing is rebuilt. Editing the template later never changes a pack already produced.

  2. The pack assembles itself from the live record

    Generation reads the register, controls, indicators, breaches and actions as they stand and writes the pack from them. Every figure traces back to the record it came from, and each page carries the data-as-at instant, so there is no doubt afterwards which version of which number it shows.

  3. Commentary is added, by a named person, dated

    Commentary sits beside each section, separate from the figures, and the audit trail holds who wrote it and when.

  4. The approval chain, with no one person clearing two steps

    The pack moves from compiled to reviewed to signed off to released, and each step records who approved, when and in what role. Whoever compiled it cannot approve any step of it, and no one person takes it through two steps. Committee reporting

  5. Export, watermarked until it is approved

    Export is to PDF or PowerPoint, watermarked DRAFT until the chain is complete, so a half-approved pack cannot circulate as a finished one. Every page carries the export instant as well as the data-as-at instant.

  6. The pack stays as the committee saw it

    The pack that went to the March meeting is still there in June, exactly as it was, alongside the audit entries for who compiled, reviewed, signed off and released it. An auditor asking how a figure reached the board gets the figure, the source it came from and the four people who took it there. The audit trail and the checks that run over it