A practical method for small teams: what to record, when to review, and how to follow up without damaging the relationship. Updated 16 November 2026.
In short: keep one register for every promise made between your company and its clients and suppliers, in both directions. Give each commitment one owner, a due date and a source. Review the register for 15 minutes every week, and make sure the other side can see and confirm what they owe.
Most missed commitments are not refused. They are forgotten. Four patterns cause most of them:
Use one row per promise. Keep clients and suppliers in the same register, and filter by counterparty when you need a view of one relationship.
| Field | What to write | Example |
|---|---|---|
| Counterparty | Company and contact person | Northline Logistics, Anna Weber |
| Direction | We owe them, or they owe us | They owe us |
| Commitment | A specific, checkable result | Confirm the revised delivery date for order 4471 |
| Owner | One named person on your side | Paul, procurement |
| Due date | A real date, not "soon" | 21 November |
| Source | Where it was agreed, with a link | Call of 14 November, recap email |
| Status | Open, at risk, done, renegotiated | Open |
| Impact if missed | Low, medium or high | High: blocks the client installation |
Direction is the field most teams skip, and the one that catches supplier slippage. When a "they owe us" item has an owner on your side, someone is responsible for noticing that it is late.
A short, fixed review keeps the register alive. Fifteen minutes, on the same day every week:
Once a month, look at the register by counterparty: which suppliers keep slipping, and which clients you keep letting down. That pattern is worth more than any single item.
For contracts, set reminders 60 to 90 days before renewal and notice dates, not on the date itself.
Send it the same day. Asking the other side to correct it is what makes the list shared rather than yours.
"Our list shows the revised delivery date for order 4471 was due on Friday. Can you confirm the new date, or tell me what is blocking it?"
A shared spreadsheet is a good start. It stops working when:
A CRM handles client commitments well, but rarely suppliers, so you end up with two systems. Project tools such as Asana or Microsoft Planner track internal tasks well, but they are built for people inside your company.
Thingz is an action tracker for work that crosses team and company boundaries. For client and supplier commitments, that means:
Team plan: €10 per internal team member per month, AI included, with a 30-day free trial. See pricing and how it works.
A single list of every promise between your company and others, with one owner, a due date, a source and a status for each. At any time it answers two questions: what have we promised, and what has been promised to us.
Yes. Use one register with a counterparty field and a direction field (we owe them, or they owe us). You can filter by relationship, and nothing falls between two systems.
Fifteen minutes every week for what is due in the next two weeks, overdue, waiting on the other side or at risk. Once a month, review by counterparty to spot patterns.
Not in a spreadsheet, unless you give them access to your file. In Thingz, yes: clients and suppliers on a project receive their commitments by email, or in their Teams or Slack when connected, and update them in one click.
Agree a new date before the old one passes, record the commitment as renegotiated, and tell everyone affected. When the same counterparty keeps slipping, discuss it as a relationship issue rather than sending more reminders.
Clients and suppliers update their own commitments, without an account. Your team stops chasing.
Start your free 30-day trial See how it works