Are you need IT Support Engineer? Free Consultant

PoE Budget Planning for Commercial Networks

  • By Rebecca Smith
  • November 16, 2026
  • 13 Views

A PoE budget is the total wattage a switch can deliver across all its ports at once, and planning it means adding up what every connected device may draw, then choosing a switch whose budget exceeds that total with room to spare. The port count on the datasheet does not tell you this. A 24-port switch can have 24 PoE ports and still only power a fraction of them at full load. For schools, warehouses, hotels, workspaces and residential developments, getting this sum right before purchase avoids access points that reboot, cameras that drop out and expensive switch swaps after installation.

Re-solution
Plan a More Reliable Network
Re-Solution provides Cisco network solutions, infrastructure audits and network surveys for organisations planning commercial networks.

Visit

TL;DR

  • The PoE budget is a shared pool of watts per switch, not a per-port promise. Plan against the pool.
  • Sum the maximum power each device can request (its class wattage at the switch), not its typical draw.
  • Add headroom, commonly 15 to 25%, for cable loss, temperature and devices you will add later.
  • Check cabling and bundling for higher-power PoE, because heat builds up in dense cable runs.
  • Document what every port powers, so the next change is a calculation rather than a guess.

Table of Contents

What a PoE budget is and why it matters

Power over Ethernet (PoE) sends electrical power to a device over the same network cable that carries its data. The switch is the power sourcing equipment (PSE), and the access point, camera, phone or sensor is the powered device (PD). Inside the switch sits a power supply with a fixed capacity, and that capacity, after the switch’s own consumption, is the PoE budget.

When the connected devices ask for more than the budget, something has to give. NETGEAR’s PoE documentation describes one common behaviour: power is prioritised by port number, and the highest-numbered active PoE port is shut off first. The symptoms on site are rarely labelled as power problems. An industrial networking article notes that devices without enough power may fail to boot or cycle on and off intermittently. In a school that means a classroom with no Wi-Fi at the start of a lesson. In a warehouse it means a camera covering a loading bay going dark.

Know what each device can draw

PoE standards group devices into classes, and each class has a maximum power at the switch port and a lower figure available at the device once cable losses are taken off. The IEEE 802.3 tutorial on practical PoE lists the higher classes introduced by 802.3bt. Crestron’s PoE budgeting guide lists the lower ones.

Class Typical standard Power at the switch port (PSE) Power at the device (PD)
1 802.3af 4.0 W 3.84 W
2 802.3af 7.0 W 6.94 W
3 802.3af (PoE) 15.4 W 12.95 W
4 802.3at (PoE+) 30 W 25.5 W
5 802.3bt 45 W 40 W
6 802.3bt 60 W 51 W
7 802.3bt 75 W 62 W
8 802.3bt 90 W 71.3 W

The column that matters for budgeting is the switch-side figure. The device’s datasheet may quote the lower number it actually receives, but the switch has to supply the higher one.

Why class wattage, not typical draw

Crestron’s documentation states that PoE switches reserve the maximum for each class regardless of what the device is actually using. It also explains that, without optional LLDP power negotiation on a 802.3at switch, the full 30 W is reserved for every Class 4 device. A camera that averages 8 W but negotiates as Class 4 still takes 30 W out of the pool.

This is the fixed-class problem that IEEE contributors have discussed. A Philips Research presentation to the 802.3bt group points out that a 15 W device in a 30 W class can leave the budget up to 50% over-allocated, and proposed Autoclass so the device can report its real maximum and cut the mismatch to 2 to 4%. If your switches and devices support that kind of negotiation, your effective budget goes further. Plan on the conservative figure first, and treat any saving as bonus capacity.

How to calculate a PoE budget, step by step

  1. List every powered device by type and location. Access points, IP cameras, VoIP phones, door controllers, PoE lighting drivers, displays and IoT sensors all count. Group them by the switch they will connect to, which usually means by cabinet or floor.
  2. Find each device’s class and maximum power. Use the manufacturer’s datasheet and note the maximum, not the average. Where a datasheet quotes the device-side figure, move up to the matching switch-side class from the table above.
  3. Add up the switch-side wattage per switch. Multiply the quantity of each device type by its class wattage and total them.
  4. Add headroom. Cable losses, hot cabinets and future devices all eat into the pool. A margin of around 15 to 25% on top of the total is a common planning allowance. Use the upper end where cabinets run warm or growth is likely.
  5. Compare the result with the switch’s published PoE budget. Use the whole-switch figure from the datasheet, not the per-port maximum.
  6. Check the port mix. Confirm the switch can supply the class you need on the number of ports you need. Some switches offer higher classes on a subset of ports.
  7. Record the outcome. Keep a simple table for each switch: port, device, class, watts. It turns later changes into a minute’s arithmetic.

Worked example: a school wing

A school wing needs 20 Wi-Fi access points, each negotiating Class 4 (30 W), plus 8 IP phones at Class 2 (7 W) and 6 cameras at Class 3 (15.4 W). Spread across two switches, the totals are:

  • Access points: 20 × 30 W = 600 W
  • Phones: 8 × 7 W = 56 W
  • Cameras: 6 × 15.4 W = 92.4 W
  • Total: 748.4 W

Add 20% headroom and the plan needs about 898 W of PoE budget across the wing. A switch with a published budget of 740 W would be short on its own for this mix, but two switches, each carrying half the load, would sit comfortably inside their pools. The arithmetic also shows how quickly a handful of high-draw devices dominate the total.

Worked example: working back from the switch

Sometimes the switch is fixed and the question is how many devices it can serve. Biamp’s switch specification guide shows the method: divide the total PoE budget by the maximum power per device. Its example is a 380 W 24-port switch, which can power a maximum of 12 Class 4 (30 W) devices, even though it has 24 ports. Half of the ports can never be used for that device type at the same time.

Capacity example for a 380 watt PoE switch

Choose between PoE, PoE+ and PoE++

The class of your devices decides which standard you need, and the standard affects switch cost and cabling.

  • PoE (802.3af, up to 15.4 W per port): suits phones, simple cameras and some sensors.
  • PoE+ (802.3at, up to 30 W): the usual choice for current Wi-Fi access points and PTZ cameras.
  • PoE++ (802.3bt, up to 60 W or 90 W): for multi-radio access points, video displays, PoE lighting and building controls.

Buy to the highest class you realistically expect on that switch in its working life. A switch that is adequate for today’s access points can become the constraint when the next generation arrives with a higher draw. Our guide to network capacity planning covers how to forecast that growth alongside bandwidth, and how a network switch works explains the switch internals behind the budget.

Sector examples

  • Education: dense access-point deployments in classrooms and halls, plus cameras and door entry. The access points are the largest share of the budget, so switch sizing follows the Wi-Fi design. Our page on DfE switching standards with Cisco Meraki sets out the switching expectations for schools.
  • Manufacturing and logistics: cameras, scanners and access points at the edge of large sites, often in warm or dusty cabinets. Headroom matters more here, and so does a cabinet’s temperature. See our guide to warehouse wireless.
  • Hospitality and shared workspaces: many rooms or desks, each with an access point, phone or sensor. Per-floor budgets and clear port documentation keep moves and changes simple.
  • Property developers and housing associations: PoE-driven lighting, door entry and smart building devices push loads up fast. Our page on PoE lighting networks covers a standards-led approach.

Cabling, heat and expansion

The budget is only one limit. Higher power also puts demands on the copper. A UK white paper on PoE reports that the temperature inside a bundle of PoE cables can rise by 40°C in some circumstances, and that repeated heating and cooling cycles may cause premature failures. It also notes that at the 75 W minimum delivery of 802.3bt, up to 25 W could be lost as heat in each circuit.

In practice, this leads to a few checks before you commit to a design:

  • Confirm the cable category and rating suit the PoE class you will run on it.
  • Avoid packing large numbers of high-power cables into tight bundles or hot containment.
  • Keep to the maximum channel length, since longer runs lose more power.
  • Leave spare switch ports and spare budget for the devices you know are coming, such as extra access points or lighting zones.

These checks are easier before the cabling is installed than after. If a building’s infrastructure is being renewed, our guide on how to upgrade building network infrastructure covers what to review first.

Common PoE planning mistakes

  • Counting ports instead of watts. A port count says nothing about the pool.
  • Using average draw. The switch reserves by class, so the maximum is what counts unless negotiation is in place.
  • Skipping headroom. A design that fits exactly on day one fails when one device is added.
  • Forgetting future classes. Replacing access points with a more power-hungry model can push a switch over its budget.
  • Leaving the budget undocumented. Without a per-port record, an engineer plugging in a new camera is guessing.
  • Ignoring the order of power priority. If a switch sheds power by port number, put critical devices on the lowest-numbered ports.

Perspective

PoE budgets rarely fail because someone cannot add. They fail because the budget was calculated once, at design stage, and never revisited. Access points get replaced, cameras get added, and a switch that was comfortable in year one is quietly overloaded in year three.

Our view, after more than 35 years working with Cisco networks, is that the budget belongs in the network documentation as a living figure, alongside the port map and the capacity plan. For sites with many switches, such as a school estate, a distribution centre or a residential portfolio, that is a good fit for a managed service, where the budget is checked against the real device mix as it changes.

Planning also pays off at the design stage. A wireless survey tells you how many access points the building needs, and that number sets the PoE budget. Doing the survey first avoids buying switches on an estimate.

Jacob

How Re-Solution helps with PoE planning

We design Cisco-based networks for education, manufacturing, logistics, hospitality, shared workspaces and property developers, and PoE sizing is part of that work. A wireless survey establishes the number and placement of access points, and a network audit shows what your existing switches are already carrying. Our managed services keep the estate monitored once it is running, and our professional services team can scope a switching refresh from the budget upward.

Re-solution

To discuss a site, start from the Re-Solution website.

FAQ

What is a PoE budget?

It is the total number of watts a switch can supply to all of its connected powered devices at the same time. It is set by the switch’s power supply, not by the number of PoE ports. If devices ask for more than the budget, the switch may shut down power to some ports.

How do I calculate a PoE power budget?

List every device, take its maximum power at the switch (its class wattage), and add them together. Add a margin of roughly 15 to 25% for cable losses, heat and future devices, then compare the total with the switch’s published PoE budget. Remember that a switch also needs to offer the right class on enough ports.

Is PoE+ enough for access points?

Many current access points work within the 30 W available from PoE+ (802.3at, Class 4), but the right answer depends on the model and on the features you enable. Check the datasheet for the maximum draw, then multiply by the number of access points per switch. Where devices may move to 802.3bt, plan the switch budget for that.

What happens if a switch exceeds its PoE budget?

The switch has to cut power somewhere. Behaviour varies by model, but one documented approach is to disable the highest-numbered active PoE port first. Devices on affected ports lose power or restart repeatedly, which users experience as dropped Wi-Fi, offline cameras or dead phones.

Sources