Kennisbank

Who decides which signal reaches the boardroom table

A board never sees all the signals that arise within an organization. Someone selects, someone summarizes, someone decides that something can still wait. That selection usually happens implicitly: a director of communications who assesses what is relevant, a secretary who fills the agenda based on what was discussed last time, a line manager who resolves a signal internally before it gets the chance to move upward. That is not necessarily a problem. It becomes a problem when no one can explain why one signal reached the table and another did not.

The question behind the question

"Which signals belong on the boardroom table" is actually two questions. The first is substantive: what is important enough. The second is procedural: who has the mandate to determine that. Organizations typically spend more time on the first question than on the second, while the second is often the root of trust problems. A stakeholder who feels insufficiently heard rarely complains about the absence of a reporting format. They complain about the feeling that someone, somewhere, decided their signal was not worth passing on.

Rhythm is a choice, not a consequence

The rhythm in which signals reach a board is often determined by the calendar rather than by the content. Quarterly reports, annual reports, standing agenda items: these structures exist for reasons other than capturing signals at the moment they become relevant. That leads to two kinds of errors. The first is that urgent signals wait for the next meeting. The second, less discussed, is that routine signals get an agenda slot simply because they always did, while no one can say anymore whether they still add anything. How these two errors relate to each other, and when a signal deserves attention outside the regular rhythm, is described on the page about the moment at which a signal counts as urgent and who assesses that.

Who makes the selection

The person or department that filters signals before they reach the boardroom table thereby exercises an influence that is rarely formally assigned. That is not strange; someone has to fulfil that role. The question becomes how transparent that role is. Can a board member ask why a particular signal was not passed on? Is there a fixed place in the meeting where stakeholder work returns, or does it depend on who happened to raise something that week? The way an organization structures that is addressed on the page about how stakeholder work gets a fixed place on the agenda and who determines the conditions for that. The frequency of reporting, and who sets that frequency, is covered on the page about how often an organization reports on stakeholders and who makes that choice.

What the Trust Baseline adds here

The Trust Baseline is not about the content of signals, but about the gap between what management thinks is going on and what is being said externally. That gap often arises precisely at the point where signals are filtered before they reach a board. An internal survey shows what the organization itself considers relevant; an external stakeholder survey shows what is actually going on. The gap between the two is not a judgment about who is right. It is a signal in itself: an indication that the selection currently taking place is missing something.

In addition, the instrument includes a commitment tracker. It exists based on an observation that has little to do with the size of decisions: a small commitment that is not kept often costs more trust than a large investment that fails to materialize. A boardroom table that only puts major themes on the agenda and leaves the small commitments to the line loses something as a result that is hard to win back. The tracker makes visible which commitments were made, to whom, and whether they were kept — not to pass judgment, but to make that information available at the moment the boardroom table asks for it.

What exactly belongs in a signal report, and who determines that content, is a separate question that touches on the rhythm but does not coincide with it; that question is addressed on the page about what a signal report should contain and who determines that. For organizations operating in specific sectors, who the relevant stakeholders are also differs; who needs to be at the table in construction is a different question from who is relevant in the installation sector, and these differences are described on the pages about who you should be talking to in the construction sector and who you should be talking to in the installation sector.

The Trust Baseline is under construction. Anyone who wants to work with it already can join the waiting list; there is no instrument ready to deliver today, and we prefer to state that honestly rather than offer something that does not yet exist.

The question that comes next

Once it is clear which signals belong on the boardroom table and at what rhythm, another question follows: who in the organization does the work of gathering those signals, structuring them, and preparing them. That work consists of a series of separate tasks — holding conversations, gathering information, writing summaries, tracking progress. Not every task in that series requires human judgment. The werkscan from FTE TO AI calculates, per task, which portion of that work can be taken over by AI, so that the time of the people who currently filter signals shifts toward assessing them rather than collecting them.