What to ask for in a small-business network handover

Handover is part of the installation

A network project is not finished merely because devices connect today. The business should receive enough information and access for a competent replacement technician to operate and recover the system. Make that a written deliverable before work starts. It protects continuity if a supplier becomes unavailable and reduces the cost of later troubleshooting.

Ask for business ownership of domains, provider accounts and equipment management wherever appropriate. A supplier can be delegated access without being the only person capable of recovery. Do not demand shared passwords by email; agree a secure transfer method and maintain individual administrative accounts where the system supports them.

Request a useful diagram and inventory

The diagram should show the internet handoff, router, switches, access points, major connected systems and links between them. Mark different network segments and any allowed exceptions. It need not be an elaborate engineering drawing, but another technician should be able to identify what is connected to what and why.

The inventory should include model, serial number, location, role, purchase date where known, support status and relevant subscriptions. Label cables and ports consistently with the diagram. An unlabelled bundle of cables can turn a small fault into a lengthy tracing exercise. Keep the record current when equipment is moved rather than treating the handover as a permanent historical snapshot.

Separate access details from public documentation

Keep a general diagram accessible to the people who coordinate support. Store administrator credentials, recovery codes and configuration exports in a suitably protected business-controlled location. Restrict access to those who need it, and ensure a second authorised person can recover access if the primary administrator is absent.

Australian cyber guidance supports protecting business accounts and using stronger authentication. Ask which management services support MFA and how it has been configured. Record account ownership and recovery method rather than copying secret codes into a general asset spreadsheet. A handover document should help recovery without creating a convenient map and password list for an unauthorised person.

Record configuration and support boundaries

Request current configuration backups in the vendor's supported format, with an explanation of how to restore them. Confirm that restoring is compatible with the relevant firmware and hardware; an export alone does not prove recoverability. Keep a record of important settings such as network ranges, VLAN purposes and remote-access methods without exposing unnecessary secrets.

List who supports internet service, internal networking, security cameras, phones and cloud applications. State support hours, escalation contacts, response arrangements and any recurring fees. If the network is cloud-managed, ask what works without a subscription or internet access. Do not assume that the business owns a management account simply because it owns the physical access points.

Agree acceptance tests

Use real business activities: wired internet, Wi-Fi in nominated areas, calls, printing, guest isolation and camera connectivity where included. Test failure and restart behaviour if resilience was part of the quote. Record results, outstanding defects and who will fix them. Avoid signing final acceptance with a vague promise that documentation will arrive later.

For illustration, spending an extra two hours on labelling and a concise handover may prevent a replacement supplier spending a day rediscovering the layout. That is a plausible benefit, not a guaranteed saving. Compare the agreed documentation cost with the actual complexity and importance of your network. A five-person office and a multi-building site need different levels of detail.

Keep a practical decision record

Use a final handover receipt listing the documents, configuration copies, account ownership and outstanding work. Have the business owner confirm access through the agreed secure process, rather than accepting a supplier's statement that it will be available on request. Ask a different authorised person to locate the support details and identify the main equipment from the diagram. That simple check can reveal unclear labels and missing recovery information. Keep the receipt with the project record so future supplier changes begin from evidence of what was delivered.

Changing suppliers safely

Plan access changes with both parties where possible. Confirm that the new supplier can administer required systems before removing the old supplier. Revoke obsolete delegated access, review recovery details and rotate shared secrets where appropriate. Keep a rollback plan for configuration changes and avoid unnecessary simultaneous equipment replacement during the handover.

Use the office setup checklist to track documentation and ownership. Put future changes through a simple process that updates the diagram, inventory and configuration backup. Good handover makes the business easier to support. It does not require the owner to become a network engineer, but it does require the business to retain control of essential information.