This section defines the audit’s context and objectives so we can focus the assessment on your most critical pain-points.
Company/Entity Name
Primary driver for this audit
Performance degradation/bottlenecks
Office relocation or expansion
Upgrading to high-density Wi-Fi
Compliance or security mandate
Periodic health-check
Other:
Business-critical applications that rely on the network
Cloud SaaS (e.g. M365, Google Workspace)
VoIP/Unified Communications
Video-conferencing (Zoom, Teams, Webex)
ERP/CRM systems
Real-time IoT telemetry
Customer-facing portals
Remote-access VPN
Other
Estimated number of on-site users during peak hours
Estimated number of concurrent wireless devices (laptops, phones, IoT)
Do you have an in-house network management team?
Target completion date for remediation
Document the quality and capacity of your copper/fibre plant, as 60-80% of network faults originate here.
Primary cabling standard in use
Cat 5e
Cat 6
Cat 6A
Cat 7 / 7A
Cat 8
Multimode fibre (OM1/OM2/OM3/OM4/OM5)
Single-mode fibre (OS1/OS2)
Mixed media
Has the cabling been certified with a cable analyser (e.g. Fluke DSX) in the past 5 years?
Physical issues observed
Kinks/sharp bends
Exceeding 90-metre permanent link for copper
Unprotected patch leads on floor
Improper fibre bend radius
Water ingress in conduits
Rodent damage
None
Overall cable labelling accuracy
Very Poor
Poor
Acceptable
Good
Excellent
Number of IDFs/intermediate closets
Are IDF rooms dedicated, locked, and environmentally controlled?
Copper/Fibre Port Inventory
Location/Closet | Installed Copper Ports | Used Copper Ports | Installed Fibre Ports | Used Fibre Ports | Utilisation % | |
|---|---|---|---|---|---|---|
Floor-1 IDF | 96 | 88 | 12 | 8 | 88.9 | |
Floor-2 IDF | 96 | 92 | 12 | 12 | 96.3 | |
Capture switch hardware, firmware, and logical topology to expose oversubscription or ageing equipment.
Number of managed switches (Layer-2+ Layer-3)
Switch vendors in the network
Cisco
Juniper
Arista
HPE Aruba
Dell
Extreme
Huawei
Ruijie
MikroTik
TP-Link
Other
Are any switches older than 5 years or EoL/EoS?
Spanning-tree flavour running
802.1D STP
802.1w RSTP
802.1s MSTP
FabricPath/TRILL
Segment-Routing
None (Layer-3 only)
Portfast/Edge-port enabled on access ports?
Is Rapid-PVST+ or MST configured consistently across all switches?
Switch Uplink Utilisation Trend (last 7 days)
Switch/Port | Avg Util % (7 d) | Peak Util % (7 d) | Severity (1 low - 5 critical) | |
|---|---|---|---|---|
Core-SW-01 Te1/1/1 | 38 | 87 | ||
IDF-1-SW Gi0/48 | 62 | 95 | ||
Is PoE budget sufficient for current and future APs/phones?
Evaluate logical addressing, routing protocols, and high-availability mechanisms that underpin performance and uptime.
Is IPv6 deployed in production?
Interior routing protocol
Static
RIPv2
EIGRP
OSPFv2
OSPFv3
IS-IS
BGP
Are point-to-point /30 or /31 subnets used for routed links?
Is VRRP/HSRP or similar first-hop redundancy active?
Number of BGP prefixes received from upstream ISPs
DHCP Scope Utilisation
VLAN/Subnet | Total Leases | Used Leases | Util % | Alert Level (1 ok - 5 critical) | |
|---|---|---|---|---|---|
VLAN-100 Staff | 1022 | 912 | 89.2 | ||
VLAN-120 Guest | 254 | 248 | 97.6 | ||
Capture Wi-Fi design density, channel planning, and security posture to ensure the wireless network meets current and future demands.
Primary Wi-Fi standard
802.11n
802.11ac Wave-1
802.11ac Wave-2
802.11ax (Wi-Fi 6)
802.11be (Wi-Fi 7)
Total access-point count
Are APs mounted in ceiling or desk height?
Is 5 GHz DFS channels enabled?
Band steering configured between 2.4 GHz and 5 GHz?
Is WPA3-Enterprise or SAE enabled?
User feedback in different areas
Meeting rooms | |
Open office | |
Canteen/Breakout | |
Warehouse/Production | |
Outdoor campus |
AP Firmware Compliance
AP Model | Current Firmware | Vendor Recommended | Criticality to upgrade (1 low - 5 high) | |
|---|---|---|---|---|
AP-AX2030 | 8.5.110.0 | 8.6.120.5 | ||
AP-AC2140 | 6.1.835 | 6.1.835 | ||
Identify attack surface, segmentation gaps, and compliance readiness.
Network segmentation techniques in use
Port-based VLANs
VXLAN/EVPN
PVLAN
ACLs only
Micro-segmentation via firewall
None
Is 802.1X/NAC enforced for wired endpoints?
Are unused switch ports administratively shut down?
Is MACsec or similar link-level encryption enabled?
Firewall Rulebase Hygiene
Firewall Context | Total Rules | Unused / Disabled Rules | Shadow / Redundant Rules | Cleanup Priority (1 low - 5 high) | |
|---|---|---|---|---|---|
Internet Edge | 482 | 97 | 43 | ||
Datacentre East-West | 1260 | 312 | 108 | ||
Is a dedicated management network or out-of-band (OOB) available?
Are logs exported to a centralised SIEM/SYSLOG server?
Assess whether traffic prioritisation, capacity planning, and observability tools are fit for purpose.
QoS mechanisms implemented
DSCP marking
802.1p COS
Priority queuing
Weighted queuing
Shaping/policing
None
Is end-to-end QoS trust boundary defined consistently?
Average WAN utilisation during business hours (%)
Is NetFlow/IPFIX or sFlow enabled on WAN routers?
Primary network monitoring tool
SolarWinds
PRTG
Nagios
Zabbix
ManageEngine
ThousandEyes
Home-grown
None
Rate the following observability capabilities
Not Available | Poor | Acceptable | Good | Excellent | |
|---|---|---|---|---|---|
Real-time alerting | |||||
Historical trend analysis | |||||
End-user experience metrics | |||||
Automated remediation | |||||
Predictive analytics |
Application Performance SLAs
Application | Target Latency (ms) | Measured Avg Latency (ms) | Packet Loss Target (%) | Measured Loss (%) | SLA Compliance (1 fail - 5 pass) | |
|---|---|---|---|---|---|---|
SAP ERP | 80 | 45 | 0.1 | 0.02 | ||
VoIP | 120 | 98 | 0.5 | 0.6 | ||
Evaluate readiness for hybrid cloud, SDN, or network function virtualisation.
Is VXLAN/EVPN overlay deployed in DC or campus?
Public cloud workloads in use
Amazon Web Services
Microsoft Azure
Google Cloud
Alibaba Cloud
IBM Cloud
Oracle Cloud
None
Is SD-WAN deployed to any branch sites?
Are virtualised firewalls or routers (NFV) running on-prem?
Is automation/orchestration (Ansible, Terraform, etc.) used for network config?
Cloud On-Ramp Bandwidth
Cloud Provider | On-Ramp Type | Provisioned BW (Mbps) | Peak Util % (last 30 d) | Upgrade Priority (1 low - 5 high) | |
|---|---|---|---|---|---|
AWS | Direct Connect | 1000 | 82 | ||
Azure | ExpressRoute | 500 | 91 | ||
Assess governance maturity and the accuracy of documentation that engineers rely upon during incidents.
Accuracy of Layer-1 to Layer-3 network diagrams
Outdated
Partially Accurate
Mostly Accurate
Accurate
Automatically Updated
Is an up-to-date IP address plan (IPAM) maintained?
Are configuration backups automated and verified weekly?
Is a formal change advisory board (CAB) in place?
Number of P1 (critical) network incidents last 12 months
List the top 3 recurring incidents and suspected root causes:
Asset Lifecycle Status
Device Role | Vendor/Model | Install Date | End of Support Date | Refresh Priority (1 low - 5 high) | |
|---|---|---|---|---|---|
Core Switch | Cisco C9500-24Y4C | 4/15/2019 | 6/30/2026 | ||
Edge Router | Juniper MX204 | 11/1/2018 | 10/31/2024 | ||
Evaluate redundancy, backup links, and recovery objectives to ensure resilience during outages.
Are core switches deployed in a redundant (VSS/Stack/MC-LAG) pair?
WAN diversity strategy
Single carrier, single link
Single carrier, diverse fibre paths
Dual carrier, dual last-mile
Dual carrier, dual CPE, dual everything
Recovery Time Objective (RTO) defined for network services (hours)
Recovery Point Objective (RPO) for configuration backups (hours)
Has the failover scenario been tested in the last 12 months?
Backup Link Utilisation
Link Role | Capacity (Mbps) | Monthly Avg Util % | Configured as Cold/Hot Standby | Confidence Level (1 low - 5 high) | |
|---|---|---|---|---|---|
MPLS Backup | 100 | 3 | Yes | ||
Internet DIA Backup | 1000 | 12 | |||
Understand power efficiency, lifecycle plans, and strategic technology roadmap.
Estimated network power consumption (kWh/month)
Have you adopted Energy Efficient Ethernet (EEE) on switches?
Is Power-over-Ethernet budget optimised (disable unused ports)?
Timeline for Wi-Fi 7 adoption
Already piloting
Within 12 months
1–2 years
2–3 years
No plans
Intent to adopt AI/ML-based network assurance
Already deployed
Evaluating vendors
Budget approved
No immediate interest
Describe any upcoming business initiatives (e.g. IoT rollout, smart-building, edge computing) that will impact the network:
Upload existing high-level network diagram (optional):
I confirm the information provided is accurate to the best of my knowledge.
Auditor/Representative Signature
Analysis for IT Network Infrastructure & Connectivity Audit Form
Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.
This IT Network Infrastructure & Connectivity Audit Form is a comprehensive, multi-layered assessment tool that excels in capturing both physical and logical network characteristics. The form's greatest strength lies in its systematic approach to diagnosing network issues, starting from the physical cabling layer and progressing through data-link, network, wireless, security, and operational governance. The structure effectively addresses the three primary use cases mentioned: performance bottlenecks, office relocations, and high-density wireless upgrades.
The form demonstrates exceptional technical depth while maintaining user-friendly navigation through well-organized sections. Each section begins with contextual paragraphs that explain the importance of that layer, helping users understand why certain information is being collected. This educational approach increases the likelihood of accurate responses and helps users identify issues they might otherwise overlook.
Company/Entity Name serves as the fundamental identifier for audit tracking and reporting purposes. This question establishes the organizational context for all subsequent technical data, enabling proper documentation trail for compliance, billing, and project management. The field's placement at the beginning of the form creates immediate accountability and ensures that all collected data can be properly attributed to the correct entity throughout the audit process.
The open-ended text format with a placeholder example demonstrates excellent UX design by providing format guidance without being restrictive. This approach accommodates various business entity types (LLC, Inc., Ltd., etc.) while maintaining consistency. The mandatory status is appropriate as anonymous audits would compromise the ability to provide actionable recommendations and track remediation progress.
From a data collection perspective, this field enables proper audit trail creation, supports compliance requirements, and facilitates the generation of customized reports. The information collected here will be used throughout the engagement lifecycle, from initial assessment through final recommendations and follow-up activities.
Primary driver for this audit functions as the strategic compass for the entire assessment process. By identifying whether the organization faces performance degradation, planning an office move, upgrading wireless infrastructure, or addressing compliance requirements, this question enables auditors to prioritize their analysis and focus on the most critical areas. The single-choice format with an "Other" option provides structured data while accommodating unique circumstances.
The follow-up mechanism for "Other" responses using a multiline text field demonstrates sophisticated form design that captures additional context without cluttering the primary interface. This approach ensures that auditors receive specific details about unusual drivers while maintaining clean data for statistical analysis. The mandatory nature is crucial as without understanding the primary motivation, the audit cannot be properly scoped or prioritized.
This question directly impacts the audit methodology by determining which sections receive deeper scrutiny. For performance issues, the switching and routing sections become critical; for office moves, the physical layer and wireless sections gain importance; for compliance drivers, security and documentation sections take precedence. This contextual intelligence enables more efficient and targeted audits.
Estimated number of on-site users during peak hours provides essential capacity planning data that directly influences infrastructure recommendations. This numeric input enables auditors to calculate user-to-infrastructure ratios, identify potential oversubscription issues, and recommend appropriate scaling strategies. The peak hours specification ensures that the audit addresses worst-case scenarios rather than average usage patterns.
The numeric field type with an example placeholder helps users provide accurate estimates while preventing text-based responses that would require manual interpretation. This data point becomes particularly critical when evaluating wireless density, switch port utilization, and bandwidth requirements. The mandatory status ensures that capacity analysis can be performed without making potentially incorrect assumptions about user volumes.
From a network design perspective, this information enables calculation of critical metrics such as AP density per user, switch port utilization rates, and bandwidth allocation per user. It also helps identify whether reported performance issues correlate with user density, potentially revealing oversubscription problems that require infrastructure upgrades or architectural changes.
Estimated number of concurrent wireless devices captures the total device ecosystem that extends beyond traditional user counts. In modern environments where each user typically carries 2-3 devices (laptop, phone, tablet) plus IoT devices, this metric provides crucial density calculations for wireless infrastructure assessment. The distinction between users and devices acknowledges the reality of multi-device environments and IoT proliferation.
The numeric format with example guidance helps organizations account for all connected devices, including often-overlooked IoT sensors, smart TVs, wireless presentation systems, and guest devices. This comprehensive count is essential for evaluating whether current wireless infrastructure can handle device density, particularly important for high-density Wi-Fi upgrade scenarios. The mandatory status prevents incomplete assessments that might miss critical density-related performance issues.
This data point enables calculation of device-to-AP ratios, channel utilization analysis, and bandwidth provisioning assessments. It helps identify whether performance issues stem from device oversubscription rather than simple user count problems, leading to more accurate recommendations for wireless upgrades or architectural changes.
Number of managed switches (Layer-2+ Layer-3) provides immediate insight into network complexity and management overhead. This single metric helps auditors understand the scale of infrastructure they are assessing and estimate the effort required for configuration review and optimization. The distinction between managed switches and unmanaged hubs or switches indicates the level of network sophistication and available management features.
The numeric format ensures consistent data collection across organizations of different sizes, from small businesses with a few switches to enterprises with hundreds of distributed switches. This count directly impacts audit timeline estimation, tool selection, and analysis methodology. The mandatory status prevents incomplete assessments that could miss significant portions of the network infrastructure.
This information enables calculation of important ratios such as users-per-switch, APs-per-switch, and switch density per floor or building. It helps identify whether performance issues relate to switch oversubscription or if there are opportunities for switch consolidation or redistribution to improve performance and manageability.
Total access-point count establishes the baseline for wireless infrastructure assessment and enables calculation of critical density metrics. This straightforward count provides immediate insight into the scale of wireless deployment and helps auditors determine whether current AP quantities align with coverage and capacity requirements. The numeric format eliminates ambiguity and enables mathematical analysis of wireless density.
The mandatory nature ensures that wireless assessments can be properly scoped and that recommendations for high-density upgrades are based on actual infrastructure quantities rather than estimates. This count becomes particularly important when evaluating AP-to-user and AP-to-device ratios, helping identify whether wireless issues stem from insufficient AP density or configuration problems.
This data point enables calculation of wireless coverage density, channel planning feasibility, and roaming characteristics. It helps determine whether current AP placement follows best practices for the identified use case (performance troubleshooting vs. high-density upgrade) and whether additional APs are needed to meet service level requirements.
I confirm the information provided is accurate to the best of my knowledge serves as a critical accountability and liability mechanism that protects both the auditing organization and the client. This checkbox requirement creates a formal attestation that the information provided is truthful and complete, establishing legal and professional accountability for the data quality. The mandatory status is essential for maintaining audit integrity and ensuring that recommendations are based on validated information.
The checkbox format provides a clear, unambiguous confirmation that can be legally documented, while the specific wording "to the best of my knowledge" provides reasonable protection for the respondent regarding information they might not have complete visibility into. This approach balances accountability with practical recognition that some network details might be unknown to the person completing the form.
From a compliance and quality assurance perspective, this confirmation enables auditors to proceed with confidence that their analysis and recommendations are based on accurate data. It also creates a feedback loop that encourages careful review of all responses before submission, improving overall data quality and reducing the likelihood of costly errors in audit recommendations.
Mandatory Question Analysis for IT Network Infrastructure & Connectivity Audit Form
Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.
Company/Entity Name
This field is absolutely critical for establishing audit accountability and creating a proper paper trail for all subsequent recommendations. Without a clearly identified entity, the audit cannot be properly documented, tracked, or referenced in future discussions, making it impossible to maintain continuity across the assessment and remediation phases. The mandatory status ensures that all collected data can be properly attributed and that legal and compliance requirements for documentation are met throughout the engagement.
Primary driver for this audit
The audit driver is fundamental to scoping the assessment appropriately and prioritizing analysis efforts based on the specific business need. Without understanding whether the organization faces performance issues, planning a move, or upgrading wireless infrastructure, auditors cannot focus on the most relevant areas or provide targeted recommendations. This mandatory field ensures that the audit delivers actionable insights aligned with the organization's primary concern rather than providing generic observations.
Estimated number of on-site users during peak hours
User count data is essential for capacity analysis and infrastructure sizing recommendations, making it impossible to assess whether performance issues relate to oversubscription without this baseline metric. The mandatory status ensures that auditors can calculate critical ratios such as users-per-switch and users-per-AP, enabling data-driven recommendations rather than assumptions. This information directly impacts the accuracy of all subsequent infrastructure recommendations and cost estimates.
Estimated number of concurrent wireless devices
Device count has become more critical than user count in modern network assessments due to the proliferation of IoT and multi-device environments, making this metric essential for accurate wireless density calculations. The mandatory requirement ensures that auditors can evaluate whether wireless infrastructure meets current density requirements and identify if high-density upgrade needs are driven by device oversubscription. Without this data, wireless recommendations would be based on incomplete information that could lead to continued performance issues post-upgrade.
Number of managed switches (Layer-2+ Layer-3)
Switch count provides the fundamental infrastructure scale metric that determines audit complexity and resource allocation, making it impossible to properly scope the assessment without this baseline information. The mandatory status ensures that auditors understand the management overhead and complexity they will encounter, enabling appropriate tool selection and timeline estimation. This count directly impacts the feasibility of configuration reviews and the identification of potential single points of failure in the switching infrastructure.
Total access-point count
AP count is the foundational metric for all wireless infrastructure assessments, particularly critical for high-density upgrade scenarios where device-to-AP ratios determine success criteria. The mandatory requirement ensures that wireless recommendations are based on actual infrastructure quantities rather than estimates, preventing under or over-provisioning in upgrade plans. Without accurate AP counts, density calculations and coverage analysis would be compromised, potentially leading to continued wireless performance issues.
I confirm the information provided is accurate to the best of my knowledge
This attestation checkbox is mandatory to establish legal accountability and ensure data quality throughout the audit process, protecting both the auditing firm and the client from liability issues. The confirmation creates a formal record that the respondent has reviewed all information for accuracy, reducing the likelihood of costly errors in recommendations based on incorrect data. The mandatory status is essential for maintaining professional standards and ensuring that the audit can be relied upon for compliance and remediation planning purposes.
The current mandatory field strategy demonstrates excellent balance between collecting essential data and minimizing user burden, with only 7 out of 80+ fields requiring completion. This approach ensures critical baseline information is captured while allowing users to provide additional details at their discretion, significantly improving form completion rates compared to more aggressive mandatory strategies. The selected mandatory fields represent the minimum dataset required for meaningful analysis without compromising the depth of insights that can be generated.
Consider implementing conditional mandatory logic for follow-up questions where appropriate, such as making the "Other driver description" mandatory when "Other" is selected for the primary audit driver. Additionally, evaluate whether certain optional fields in critical sections like security and business continuity should become conditionally mandatory based on the primary audit driver—for example, making WAN diversity strategy mandatory when the driver is "Performance degradation" to ensure redundancy issues are captured. This refined approach would maintain the form's user-friendly completion characteristics while ensuring that audit depth aligns with the identified business need.