TL;DR
A connectivity stipend is the smallest line in a remote budget and the one most likely to be argued about, because it sits where company cost and personal household bill blur. The decision is less about the amount than about which of three mechanisms you pick, and they behave very differently.
- Three mechanisms: flat payment, reimbursement, or nothing. Pick deliberately.
- Flat is cheapest to administer and the easiest to defend as fair.
- Reimbursement invites receipts, and receipts invite an approval queue.
- Tax treatment differs by country. Finance decides, not IT.
- The upgrade case is the real one: people on inadequate connections.
- Mobile data as a fallback is cheaper than a day of lost work.
The three connectivity stipend mechanisms
They differ far more in administration than in cost, and the administration is what people actually complain about.
| Mechanism | Admin burden | Main drawback |
|---|---|---|
| Flat monthly payment | Lowest | Pays people who did not need it |
| Reimbursement against a bill | Highest | Receipts, queues, and awkward edge cases |
| Nothing, with an upgrade fund | Low | People have to ask, so some will not |
Why flat usually wins
Because the amounts are small and the administrative cost of the alternative is not. A reimbursement scheme generates a monthly receipt, a check, an approval and an occasional dispute about whether a household bill counts, and all of that costs more staff time than the payment itself.
Flat also avoids the most uncomfortable version of this conversation, which is a company asking to see somebody’s household bills in order to pay them a modest sum.
Where flat is the wrong answer
When connections genuinely differ in ways that matter. If part of your team is in places where a usable connection costs several times what it costs elsewhere, a flat figure is simultaneously too much for some people and not enough for the people who actually have a problem.
The fix is not a complicated matrix. It is a flat figure plus a route for the exceptions, which is the pattern that works in almost every equipment policy.
They also create an expectation that every number is individually defensible, which invites exactly the line-by-line argument a flat figure avoids.
Matrices by country look fair on paper and age badly. Costs move, markets get added, and within two years somebody is maintaining a table nobody can justify line by line.
The real problem is a small number of bad connections
Most people in most places have a connection adequate for work, and paying all of them a monthly sum does not improve anything. The people who matter here are the minority for whom the connection genuinely is the bottleneck.
That is a different and cheaper problem to solve, and it responds to a fund rather than to a stipend.
A one-off upgrade. A better router, a mesh unit, a wired run to wherever they actually work. Frequently a few hundred once, rather than a payment forever.
A faster tier for a few months. Sometimes the only thing needed, and sometimes the thing that reveals the problem was never the line speed.
A mobile data fallback. The most underrated item on the list. A data allowance that lets somebody keep working through an outage costs little and prevents whole lost days.
Why people do not ask
Because asking means saying their home setup is inadequate, which feels personal in a way that asking for a monitor does not. That is the main argument for a flat payment: it reaches people who would never have raised it.
If you run an exceptions route instead, say explicitly and repeatedly that it exists and that using it is normal. Otherwise it serves the confident and misses the people it was built for, which is the usual failure of any opt-in arrangement.
Tax is finance’s call, and security is not optional
Disclosure: RemoAsset, named below, is owned by the same people who publish PeopleOpsHQ. It is described with its limitations stated, on the same terms as every other supplier. This site takes no vendor money.
Two things that sit outside the policy decision and routinely get skipped.
Tax treatment differs by country and by mechanism. A flat allowance and a reimbursement against a receipt are frequently treated differently, and both differ by jurisdiction. This is a finance question, it should be answered before the policy is published rather than after the first payroll run, and it is a reason not to design the scheme in IT.
A home connection is not a company network. Paying for somebody’s broadband does not make their home router a managed device, and it should not be treated as one. the UK National Cyber Security Centre device security guidance frames the managed state of the device as the control rather than the network it sits on, which is the right position for distributed work: assume the network is untrusted and secure the endpoint.
What not to do with the money
Do not attach monitoring to it. A stipend that comes with inspection of somebody’s home network is a different proposition entirely, and it is one most people would decline if asked plainly.
The same applies to anything that touches the household rather than the work: who else uses the connection is not a company question, and treating it as one under the consolidated text of the General Data Protection Regulation brings in household members who never entered into any arrangement with you.
Worth noting where this sits relative to equipment: an equipment platform ships and recovers devices. Configured device procurement and delivery covers the machine, and it has nothing to do with broadband, mobile contracts or routers. That is a different supplier and usually a local one, which is part of why this line gets forgotten.
The decision table
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| One country, decent infrastructure | Any | Remote team | Admin cost | Flat, small, no receipts |
| Wide variation between markets | 50 plus | Multi-country | Flat fits nobody | Flat plus an exceptions fund |
| A few people genuinely struggling | Any | Any | Minority problem | Upgrade fund, not a stipend |
| Frequent outages in one region | Any | Any | Lost days | Mobile data fallback |
| Finance has not been asked | Any | Policy drafted | Tax treatment unknown | Stop and ask before publishing |
Writing it so it survives a year
Four lines, and the fourth is the one that gets left out.
The amount and the mechanism. One sentence. If it needs a paragraph of conditions, the conditions are the policy.
Who is eligible. Usually everyone who works remotely for some stated proportion of the week. Drawing that line precisely matters less than drawing it visibly.
What happens for the exceptions. Who to ask, and a statement that asking is normal. This is the line that determines whether the exceptions route works at all.
When it gets reviewed. Connectivity costs move, and a figure set three years ago is now either generous or insulting, usually without anybody noticing which.
The question to ask at the review
Not whether the amount is still right, which invites an opinion. Ask how many people used the exceptions route in the last year, and what for.
Ask it of the people who did not use it as well. A short note to a handful of remote staff asking whether their connection has ever stopped them working will find more than the request log does, because the log only contains people who already decided to act.
Zero usually means people do not know it exists rather than that nobody needed it. A handful of similar requests means the flat figure is wrong for a specific group, which is a far more useful finding than a general sense that the number feels low.
Finally, check that the route itself is usable by everyone who might need it. the W3C Web Accessibility Initiative introduction to accessibility covers the digital side, and an exceptions process that lives in a form some people cannot use is an exceptions process that does not exist for them. For the wider question of what belongs in a remote setup budget, see our piece on desk and chair budgets.
See what an equipment platform does cover at configured device procurement and delivery, or read our piece on desk and chair budgets.
Frequently asked questions
What are the options for a connectivity stipend?
Three. A flat monthly payment, which has the lowest administration and pays some people who did not need it. A reimbursement against a bill, which has the highest administration and invites receipts and disputes. Or nothing, with an upgrade fund for people who ask, which is cheap but misses those who will not ask.
Why does flat usually win?
Because the amounts are small and the administrative cost of the alternative is not. A reimbursement scheme generates a monthly receipt, a check, an approval and the occasional dispute about whether a household bill counts. It also avoids a company asking to see somebody’s household bills in order to pay them a modest sum.
When is flat the wrong answer?
When connections genuinely differ in ways that matter, so a single figure is simultaneously too much for some people and not enough for those with a real problem. The fix is not a complicated matrix but a flat figure plus a visible route for exceptions, which is the pattern that works across equipment policy generally.
What is the real problem this should solve?
A small number of genuinely inadequate connections, not the general population. That responds to a one-off upgrade such as a better router or a wired run, a faster tier for a few months, or a mobile data fallback. The last is the most underrated: it prevents whole lost days for very little money.
Why do people not ask for help?
Because asking means saying their home setup is inadequate, which feels personal in a way that asking for a monitor does not. That is the strongest argument for a flat payment, since it reaches people who would never raise it. If you run an exceptions route instead, say repeatedly that using it is normal.
Who decides the tax treatment?
Finance, before the policy is published. A flat allowance and a reimbursement against a receipt are frequently treated differently, and both differ by jurisdiction. It is a reason not to design the scheme inside IT, and the answer should be in hand before the first payroll run rather than after it.
Does paying for broadband make it a company network?
No, and it should not be treated as one. The managed state of the device is the control rather than the network it connects through, so assume the network is untrusted and secure the endpoint. Attaching monitoring or inspection of a home network to a stipend is a different proposition that most people would decline if asked plainly.
PeopleOpsHQ covers the operational side of distributed work. We describe suppliers with their limitations stated, and we take no vendor money.