Before renewing an IT supplier’s contract, compare its service reports with the incidents your team actually handled. A report showing targets were met can sit beside a record of long waits, repeated transfers and disrupted work.
Contracts with suppliers define the service, responsibilities and commercial terms. The renewal review should establish whether those commitments still fit the business, whether delivery matches them and what changing providers would involve.
Confirm the deadline and applicable documents
Assign a review owner who can bring together service, procurement and contractual questions. Gather the signed agreement, relevant service schedules and amendments, then identify which documents apply to the current service.
Renewal decisions are part of IT supplier management: they connect contractual commitments with evidence of the service your organization receives. Keep the renewal proposal alongside the existing documents so changes in price or scope are visible.
Record the contract end date separately from any deadline for giving notice. Check how notice must be delivered and who is authorized to send it. Work backward to allow time for approvals, negotiation and, if necessary, selecting and transitioning to another provider. Have ambiguous notice or termination wording reviewed before acting.
Set a decision date early enough to preserve those options.
Compare reported performance with service records
Compare supplier reports and internal incident records using matching periods, support hours, service definitions and exclusions. Identify what each measure covers: acknowledgment, an initial response, restoration of usable service or final resolution.
Imagine a support provider whose dashboard shows it met its acknowledgment target. The incident record, however, shows the ticket passing between teams while employees remained unable to work.
Trace a significant incident from initial report to restored service. Note when the supplier accepted responsibility, requested information, transferred the ticket and completed its work. Include delays caused by your own teams so the timeline reflects everyone’s contribution.
Then separate missed commitments from unsuitable ones. Failure to meet an agreed target calls for corrective action. A target that is consistently met but leaves the business poorly served calls for renegotiation. Assess any suspected breach against the specific obligation, rather than the frustration the incident caused.
Check who owns cross-provider incidents
When several suppliers support one service, examine the connections between their obligations. An application provider, hosting company and network provider might each handle its own component while coordination of the full incident remains unassigned.
Use the timeline to locate the handoff where progress stopped. Was a team waiting for diagnostic information? Who could convene the providers? Who was responsible for keeping your service owner informed?
Turn the finding into a specific action. Instead of “improve communication,” identify the party responsible for coordinating cross-provider incidents and agree escalation triggers. Check the organization’s own obligations too, including approvals and access needed for troubleshooting.
Establish a workable exit
Review the agreement’s provisions for data return, documentation, transition assistance, continued access and potential charges. Determine which assistance is included and which would require a separate agreement.
Ask what information a replacement provider would need, how long access to the outgoing service would remain available and which other services depend on it. An export option addresses only part of the handoff; documentation, support and timing also need attention.
Estimate transition effort and lead time before treating replacement as the preferred option. Detailed migration planning can follow if replacement is pursued.
Record the decision and required actions
Create a short decision record linking each material commitment to supporting evidence, the observed gap and the required action. Label disputed findings as unresolved and assign someone to reconcile the evidence.
Renewal is supported when the commitments and delivery remain suitable. Renegotiation makes sense when scope, targets, responsibilities or commercial terms need adjustment. Unresolved material problems justify assessing replacement, taking transition costs and dependencies into account.
Where improvement is promised, specify what will change, who owns it and how completion will be checked. A general assurance leaves the original finding open.
Confirm who will approve the decision and give outstanding actions owners and completion dates. The approval schedule should leave time to carry out the chosen course before the applicable notice deadline.
