Keeping a register
What to record for every agreement
A vendor record earns its keep when it answers four questions without opening a document: what did we buy, what does it cost across its term, when must we act, and what does leaving cost. That is roughly a dozen fields. Everything else is useful, but it can be added later without the record being wrong.
The Vendor Squeezer team. Last reviewed 2026-08-08. General guidance on contract structures, not legal advice, and not a statement about any particular vendor's terms.
The fields that do the work
Start with these. They are almost always on the first two pages of the document, and together they answer the questions a budget owner is actually asked.
| Field | Answers | Note |
|---|---|---|
| Counterparty | Who are we contracted with | The legal entity, not the brand |
| Document role | Does this commit money | Framework, commitment, amendment, or ancillary |
| Term shape | Does this have an end date | Fixed, evergreen, rolling, perpetual |
| Start and end date | When does the current period run | End date is blank for evergreen, on purpose |
| Auto renewal | Does it continue by default | Yes or no, and the renewal period |
| Notice period | When is the real deadline | Length, form, and recipient |
| Termination for convenience | Can we leave without cause | Record the absence too |
| Early termination cost | What does leaving cost | Amount with currency, or the basis |
| Committed amount | What do we owe per period | Integer amount with an ISO currency code |
| Pricing model | Can this be forecast | Unknown is a legitimate value |
| Owner | Who decides at renewal | A person, not a department |
| Parent document | What governs this | Blank means standalone, or means missing |
Rules that keep the record honest
The fields matter less than the discipline applied to them. Three rules do most of the work.
- Never record an amount without its currency. A number alone is ambiguous the moment more than one currency exists in the portfolio.
- Record a gap as a gap. A blank that means unknown and a blank that means not applicable are different, and only one of them is work.
- Record where a value came from. A figure someone remembers and a figure read off a signed document should not look identical.
What can wait
Plenty of detail is genuinely useful and none of it should block a record from existing. Liability caps, governing law, invoicing addresses, and service level targets are all worth having eventually. None of them change what you are committed to or when you must act, which is why they come second.
The failure mode to avoid is a record template so complete that nobody finishes one. A vendor with a name, an owner, and a renewal date is more useful than a perfect record that was never created.
Questions to ask about your own agreement
- 1.Can this record answer what we owe and when we must act, without opening a file?
- 2.Does every amount carry its currency?
- 3.Is every blank field either a known gap with an owner or a genuine not applicable?
- 4.Does the record say where each value came from?
- 5.Is there a named person responsible, rather than a team?
Common questions
Is a vendor with no contract worth recording?
Yes, and it is a complete record rather than a draft. Knowing that a vendor exists, what they do, and who owns the relationship is useful on its own, and it makes the missing paperwork visible as something to chase.
How much detail is too much?
When the template stops records being created, it has too much. Start with the fields that answer the four questions and let the rest accumulate as documents come in.
Put this against your own vendors
Record the term, the notice deadline, and the exit cost against the vendor once, and the next renewal review starts from an answer instead of a search. Free while in early access.