Checklist · Technology, Media & Telecommunications / IT Contracts
AI vendor terms review checklist
Questions for a contract with a vendor that provides or hosts an AI system. The NIST AI Risk Management Framework is voluntary. No statute opened here requires a vendor to adopt it or sets who owns model outputs.
- Kind
- Checklist. Steps or checks to work through and tick off.
- Where it applies
- United States
- AI use
- Yellow You and the tool draft together, with you directing. You check every statement you rely on.
- Law stated as at
- 22 October 2026
- Status
- Maintained. Checked on 22 October 2026 against the 3 authorities it cites, for United States.
- Version
- 1
- Source
- Written for this library
When to use it
Use when reviewing an AI vendor's terms before signature. Record what the draft says. Do not add a training ban, an output license, or an incident deadline that the draft and the opened sources do not contain.
Used for these tasks
- Review a SaaS agreement for AI-specific clauses
- Review a GenAI vendor contract for TMT clients
- Draft AI-use, training-data and output-warranty clauses for a vendor contract
Each task page says how far AI may help with the task and what the lawyer must review.
How AI may be used
AI may quote the clauses on training, outputs, testing, and incidents from the draft. The lawyer decides which gaps matter and whether any statute applies.
AI may
- Quote the training, output, testing, and incident clauses from the draft
- Mark a topic the draft does not address as silent, not as forbidden
- Point a Safeguards Rule customer to the safeguards addendum rather than inventing controls
AI must not
- Must not state that the AI RMF is legally required
- Must not invent an ownership rule for outputs or a ban on training
- Must not insert an incident-notice period
The lawyer checks
- Each row is a quotation from the draft or an express 'silent'
- Part 314 is raised only if the lawyer decides the customer is covered
- The checklist is not signed as the contract
Method: how the Green, Yellow and Red levels are decided. This is guidance for planning, not legal advice.
Read the full text
The full text is available after you log in. It is free. When you log in you can:
- read the whole precedent, with its drafting notes beside it;
- copy it, or download it as a Word file or Markdown;
- add it to your firm’s knowledge base, so colleagues can find it;
- let the AI tools you connect read it from that knowledge base.
The summary, the law it rests on and the AI-use guidance above stay public. Privacy.
More in Technology, Media & Telecommunications / IT Contracts
- IT services statement of work template (under a master services agreement)
- Ransomware or cyber extortion payment report: fields on the ACSC form
- SaaS / cloud services agreement (Australian law, business customers)
- CCPA service provider and contractor addendum
- SaaS subscription and negative-option checklist
- Website and online platform terms of use (Australian business, with Australian Consumer Law carve-outs)
- AI standard clauses for AI features in cloud services (Bonterms AI Standard Clauses v1.0, CC0)
- Deed of assignment of intellectual property and moral rights consent (contractor or developer software)
- Service level schedule with service credits (SaaS, managed or hosted services)
- Register of Critical Infrastructure Assets: what the CISC page asks for
- Checklist for electronic consumer records
- SaaS subscription agreement
- AI addendum: ownership of AI-generated output, training-data rights and AI-specific warranties (customer-side)
- Email and SMS marketing campaign checklist (Spam Act consent, sender identification and unsubscribe)
- SOCI Act cyber incident report: 12-hour and 72-hour clocks
- Software source code escrow agreement (three-party: supplier, customer and escrow agent)
- Statement of work
- Cross-border disclosure assessment for a technology vendor (APP 8 and s 16C checklist and record)
- Critical infrastructure risk management program: annual report contents
- Australian Government AI model clauses (DTA, BuyICT ClauseBank): use guide for agencies and suppliers
- Open source licence compliance review checklist (technology transactions and product releases)
- Security incident clause
- Consumer Data Right: data holder obligations on the CDR site
- Data protection, security and breach-notification schedule (processor terms)
- Software development agreement with AI coding-assistant and open-source terms
- Checklist: reviewing a vendor SaaS or technology contract (customer side, including AI terms)
All precedents for Technology, Media & Telecommunications / IT Contracts · Tasks and AI use in this area