Board Intelligence
Fewer pages, and a conclusion on each one. Boards are not short of information — they are short of information structured for judgement.
The board pack has become an accumulation. MIS tables, departmental dashboards, compliance trackers, project updates, retrospective commentary — accurate, timely, well-intentioned, and leaving the directors to do the hardest part of the work themselves: finding the signal.
The cause is structural rather than editorial. Management information is designed to tell an organisation whether activity is happening: how many transactions, how many observations open, whether costs are inside budget. Oversight operates at a different altitude. Is the trend material? Does the variance affect strategy? Is the control weakness isolated or systemic? Is management’s response adequate? A pack built for the first set of questions cannot answer the second, however many pages are added.
This is not a report-design problem, and treating it as one is why the redesigns fail. It is a question-design problem: decide what the board must conclude, then build backwards to the operating data that supports the conclusion.
How I work it
Read the last four packs against the minutes. Identify which board questions the pack answers, which it leaves the directors to infer, and which nobody asked because the data made it invisible.
Restructure the pack around board questions: what changed, why, what could happen next, what it means for strategy or risk appetite, and what decision or assurance is required. One page per question, with the operating data behind it.
A standing pack structure, an exception-based operational section, and a decisions log carried forward so the same question does not arrive twice.
Tools and frameworks
Placed against the stage each one serves, and against the artefact it leaves behind. A framework that produces no artefact is a word.
| Framework or instrument | Analyse | Act | Adhere | Artefact it produces |
|---|---|---|---|---|
| Board pack review against the minutes | ● | – | – | Gap list — questions asked but not answered by the pack |
| Question-driven insight design | ● | ● | ○ | The board question set the pack is built backwards from |
| MIS-to-oversight translation | ○ | ● | ○ | One page per question, operating data behind it |
| Operational risk register for the committee | ○ | ● | ● | Register by materiality, with management response rated |
| Exception-based operational reporting | – | ● | ● | Operations section that reports variance, not volume |
| Decisions and assurance log | – | ○ | ● | Carried-forward log; nothing arrives twice unresolved |
The responsibility matrix — preparing the pack
The artefact the Act stage produces. “As found” is what a typical intake looks like — not a description of your operation.
| As found — typical intake | As governed — on exit | |||
|---|---|---|---|---|
| Control activity | Accountable | Evidence | Accountable | Evidence |
| Defining the board question set | Nobody named | Agenda template | Company Secretary | Question set agreed with the chair |
| Operational section content | Each function, unedited | Departmental slides | CFO | Exception report against tolerance |
| Risk materiality assessment | Risk register, static | Annual review | Audit committee chair | Materiality rating reviewed each meeting |
| Management response adequacy | Implicit | Verbal | CEO | Written response rated against the finding |
| Carry-forward of decisions | Minutes only | Minutes | Company Secretary | Decisions log with owners and due dates |
A scoped, paid review of the last four packs against the minutes — what the board asked, what the pack answered, and what it obscured.
Quarterly review of the pack before it goes out, and a standing check that carried-forward decisions actually closed.
What good looks like
The state a completed engagement leaves behind — the definition of done we agree at the start. Not a result already achieved.
| Area | What good looks like | How you would know |
|---|---|---|
| Structure | Every section of the pack exists to answer a question the board actually asked. | Board question set |
| Operations | The operational section reports what is outside tolerance, not what happened. | Exception report |
| Risk | Materiality is re-rated each meeting rather than inherited from last year’s register. | Risk register, dated |
| Response | Management’s response to every finding is written down and rated for adequacy. | Response log |
| Continuity | No question reaches the board twice unresolved. | Decisions log |
Every section of the pack exists to answer a question the board actually asked.
The operational section reports what is outside tolerance, not what happened.
Materiality is re-rated each meeting rather than inherited from last year’s register.
Management’s response to every finding is written down and rated for adequacy.
No question reaches the board twice unresolved.
Thirty minutes, and you will know whether this is worth pursuing
A structured conversation about where your operation is losing money, not a sales call. Mon–Sat, 09:00–18:00 IST, on Google Meet, in English or Hindi. Nothing is required from you in advance.
Book a Board Intelligence DiagnosticThe questions your board pack should answer and usually does not: what changed, what it means, what is outside tolerance, and what decision or assurance is required.
↓ Download · PDF, 3 pp