The Handover File: Disconnection Evidence When a UK Office Lease Ends

A lease event is rarely a technology project. It arrives as a property decision, negotiated between surveyors and finance, and only later becomes an operational one. By the time the network team is asked to "switch the office off", notice periods are already running, landlords are preparing schedules of condition, and invoices for circuits that left the building months ago are still arriving at a shared mailbox nobody owns.

The pattern is consistent across UK estates. Organisations consolidate two floors into one, sublet a wing, or exercise a break clause and move to a smaller footprint with more meeting space. The people move in a weekend. The services take considerably longer, and the liabilities attached to them longer still.

What follows is a disconnection discipline rather than a demolition plan: a way of establishing, service by service, what was connected, who held the contract, when notice must be served, and what evidence proves the obligation has ended.

Begin with the lease, not the rack

The property timetable should set the technology timetable, not the reverse. Break dates, reinstatement obligations and dilapidations negotiations all determine how much of the estate you are permitted to remove and how much must be left in situ and made good.

Two questions should be answered before any cease request is raised. First, does the lease require the premises to be handed back with services live, or with containment and cabling stripped to a defined standard? Second, does the landlord intend to remarket the space to a tenant who will want connectivity on day one? In practice, many landlords prefer a working fibre bearer and a labelled comms room to a stripped shell, and may accept a dilapidations offset in exchange. Establishing that preference early converts a cost into a negotiation.

Equally, confirm who controls the building's entry point. In multi-let premises, the lead tenant or managing agent often holds the wayleave for risers and the main distribution frame. Your organisation may own the service without owning the route, and no amount of internal paperwork resolves that.

Build a circuit ledger before serving notice

Every disconnection programme should open with a ledger that reconciles three sources that rarely agree: the finance accounts payable record, the service provider's customer portal, and the physical labels in the comms room.

For each circuit, capture the service reference, the billing entity, the site address as held by the supplier, the technology type, the contract end date, the notice period and the early termination charge basis. Include the legacy services that survive through inertia: analogue lines supporting lift alarms and PDQ terminals, low-bandwidth bearers retained for a single legacy device, and secondary connections installed for resilience that have since been superseded.

Notice periods deserve particular scrutiny. Many business circuits require 90 days' written notice, some longer, and a missed window rolls the contract into a further minimum term. Where a break clause gives eight weeks, the technology notice must be served before the property decision is announced internally, not after.

Number porting belongs in the same ledger. A block of direct dial numbers attached to a site that is closing has to be either ported to a surviving location, parked with a provider that supports number retention, or formally relinquished. Numbers released without a decision are difficult to recover and may sit on published material for years.

Cabling, containment and the demarcation question

Structured cabling is where disconnection cost estimates most often go wrong. Removing Cat 6A horizontal runs, fibre backbones and containment is labour-intensive and rarely recoverable value. Leaving it behind can attract a dilapidations claim.

The workable approach is to survey and document rather than assume. Label the main and intermediate distribution frames, record port counts by cabinet, photograph the containment routes, and note which cabling is landlord-owned, which was installed by a previous tenant, and which your organisation commissioned. Where removal is required, obtain a fixed-price quotation before the schedule of condition is agreed, and where retention is permitted, seek written confirmation that the installation will be accepted as found.

Do not overlook the physical risk in removing active kit from shared spaces. Access to risers and comms rooms in occupied buildings requires coordination with the managing agent, and works in live cupboards carrying other tenants' services need method statements and out-of-hours scheduling.

Wireless, print and the systems that were never IT's

Wireless access points are simple to unbolt and surprisingly easy to leave financially active. Controller subscriptions, cloud management licences and per-device support contracts frequently bill annually regardless of whether the hardware is still in the building. Decommissioning an access point means removing it from the management platform, releasing the licence, updating the site survey record and, where the access layer is shared with a landlord-provided network, confirming which party owns which radio.

Print estates carry similar hidden tails. Managed print agreements often bundle hardware, consumables and software under a single per-page charge with a minimum volume commitment. Ending occupancy does not end the commitment. Establish the minimum billing threshold, return the devices under the terms of the agreement, and recover or securely destroy embedded storage.

Then there are the systems that sat outside the IT function entirely: door controllers and access control head-end servers, intruder alarms, CCTV recorders, lift monitoring, energy sub-meters and building management gateways. Each has a network connection, a support contract and, frequently, a data protection implication when recordings or access logs are removed. For access control, coordinate with the fire strategy before isolating door hardware; for building IoT, confirm whether the landlord's BMS depends on your connectivity.

A contract-by-contract evidence model

Proving disconnection is a documentary exercise. For each service, the file should contain the cease request and its acknowledgement, the supplier's confirmation of service termination with a date, the final invoice showing zero forward charges, and photographic evidence that the associated equipment has been removed or formally transferred.

Maintain a single register that records, per line item, the responsible owner, the current status and the evidence reference. Status values should be unambiguous: notice served, ceased, final billed, closed. Anything less invites a service to be marked complete when only the request has been sent.

Where equipment is transferred to a landlord or incoming tenant, record the transfer in writing with asset identifiers. Where it is disposed of, retain waste transfer notes for electronic equipment and certificates of data sanitisation for anything that stored credentials, recordings or personal data.

The handover pack

The final deliverable is a handover pack, issued to the property team and retained by IT. It should include the disconnection register, the site asset schedule, the cabling survey, copies of all cessation confirmations, the dilapidations position for technology items, and a short note listing any service that remains live and why.

That last item matters most. Legitimate reasons exist for retaining a circuit after occupation ends, such as a lease obligation to maintain connectivity, a retained comms room serving another site, or a migration window that overlaps the handover. Naming them explicitly prevents an exception from quietly becoming a permanent line on the telecoms bill.

The test of a good exit is not whether the move went smoothly. It is whether, six months later, someone can prove that nothing remains connected, nothing remains invoiced, and nothing was left behind that the organisation did not agree to leave.