Most boards know when the quarterly figures are due. Few boards can say without thinking when the last overview of stakeholder signals was on the agenda. Not because the subject is unimportant, but because its rhythm usually moves along with other subjects. A report is produced when something has happened, or when someone asks for it. A fixed rhythm is something different from reporting on an ad hoc basis.
The difference seems administrative. It is not. A signal that takes three months to reach the boardroom has a different value than a signal that arrives after two weeks. By the time the board reads it, the situation has often already changed, and what ends up on the agenda is then a description of something that has already passed, not a reason to act.
The answer to the question of how often depends on a number of things that differ per organization: the speed at which a subject can change in the outside world, the degree of public exposure, and whether there is already a fixed moment at which stakeholder matters are discussed. An organization with an ongoing process around a sensitive dossier needs a different rhythm than an organization for which the subject plays more in the background. There is no fixed interval that applies to everyone, and we do not name a figure either, because that depends on the organization's own context.
What is certain, however, is that a rhythm that is entirely dependent on chance or incidents is not a rhythm. It is a reaction. The distinction between the two is discussed on the page about how stakeholder work gets a fixed place on the agenda, which covers the step from incidental attention to a recurring item.
A fixed moment on the agenda solves nothing if it is not clear what will actually be discussed there. Reporting is not the goal; the goal is that the right things are known in time by whoever needs to act on them. This raises two follow-up questions. The first is what should actually be included in such a report, a question that is discussed in more detail on the page about what content belongs in a signal report. The second is who determines whether something deserves the board's attention, and that is a different question from how often reporting takes place. That question of ownership is discussed on the page about which signals belong on the boardroom table and who determines that.
Rhythm and content are related, but they are not the same problem. An organization can report monthly and still pass on the wrong signals, or report irregularly but still include the right signals when it happens. The question of how often is therefore not a question that stands on its own; it is part of a larger issue about urgency, ownership and content, which comes together on the page about how often reporting on stakeholders takes place and who determines that.
There is a pattern that recurs more often than expected: a small commitment that is not kept costs more trust than a large investment that is not made. An organization that promises to respond to a question from a nearby resident, a journalist or a supervisory authority within a certain period, and fails to do so, leaves an impression that weighs more heavily than the failure to deliver an announced project. Commitments that are not visibly tracked easily disappear from the sight of whoever made them. That is why a commitment tracker is part of the Trust Baseline: not to guard large promises, but to prevent small commitments from silently lapsing.
This page describes the rhythm at which signals should reach the boardroom. It says nothing about what a specific stakeholder currently thinks of your organization. We do not know that, and we cannot claim to know it until a stakeholder has said so themselves. What the Trust Baseline does do is make visible the difference between what management thinks is going on and what is being said externally. That difference is an outcome, not advice, and it is up to the organization itself to decide what to do with it.
The Trust Baseline is under construction. Anyone who wants to know when this tool becomes available can sign up for the waiting list. There is currently no service to order and no advisory process to start; there is an internal tool in development that asks questions and delivers structure, not someone who comes by to tell you what needs to happen.
A fixed rhythm of reporting on stakeholders requires time: time to gather signals, weigh them, summarize them and put them on the agenda. That time is often filled in by people who do this alongside other work, which explains why the rhythm is the first thing to disappear under pressure. Anyone who wants to know which part of that gathering and summarizing work can be taken over by AI, so that capacity remains for the judgment that stays human work, can have this calculated with the work scan from FTE TO AI, which maps out per task which part is suitable for automation and which part is not.
Vraag maar. Het interessantste antwoord komt meestal van wie u nog niet heeft gesproken.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.