Skip to main content
Steady at the Top
← All articles

How to keep track of promises made during company change

Track promises made during company change in a visible commitments register. Give each commitment an accountable owner, a clear completion condition, and a review date. When circumstances require revision, preserve the original promise and explain what changed before employees have to discover the gap themselves.

A visible commitments register is a working record of what leadership has promised, who owns delivery, and how others can verify the current status. It is a practical method grounded in Daft and Lengel’s (1986) distinction between missing information and unclear interpretation in organizational information processing. It is not a validated trust measure.

A commitment is an undertaking to act. An intention states a preference, and an investigation promises only to examine a question. Put each in the record accurately. Employees should not need to infer whether “we will look at workload” means a review, a staffing increase, or an immediate reduction in demand.

Capture the promise as the audience heard it

Start with leadership announcements, manager briefings, and answers given in live meetings. Identify statements that an employee could reasonably interpret as a future obligation. Include commitments about information, consultation, tools, authority, timing, and work conditions, not only major project milestones.

Do not rely on the CEO’s memory. Ask communication and implementation owners to flag promises as they arise. Give employees a route to identify a statement the register missed. Resolve differences by checking the actual wording and context rather than choosing the interpretation most convenient for leadership.

Industrial/organizational psychology is the psychology of work and organizations. Its research can inform communication and trust, while the register here is an operating tool. Its value comes from accurate entries and follow-through, not from calling it a psychological intervention.

Use How to explain company change so people know what to do for the wider change explanation. A commitments register should connect to the decision and work implications already communicated. It should not become a disconnected list that nobody consults when the implementation plan changes.

The visible commitments register method

1. Record the statement and its boundary

Keep the original statement, the audience, and the date. Then write a concise operational interpretation. If the original wording was ambiguous, clarify it with the audience and preserve the correction. Do not silently replace the statement with a narrower promise.

For example, “Managers will receive briefing materials before the employee announcement” can have a clear completion condition. “Managers will be supported” needs further definition. Ask what support was intended and what an affected manager can expect to receive.

Include conditions that were stated at the time. A promise subject to approval should remain visibly conditional. Do not add a new condition later while presenting it as part of the original agreement. If the boundary changes, record a revision.

Keep restricted information out of the broad register. Personnel matters, sensitive commercial terms, and legally protected information need appropriate handling. The public-facing internal entry can state the operational obligation without reproducing private details.

2. Name an owner who can deliver

Assign one accountable owner for each commitment. The owner needs authority over the required work or a defined route to obtain it. Naming a communication manager to own a staffing decision does not create the authority needed to fulfill the promise.

Record supporting dependencies separately. A training commitment may need approved materials, manager time, and access to a system. The accountable owner should coordinate those inputs rather than treating the existence of several contributors as an excuse for unowned delivery.

Ask the owner to confirm the entry. They should understand the audience, output, and boundary. A register populated by the CEO’s assistant without owner acceptance can create another set of commitments people discover only when they are late.

Where the commitment exceeds current authority, escalate it immediately. Leadership may need to authorize resources, narrow the promise through an explicit correction, or state that the obligation cannot be met. Do not leave an impossible entry green until the due date.

3. Define evidence and the next review point

State what counts as completion. A document published is different from employees gaining usable access. A meeting scheduled is different from the promised review occurring. Choose the evidence that matches the statement the audience received.

Set a due date where the commitment supports one. For uncertain work, record the next review point and the decision required there. Avoid a distant final date that leaves no opportunity to detect a missed dependency before the promise fails.

Distinguish status from confidence. “On track” describes a judgment about the future. “Briefing materials approved and distributed to named managers” describes completed work. Keep enough evidence behind the judgment for another person to inspect it.

Use a maintained source record rather than duplicating every artifact. Link to the current policy, approved material, or decision note within the company’s appropriate systems. The register should direct people to evidence without becoming another uncontrolled copy of it.

4. Explain revisions before replacing the promise

When a commitment changes, record the original date or scope, the reason, the new boundary, and the affected audience. Explain the consequence for employees. A delay in a tool launch may require a temporary work process, not merely a revised calendar entry.

Use direct language: “We said the new approval route would begin on this date. Access testing is incomplete, so the current route remains in force. The operating owner will confirm the next date after testing.” Use only facts that are true in your case.

Do not turn every revision into an apology performance. State the error or changed condition, the consequence, and the action. If leadership overpromised, own that specific decision rather than implying that circumstances alone explain it.

Kramer’s 1999 review examines barriers to sustaining organizational trust. The register should let employees inspect follow-through and revision. It cannot guarantee trust or erase the consequence of a broken promise.

5. Close the loop with the affected audience

Notify people when the commitment is complete, revised, or withdrawn. State the practical implication. A status field changing in a tracker may not reach the employees who relied on the original statement in a meeting.

Morrison’s 2014 review examines employees choosing to share or withhold upward input. Provide a route to report that a claimed completion does not match experience. An employee may reveal that access exists on paper but not for their role.

Use How to show employees a change is helping their work to collect frontline evidence. Check a relevant example of the promised change in use. Keep the check proportionate. You need enough evidence to confirm the obligation, not a new reporting burden larger than the original work.

Archive completed entries without erasing them. Future leaders should be able to see what was promised and how it ended. Keep the current view concise, while preserving the history needed to understand a later disagreement.

A hypothetical register entry

Leadership promises that a new operating model will reduce duplicate reporting. The initial entry says, “Reporting simplification: complete.” The evidence is that the new reporting tool went live. Employees still produce the old spreadsheets for several executives.

The owner revises the completion condition to match the original promise. The company names the reports that will stop, confirms the recipients’ information needs, and tells managers which old requests should no longer be fulfilled. The entry remains open until that decision is implemented.

This is a hypothetical illustration. The tool launch may have been completed correctly, but it was not the same commitment as reducing duplicate work. The register helps distinguish an implementation milestone from the benefit employees were told to expect.

Use When corporate language makes difficult news harder to trust to inspect euphemisms in the entries. A label such as “rightsizing support” may conceal the actual action and its consequence. Plain wording helps employees identify whether the company delivered the promise they heard.

The private-life composite

A founder receives an employee message while helping a family member move house. The employee asks about a promise made at the last all-hands meeting. The founder remembers the conversation but cannot recall who was assigned to follow through.

This composite shows how private memory can become an unreliable company system. The founder can acknowledge the question, check the record, and assign a response. A maintained register would make the obligation visible before it interrupts another personal commitment.

If stress symptoms persist or affect daily life, consult a licensed clinician. The operating task is to make promises retrievable and owned. It should not depend on the CEO retaining every conversation or remaining available through every private event.

Keep the register small enough to use

Capture material commitments, not every expression of hope. Define the threshold with examples so employees know what belongs. A promise that affects how people plan their work deserves attention even when it concerns a modest output.

Review the register within the existing implementation cadence. Do not create a separate meeting unless it serves a clear decision. The owner should arrive with evidence, an unresolved dependency, or a proposed revision requiring action.

Use How to rebuild employee trust after leadership breaks a promise when a broken promise needs a wider repair. Completing the delayed task may not address the cost employees already carried. Acknowledge that consequence and explain what leadership will change about future commitments.

Before the next announcement, ask who will own each forward-looking statement. If nobody can own it, revise the language before speaking. A credible promise is narrow enough to deliver, clear enough to inspect, and honest about the conditions that could require change.

Check the next leadership briefing for new promises before publishing it. The register works best when it prevents an unowned commitment, rather than only documenting one after employees ask what happened.

Sources

Steady at the Top