A commitment to a stakeholder often arises in a conversation, a letter, a response to an incident. Someone states on behalf of the organization that something will happen by a certain date. After that, the commitment often disappears into a report, a mailbox, or the memory of one person. Whoever replaces that person, moves on, or forgets, takes the commitment with them.
The question of who monitors a deadline seems administrative. It is not. It touches the core of what an organization delivers on to the outside world. A commitment that no one monitors becomes, in practice, a commitment that no one fulfills — not out of unwillingness, but because there is no mechanism that brings it to the surface at the moment it matters.
Most organizations do record commitments. In minutes, in an action list, in an annual report. The problem does not lie in recording, but in what happens afterward. An action list that is never revisited is an archive. A commitment that exists only in the memory of the person who made it is vulnerable to staff turnover, reorganization, or simply time pressure.
What is missing is a structure that keeps three things separate: what was committed to, who is responsible for it, and by when it must be demonstrably fulfilled. Without that separation, a commitment lapses into an intention, and an intention is not what a stakeholder remembers.
There is a pattern that occurs more often than it seems: failing to fulfill a small commitment costs more trust than not making a large investment. A stakeholder who hears that a large promise was not feasible accepts that more readily than a stakeholder who notices that a small, concrete commitment — a follow-up, a report, a conversation — was simply forgotten. The first is explained away as complexity. The second is remembered as unreliability. More about what that difference costs in practice can be found on the page about the price of a small commitment that is not fulfilled.
This is precisely why a commitment tracker is not decorative. It does not exist to monitor large strategic promises — those usually already receive attention. It exists to keep the small, specific, dateable commitments visible, precisely because those disappear from view the fastest and weigh the most when they do.
A familiar scenario: an executive makes a commitment, is replaced, and the new executive does not know the commitment exists — or does know, but does not feel bound by it because he did not make it himself. Stakeholders do not make that distinction. To them, the organization is the party that said something, not the person. How to handle this depends on how explicitly the handover is arranged and whether the commitment has been decoupled from the person who made it. That question is addressed on the page about commitments made by a predecessor.
A tracker that links commitments to a role instead of a name, and to a date instead of a vague "soon," survives staff turnover. Without that structure, a commitment rarely survives a reorganization.
An organization that says it has fulfilled a commitment, and an organization that can prove it, are not treated equally by stakeholders. Proving requires a trail: what exactly was the commitment, when was it supposed to be fulfilled, what concretely happened, and who can confirm that. Without that trail, a claim remains a claim, and a stakeholder who has been disappointed before no longer believes a claim on authority alone.
This also touches on the question of how and how often an organization communicates about this externally. A commitment that is only mentioned at the moment it is fulfilled — or just missed — feels different from a commitment that is already visible in the interim as an ongoing process. What that rhythm looks like is discussed on the page about reporting frequency for stakeholders and on the page about reporting on commitments and proving fulfillment.
A commitment that has never been discussed at a board table is, in practice, a commitment the organization has not made consciously — even if it was voiced by someone with authority. Which signals should structurally reach that table, and which should specifically not be allowed to linger there as a vague concern without an owner, is a separate question. That is addressed on the page about which signals belong at the board table, as is the question of how to prevent a commitment from arising outside the organization's view — covered on the page about commitments no one knows about.
A commitment tracker as part of the Trust Baseline is not a reporting tool and not an archive. It is a structure that links a commitment to a role, a deadline, and a burden of proof, so that monitoring does not become a matter of memory. The tool that supports this is under development. Anyone who wants to work with this already can sign up for the waiting list; there is nothing to order yet, but something to look forward to.
Monitoring commitments is one of the tasks that now often rests on a single person, with all the vulnerability that entails. Which part of that monitoring — flagging deadlines, compiling evidence, reminding owners — is suitable to hand over to AI is something that varies per organization. The work scan from FTE TO AI calculates, per task, which part of the work can be taken over, so that this assessment does not have to rest on gut feeling.
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.