Vendor Contract Review Checklist (2026)

The checklist, top to bottom Here is a vendor contract review checklist you can run on any supplier agreement. Work down it in order. Each item is a question to answer from the document, not a box to tick blindly. 1. Parties and signing authority. Are the correct legal entities named, with the right registered details, and is the person signing authorised to bind that entity? A contract signed by the wrong entity or an unauthorised person is a problem you discover at the worst time. 2. Scope of work and deliverables. Is it precisely clear what the vendor will supply, to what standard, and by when? Vague scope is the single biggest source of vendor disputes. If there is a statement of work or specification, confirm it is attached and referenced, not "to be agreed later". 3. Price, payment terms and increases. What is the total price, what triggers payment, and when is it due? Watch for price escalation clauses, pass-through costs, expenses billed on top, and any right for the vendor to raise prices during the term. Confirm whether tax is included. 4. Term, renewal and termination. How long does it run, does it renew automatically, and what notice must you give to stop it? Note the exact notice window. Confirm you can terminate for convenience, for cause on uncured breach, and on the vendor's insolvency. 5. Service levels and remedies. If performance matters, is there a measurable service level, and what happens when the vendor misses it? Check whether remedies are automatic or must be claimed, and whether chronic failure lets you exit. 6. Warranties. What does the vendor actually promise about the goods or service, for how long, and what is the fix if the promise is broken (repair, replace, refund)? A warranty with no remedy is decoration. 7. Limitation of liability. What is the cap, and what does it exclude? Push for data breach, confidentiality breach and IP infringement to sit outside the cap. Be wary of any clause excluding all indirect or consequential loss combined with a very low cap, which can leave you with almost no recovery. 8. Indemnities. Who protects whom, and against what? You typically want the vendor to indemnify you against third-party IP claims and against loss caused by its negligence or breach. Check the indemnities are not one-sided against you. 9. Data protection and security. If the vendor touches personal data, is there a data processing agreement covering storage location, sub-processors, breach notification timing and deletion? Confirm security standards and ask for current, dated certification rather than claims. 10. Confidentiality. Is confidential information defined, are the obligations mutual, and do they survive termination for a sensible period? Make sure the definition covers what you actually need protected. 11. Intellectual property. Who owns what is created or supplied, and do you get the licence you need to use it after the contract ends? For bespoke work, confirm ownership or a wide enough licence is explicit. 12. Insurance. Is the vendor required to hold relevant insurance at adequate levels, and can you ask for evidence? This matters most where the vendor could cause you real loss. 13. Subcontracting and assignment. Can the vendor hand the work to someone else or assign the contract without your consent? For important suppliers you usually want a say. 14. Compliance and audit. Does the vendor commit to following the laws that apply to the work (for example anti-bribery, sanctions, data protection), and can you audit where it matters? 15. Exit and transition. When the contract ends, what help do you get to move on, how do you get your data or materials back, and in what format and timeframe? An exit you negotiate at the start is cheap. The same exit negotiated in a dispute is not. 16. Governing law and dispute resolution. Which country's law applies, and where and how are disputes resolved? For a cross-border vendor this decides how hard and expensive enforcement will be. ## How to use the checklist well Reading in order is good, but you do not have to treat every item equally. Before you start, decide what this particular vendor could realistically do to harm you. A cloud provider holding your customer data lives or dies on the data, security and exit clauses. A one-off equipment supplier is mostly about scope, price and warranty. Spend your attention where the risk is. Then triage each clause into three buckets: acceptable, negotiate, and red line. Mark up the document as you go so the vendor gets your words, not a list of questions. Keep a one-page summary of your positions so you do not reargue settled points. ## The clauses that cause the most disputes Across vendor relationships, the recurring failure points are narrow and predictable: - Scope creep, because the deliverables were never defined tightly.

• Silent auto-renewal, because nobody tracked the notice window.
• A liability cap that swallows the real risk, discovered only after something goes wrong.
• No clean exit, so leaving a bad vendor is slower and costlier than staying.
• Working from the wrong version, so the signed contract is not the one everyone thinks they agreed. Catch those five and you have avoided most vendor pain. ## Tools that help, named plainly Contract review tools can speed this up. Platforms such as Ironclad, LinkSquares, Juro, Spotdraft and DocuSign CLM offer clause libraries, approval workflows, renewal reminders and AI that flags off-standard terms against your playbook. For a small team, a saved checklist like this one, a redline in your word processor and a shared renewal calendar cover most of the need. Pick the tool for your volume, not the demo. ## Bringing the review into one place Step back and a vendor review is really the same few jobs repeated: understand what each clause means, compare it to your standard position, flag the risky terms, keep one current version, and remember the renewal date so the next cycle starts from strength. When those jobs are spread across a PDF, an inbox and someone's memory, items on this checklist get missed, not because anyone is careless but because the work is scattered. That is the single-workspace idea behind Adira: open a contract and see each clause marked favourable, neutral or unfavourable to your company, change terms in plain English, and keep versions and key dates in one record. Adira is India-first today with more jurisdictions on its roadmap, so for a cross-border supplier you would still rely on local counsel for the governing-law detail. The point is the direction: a review you can run in one place is a review that does not leak. This article is general information, not legal advice. For a material vendor contract, have qualified counsel review the final terms.