One page, five rules: a travel data policy
Who buys, who approves, who keeps the receipts and what happens when a plan runs out. The minimum viable policy.
The first 24 hours are the riskiest: a short protocol for landing, connecting and reporting in.
Sample editorial
Most policies fail because they are written for procurement, not for the person standing in a taxi queue. One page, five rules and a named owner is enough.
Comnexa publishes general business-travel information. It does not provide legal, tax or procurement advice, and it does not sell connectivity. Adapt any policy to your own organisation.

Who buys, who approves, who keeps the receipts and what happens when a plan runs out. The minimum viable policy.
Email is cheap, video is not, and cloud sync is the quiet line item. A working estimate for a normal week.
What survives a tunnel, what does not, and how to structure a travel day around the difference.
Dual SIM is a boundary tool as much as a technical feature. Set the default line before the trip, not during it.
A three-field note at the point of purchase saves an afternoon of reconstruction at the end of the quarter.
A planning table for one traveller with a laptop. Multiply by the number of people who need their own connection.
| Activity | Typical daily use | Notes |
|---|---|---|
| Maps and transport | 150 MB | More if you stream navigation audio |
| Email and messaging | 100 MB | Attachments are the variable |
| Video calls | 250 MB per hour | Lower the resolution to halve it |
| Cloud file sync | 300 MB | Pause large folders before you travel |
| Hotspot for a laptop | 500 MB | Only for short, focused sessions |
Estimates for planning, not promises. Video quality settings change everything.
Practical routines for people who travel to work.
Simple rules that survive contact with a taxi queue.
Estimates, approvals and the cost of video.
What actually works on a train or in a hotel room.