Make the commitment observable
Replace “work on the account” with a named action, owner and date. Record what must happen with the customer, what the seller controls and any dependency on someone else. A promise that depends on customer approval should not be represented as a guaranteed outcome.
Close the loop at the next review
Start with the prior commitments. What happened, what changed and what should happen now? Make it possible to report a genuine blocker early. Distinguish a changed circumstance from repeated failure to follow through. Consistency gives performance conversations a factual basis instead of relying on memory.
Keep the system light enough to use
Use the existing CRM or a small shared record where practical. Decide which fields actually support action and remove duplicate reporting. A manager still has to inspect, coach and resolve dependencies. A new dashboard cannot take responsibility for the commitments it displays.