HLD vs LLD: what a complete network design package should include

Most network projects that overrun do not fail during installation — they fail in the design gaps that installation teams discover on site. A complete design package, split clearly into a High-Level Design (HLD) and a Low-Level Design (LLD), is the cheapest risk control available.

What the High-Level Design answers

The HLD is the architecture. It should let a decision-maker understand what is being built and why, without needing to read a port map.

• Requirements and assumptions — users, sites, applications, growth and availability targets.
• Topology — core, distribution and access layers, or ring and spur structures for fiber.
• Redundancy model — which failures the network survives, and how.
• Technology choices — routing, switching, transport and security approach, kept vendor-neutral where possible.
• Capacity plan — bandwidth, port counts, rack space, power and cooling headroom.

What the Low-Level Design adds

The LLD turns the architecture into instructions a field team can execute without guessing.

• Rack elevations and floor layouts
• Port-to-port connection and cable schedules
• IP addressing, VLAN and routing plans
• Fiber core allocation and splice plans
• Device configuration templates
• Labelling conventions and test criteria

If a technician has to make a design decision on site, the LLD is incomplete.

Bills of quantities and acceptance criteria

Two documents are often forgotten: a bill of quantities that ties directly to the LLD, and acceptance criteria that define what “done” means — for example OTDR loss limits, Wi-Fi coverage thresholds or failover tests. Agreeing these before procurement avoids disputes at handover.

A quick checklist

Need a second opinion on an existing design? Our engineers can review your HLD/LLD and highlight gaps before you go to tender.

Talk to an engineer