01
Subnet overlap
Do the office, stores and home networks share private ranges (usually 192.168.1.0/24)? Re-plan before launch day, not during it.
02
DNS plan
Will systems be reached by name or by IP? Decide before training staff; changing it later is a company-wide announcement.
03
Who approves devices
Name the approver and the person responsible for disabling departing staff. Without an owner, the account list only grows.
04
Offboarding runbook
Disable the account, revoke the device, check for shared credentials. Put it in the offboarding process, not in someone's memory.
05
Relay bandwidth
When hole punching fails, all traffic relays. Size the relay for worst-case concurrent users × per-user bandwidth, not for the average.
06
Log retention
Depends on what you must answer: internal audit, regulatory requirement, or just who changed a rule. Retention drives which tier you buy.
07
Backup and restore
Control-plane config, keys and device inventory must be recoverable. Scheduled exports stored separately is the cheapest insurance.
08
Upgrade window
Fix a maintenance window and announce it. Remote access is production dependency by then; it cannot be restarted at will.
09
Cross-platform check
Can Windows, Mac and phones all connect, and what happens when someone replaces a device? Mobile is usually the last thing tested.
10
Least-privilege baseline
Deny by default, open only the subnets and ports required. "Allow everything" to save time is handing over the internal network.
11
Rollback plan
If the experience is unacceptable, how do you go back? Keeping the old path running in parallel for a while is the cheapest option.
12
One measurable acceptance criterion
For example: "a travelling colleague opens the ERP and exports an invoice within one minute." Without one, you cannot say whether the rollout worked.