Engagement details
Use this section to define the visit clearly before the technical checks begin.
Client / Site Name
Contact Person
Audit Date
Technician / Engineer
Site Type / Department
Review Scope
Audit checklist and findings
Mark each line item as OK, Attention, Urgent, or Not Reviewed and record a short finding or action.
| Area | Check | Status / Action Notes |
|---|---|---|
| Internet edge | ISP handoff, router model, WAN uptime, failover readiness | OK / Attention / Urgent / N.R. |
| Switching | Core and access switch inventory, uplinks, spare ports, PoE margin | OK / Attention / Urgent / N.R. |
| Addressing | Subnet design, gateway, DHCP range, reservations, duplicate IP risk | OK / Attention / Urgent / N.R. |
| Wi-Fi | SSID list, AP placement, guest separation, weak-zone complaints | OK / Attention / Urgent / N.R. |
| Critical systems | Servers, NVRs, NAS, printers, biometrics, static-IP assets | OK / Attention / Urgent / N.R. |
| Backup and power | Backup status, restore confidence, UPS runtime, shutdown handling | OK / Attention / Urgent / N.R. |
| Security posture | Admin access control, default credentials, remote access exposure | OK / Attention / Urgent / N.R. |
| Documentation | Rack labels, port maps, passwords handover, diagrams, contacts | OK / Attention / Urgent / N.R. |
Immediate risks and recommended actions
Priority issues to correct first
Recommended follow-up work / quotation notes
Sign-off and handover record
Prepared by
Client acknowledgement
Date
Next review due
Usage notes
- Use short, specific findings instead of broad comments like "check network later."
- Record only confirmed risks, not guesses, and separate urgent items from future improvements.
- This format works especially well when paired with the patch panel and port-labeling sheet.