Start at the ISP handoff
- Carrier and circuit identifier
- Service bandwidth
- Modem/ONT location
- Static IP details when applicable
- Support account information
- Backup/failover service
- Demarcation responsibility
Document the network core
- Gateway/firewall model and location
- Core and distribution switches
- Rack and closet locations
- Uplink media and speeds
- UPS/power information
- Controller or management platform
Map buildings and interconnects
For multi-building hotels, document exactly how each building reaches the core. If the connection is wireless point-to-point, record both endpoints, mounting locations, alignment/visibility concerns, and expected link capacity. If fiber is used, record strand count, termination points, and switch ports.
Access point record
- AP model
- Physical location
- Switch and port
- Cable identifier if available
- Controller/site assignment
- Coverage purpose
- Known dead zones or capacity concerns
VLANs and operational segmentation
Record the purpose of important networks without turning the document into a security-sensitive configuration dump. Staff, guest, voice, cameras, locks, management, and vendor devices often have different requirements and troubleshooting paths.
Vendor and responsibility boundaries
Write down where ISP responsibility ends, where the network provider begins, and which systems are managed by other vendors. This is especially useful when a guest complaint, PMS issue, phone failure, or camera problem is initially blamed on Wi-Fi.
Recovery information
- Safe reboot order for critical equipment
- What staff should not unplug
- Backup configuration location
- How to reach the controller if local internet is down
- Vendor escalation path
- Known single points of failure