A director who postpones a large investment usually gets to explain that, and that explanation is often accepted. A spokesperson who says at a meeting "we'll get back to you on that" and then does not, leaves something different behind. Not disappointment about an outcome, but an observation: something did not add up between what was said and what happened. That observation piles up, and piles up faster than most organisations realise, because small commitments rarely appear on a list.
Large decisions have a file, an approval process, a person responsible. Small commitments — a remark made in a meeting, a reply to a letter, an informal promise to a local resident or an NGO — usually do not have that. They exist in someone's head, in a report nobody opens anymore, or nowhere at all. When they are then asked about, months later, the answer is often: we no longer remember exactly.
Before anything can be tracked, a commitment must be recognised as a commitment. That sounds simple, but in practice a large part of what is later interpreted as a commitment was not seen as such at the moment it was said, by the person who said it. A director who says in an interview "we'll look into that" may mean nothing more than a polite deflection. A stakeholder who hears it notes a commitment. Anyone who ever sets out to record a commitment quickly runs into this first hurdle: what exactly counts as a commitment, and who decides that.
Then there is the legacy. An organisation exists longer than a single term of office, and commitments made years ago sometimes remain in effect, even when nobody still knows they were made. The question of what you do with a commitment made by a predecessor is not a theoretical matter; it is one of the most common situations in which an organisation is confronted with something the current leadership was unaware of.
Once a commitment has been recorded, someone must follow it. Not occasionally, not when a journalist asks about it, but structurally. That requires a rhythm: a fixed moment at which it is reviewed which commitments are outstanding, which have been kept, and which have been delayed or have stalled. Without that rhythm, commitments disappear the same way they arose: silently.
At its core, a tracker is nothing more than a list that does not forget. What it adds is that it links a commitment to a status and a moment of reassessment, so that an organisation is not reminded of a promise only at the moment an outsider brings it up. The question of how often you report on stakeholders is connected to this: a tracker without a reporting rhythm is an archive; only with a fixed moment of feedback does it become an instrument that influences behaviour.
The third step, demonstrating that a commitment has been kept, is often underestimated. It is not enough to say that something happened; there must be a trail that shows this at the moment it is asked about, not only once reconstructing it becomes necessary. That trail is not primarily meant to be published, it is meant to exist, so that an organisation does not depend on one person's memory. What that demonstration looks like, and how it relates to regular reporting, is set out in how you report on commitments and demonstrate that they have been kept.
A single missed commitment is rarely discussed at board level; it feels too small. But the pattern of missed commitments — the sum over time — is exactly the kind of signal that does belong there, because it says something about the reliability of the organisation as a whole, not about a single incident. The question of which signals belong on the board's table is about that selection: not every detail, but certainly the pattern.
This is connected to a broader problem, namely commitments that are made without anyone centrally registering them. The question of how you prevent commitments from arising that nobody knows about touches the core of this: a commitment that has not been recorded cannot be tracked, and can certainly not be demonstrated.
The Trust Baseline starts with an internal survey alongside an external stakeholder survey, and the difference between those two pictures is the first outcome — including the picture of how well commitments are internally recognised as commitments. After that comes a commitment tracker and a signal rhythm, built on exactly the steps above: recording, tracking, demonstrating. What the Trust Baseline does not do is make statements about what a stakeholder thinks of a missed commitment; we only know that once the stakeholder says so themselves. The tool measures the difference between what management thinks and what is established internally and externally, not the opinion of an individual stakeholder.
The Trust Baseline is under construction. Anyone who wants to work with it can sign up for the waiting list; nothing is currently being offered that does not yet exist.
Recording and tracking commitments is, in part, administrative work: flagging deadlines, reminding people of outstanding points, compiling an overview for a reporting moment. Which part of that work can be taken over by AI and which part remains dependent on human judgement is precisely what the work scan from FTE TO AI is designed for: it calculates per task which part of the work can be taken over, so that it becomes clear where time is spent following a list, and where that time is needed to assess what a commitment actually means in practice.
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.