AI terms in vendor contracts

The decision on your calendar.

A renewal or feature add-on includes AI. The quote says little about training use, retention, subprocessors, incident notice or export.

Bring the sources you are allowed to share.

• Contract and addendum versions you may share
• The vendor feature description
• Institution requirements and renewal deadline
• The vendor owner and legal-review route

The file your institution keeps.

• A source-linked AI terms register
• Entitlement and training-use questions
• Retention, export and exit questions
• Incident, subprocessor and control questions
• A recommendation with unresolved terms retained

Four working steps.

1. Agree the questionOne workflow, permitted inputs, accountable owner and the decision due.
2. Prepare the sourcesKeep versions, missing records and assumptions visible.
3. Review the evidenceRetain failed cases. Your team reviews the proposed answer and open questions.
4. Leave the fileA one-page recommendation, supporting records and named next actions.

Your team owns review and acceptance.

Your vendor owner obtains missing terms. Your counsel interprets the contract. We compare supplied terms with your stated requirements.

Timing depends on agreed inputs and customer review. Corrections within the agreed scope are recorded in the file; a new use or workflow requires a new scope.

Inspect the method.

Read the secondary renewal example. Browser methods work on supplied inputs or inspectable examples.

Scope and fee.

Scope and fee fixed in writing after one working session. The written scope names the sources, customer review responsibilities, deliverables and corrections included.