Start before the relevant notice deadline, compare observed service with the approved baseline, and reassess rights, costs and dependencies. Record an explicit renew, renegotiate, restrict or exit decision with evidence for each unresolved issue.
Schedule the decision from the contract backward
Identify the contractual notice requirements and the internal time needed to evaluate alternatives, obtain approvals and carry out any authorized action. Ask the responsible reviewer to confirm the relevant dates and process for this agreement. Do not assume a standard cancellation window. A renewal review that begins after the meaningful decision point can become a retrospective explanation for a commitment already made.
Invite the operational owner, research user, budget owner and relevant specialists early enough to provide evidence. The meeting should not depend solely on the supplier's account review. Request actual usage, incident history, change records and open conditions from buyer-controlled sources. Make the current approved scope available so participants can distinguish disappointing performance within scope from a new requirement that was never purchased.
- Plan evidence gathering early enough to preserve real contractual choices.
Compare service against the original purpose
Ask whether the workflow still needs the licensed model and whether the actual recipients and uses remain within the approval. A feed may be reliable but no longer used, or heavily used in a way the original licence did not cover. Separate workflow usefulness from investment outcomes. Neither a favorable market period nor a single successful research decision proves that renewing the service is justified.
Collect evidence of repeated operational workarounds, manual corrections and unplanned support effort. These observations can change the effective cost even when the invoice is unchanged. Ask users to identify specific missed tasks or useful outputs instead of giving an undifferentiated satisfaction score. The review should reveal which aspects of the service create value and which consume capacity the original budget did not anticipate.
- Review actual use and manual work, not only uptime and invoices.
Read a fictional service scorecard correctly
In a hypothetical fictional renewal review, the buyer expected 120 publications over a defined observation period. Of those, 114 arrived by the agreed cutoff, giving 95% on-time delivery. Six of the on-time publications lacked required revision identifiers, leaving 108 that were both on time and usable under the buyer's declared acceptance rule. That combined usable-timely rate is 90% of expected publications.
The remaining six publications arrived late and are counted separately. The three groups therefore total 120: 108 timely and usable, six timely but unusable, and six late. Later corrections may restore archive completeness but do not retroactively meet the original cutoff. The review retains both facts rather than allowing a corrected download to erase a missed decision-window incident.
- Keep original timeliness distinct from eventual corrected completeness.
| Fictional publication category | Count | Share of expected |
|---|---|---|
| Timely and usable | 108 | 90% |
| Timely but missing required identifiers | 6 | 5% |
| Late | 6 | 5% |
| Expected total | 120 | 100% |
Reassess changed dependencies and conditions
NIST SP 800-161 Revision 1 treats supply-chain risk as a continuing organizational concern. At renewal, ask what changed in the supplier's hosting, subprocessors, upstream data, staffing and support arrangements. A prior assessment can remain useful, but its scope and assumptions need checking. Identify evidence that has expired or no longer covers the delivered service before carrying its conclusion into another term.
Review every condition from the previous approval. For each one, show closure evidence, an authorized extension or the consequence of noncompletion. A repeated promise to provide recovery evidence is not equivalent to a completed test. If the buyer tolerated a restricted use temporarily, ask whether that use should remain restricted, be discontinued or receive a fresh approval based on new evidence.
- Carry forward unresolved conditions visibly, with their actual status.
Reconcile the next quote with observed demand
Use actual seat and consumption records to construct the next budget, while separating recurring demand from one-time backfills. Check whether the proposed renewal alters permissions, support hours or included models alongside price. A flat headline fee can conceal a reduced allowance. Conversely, an expanded package is not automatically worth more if the buyer does not need or cannot authorize its additional scope.
For the fictional service, suppose the next annual quote rises from USD 20,000 to USD 21,600. That is an 8% increase. The review should compare the USD 1,600 increment with scope and observed use, not offset it against invented investment gains. If the provider proposes a lower price in exchange for a longer commitment, compare the entire commitment and realistic exit options before recommending the change.
- Explain changes in price, allowance and rights independently.
Choose a decision that matches the evidence
Possible outcomes include renewal as proposed, renewal with a narrower use, renegotiation of material terms or an authorized exit. A short bridge arrangement can be considered where its scope, cost and purpose are explicit. Avoid using a bridge simply to postpone an unanswered question indefinitely. Give the decision an evidence-based rationale and identify the person responsible for carrying it into the contract and operational configuration.
FINRA Regulatory Notice 21-29 discusses ongoing oversight for member firms using vendors. It does not prescribe one renewal score or a universal pass rate. A relevant firm's reviewers should assess its actual obligations; other buyers can still use a documented review as procurement discipline. In the fictional scorecard, 90% is an observed metric, not a legal threshold or a verdict about every use.
- Do not invent a universal regulatory pass mark for renewal.
Record the next review triggers
The renewal record should name the effective scope, new term, funded amount, outstanding conditions and monitoring owner. Set event-driven review triggers for material changes or repeated failures instead of relying only on the next annual date. Link the prior decision so a later reviewer can see why an exception was accepted and whether the promised improvement actually occurred.
If the fictional buyer renews despite the delivery shortfall, the rationale should identify the permitted workflow and the agreed corrective evidence, not merely say the supplier is familiar. If it exits, preserve the evidence that informed that choice without turning a single example into a claim about a real provider. All prices, counts and procurement outcomes in this guide are hypothetical illustrations.
- State which events reopen review before the next scheduled renewal.
Evaluation checkpoints
- Renewal should use current evidence and actual consumption.
- A later correction does not erase an earlier missed cutoff.
- Unresolved conditions need a decision, not silent rollover.
Source notes
Related questions
Specify service levels that match the decision window
Separate endpoint availability, publication timeliness, support response and recovery commitments when negotiating model delivery.
Price renewal and exit on the same horizon
Compare a renewal offer with replacement, overlap, migration and archive costs without allowing sunk spending to determine the decision.
Plan an exit that preserves usable, permitted records
Define export scope, transfer verification, continuing permissions and access closure before terminating a model licence.
First edition, 16 October 2026. Illustrative procurement situations are not actual client engagements or legal advice.