Pooled data or individual allowances: which one suits your team

Most businesses buy mobile data the way they buy stationery — a set amount per person, the same for everyone, reviewed when someone complains. It is the most expensive habit in a mobile fleet, and it is the easiest one to fix.

The alternative is pooled data: every service on the account draws from one shared allowance instead of holding its own. It is not a discount scheme or a loyalty tier. It is a different shape of purchase, and for most fleets it is simply the correct one. Here is how it works, where it does not, and how to tell which side of the line your business sits on.

What “pooled” actually means

With individual allowances, each service gets its own bucket. Whether that bucket is emptied or barely touched, you paid for all of it.

With pooled data, the max speed data from every eligible service on the same billing account is added together into one pool, and the fleet draws from it first in, first served. Nothing is slowed until the whole pool is gone. A driver who uses almost nothing is, without anyone managing it, funding the estimator uploading photos from a site all afternoon.

That is the entire mechanism. The value comes from a fact about how teams actually use data.

Why the average is a lie

Pull the per-service data usage for any fleet of twenty and the shape is almost always the same. Two or three people use a great deal. A middle group uses a moderate amount. The rest use so little that their allowance is effectively decoration.

Now size individual plans for that fleet. You cannot size to the average, because the heavy users would run out in the first fortnight and you would spend the month buying top-ups. So you size to the heavy users — and then you buy that same headroom twenty times, nineteen of which will never be touched.

Pooling buys the headroom once. The heavy users draw on the allowance the light users were never going to use, and the total you need to buy drops to something close to what the business genuinely consumes. That is the whole argument, and it holds for almost any team with more than a handful of services and any variation in how they work.

Where pooling does not help

It is worth being straight about the cases where this is not the answer.

Everyone uses roughly the same amount. If your team all do the same job in the same way, there is little variance to average out and the saving is small. Real, but small.

Your services are spread across separate billing accounts. Pooling happens within an account. Services on different accounts do not share, no matter whose name is on them. Consolidating accounts is usually step one, and it is a bigger win than any plan change.

Unlimited inclusions do not pool. This one catches people, because it is the opposite of what you would assume. Unlimited international minutes belong to the service that has them and cannot be spread across the fleet. Counted international minutes do pool. If international calling is central to a role, that role needs its own inclusion rather than a share of someone else’s.

One person can drain it. First in, first served means exactly that. A tablet left tethering in the back of a ute is a fleet-wide problem rather than a personal one, so pooling is worth pairing with a look at usage every quarter or two.

What happens when the pool runs out

On the current business range there is no excess data charge in Australia. When the pool is gone, services drop to a reduced speed — up to 2Mbps — until the next billing period.

That is a meaningfully better failure mode than a surprise bill, and it changes how you should plan. There is no financial penalty for occasionally running close to the line, so there is no reason to buy a large safety margin you never use. Buy roughly what the fleet consumes, add a booster in the month a project runs hot, and let the speed limit be the backstop rather than the invoice.

Tablets, routers and the things nobody thinks about

The services that benefit most from pooling are often the ones nobody remembers owning. Tablets in the field. A router in a site office. Card terminals. Cameras. Individually each carries a small allowance that mostly goes unused; together they are a real line on the bill.

Tablet plans and data-only services can sit in the same pool as your phones, which usually means they can carry a smaller allowance each and draw on the fleet when they need more. The smallest data-only plans are built on exactly that assumption — they are designed to sit alongside a pool rather than stand alone.

The trade-off to know: a data-only service has no calls and no SMS beyond emergency and whitelisted numbers. That is fine for a camera and wrong for anything a person needs to answer.

How to work out what you would actually save

You need three numbers, and only one of them is hard to find.

Total fleet data used per month, across three months. Not per service — the total. Three months, because one month is a story and three is a pattern.

Total allowance you are currently paying for. Add up every service’s allowance. The gap between this and the number above is what pooling is being wasted on.

Your peak month. The highest of the three. This is what you size the pool to, and it is usually far below the sum of individual allowances.

The business connectivity health check will give you a quick read on whether your setup is costing you more than it should. If you do not have easy access to those figures, we can pull them from your account and set them out service by service. That report is free and it is useful even if you change nothing.

The short version

If every service in your fleet has its own data allowance, you are almost certainly buying the same unused headroom several times over. Pooling is not a clever trick — it is just buying once what you currently buy repeatedly. The work is in consolidating onto one account and sizing the pool to real usage, and that is the part we do with you.