Record the site, applications, busy periods, representative devices and constraints.
RECORD · REVIEW · DELIVER
Make every project a delivery that can be reviewed
Agree what will be delivered, then record execution and acceptance. Assign owners, reviewers, dates and evidence so the team can execute, customers can confirm and future maintenance can follow the records.
From discovery to handover
Agree test conditions and pass criteria. Plan APs, channels, power, uplinks and Guest/VLAN access policies.
Confirm work permission, the change window, configuration backups and rollback plan. Install to the design and record changes.
Keep equipment IDs, cable ends, port mapping, photographs and test records consistent. Do not reuse retired IDs.
Test coverage, capacity, roaming, isolation and recovery with real applications and representative clients. Retain results and exceptions.
Retest resolved defects or obtain written customer acceptance. Hand over equipment lists, configuration, tests, access ownership and maintenance arrangements.
Use the same ID at both cable ends
Equipment
HKG01-F02-AP001Permanent cable
HKG01-F02-C001Patch lead
HKG01-F02-PC001HKG01 is the site, F02 the floor, and AP001/C001/PC001 their respective serial IDs. This is an internal naming example and may be adapted for a project.
Record endpoint mapping separately: RK01/PP01/P24 ↔ AP001. Update the mapping when ports change; retain the permanent cable ID.
Print → Apply → Trace → Test → Photograph → Register
Choose label media for the surface and environment. Keep vents, indicators and connector latches clear. Do not put passwords, private keys or public links to sensitive records on labels.
Delivery completion requires real evidence
The workspace checks SOP items, tests, defects, customer confirmation and the handover list. Required records must be present before delivery can be marked complete. Not-applicable items also need a reason and review.
A VLAN alone does not prove isolation
Alongside SSID/VLAN settings, test which resources Guest/IoT clients can reach, which internal resources are blocked and whether clients can communicate with each other. Review firewall and authentication policies together.
Help the next engineer continue the work
Keep project details, SOP records, tests, labels and attachments in the protected workspace. Each save records a version. Print project reports, download project JSON and export label CSV; authenticated administrators can download attachments.
The template is a starting point. Confirm scope, test criteria and customer deliverables before each project. The public template contains no customer data and is not evidence of completed work or certification.