A report on commitments is usually only produced at the moment someone asks for it. A supervisory board, a journalist, an auditor. It then turns out that the commitment itself can still be found — in a minutes report, a press release, an email — but that no one can show what happened after that. Reporting on commitments is therefore not primarily a writing question. It is a question about what you recorded at the moment you made the commitment, and what you kept track of in the period afterward.
A list of commitments is a collection of sentences. A report is something else: it shows, per commitment, who made it, when, to whom, what the deadline was, and what happened when that deadline passed. Without that structure, a report falls back on memory and on the goodwill of the people who were present at the time. That works as long as those people are still there. It stops working after a handover, a reorganization, or simply the passing of time. What you do with a commitment made by a predecessor and that you did not make yourself is what do you do with a commitment made by a predecessor a question that comes up in virtually every report, usually without there being a fixed answer to it.
A report can never show more than what has been recorded. That means that the quality of a report on commitments is determined at the moment the commitment is made, not at the moment accountability is requested. Anyone who only tries to reconstruct afterward what was promised and to whom often discovers that part of the commitments was never written down anywhere. They were made in a conversation, a panel discussion, an informal briefing, and now only exist in the memory of whoever was present. How you prevent that, and which commitments most easily slip through the cracks, is described at how do you prevent commitments that no one knows about. A report is therefore always only as good as the recording that preceded it.
There is a difference between writing down a commitment and demonstrating that it has been fulfilled. The first requires a fixed moment: a place where the commitment is registered as soon as it is made, together with the date, the source, and the deadline. The second requires something else: a trail of what happened between the moment of commitment and the moment of fulfillment, with the actions and the corresponding dates. Reporting only becomes possible once both steps have taken place. How this recording and this evidence relate to each other is set out at how do you record a commitment and how do you demonstrate that it has been fulfilled. Anyone who does not keep these two steps separate often ends up, when writing a report, concluding that there was an intention, but no evidence.
A commitment without a deadline is difficult to report on, because there is no moment at which it can be established whether it has been fulfilled. But a deadline alone is not enough either: someone must monitor that deadline, and that monitoring itself must also be visible. Otherwise, a report emerges that claims something happened without being able to substantiate it. Who within an organization takes on that monitoring, and how it is demonstrated, is set out at who monitors a deadline and how do you demonstrate that it happened. This is usually the weakest link in a report: not the absence of the commitment, but the absence of someone who was responsible for monitoring it.
A report on commitments is often built around the large, visible promises: an investment, a target, a structural change. But failing to fulfill a small commitment — a follow-up, a response, a minor adjustment — usually costs more trust than failing to make a large investment. A large commitment is understood as something with a long horizon and many dependencies. A small commitment is seen as a test: does this organization stick to what it says, even when it costs little effort. What failing to fulfill such a small commitment actually costs, and why that cannot be expressed in money, is described at what does a small commitment you fail to fulfill cost and how do you demonstrate that. A report that only includes the large commitments leaves the largest part of the risk unaddressed.
If reporting on commitments only happens at the moment it is asked for, then every report is a reconstruction. If keeping track of commitments and monitoring deadlines becomes an ongoing process, then reporting becomes a matter of consulting what has already been recorded. That difference — between reconstructing and consulting — is exactly where the question of reporting on commitments begins and ends. More on how these two relate to each other, and what can be demonstrated in the process, is at how do you report on commitments and how do you demonstrate that it is correct.
Writing down a commitment, linking a deadline, logging an action, and compiling a report are each tasks that consist of recurring, recognizable steps. Such tasks are exactly what the work scan of FTE TO AI looks at: it calculates, per task, what portion of the work can be taken over by AI, without deciding anything about the commitment itself in the process. Anyone who wants to know what portion of reporting on commitments qualifies as a task can have that calculated with the work scan.
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.