← Notebook · 34 essays

The Reporting Layer Is the Last Thing to Fail

4 min read

Most boards discover a problem at the moment their reporting turns red. By then the problem is old. A point-in-time assurance pack describes a position that was true when the data was gathered, not the position the organisation occupies when the board reads it. That gap is where governance now fails. In social housing it is widening.

A growing number of housing leaders are saying the same thing in different words. Internal reporting snapshots, on their own, no longer settle the question that matters. The harder question is whether the operational position holds together over time, once systems change, people move on and responsibility spreads across more hands. An organisation can look stable in reporting terms right up to the point continuity starts to give way underneath it.

A snapshot cannot show you a direction

Picture two landlords with the same number of upheld Housing Ombudsman determinations this quarter. On a point-in-time assurance pack they look identical. One of them has halved its rate over eighteen months. The other has doubled it. The snapshot cannot tell the board which is which.

Direction is the governance signal. A standalone count is not. Yet most assurance reporting is built to answer 'where are we now', and stops there. The board reads a number, the number looks tolerable, and the meeting moves on. Nobody in the room has been shown the line that number sits on.

This is why stability is a poor source of comfort. By the time the snapshot moves, the organisation has been heading the wrong way for two or three reporting cycles.

Continuity fails quietly, and attribution goes first

There is a second failure that boards rarely see coming. As systems are replaced and people change roles, the first thing to degrade is not the number. It is whether anyone can still say where the number came from.

A figure that no one can trace to a source is not assurance. It is a guess wearing the costume of assurance. Reporting can stay green for a long time while the data feeding it loses its provenance - the original system retired, the analyst who built the query gone, the definition quietly changed by someone who did not know it was load-bearing. The board pack still renders. The confidence behind it has already drained away.

This is what 'coherent, attributable and survivable over time' actually means in practice. It is not an abstract governance ideal. It is a hard test: can every figure in front of the board be walked back to the document it came from, today, by someone who was not there when it was created.

The board question worth asking now

The shift is from 'what is our count' to 'which way are we moving, and against whom'. That requires two things a quarterly snapshot cannot give you - a continuous signal, and a peer comparison.

This is the problem ScoreView was built to address for social housing. It watches the Housing Ombudsman's determination record continuously rather than as a quarterly gather. It tracks the trajectory of outcomes for a landlord and sets that line against sector peers. Every figure links back to the source determination, so provenance is built in rather than reconstructed under pressure.

I want to be precise about scope, because precision is the point. ScoreView covers external regulatory exposure. It does not monitor internal operational continuity - personnel, systems, fragmenting ownership. That is a real and separate discipline, and any board should hold it as one. What ScoreView removes is the excuse that the regulatory side of the picture can only be seen four times a year. That part can now be continuous and attributable, so it is not the part that quietly degrades under the reporting layer.

The convergence that housing leaders are sensing across sectors is real. Point-in-time assurance answered the question its era could afford to ask. The era changed. Boards that keep governing from snapshots will keep being surprised by positions that were visible, as a direction, long before they became a number.

The question to put to your own reporting is simple. If the operational position started degrading today, how many board meetings would pass before the pack showed it. If the honest answer is more than one, the reporting layer is doing less than the board thinks.

Richard SutcliffeCTO at ThinkTribalfield notes on AI in regulated sectors