1. Why the estimate must be based on real traffic
Many companies choose an internet line on price or on the speed written in the contract. The trouble is that nominal speed is only a theoretical maximum, and the speed users actually experience depends on many factors: simultaneous traffic, the quality of the equipment, distance from the access point and the cloud services in use. An estimate based on generic assumptions often leads to a line that is either oversized or insufficient.
2. Distinguishing nominal speed, usable speed and peaks
Nominal speed is the figure in the contract. Usable speed is what is actually available at a given moment, which can vary during the day. Peaks are the moments when many activities overlap: start of the working day, backups, group video calls, system updates. The estimate must be made on peaks, not on averages. This distinction should be clarified with the provider before signing.
Upload and download must be considered separately. Many lines are asymmetric between the two directions, and some business activities, such as sending large files, synchronisation or backups to external locations, make heavy use of upload. A contract with high download and low upload may be unsuitable for a company that frequently sends data. If the line is asymmetric, ask whether alternatives with more balanced capacity exist.
| Concept | What it indicates | Why it matters |
|---|---|---|
| Nominal speed | The value stated in the contract | A starting point, not a guaranteed result |
| Usable speed | Capacity measured at a specific moment | Shows what actually reaches users |
| Peak | Moment of maximum simultaneous use | The criterion for sizing the headroom |
| Asymmetry | Difference between upload and download | Affects backups, sending and synchronisation |
3. Measuring current traffic
The measurement must be repeatable and documented. A single test taken early in the morning tells you very little. You need a set of measurements at several times of day, with notes on what was happening. The more representative the sample is of real work, the more reliable the estimate. Measurements should be taken on both the wired connection and the wireless network, because results can differ considerably.
- Choose a normal working week, without exceptional events.
- Record speed with repeated tests at different times, including the start-of-day and lunchtime peaks.
- Note how many people are connected and which activities are running at the times measured.
- If available, read the traffic data from the router to see who is using the most.
- Compare the measurements with the contracted line and note any differences.
4. Estimating requirement and headroom
Requirement is estimated from the measured peak, to which a margin is added for expected growth and variability. The margin is not a detail: a line that always runs at its limit makes every new activity a problem. The size of the margin depends on the sector, the type of work and the cost of a slowdown, and must be decided with someone who knows the business.
Distinguish services that require continuity, such as voice and video conferencing, from those that can slow down, such as email or downloads. The former need a stable response at peak times; the latter can tolerate an acceptable queue. This distinction often reduces the required capacity more than expected, and it links directly to service quality. Each service should be treated according to its profile.
5. What to ask the line provider
Read the contract with the same questions you would ask of a provider of essential services. Nominal speed alone says nothing about what happens at peak times. Ask what is guaranteed, what is maximum and what is excluded, and have the meaning of every term confirmed in writing. The contract is also the document on which any later comparison will rest.
Compare several offers on the same basis: minimum capacity, upload, support, declared restoration times. An offer with a lower price may have limitations that emerge only under heavy use. Sizing should be the selection criterion, not just the monthly cost. Also compare the terms for termination and upgrades, because they affect cost over time. Ask whether the same offer can be compared with those of other providers on equal terms.
- Guaranteed minimum speed and under what conditions.
- Asymmetry between upload and download, and whether it can be changed.
- How the public IP address is assigned and whether it can change over time.
- Times and procedures for fault repair, written into the contract.
- Option of a second connection for continuity, with its limits.
6. Common mistakes in sizing
The first mistake is sizing on the speed written in the contract rather than on measured traffic. The second is measuring once, at a quiet moment, and concluding that the line is enough. The third is assuming that more bandwidth solves every problem, without checking whether a single service or device is occupying the line. A mistake of this kind only becomes visible when the work grows.
Another frequent error is overlooking upload. Backups to external locations, file synchronisation and sending large documents can slow down all work even with an excellent download speed. Finally, many companies forget that the connection is a single point: a fault stops everything, regardless of speed. Sizing must also consider continuity. Whoever is responsible for the network should review the estimate every year.
7. When a larger line is needed and when it is not
A larger line makes sense when measurement shows frequent saturation at peak times, when essential services slow down because users compete for capacity, and when the company's growth is documented. If, however, the problem is a single service or a badly configured device, increasing bandwidth costs more and solves less. The key is always the measurement, not the impression of whoever uses the network.
Before requesting a larger line, try reducing unnecessary consumption, giving priority to critical services or moving backups outside working hours. If saturation persists after these steps, the request for capacity is justified and can be presented to the provider with the measurement data. A request for an upgrade should be accompanied by measurements taken after the intervention.
8. How to start
This week, choose a normal working day and run speed measurements at several times: at opening, in the middle of the morning, after lunch and in the afternoon. Note what is happening in the office at each moment. It takes little time and provides more information than any data sheet. Choose times that represent real work, not only quiet moments. Also note what users are doing, so the data has context.
Then gather your current contract, with its written conditions, and prepare a request to the provider based on the measurements: observed peak, required upload, critical services and continuity requirements. With these elements the conversation changes: you are no longer asking for a faster line, but for a line suited to the work you have measured. Read the contract together with those who used the network on the days of measurement.
Frequently Asked Questions
How much bandwidth does an office need?
There is no single value that suits everyone. It depends on how many people work at the same time, the applications used, video conferences, backups to external locations and cloud services. The correct answer comes from measuring real traffic at peak times, not from a generic table.
Why do speed tests give different results?
The result depends on the time, the device used, the connection (wired or wireless), network load and the test server. That is why several measurements at different times, with wired devices, are needed to obtain comparable data. Always note the conditions of each measurement.
Does upload matter more than download?
It depends on the work. For browsing, email and web applications, download is often the main element. For companies that send large files, synchronise data or back up externally, upload becomes the bottleneck. Check which direction is used more before choosing the contract.
Does a second connection solve everything?
It increases continuity, but not capacity as such. Two lines can be used to balance traffic or to take over in the event of a fault, under different rules. It must be designed with the provider, because a second connection that is badly configured may fail when it is needed.
Who should prepare the estimate for the company?
The IT manager or the network provider, with input from those who know the real work and the critical services. The final decision on how much headroom to pay for rests with management, because it balances cost against the risk of a slowdown. A shared estimate is easier to defend than a choice made by one person alone.