How to Document a Home Network Setup: A Practical Step-by-Step Guide

Documenting a home network setup gives you a reliable reference when something stops working, you replace a router, add a device, or need to explain your configuration to someone else. The goal is not to record every technical detail—it is to create an accurate, secure snapshot that another person could understand.

Decide What Your Documentation Must Cover

Start by defining the purpose of the document. A small apartment network may only need a one-page diagram and a device list. A larger home with cameras, smart-home equipment, work computers, a NAS, or multiple access points needs more detail.

At minimum, document these areas:

• Internet service information and the location of the modem or gateway
• Router, firewall, switch, and access-point details
• Network names, IP ranges, and important configuration choices
• Wired and wireless devices connected to the network
• Physical cable paths and equipment locations
• Administrative access and backup procedures
• Troubleshooting steps and dates of major changes

Separate facts from sensitive secrets. Your documentation should identify where passwords are stored without necessarily printing those passwords in the main file. A secure password manager is usually better than a text document, spreadsheet, or printed sheet kept near the router.

Before you begin, choose a format you will actually maintain. A Markdown file, shared document, spreadsheet, note-taking application, or diagramming tool can all work. A simple folder containing a network diagram, inventory spreadsheet, router backup, and change log is often more useful than an elaborate documentation system that becomes outdated.

Build a Physical Network Map

Walk through the house and record where each important component is located. Begin at the service entrance and follow the connection inward:

1. Identify where the internet connection enters the property.
2. Record the modem, optical network terminal, or ISP gateway location.
3. Find the main router or firewall.
4. Trace Ethernet cables to switches, access points, televisions, computers, cameras, and other equipment.
5. Note wireless access-point locations and the areas they are intended to cover.
6. Mark wall jacks and, if possible, the patch-panel ports that connect to them.

Create a simple physical diagram using labels such as “office,” “hallway,” and “living room.” You do not need architectural precision. The important information is which equipment is in each location and which cables connect the devices.

For every cable, record both ends when practical. For example, write “Switch port 8 to office wall jack” rather than “office cable.” Use labels on both ends of long or similar-looking cables. A small label printer is helpful, but removable cable tags or numbered stickers also work.

If equipment is mounted in a cabinet, photograph the front and rear connections. Make sure the images are clear enough to identify port numbers. Store the photos with the documentation and add dates, because wiring often changes during upgrades.

Draw a Logical Network Diagram

A physical map shows location; a logical diagram shows how traffic moves. Begin with the internet and work toward individual devices:

Internet service
      |
ISP modem or gateway
      |
Main router/firewall
   |       |        |
Switch  Wi-Fi AP  Guest Wi-Fi
   |
Wired devices, NAS, printer, cameras

Expand this diagram if your network uses multiple VLANs, separate subnets, mesh nodes, a managed switch, or a second router. Label each network with its purpose and address range. For example:

• Main LAN: 192.168.1.0/24
• Guest network: 192.168.20.0/24
• IoT network: 192.168.30.0/24
• Management network: 192.168.99.0/24

Only include networks that actually exist. Do not copy address ranges from an example without verifying your own configuration.

Use arrows or short notes to show important restrictions. You might record that guest Wi-Fi can reach the internet but not the home printer, or that cameras can communicate with a recording server but not with ordinary computers. These rules are often more useful during troubleshooting than a list of device names.

A diagramming application is convenient, but a clean hand-drawn diagram scanned as an image is acceptable. Keep a source version that can be edited later. Export a PDF or image for quick reference.

Record Router and Wireless Settings Safely

The router is usually the central source of network information. Open its administration interface and record configuration details without exposing secrets unnecessarily.

Record the following:

• Manufacturer, model, hardware revision, and serial number
• Firmware version and the date it was last checked
• Router management address
• LAN address and subnet mask
• DHCP address pool and lease duration
• DNS settings
• Internet connection type, such as DHCP, PPPoE, or static addressing
• Port-forwarding rules, if any
• Firewall or inbound access rules
• VPN settings or remote-access configuration
• Time zone and automatic time synchronization settings
• Wireless network names and security modes
• Separate guest, IoT, or work network settings

Do not place Wi-Fi passwords, administrator passwords, recovery codes, VPN private keys, or ISP credentials in an unprotected document. Instead, write a reference such as “stored in the household password manager under Router Administration.” If you must keep an emergency paper copy, store it in a locked location and mark the date it was created.

Record the wireless security mode, not just the network name. WPA3-Personal is a strong choice where all important devices support it. WPA2-Personal may be needed for older equipment. Avoid documenting or continuing to use obsolete, open, or weak security modes unless you understand the risk and have a specific compatibility reason.

If your router supports configuration export, create a backup after documenting the settings. Store it in an encrypted location and label it with the device model and backup date. Check whether the export contains passwords or private keys before placing it in cloud storage.

Create a Device Inventory

A device inventory turns a confusing list of connected clients into something you can recognize. Review the router’s DHCP lease list, wireless client list, switch status, and access-point clients. Then match technical identifiers to real equipment.

Use columns such as:

Device or role	Location	Connection	Identifier	Address method	Notes
Work laptop	Office	Wi-Fi	Hostname or MAC address	DHCP reservation	VPN used for work
Network storage	Office cabinet	Ethernet	Hostname or MAC address	Static or reservation	Backups stored here
Smart thermostat	Hallway	IoT Wi-Fi	Hostname or MAC address	DHCP	Vendor cloud required
Printer	Office	Ethernet	Hostname or MAC address	DHCP reservation	Shared by main LAN

Useful fields include device type, manufacturer, model, operating system, hostname, MAC address, IPv4 address, IPv6 status, switch port, access point, owner, and replacement date. Avoid treating a MAC address as permanent identification: some phones and computers use randomized wireless addresses, and hardware replacements change the address.

For devices that use DHCP, record whether the address is ordinary dynamic DHCP or a reservation tied to the device. A reservation is usually easier to manage than manually configured static addresses because the device remains set to automatic addressing while the router consistently assigns the same address.

Do not assume an unknown client is malicious immediately. It may be a television, streaming stick, printer, game console, camera, or a device with an unhelpful hostname. Temporarily disconnect suspected equipment one at a time and observe which client disappears. Rename recognizable devices in the router interface if that feature is available.

Document Addressing and Name Resolution

Write down the address plan in plain language. Include the router address, subnet size, DHCP pool, reserved addresses, and any static addresses configured on devices.

For example:

• Router: 192.168.1.1
• Subnet: 192.168.1.0/24
• DHCP pool: 192.168.1.100–192.168.1.220
• Reserved infrastructure addresses: 192.168.1.2–192.168.1.20
• Reserved servers and printers: 192.168.1.30–192.168.1.60

If you use IPv6, record whether the ISP delegates a prefix automatically, whether devices receive public addresses, and whether firewall rules are enabled. IPv6 details can change when the provider changes the delegated prefix, so include a note explaining what is stable and what is expected to change.

Also document how devices find one another. Some networks rely on local DNS names, router hostnames, multicast discovery, or manually configured addresses. Record important names such as nas.home, printer names, camera recorder names, and administration URLs. If a service works only by IP address, note that limitation and consider correcting it later.

Add Security and Access Procedures

Documentation should explain how the network is protected and how an authorized person can recover access.

Record whether you use:

• A unique router administrator account and strong password
• Multi-factor authentication for cloud-managed equipment
• Separate guest and IoT networks
• Automatic firmware updates or a manual update schedule
• Disabled remote administration from the internet
• A VPN for remote access
• Regular configuration backups
• Alerts for new devices or failed login attempts
• A defined process for removing old equipment

Describe who is allowed to make changes. For a family network, identify the primary administrator and a backup person. For a home office, separate personal equipment from work-managed equipment and avoid storing employer credentials in household documentation.

Keep a short emergency procedure nearby or in the document. It might say: confirm the modem has service, check router power, verify cables, test the router address, restart equipment in the correct order, and contact the ISP only after local checks. Do not publish remote-management addresses, public IP addresses, or sensitive credentials in a document shared broadly.

Maintain a Change Log and Backups

A network document becomes trustworthy when it records change history. Add a table with the date, change, reason, affected equipment, and rollback information.

Example entries include:

• Replaced the ISP gateway and changed the router’s WAN connection type
• Added a reservation for a new printer
• Moved cameras to the IoT network
• Updated access-point firmware
• Removed an old port-forwarding rule
• Replaced a failed switch and moved cables to different ports

After a major change, update the logical diagram, physical notes, device inventory, and router backup together. Add a “last verified” date to every major section. This makes it obvious which information may be stale.

Keep at least two copies of the documentation. One can be stored digitally, and another can be available offline in case the network or internet connection is unavailable. Protect both copies. An offline copy should not include unprotected passwords merely for convenience.

Review the document every three to six months and after any major upgrade. Compare the inventory with the router’s current client list, remove retired devices, confirm important addresses, and test whether backups can actually be opened.

Troubleshoot Using the Documentation

When a device cannot connect, use the record to narrow the problem instead of resetting everything immediately.

First, identify whether the failure affects one device, one network, one room, or the entire house. Check the physical diagram for a shared cable, switch, access point, or power source. For one device, verify its expected connection type, network name, address method, and reserved address.

If a wired device has no link, inspect both cable ends and the documented switch port. Try a known-good cable and check whether the switch reports link activity. If an access point is offline, check its power source, Ethernet uplink, and documented management address.

If a device has an IP address but cannot reach the internet, test the router address first. Reaching the router but not external sites may indicate an ISP, DNS, or firewall issue. If the device cannot reach the router, investigate Wi-Fi association, VLAN assignment, DHCP, cable wiring, or a local firewall.

If a service works by IP address but not by name, investigate DNS or local discovery. If guest devices can reach private devices, compare the documented firewall and network-isolation rules with the current configuration.

Avoid factory-resetting the router until you have confirmed that configuration backups are available. A reset can remove reservations, port rules, wireless settings, VLANs, and ISP credentials, making an otherwise simple fault harder to recover from.

Common Limitations and Documentation Mistakes

A home network record cannot compensate for inaccurate information. Dynamic public IP addresses, randomized MAC addresses, changing IPv6 prefixes, cloud-dependent devices, and automatic firmware updates can make parts of the document change over time.

Common mistakes include:

• Recording passwords in plain text
• Listing device names without locations or identifiers
• Drawing only the physical layout and omitting network separation
• Forgetting the ISP gateway or modem mode
• Failing to document switch ports and cable labels
• Keeping an old diagram after changing the router
• Treating DHCP addresses as permanent without reservations
• Ignoring devices that connect only occasionally
• Saving a router backup without protecting it
• Creating documentation that only one technically skilled person understands

Write for the person who may need the information during an outage. Use plain labels, define abbreviations, include dates, and explain unusual choices. A short, accurate record that is updated regularly is more valuable than a detailed document that no longer matches the network.