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.
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
| Name | Kind | Subnet | VLAN | Notes |
|---|---|---|---|---|
| Office LAN | Segment | 192.168.1.0/24 | 10 | - |
| Servers | Segment | 192.168.10.0/24 | 20 | - |
| Guest Wi-Fi | Segment | 192.168.50.0/24 | 50 | Internet 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.
| Device | Type | Hostname | IP address | Role | Owner | Segment |
|---|---|---|---|---|---|---|
| Internet | Internet | - | - | - | - | - |
| ISP modem | Modem | - | - | - | IT | - |
| Edge firewall | Firewall | fw-01.office.example | 192.168.1.1 | Gateway | IT | - |
| Core switch | Switch | sw-core-01 | 192.168.1.2 | - | IT | Office LAN |
| Office Wi-Fi | Access Point | - | 192.168.1.3 | - | IT | Office LAN |
| Reception PC | Workstation | - | 192.168.1.50 | Workstation | - | Office LAN |
| Staff laptops | Laptop | - | - | End User Device | - | Office LAN |
| Finance PC | Workstation | - | 192.168.1.51 | Workstation | - | Office LAN |
| Printer | Printer | - | 192.168.1.20 | - | - | Office LAN |
| Domain controller | Directory / IdP | dc-01.office.example | 192.168.10.10 | Domain Controller | IT | Servers |
| File server | Server | fs-01.office.example | 192.168.10.20 | File Server | IT | Servers |
| NAS | NAS / SAN | - | 192.168.10.30 | - | IT | Servers |
| Offsite backup | Backup | - | - | Backup | IT | Servers |
| Guest AP | Access Point | - | 192.168.50.2 | - | - | Guest Wi-Fi |
| Visitor devices | Phone | - | - | - | - | 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 freeOther templates
- Three-tier web applicationDMZ, web, app and data tiers with addressed hosts, labelled flows and two firewall boundaries.
- Hybrid cloudA head office joined to a cloud VPC by site-to-site VPN, with public and private subnets.
- Zero trust accessUsers reach private apps only through an identity-aware access proxy backed by SSO, device checks and a SIEM.
- Home labRouter, managed switch and three VLANs - home, lab and IoT - for documenting your own setup.