An AI renewal is a workflow review, not a seat-count negotiation

The renewal spreadsheet has everything procurement expects: licensed seats, active users, unit price, contract term, support tier, and the discount available for a longer commitment.

It does not say that the support team stopped using the assistant for policy exceptions. It does not show that sales copied its summaries into the customer record, although the original review covered private drafts only. It does not name the operations manager who maintains the shared instructions, the security analyst who investigates unusual access, or the person who can export the records if the company changes vendors.

The spreadsheet can negotiate a price. It cannot decide whether the organization should renew the work.

Treat an AI-tool renewal as a workflow review with a commercial decision attached. Before procurement asks how many licenses to keep, ask which business workflows now depend on the tool, what evidence supports that dependence, what changed after approval, and what it would take to continue without the vendor.

The decision is larger than the contract

A conventional software renewal can often start with access, utilization, support history, overlap, and price. Those remain useful for an AI tool, but they describe the account more reliably than they describe the work.

A person may open an assistant every day for disposable drafts that create little business value. Another team may use a shared integration rarely, yet depend on it for a consequential monthly review. A low seat count can hide an important workflow; a high prompt count can hide rework, curiosity, or use that should never have passed the data boundary.

Renewal therefore needs evidence at both contract and workflow levels:

Level	What the record should answer	Decision it informs
Contract	What is licensed, used, supported, integrated, and paid for?	Commercial terms, capacity, consolidation
Workflow	What work depends on the tool, under which controls, with what outcomes and failure burden?	Continue, narrow, redesign, replace, or stop

The US Government Accountability Office organizes AI accountability around governance, data, performance, and monitoring, and applies those principles across selection, implementation, and continued operation GAO AI Accountability Framework. That is a useful corrective to a renewal process dominated by license telemetry. Utilization belongs in the evidence packet; it is not the whole packet.

Put a workflow register beside the quote

Do not ask the vendor dashboard to tell you what the organization built around the product. Ask each accountable workflow owner to update a short renewal row:

Renewal field	Question
Business use	Which task or decision does the tool support, and who receives the result?
Approved boundary	Which data, users, outputs, integrations, and actions were approved?
Current boundary	What does the live workflow actually read, produce, retain, and affect?
Outcome evidence	Did the workflow improve the intended result after review effort, exceptions, and corrections are included?
Control evidence	Did access, human review, monitoring, escalation, and fallback work in practice?
Change record	Did the model, vendor terms, data source, audience, permission, or use change?
Operating cost	Who maintains instructions, integrations, evaluations, support, review queues, and incident handling?
Exit position	What must be exported, deleted, replaced, retrained, or communicated if the contract ends?
Disposition	Continue, narrow, redesign, replace, stop, or escalate for specialist review?

The NIST AI Risk Management Framework calls for an AI-system inventory, planned periodic review, documented third-party risk, and safe decommissioning NIST AI RMF Core. A renewal review is a convenient place to connect those activities. The contract list says what the company buys. The workflow register says where it matters.

This is not a request for teams to preserve every prompt. Keep the minimum evidence needed for the decision. Raw prompts and outputs can contain customer records, employee information, source code, commercial plans, or privileged material. Prefer workflow-level measures, sampled and appropriately prepared review cases, incident summaries, access records, and documented decisions. Set access and retention rules for the review material itself.

Give each workflow a disposition

A portfolio-level answer such as “renew the enterprise assistant” is too blunt. The same product may support a low-risk drafting aid, an unreliable research shortcut, and an integration that writes to a system of record. Those uses do not deserve the same decision.

Have the workflow owner recommend a disposition and show the evidence behind it.

Continue when the use still fits its approved boundary, the outcome holds after review and exception work are counted, the controls operate, and the organization can support it.

Narrow when part of the use is valuable but certain data, cases, users, outputs, or integrations create disproportionate risk. The contract may continue while the eligible workflow gets smaller.

Redesign when the underlying job is worth supporting but the current review gate, interface, instruction set, integration, measurement, or fallback is weak. Renewal should fund a specific correction, not preserve an indefinite pilot.

Replace when another product, an internal capability, a deterministic rule, better search, or a repaired process can perform the job with a better cost and risk profile.

Stop when the workflow has no accountable owner, no defensible outcome, an unacceptable data boundary, a review burden that erases the benefit, or a dependency the organization cannot safely support.

Escalate when the use affects employment, eligibility, safety, legal rights, regulated activity, sensitive personal data, or another high-consequence domain. A renewal memo is intake for legal, privacy, security, compliance, procurement, worker-relations, and domain review; it does not replace them.

If an owner cannot make one of those recommendations, the missing decision is itself useful evidence. Procurement should not quietly convert an ownerless experiment into another contractual term.

The commercial questions improve after the workflow review

Once the organization knows which uses it wants, the vendor conversation becomes more precise.

Ask whether the contracted product still matches the reviewed product. Vendors change models, subprocessors, retention controls, training practices, regional processing, administrative visibility, safety features, prices, and service limits. An unchanged product name does not prove an unchanged workflow boundary. Route material changes through the same change review that applies between renewals.

Check whether the company can obtain the evidence its controls require. That may include administrative access records, model or feature change notices, output provenance, incident information, data-location details, deletion confirmation, integration logs, and support response for a critical failure. Do not buy an audit promise that the operating team cannot use.

Price the work around the license as well as the license itself. Include integration maintenance, evaluation, verification, exception handling, training, internal support, security review, privacy work, recordkeeping, and fallback capacity. Some of this cost belongs to adoption and would exist with another product. Some is specific to the vendor or workflow. The point is to make the distinction visible before comparing quotes.

The UK Government’s AI procurement guidance says lifecycle oversight and ongoing evaluation matter because important functionality and consequences may become visible only during deployment. It also tells buyers to consider support gaps, knowledge transfer, vendor lock-in, auditability, and end-of-contract responsibilities UK Government Guidelines for AI Procurement. Although the guidance addresses central government procurement, those questions travel well: a renewal should test the dependency the organization actually created, not the one described in the original sales process.

Treat data and know-how as exit costs

The hardest part of cancellation is often not disabling seats. It is recovering the business state that accumulated around the tool.

Map what the organization would need to leave:

• source documents or connected records that remain authoritative outside the tool
• saved instructions, approved templates, evaluation cases, and workflow configurations
• generated material that became part of a company record
• decision and approval evidence needed for audit, complaint, investigation, or continuity
• integration logic, identity configuration, access groups, and support procedures
• deletion steps for vendor-held prompts, files, outputs, logs, derived data, and backups where the contract and applicable rules allow them
• staff knowledge needed to operate the fallback or move to a replacement

Then test the answer before the renewal deadline. An export that technically exists may omit configuration, provenance, comments, links, or permission context. A deletion control may apply to a user conversation but not an administrator log or integrated data store. A replacement may accept the files but not reproduce the review workflow.

Do not copy sensitive material into a new repository merely to prove portability. Use representative or safely prepared data where possible, restrict the people who can run an export, document where the result is stored, and remove test artifacts when the exercise ends.

The exit test connects renewal to the off-switch design. It also changes negotiating leverage. A team that knows its fallback, data obligations, and migration limits can evaluate a longer contract without pretending the vendor is interchangeable.

Use a lighter review when the dependence is light

This process is for organizations with shared AI tools, repeated workflows, meaningful integrations, sensitive data, or growing operational dependence. Procurement, the AI program owner, security, privacy, finance, and workflow owners all have a part, but they do not need to attend together. Collect the workflow evidence first and route only the exceptions that need specialist judgment.

A small team renewing a low-cost tool used only for private drafts from approved public information may need a short owner attestation, access check, overlap check, and acceptable-use reminder. Do not build a governance ceremony whose cost exceeds the decision.

At the other end, a contract anniversary may be the wrong clock for a high-consequence system. Use continuous monitoring, incident triggers, change-based review, formal assurance, and applicable regulatory or contractual processes. Do not wait for procurement to discover a harmful workflow at renewal.

Some organizations should avoid renewal altogether while evidence is missing. If the team cannot identify current uses, data flows, owners, affected people, or a viable stop path, a shorter extension with explicit remediation may be safer than a long commitment. If the tool is non-essential, stopping and rebuilding the case may be cleaner.

Leave procurement with an executable decision

The final memo should state which workflows continue, which conditions attach to them, who owns each condition, what the contract must preserve, and what will trigger another review. It should also name the uses that are being narrowed or stopped; otherwise, the organization may renew fewer seats while leaving the risky behavior untouched.

Keep the commercial and workflow decisions linked but separate. Procurement negotiates the supplier relationship. The accountable business owner answers for the use. Security, privacy, legal, compliance, finance, and affected operational teams decide within their existing authority. The AI program coordinates the evidence and detects patterns across the portfolio.

Measure the renewed workflow against outcomes, review effort, failure burden, and total operating cost—not only whether people open the tool. The workflow scorecard provides the operating view that license utilization cannot.

A renewal approved on price alone preserves a subscription. A renewal approved with workflow evidence preserves only the work the organization is still prepared to own.