What should you assess before upgrading business connectivity?

Before upgrading business connectivity, assess the performance of the existing network, the technical design of the proposed service, its resilience, implementation requirements and total cost. A suitable upgrade is not simply the connection with the highest advertised speed; it must provide the right service characteristics, integrate with the current infrastructure and be capable of being introduced without avoidable disruption.

Establish how the current service is performing

Review more than the headline connection speed. Collect evidence about latency, packet loss, jitter, failed connections and performance at different times. These measures are particularly important for voice, video, hosted applications and real-time operational systems, where a connection can appear fast but still deliver a poor experience.

Check whether reported problems originate from the provider circuit, internal switching and wireless infrastructure, firewall capacity, cabling or a particular application. Separating these causes prevents a business from paying for a larger circuit when the actual constraint is elsewhere. Existing monitoring data, fault records and user reports can provide a useful baseline for comparing proposals.

Map the network and its dependencies

Document how connectivity enters each site and identify the equipment, circuits and services that depend on it. The assessment should include:

• the provider hand-off and demarcation point;
• routers, firewalls, switches and wireless controllers connected to the service;
• site-to-site links, private networks and internet-based tunnels;
• public IP addresses, DNS records and externally accessible services;
• traffic between offices, data centres, hosted platforms and remote users; and
• any systems that require fixed addressing, particular ports or low-latency communication.

This map exposes dependencies that may otherwise be missed during installation. It also clarifies which equipment must be replaced, reconfigured or tested when the new service is introduced.

Compare technical characteristics, not just advertised speed

Connectivity proposals should be compared using consistent criteria. Consider whether the service is symmetrical or has different upload and download capacities, whether traffic is contended, how the provider manages routing, and whether the service includes static public addresses. The relevant access technology, installation method and distance to the provider’s network may also affect its suitability.

For businesses with several sites, assess how locations will communicate with one another rather than considering each internet circuit in isolation. A faster internet connection does not automatically improve inter-site traffic, application access or routing between locations. Confirm which routing functions are included and which will remain the business’s responsibility.

Identify single points of failure

Examine the complete path from the business’s equipment to the services it uses. A second circuit may not provide meaningful resilience if both connections share the same entry route, building equipment, carrier infrastructure or power source. Ask whether diverse paths are available and how failover would operate.

Consider the devices that sit between the circuit and the local network. A single firewall, router, power supply or switch can still interrupt connectivity even when the provider supplies a resilient service. Decide which components need standby capacity, how failover will be tested and how normal operation will be restored after an incident.

Check compatibility with security and network policy

The proposed service must work with the organisation’s existing firewall rules, segmentation, address plan and authentication arrangements. Confirm how provider equipment will be managed, where administrative access is held, and how configuration changes will be authorised and recorded.

Review any implications for public-facing systems, encrypted tunnels, filtering, traffic inspection and security monitoring. An upgrade that changes public addresses or routing can require coordinated changes to access rules and external services. These dependencies should be identified before an installation date is agreed.

Assess installation and change risks

Request a written implementation plan covering survey work, equipment delivery, configuration, testing, cutover and rollback. It should identify the person responsible for each task and explain how faults will be separated between the access provider, network equipment supplier and internal team.

Plan how the new service will be tested before the old arrangement is removed. Useful acceptance checks include connectivity from each relevant network segment, access to important applications, operation of site-to-site links, inbound and outbound services, failover behaviour and monitoring alerts. Keep the existing service available until the new connection has passed agreed tests and recovery steps are documented.

Calculate the complete cost

Compare the total cost rather than the monthly circuit charge alone. Include installation, surveys, managed equipment, licences, public IP addresses, configuration, support, migration work and any charges for retaining or terminating the existing service. Clarify ownership of supplied hardware and what happens if the business later changes premises, increases capacity or needs an additional site.

Contract terms should be read alongside the technical proposal. Check the service level definitions, planned maintenance process, fault escalation route, service credits if applicable, renewal arrangements and any limits that could affect use. Ensure the named responsibilities match the organisation’s internal capability.

Define a measurable decision process

Set acceptance criteria before comparing providers. These might cover minimum performance, required features, resilience design, installation conditions, documentation and support responsibilities. Score each proposal against the same criteria and record assumptions, exclusions and unresolved questions.

The final assessment should produce an accurate network diagram, an equipment and addressing schedule, a change plan, test results and an ownership record. S2 Technology Group can help businesses review these areas, plan infrastructure upgrades and manage connectivity as part of a wider IT environment, allowing the proposed service to be judged on operational fit rather than speed alone.