S10 · Solution for organisations

Board and Committee Pack Preparation with a source map

Board and committee papers are assembled from approved inputs, checked for completeness against the agenda, and given a cover summary with a source map. No figure enters that its owner did not supply.

Status · Proposed

The problem it answers

Board papers are assembled by hand from many owners, and iSystematic's Board and Committee Pack Preparation solution assembles them from approved inputs, with a source map for each paper.

What it does

It collects approved inputs, checks completeness against the agenda, and drafts the cover summary with a source map. No figure enters the pack that its owner did not supply.

A missing paper or missing data is shown as a gap, not filled in.

The pack follows the board's cadence and decision rights and names each paper's owner. It can also carry the organisation's current four-altitude profile under the MESA Framework™, so the board sees which altitude is weak.

At municipal scale, the same preparation serves council and committee packages.

Built from

It is built from two catalogue workflows and three catalogue patterns.

IdNameWhat it brings
W19Weekly Owner ReviewSupplied figures only; missing data shown; observation kept apart from interpretation
W20Research to Decision MemoEvidence kept apart from assumptions and unknowns
P01Retrieve, Ground, Draft, ReviewApproved inputs and cited passages
P02Extract, Validate, ProposeFigures and dates validated; missing values are never inferred
P08Fail VisiblyA missing paper is a visible gap

What it is built on

Three parts of the framework corpus decide what enters the pack, and each leaves a record the client keeps.

FrameworkIn this solutionClient keeps
MESA Framework™The pack can carry the organisation's current four-altitude profile, so the board sees which altitude is weakMESA profile page
CADRE™ (AI governance operating model)The pack follows the board cadence and decision rights; each paper's owner is namedCadence and owner record
PEVGNo figure enters the pack that its owner did not supply; the verifier checks completeness against the agendaSource map per paper

Five parts apply to every build and are not repeated here: decision rights, the five gate records, a BOE Declaration per control, a vendor assessment for every vendor, and incident response. How we build sets out all of them.

The evidence it leaves behind

Every pack leaves records the client keeps.

  • A source map for each paper
  • A cadence and owner record
  • A MESA profile page, where the pack carries one
  • The five gate records and a BOE Declaration per control, as for every build

Typical buyer

The typical buyer is a corporate secretary or the office of the chief financial officer; at a municipality, the clerk's office.

Status

Proposed, as of 9 October 2026. A solution becomes Piloting or Released only after a documented pilot, and no result is shown for it before then.

How to start

Most organisations start with the Automation Assessment. When pack preparation is already the clear first task, a six-week Pilot runs it for one board or committee cycle, with the baseline measured first.

Conformance is self-declared; no regulator endorses this work.

Start

Start with the Automation Assessment

Two weeks, a fixed fee shared on a short call, ten candidate tasks scored and three solutions recommended.