Almost every organisation reports on stakeholders at some point. Quarterly reporting, an annual reputation survey, a risk memo for the supervisory board. But the question of who determines the rhythm of that reporting is rarely asked. Is it the calendar of the planning and control cycle? Is it the communications department that flags when something is going on? Or is it chance — an incident that pushes the question to the surface, after which things go quiet again until the next incident?
Most organisations report on stakeholders at the rhythm of their own internal cycle, not at the rhythm at which the outside world changes. That is not a reproach. It is a logical consequence of how agendas are built: around what is measurable and repeatable, not around what is urgent at any given moment.
There are two things that are often confused. The first is the frequency with which you measure: how often surveys are conducted, internally and externally. The second is the frequency with which that measurement reaches the boardroom table. These two do not automatically run in parallel. An organisation can receive signals continuously — through relationship managers, through the complaints line, through the press — without those signals ever reaching management in a fixed form. Conversely, a quarterly report can appear neatly on time, while its content says nothing about what has changed between reporting moments.
The question "how often do you report" is therefore incomplete without the question "who decides when something is worth reporting". The latter determines the rhythm more than the calendar does. What belongs on the boardroom table is rarely laid down explicitly; it often grows organically, based on who happens to pick up the phone when a stakeholder calls.
In practice, there is often no conscious owner of this rhythm. One department collects, another assesses, a third decides on agenda placement — and between those handovers, the urgency the signal once had disappears. An external party that reported something about a permitting process three months ago may well have reached a different decision by the time the report appears. The rhythm of reporting then says more about the internal organisation than about the relationship with the outside world.
The question of how stakeholder work gets a fixed place on the agenda, and who decides that is therefore not just a process question. It is a question of ownership: who is responsible for the moment when a signal from outside is translated into an agenda item on the inside. As long as that is not assigned, chance decides — or the person who shouts loudest.
Not every signal deserves the same rhythm. Some matters can wait until the next regular reporting cycle; others require immediate attention, even if the calendar does not allow for it. The distinction between these two categories is rarely made in advance. Often it only becomes clear afterwards that something was urgent — at the moment it had already escalated. The question of when a signal is urgent, and who decides that touches the core of the rhythm problem: a fixed quarterly rhythm does not work for something that does not adhere to a quarter.
This plays out differently per sector. Those in construction who need to know with whom to speak — environmental agencies, chain partners, local resident groups — deal with a different rhythm than those operating in the installation sector who need to know which contacts are decisive there. The nature of the relationship partly determines how often an update is needed; a permitting authority requires a different rhythm than a supplier.
If the rhythm of reporting is unclear, the content of that reporting often is too. What belongs in it — only incidents, or also gradual shifts in tone and expectation? And who determines that selection: the one who picks up the signal, or the one who receives it? The question of what belongs in a signal report, and who decides that is directly linked to the rhythm question. A report that contains too much gets bogged down in noise; a report that contains too little misses the signals that actually matter.
We cannot determine what the correct reporting frequency is for a specific organisation, and we make no statement about what your stakeholders currently think. What the Trust Baseline does do is make visible the difference between what management believes it knows and what is being said externally — as a starting point, not as a final verdict. A commitment tracker and a signal rhythm belong to this: not to advise you on when to report, but to make visible whether commitments are being kept and whether signals reach the table on time. A small commitment that is not kept often costs more trust than a large investment that fails to materialise — which is precisely why that rhythm matters.
The tool for this is under construction. Those who want to make use of it already can join the waiting list; we do not offer anything yet that does not exist.
Maintaining a signal rhythm, collecting internal and external surveys, monitoring commitments — part of that work is repetitive and follows a fixed pattern, even though it still feels like bespoke work now. Those who want to know which part of this kind of task can be taken over by AI, and which part remains dependent on human judgement, will find a task-based breakdown at the werkscan of FTE TO AI: not advice, but a task-by-task classification of what automation can relieve and what remains human work.
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.