A commitment that only exists in a minutes-pdf does not exist for most people in your organization. The executive who made it may have forgotten it, the colleague who has to carry it out has never seen it, and the stakeholder who heard it is waiting. The moment someone from outside asks about it, it often turns out that nobody can say with certainty what was promised, to whom, and whether it happened.
That is not a matter of unwillingness. It is a matter of recording. A commitment made during a conversation, a panel or an interview rarely lands automatically in a system that keeps track of who owns it and when the deadline falls. It disappears among the action points of another topic, or it stays verbal and is never noted down anywhere.
Recording is the first step: who committed to what, to whom, and within what timeframe. Without a fixed moment at which that happens, it depends on who happened to be taking notes. How you record a commitment determines whether that commitment can still be found after a month, or whether it only exists in the memory of the person who made it.
Monitoring is something else. A commitment with a deadline needs an owner who is responsible for progress, and a moment at which someone checks whether that deadline is being met. Without that oversight, a deadline slips, and nobody notices until the stakeholder asks about it themselves. That raises the question of who monitors a deadline within your organization, and what happens when that person is on leave or changes roles.
An executive who fails to make a large investment is held accountable for that at a strategic level. Failing to keep a small commitment — a follow-up that never comes, a conversation that is not scheduled, a report that arrives a quarter later than promised — often costs more trust than that large investment could ever have cost. The reason is simple: the small commitment is concrete and personal. The stakeholder who received it remembers exactly what was said and when.
What a small commitment you don't keep costs you shows why this pattern repeats itself: most of the reputational damage in situations like this does not arise from failing policy, but from unnoticed negligence at the detail level. That is precisely the reason a tracker adds value. Not to monitor major decisions — those get attention regardless — but to keep visible the small commitments that would otherwise disappear silently.
Recording and monitoring solve part of the problem. The other part is accountability: being able to demonstrate, at the moment it is asked of you, that a commitment has been kept. That requires a format that is not only readable internally, but also holds up against someone from outside looking on critically. How you report on commitments is about that format: what a report must contain to be credible, and what makes a report look suspicious instead.
That reporting does not stand on its own. It should connect to what is already being discussed at board level. Not every signal belongs on the boardroom table, and not every commitment is board-relevant, but the distinction between what should and should not be escalated is rarely established in advance. Which signals belong on the boardroom table describes where that line lies, and why the absence of that line often means a board only hears about a problem once it has already leaked outside.
The Trust Baseline asks your own organization and an external stakeholder group separately for their view of the state of affairs. The difference between those two views is the first outcome — not a verdict on who is right, but an exposure of where perception diverges. A commitment tracker and a signal rhythm follow from that: commitments that have been recorded, deadlines that are being monitored, and a fixed moment at which that picture is repeated. How often that needs to happen depends on your sector and your exposure; how often you report on stakeholders describes what that choice depends on.
This inquiry says nothing about what a stakeholder actually thinks. Nobody knows that until they say it themselves. What the Trust Baseline does expose is the difference between the internal picture and what is reflected back externally — and that difference is often the first place where a commitment goes missing.
The Trust Baseline, the commitment tracker and the signal rhythm are being built now. Anyone interested can sign up for the waiting list; there is nothing to use today yet, and we would rather write that down honestly than offer something that does not yet exist.
Recording and monitoring commitments is work that partly consists of fixed, repeatable steps: noting a deadline, linking an owner, sending a reminder, compiling a report from fixed components. Which part of that work can actually be taken over, and which part continues to require human judgment, differs per organization and per task. The werkscan by FTE TO AI calculates that per task, and shows which part of the work around recording and accounting for commitments lends itself to that takeover.
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.