BAMML Executive Insights

The Board Asked for Assurance and You Gave Them a Status Update

Industry: Cross-sector C-suite & Board · Primary pillar: Executive Decision Intelligence · Secondary: Risk & Compliance

5 min read

Read a board pack carefully and sort its contents into two piles.

In the first pile: statements about what is intended, in progress, being reviewed, on track, under consideration, receiving attention.

In the second: statements about what was tested, what was found, and what was done about it.

In most board packs, the first pile is considerably larger. And the second pile is the one the board actually needs.

What is actually happening

A status update tells the board what management believes or intends. The project is on track. The policy has been approved. The system is being implemented. Compliance is being monitored.

A board member at a table sorting a board pack into two piles, one much larger than the other

Assurance tells the board what was examined and what the examination found. Twenty transactions were tested against the approval policy; three failed; here is why, here is the corrective action, here is the owner and the date.

Those are different categories of information, and only the second allows a board to discharge oversight. The first allows it to feel comfortable, which is not the same thing and is occasionally the opposite.

The reason this happens is rarely concealment. Most management teams are not hiding anything. They provide status because nobody has ever defined what assurance would look like in their organisation, and because status is what has always been accepted.

Over time the pack settles into a format, the format is reproduced each cycle, and the question of whether it actually evidences anything stops being asked.

Why it matters

Three consequences follow, and the third is the most damaging.

A director asking a question across a boardroom table while a member of management listens carefully and other directors look on

The board cannot distinguish controlled from uncontrolled. A risk described as "being managed" reads identically whether the control is operating perfectly or has not been tested in two years. The language is the same. The reality is not.

Problems surface late and whole. In a status culture, an issue is reported when it can no longer be described as being managed. So it arrives at the board fully formed, usually with limited options remaining, and the board's reasonable question — why are we only hearing this now — has an uncomfortable answer: because until last month it was on track.

The board's own reaction determines what it receives next. This is the part boards control and rarely examine. If a failed test is met with sharp questioning of the person reporting it, the organisation learns that failed tests are costly to report. The next pack contains fewer of them — not because there were fewer failures, but because reporting them was punished.

A board that wants assurance has to be visibly safe to bring bad news to. Those two things cannot be separated.

The Integrated View

Discipline Status version Assurance version
Risk & Compliance "Controls are in place" "We tested these controls, here is what failed"
Financial Governance "Reconciliations are performed monthly" "We sampled three months; two had unreconciled items over X days"
Operational Performance "SOP compliance is monitored" "We checked 20 instances; compliance was 15 of 20; here is the pattern"
Workforce Governance "Training is up to date" "Records show these gaps, by department, being closed by this date"
Executive Decision Intelligence A pack that describes activity A pack that evidences control, including where it failed

What good looks like

Define, once, what assurance means in this organisation: a test was performed, on a sample, against a standard, with a result, including failures, with corrective action owned and dated. Write that definition into the reporting template so it is not a matter of individual judgement each cycle.

An internal reviewer at a desk testing a sample of transactions on a laptop, with tabbed documents in front of her and one document set aside

Then require that every material risk carries assurance rather than status — not every item, every cycle, which is unaffordable. Rotate. A small number of controls genuinely tested each cycle produces far more insight than everything described as monitored.

Make failures the expected content. A report of twenty tests with zero failures should prompt curiosity about the test, not satisfaction about the control. Perfect results usually indicate a test designed not to fail.

And handle the first uncomfortable report well. Every subsequent pack is shaped by what the board did the first time someone brought it a failure.

What to do on Monday

  1. Take the last board pack and mark every item as status or assurance. The ratio is your diagnosis.
  2. Pick your three most material risks. Ask what test would evidence that each control operated.
  3. Commission one of those tests and require the result to include failures.
  4. Look at how the last piece of bad news was received. That, not the reporting template, determines what you will be told next.
  5. Change the template so assurance is a required field rather than an optional one.

A board that receives only good news is not being well served. It is being managed.

Share this insight LinkedIn Email Book a conversation

← All Executive Insights