On track
Progressing as intended
Implementation is active, up to date, and unfolding in line with the strategic objective. The board has no action to take.
Generated automatically - from activity and progress in the implementation layer
Governance insight
The strategic plan is approved.
Unanimously, usually. After real effort. Priorities agreed, language refined, the board aligned on what matters most for the year ahead.
Then something subtle happens.
The plan moves into implementation. Into leadership workstreams, meetings, decisions. And between approval and the year-end report, the board typically has no clear view of:
- Which priorities are actively progressing - and which have quietly stalled
- Whether implementation is unfolding as the board intended
- Where something has shifted or been reinterpreted along the way
- Whether any strategic objective needs the board's attention right now
The gap between what boards approve and what they can see.
Approved unanimously.
Not seen again until it's already a story.
The problem
The year-end narrative is not governance.
It's a verdict.
When the board next encounters the strategic plan at year-end, the framing is already set. "Strong progress." "Most priorities addressed." "More to do, but overall a successful year." Approved unanimously - again.
But there was no moment during the year when the board could see what was actually happening. No point at which they could adjust, redirect, or signal concern before the narrative was already written.
The issue is not effort or intent. It is that the board had no shared way to see the plan as it was unfolding - only to approve it at one end and receive a report at the other.
The question to ask
Most boards ask
"Have we made progress against our strategic priorities?"
The question that actually matters
"Can we see - right now - which priorities are on track and which need our attention?"
These are different questions. The first is answered at year-end with a narrative. The second requires continuous visibility - something most boards do not have.
Two governance rhythms
Episodic governance vs continuous governance
Most boards operate episodically - approval and reporting as the two contact points, with trust filling the space between. Continuous governance does not mean more meetings or more reporting. It means the board can see what is happening, in real time, without waiting for the next report.
Episodic governance
1
Approve the plan→
Trust that implementation is unfolding2
Receive the year-end reportContinuous governance
1
Approve the plan2
Track progress against outcomes3
Adjust - before the story is already writtenThe shift
Govern outcomes. Not activity.
Continuous governance does not mean the board steps into leadership's work. The implementation detail - the workstreams, the tasks, the day-to-day decisions - belongs to leadership. The board governs the outcomes: whether each strategic priority is on track, whether something has stalled, and where the board's attention is actually needed.
That distinction - between governing outcomes and managing activity - is what makes continuous governance possible without it becoming operational overreach.
The board sees strategic outcomes. Leadership owns the implementation. Progress and status signals travel up - not the other way around.
What the board sees
Four signals. Not a report.
Rather than waiting for a narrative, the board sees a small number of clear status signals for each strategic objective - surfaced continuously from the implementation layer below. Three of those signals are generated automatically; one is set deliberately by the board itself.
At risk
Flagged for board awareness
Progress is low relative to the timeline, or implementation activity has been absent for an extended period. The strategic objective may not be achieved without adjustment.
Generated automatically - when progress is low with an imminent deadline, or when no update has been recorded in 45 days
Stalled
No visible movement
Implementation activity has stopped. No update, no progress, no signal of active work. The strategic objective is not progressing.
Generated automatically - when no activity has been recorded in the implementation layer for 30 days or more
Attention required
A governance signal from the board
This signal is different. It is not generated by the system - it is set deliberately by the board or chair as a formal escalation. It records that the board has exercised oversight and determined that something needs closer scrutiny.
Set deliberately - by the board or chair, as a governance act, not a system alert
What this enables
Four questions. At any point in the year.
With this structure in place, these questions are answerable by the board at any time - not only at the point when a report has been prepared. If they cannot be answered without a report, the board is operating episodically.
Question 1
Which of our strategic priorities are currently on track, and which are not?
Question 2
Is anything stalled - and how long has it been without visible progress?
Question 3
Which objectives have we formally placed under observation, and why?
Question 4
Where is our attention genuinely needed - before it becomes a year-end story?
The standard to aim for
A board should be able to answer these questions at any meeting - not only when a report has been tabled. If that is not possible, the strategic plan is being managed, not governed.
The honest limitation
Where episodic governance fails quietly
Most boards do not feel they are operating without visibility. Trust in leadership is genuine, and year-end reports usually confirm it. The failure is subtle:
- Strategic objectives drift without the board noticing until the report is written
- Stalled priorities are absorbed into the narrative as "more to do"
- The board cannot distinguish between what is genuinely on track and what has been quietly deprioritised
- Attention lands on what is reported, not on what actually needs it
- Governance becomes an endorsement of outcomes rather than an oversight of the journey
The question is not whether leadership is trustworthy. It is whether the board's oversight depends entirely on that trust - or whether the structure holds it independently.
Loom is built for this
Loom separates the two tiers of strategy formally. Leadership owns and drives operational implementation. The board governs the strategic outcomes - and the status signals surface automatically from what is actually happening below.
- Board members see strategic objectives with live status - on track, at risk, or stalled
- Status is derived from implementation activity, not from what leadership chooses to report
- The board can mark any objective as requiring attention - a deliberate governance act, not just a system flag
- Leadership retains full ownership of the implementation layer - the board does not see task-level detail
- The gap between approval and reporting is not filled with trust - it is filled with visibility
Not more reporting. A shared way to see the plan as it unfolds.
Board Deck Standard 2.2: Strategic Planning and Innovation ↗The test
Think about your current strategic plan
Without looking at a report, can your board answer these right now?
You can name which strategic priorities are currently on track and which are not - without waiting for the next headteacher's report.
You know if any objective has stalled - and roughly how long it has been without visible progress.
The board can distinguish between what is genuinely progressing and what has been quietly deprioritised since approval.
If any of those requires a report to answer, strategy is being managed - not governed. The plan is approved at one end and narrated at the other. The oversight in between is episodic, and what falls through the gap is invisible until it is already a story.