What evidence should a connectivity provider supply before contract renewal?

Before contract renewal, a connectivity provider should supply an auditable renewal pack that allows the business to verify what it has bought, how the service has operated, what will change, and what obligations will apply after renewal. The evidence should be specific to the circuits, sites and services covered by the agreement rather than limited to general statements about network quality.

Ask for evidence in an agreed format. A useful pack should identify each service by site, circuit reference, access type, bandwidth, handover point and contract status. It should also show which elements are provided directly by the connectivity provider and which depend on carriers, access networks, hosting facilities or customer-owned equipment. This prevents a renewal decision being based on an unclear description of a multi-provider service.

Request the underlying data where it is relevant, not only a summary written by the provider. For example, management information should state the measurement period, monitoring points, calculation method and exclusions. If a provider reports service levels as an average, ask how individual incidents, short interruptions, packet loss and degraded performance are treated. The business should be able to compare the provider’s figures with its own monitoring and incident records.

Evidence of capacity and technical suitability is also important. A provider should explain current utilisation and any known constraints affecting the service. Depending on the connection, this may include:

• peak and typical bandwidth usage;
• latency, jitter and packet-loss measurements where these affect voice, video or cloud applications;
• traffic-management or contention arrangements;
• the capacity available for expected changes in users, sites, applications or data volumes;
• dependencies on routers, firewalls, wireless equipment or other customer-managed components; and
• the technical design of any diverse or backup connection, including whether it uses genuinely separate routes and equipment.

These details help distinguish a service that is technically appropriate from one that is simply being rolled forward because renewal is administratively convenient. A provider should identify assumptions behind its recommendation, such as expected traffic growth, required application performance or the number of locations connected.

Request a complete commercial comparison. The renewal proposal should show the current recurring charges, any one-off costs, installation or migration charges, equipment rental, support fees, usage-based charges and applicable taxes or pass-through costs. It should make clear whether the proposed price depends on a new minimum term, revised bandwidth, bundled services or the return of supplied equipment.

Ask the provider to mark every change between the existing agreement and the proposed agreement. Important points include the renewal date, notice period, automatic-renewal mechanism, minimum commitment, termination charges, price-review wording, service suspension rights and treatment of services at each site. A clear comparison reduces the risk of accepting a contractual change hidden within a routine renewal quotation.

Evidence about incidents should be traceable to corrective action. Rather than asking only whether faults have been closed, review recurring fault categories, root-cause analyses, post-incident reports and outstanding remedial actions. For repeated problems, the provider should identify whether the cause was access infrastructure, configuration, equipment, power, a third-party dependency or an issue within the customer environment. The evidence should show who owns each action and how completion will be verified.

Where the service level agreement uses credits or other remedies, ask for a record of qualifying events and any remedies applied or declined. Check how exclusions were used, whether incidents were combined into a single event, and whether the agreement measures restoration, service quality or both. This establishes whether the contractual remedy reflects the operational impact of the service.

Review the proposed operating model. The renewal pack should identify the support route, case-handling process, escalation path and information the provider requires when diagnosing a fault. It should also clarify responsibilities for monitoring, equipment management, site access, configuration changes and communication during an incident. A responsibility matrix is useful where more than one supplier or internal team is involved.

Planned-change evidence should include a record of material changes made during the current term, their approval route, implementation results and any associated incidents. For the renewed service, request the change-control process, maintenance notification rules, testing requirements and rollback arrangements. This shows whether the provider can manage future changes in a controlled way rather than treating renewal as a purely commercial event.

Security and resilience evidence should match the service design. Ask for relevant information about access controls, administrative separation, equipment hardening, logging, incident handling and the protection of management interfaces. Where connectivity carries sensitive business traffic, confirm how traffic is separated and where encryption is applied, if applicable. The provider should also explain how it manages service dependencies, equipment failure, site loss and loss of a primary route.

Do not accept a generic resilience statement as proof of continuity. Request the documented design, dependency information, test records and any limitations that could prevent a failover arrangement from working as expected. The evidence should distinguish between a physically separate connection, a separate logical service and a connection that merely uses different customer equipment.

Check governance and exit evidence before signing. The provider should confirm who owns service data, configuration records, IP addressing, domain or routing information and supplied equipment. Ask what information will be returned if the contract ends, in what format, and what assistance is included for migration or decommissioning. Also confirm how long records are retained and how access is removed when the service is terminated.

A practical renewal review should record each evidence item, the document or data source supplied, the person responsible for checking it, any unresolved limitation and the decision taken. Renew only when the evidence supports the required technical performance, operational responsibilities, commercial terms, security controls and exit arrangements. If information is missing, make its provision a written precondition of renewal or record the risk and an agreed action in the contract.