Network planning for SMEs: what to clarify first

Anyone planning or expanding a network should settle five things before placing the first order: how many ports each room actually needs, whether and how the network is split into VLANs, where Wi-Fi access points need to sit, which cabling goes where, and who maintains the documentation afterwards. Skip this and every later change costs a multiple of what it should – you can't just pull an extra cable through a finished wall after the fact.

How many network ports does each room really need?

The most common planning mistake is cabling that's too tight from the start. A desk with a single port rarely stays that way – as soon as an IP phone, a second monitor with its own adapter, or a laptop dock shows up, the port is missing, and people improvise with switches under the desk that nobody documents. It's better to plan two ports per desk from the outset. Meeting rooms often need more than expected: one for the display, one for the conferencing camera, ideally a separate one for guest devices. Production areas, storage and reception are easy to forget during planning, even though cameras, label printers or time-clock terminals often end up there later. The best approach is to go room by room, note which devices could realistically end up there over the next few years, and only then calculate the port count – not the other way round.

• Plan at least two ports per desk, even if only one device is connected today
• Design meeting rooms with separate ports for the display, conferencing gear and guest access
• Don't forget reception, storage and production areas – cameras, printers or terminals often land there later
• Leave spare ports on the patch panel and switch instead of using up every port immediately

Why VLANs make sense even for small networks

VLANs split one physical network into several logically separated zones. In practice that means the guest Wi-Fi at reception has no access to the accounting software in the office, and a compromised IP camera can't reach the workstations. Without that separation, every device sits on the same network as every other one – an infected device on the guest Wi-Fi could, in theory, talk to the server. For a company with ten or twenty employees this can sound like overhead, but with a managed switch and a bit of planning it's achievable without much extra effort.

• Keep the guest Wi-Fi strictly separated from the internal network, with no access to internal shares or printers
• Put cameras and other connected devices on their own segment with no access to workstations
• Give servers, accounting and other sensitive systems their own zone with tighter rules
• Separate the production or machine network from office IT, where one exists

Wi-Fi coverage: where do you actually need access points?

One access point per floor is rarely enough. Concrete walls, steel beams and storage racking damp the signal far more than in a new building with drywall partitions. If you run the cabling first and only then find out where the Wi-Fi is weak, you end up wiring twice. It makes more sense to survey the site before the cable routes are fixed – that shows where access points genuinely need to sit, and how many simultaneous users an area needs to handle, not just how large it is.

Copper or fibre, and where should each go?

Cat6a copper cabling is perfectly adequate for most desks and access points. Fibre becomes relevant once distances exceed the usual limits for copper – between two buildings on the same site, between floors that are far apart, or when it's already clear that far more bandwidth will be needed in a few years. One point that's often missed at the planning stage: laying spare empty conduit. An extra empty conduit next to the active cabling barely adds to the cost of installation, but saves years of chasing walls open later when an additional cable is needed.

• Cat6a copper cabling is generally sufficient for desks and access points
• Fibre for runs between buildings, floors that are far apart, or where bandwidth needs are clearly going to grow
• Lay spare empty conduit alongside the active cabling so you can add capacity later without breaking open walls

Documentation: what needs to be in the folder at the end

A network that only exists in one person's head is a risk – for the business as much as for that person's own holiday plans. As soon as that person is out, changes jobs, or the IT provider changes, someone else needs to be able to understand how the network is built without opening every switch individually. That means more than a spreadsheet of IP addresses: a current network diagram, an overview of the VLANs and what they're for, and an access concept that records who is allowed to reach what. This shows up fastest during a change of IT provider – if the documentation doesn't actually exist, the handover starts with days of stock-taking instead of the actual work.

• A current network diagram showing switches, patch panels, cable routes and access points
• An IP address and VLAN overview that's understandable without prior knowledge
• Access credentials in a password vault with clearly defined permissions, not on notes or in open files
• Contact details, maintenance contract and response procedures documented and ready to hand

Plan for growth from the start

A network sized exactly for today's needs is too small within two years. New employees need new desks, new cameras or sensors take up additional ports, and some companies open a second site that needs to connect back to the existing network. Building in a noticeable reserve on switches, patch panels and backbone cabling from the outset, instead of stretching every port and every bit of capacity to its limit, means you can absorb this growth without rebuilding the infrastructure from scratch a short time later.