A board member tells a nearby resident during a conversation that noise pollution will be looked into. A spokesperson promises a neighborhood organization a follow-up before the end of the quarter. A director mentions a target date for a measure in an interview. None of these statements appear in an annual report. None of these statements make it into a strategy document. But they are remembered, and not by your organization.
The damage of a broken small commitment is not small. Someone who postpones a large investment can explain that: market conditions, priorities, capital. Someone who simply lets a small commitment slide gives no explanation, because no one saw it coming. The stakeholder who was waiting for it draws their own conclusion. That conclusion is not about that one commitment. It is about whether your word means anything.
Projects have owners, steering committees, and reporting lines. Commitments to external stakeholders usually don't have that. They arise in a conversation, a letter, a panel discussion, a response to a question from the floor. They are made by people who then move on with their agenda, and the commitment disappears into notes, emails, or nowhere.
That is a different problem than poor project management. It is a registration problem: there is no place where these statements automatically end up. Without that place, no one knows how you prevent commitments that no one knows about, because the first step is not keeping the commitment, it is recognizing that something was promised.
Writing down a commitment is not difficult. Being able to find a commitment again months or years later, with the right context, the right deadline, and the right owner, is difficult. Especially when the person who made the commitment now holds a different position, or has left the organization.
This comes up at every handover. A new director, a new corporate affairs manager, a new spokesperson inherits a collection of commitments they did not make themselves and whose background they do not know. The question what do you do with a commitment made by a predecessor is then not theoretical. The answer determines whether the organization shows continuity or a memory that starts from zero with every change.
Recording a commitment is a moment. Monitoring it is a period: someone must know when a deadline is approaching, and that person should not just happen to be the one who remembers it. Demonstrating that a commitment has been kept is a third step, separate from the first two, and often the step that is missing.
An organization that has kept a commitment but cannot show it is no better off than an organization that did not keep the commitment. For a stakeholder asking whether anything was done, "yes, we did that" without substantiation is little different from a new promise. Anyone who wants to know how you record a commitment and how you demonstrate that it has been kept runs into exactly this difference between doing and proving.
A deadline without an owner is not a deadline, it is a date that passes by. Once a commitment has been recorded, it must be clear who is responsible for follow-up and who is held accountable if nothing happens. Without that assignment, responsibility disappears into the space between departments, and that is exactly where commitments die.
The question who monitors a deadline and how do you demonstrate that it happened is therefore not just an organizational question. It is a question that must be answered in advance, not afterward when a journalist or a regulator asks about it.
There is no legal obligation to show the outside world which commitments have been made and which have been kept. That makes it a choice. Organizations that make this choice deliberately give stakeholders something to rely on: not a word spoken in a conversation, but a trail that can be followed. What that trail looks like and what it delivers depends on the organization and its stakeholders; anyone who wants to explore this further can read on about how you report on commitments in a way that fits what is already being recorded.
The full question, from cost to proof, comes together on the page about what a small commitment you don't keep costs you and how you demonstrate that the next one will be kept.
The Trust Baseline places the internal picture of what has been committed to alongside the external picture of what stakeholders say about it. The difference between the two is the first outcome, not a verdict on who is right. In addition, a commitment tracker keeps track of commitments, deadlines, and owners, and a signal rhythm ensures that an approaching deadline does not depend on someone's memory. The tool is under construction. Anyone who wants to work with it once it is available can sign up for the waiting list.
Tracking commitments, monitoring deadlines, and drawing up evidence are themselves tasks too, with fixed patterns and repetition. Anyone who wants to know which part of that work can be taken over by AI, and which part continues to require a human's attention, will find a calculation per task at the work scan from FTE TO AI.
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.