Small office network diagram template

The standard single-site layout for a small or medium business: an ISP modem, an edge firewall, a staff LAN, a separate server VLAN and a guest Wi-Fi network that can only reach the Internet.

Every device has its address, role and owner filled in, so the template works as a starting inventory as well as a diagram. Change the addresses to your own and Schema checks each one against the subnet it sits in.

Use this template freeIn the editor: File → New from template → Small office network
Office LAN192.168.1.0/24 · VLAN 10Servers192.168.10.0/24 · VLAN 20Guest Wi-Fi192.168.50.0/24 · VLAN 50InternetISP modemEdge firewall192.168.1.1Core switch192.168.1.2Office Wi-Fi192.168.1.3Reception PC192.168.1.50Staff laptopsFinance PC192.168.1.51Printer192.168.1.20Domain controller192.168.10.10File server192.168.10.20NAS192.168.10.30Offsite backupGuest AP192.168.50.2Visitor devices
The template as it opens in Schema: 15 devices, 3 zones and segments, 14 connections.

How it's laid out

  • Staff devices are on the Office LAN (VLAN 10). Servers are on their own VLAN (20), so file shares and the domain controller aren't on the same broadcast domain as every laptop.
  • Guest Wi-Fi (VLAN 50) connects to the firewall, not the core switch, which keeps visitors off the internal network.
  • The file server backs up nightly to an offsite target, shown as a one-way data flow.

Networks and segments

NameKindSubnetVLANNotes
Office LANSegment192.168.1.0/2410-
ServersSegment192.168.10.0/2420-
Guest Wi-FiSegment192.168.50.0/2450Internet only - isolated from the LAN

Device inventory

In Schema this table isn't a separate document. It's generated from the diagram, can be edited in place, and exports as CSV.

DeviceTypeHostnameIP addressRoleOwnerSegment
InternetInternet-----
ISP modemModem---IT-
Edge firewallFirewallfw-01.office.example192.168.1.1GatewayIT-
Core switchSwitchsw-core-01192.168.1.2-ITOffice LAN
Office Wi-FiAccess Point-192.168.1.3-ITOffice LAN
Reception PCWorkstation-192.168.1.50Workstation-Office LAN
Staff laptopsLaptop--End User Device-Office LAN
Finance PCWorkstation-192.168.1.51Workstation-Office LAN
PrinterPrinter-192.168.1.20--Office LAN
Domain controllerDirectory / IdPdc-01.office.example192.168.10.10Domain ControllerITServers
File serverServerfs-01.office.example192.168.10.20File ServerITServers
NASNAS / SAN-192.168.10.30-ITServers
Offsite backupBackup--BackupITServers
Guest APAccess Point-192.168.50.2--Guest Wi-Fi
Visitor devicesPhone----Guest Wi-Fi

Rules it checks

The template comes with these rule packs switched on. Schema checks them as you edit and marks anything that breaks a rule on the canvas. Every rule can be edited, turned off or deleted.

Perimeter & segmentation

Internet-facing systems sit behind a firewall, databases aren't exposed directly, and traffic between networks passes a firewall.

  • Internet-connected servers must sit behind a firewall
  • Databases must not connect directly to the Internet
  • Storage must not connect directly to the Internet
  • Servers reaching across a network boundary need a firewall in the path
  • Databases reaching across a network boundary need a firewall in the path
  • Workstations must not connect directly to databases

Documentation completeness

Every server, database and network device has the fields someone on call at 3am will need: an address, an owner, a role.

  • Servers must have an IP address
  • Servers must have an owner
  • Servers must have a role
  • Servers must record their OS
  • Databases must have an IP address
  • Databases must have an owner
  • Firewalls must have an IP address
  • Routers must have an IP address

Start from this template

Open it in Schema, replace the example addresses with yours, and you have a diagram, an inventory and a written report of your network. Free during early access.

Use this template free

Other templates