Connectivity for event teams and travelling crews

Events and shoots share a shape: the heavy demand is concentrated in a few hours, and failure costs far more than the plans do. Plan from the critical window rather than from the trip total.

Group by role

Before travel

1. Verify every device supports eSIM and is not carrier-locked
2. Install profiles in advance on office Wi-Fi
3. Keep a list mapping each person to an order number so issues can be traced quickly
4. Hold a small pool of spare profiles for the unexpected

Keeping spend predictable

• Bill per project rather than reimbursing individually
• Set a rule that large uploads happen on accommodation Wi-Fi
• Review actual usage afterwards to size the next job correctly

Talk to the business desk

A crew is not simply a lot of business travellers

If you have arranged connectivity for one employee flying to a meeting, doing it for a crew of thirty travelling together is not that job multiplied by thirty. Three things differ. Everyone is in the same place at the same time, which changes how the network behaves there. One person's failure lands on other people's schedules. And once you are on site there is no time to troubleshoot devices one at a time.

The consequence is that most of the work has to be finished before departure rather than in transit. Preparation done well means the event day contains no connectivity thinking at all, which is the correct target: a team lead's time on the day belongs to the job, not to walking ten people through a settings menu.

Plan from the critical window, not the trip total

Events and shoots have a lopsided usage shape. Three days may pass using very little, and then four hours arrive in which everything happens at once: files going out, coordination traffic, updates to the client. Planning from the trip total therefore gets it wrong in both directions — too generous on the quiet days and too thin in the hours that matter most.

A more direct method is to write the run of show first and mark the windows in which being disconnected is unacceptable. Then ask what each person has to do during those hours. The answer usually shows that two or three people need substantially more than everyone else, while a much larger group only needs to be reachable.

Audit the devices before buying anything

The step that cannot be skipped, and usually is, is confirming that everyone's phone can actually take an eSIM. Crews carry personal devices of many models and ages, and there is always someone with a handset too old to support it, or one still locked to a previous operator. Discover that after buying and you are left holding plans nobody can install and a person with no connection on the day.

Check whether your team's devices support eSIM

Sizing by role, in more detail

Giving everyone an identical allowance is simultaneously the easiest and the most expensive approach, because you must buy for the heaviest user and then pay that price for people who only use chat and maps. Sizing by role takes under an hour more and usually cuts the total meaningfully.

Distributing profiles to dozens of people

The slowest part of provisioning a crew is not buying; it is getting everyone to install, and to install correctly. Leave people to do it when convenient and some will forget, some will install on the wrong device, and someone will try it at the airport and find the Wi-Fi unusable. What works is scheduling everyone to do it together, somewhere with reliable Wi-Fi and someone on hand to help.

1. 1Collect the full list of people and devices firstName, role, handset model and destinations, in one table. An incomplete list is the leading cause of someone being left without a connection on the day.
2. 2Audit every device before orderingConfirm eSIM support, no carrier lock and no IT policy in the way. Anyone who fails needs an alternative arranged now, not later.
3. 3Run one installation session on office Wi-FiOne scheduled time, a stable connection, and someone to help whoever gets stuck. An hour here saves a day on site.
4. 4Test each device before people leave the roomHave everyone turn Wi-Fi off and load one page. Fix anyone who cannot, on the spot; do not let a problem walk out of the building.
5. 5Record who received which profileMap each person to an order reference in one sheet, so an individual problem can be traced quickly without questioning the whole crew.
6. 6Hand out one page of instructionsWhat to do on travel day, how to switch lines, and how to get help. One page people actually read beats a manual nobody opens.
7. 7Hold spare profiles in advanceFor replacements, broken handsets and failed installations. How many is right depends on the size of the crew and the risk profile of the job.

Personal devices and company devices

Most crews work from personal phones, which raises questions worth answering before departure. Who owns the plan? What happens if that person leaves mid-project? What can the organisation reasonably ask of a personal device? These are policy questions rather than technical ones, and they are best settled in advance, because working them out during an incident is too late.

Something else that gets overlooked is that people want to keep their own number live for calls and verification codes. Running two lines — the personal number for calls and messages, the travel plan for data — answers that, but it must be explained clearly: which line is set as the data line, and that data roaming on the personal line should be switched off. Otherwise unintended usage follows.

The venue is a problem no plan can solve

In a place holding several thousand people at once — a trade show, a concert, a competition — the mobile network in that area becomes heavily congested. It affects everyone present regardless of what they bought, because the limit is the capacity of the local masts rather than your entitlement to use them.

What you can do is plan around it: move large files before the doors open or after the crowd leaves, use low-bandwidth channels for coordination during the event — text rather than app calls or video — and agree beforehand how you will communicate if the network genuinely fails. Crews with a non-network fallback keep working; crews without one stop.

The devices that are not phones

Crews carry devices besides phones that also need to be online: tablets for scripts and schedules, laptops for rough cuts, portable routers for positions that need a shared connection. Their eSIM support is uneven — some models have it, some do not, and some do but with a process quite different from a phone's.

Audit those with the same care as the phones, and do not assume they can simply use the same plan. Where a device has no support, the most direct answer is tethering from a phone that does, but that phone then needs extra allowance and extra battery, because a device acting as a hotspot drains far faster than usual.

The timeline before departure

What sinks a crew's connectivity is rarely a wrong decision; it is a right decision made too late. The list below is ordered by when things should happen rather than by importance.

• As soon as the itinerary exists, list every destination country including connection days
• Before ordering, audit every device for support and carrier lock
• Before ordering, split the team by role and size each group separately
• Several days before departure, run the installation session on office Wi-Fi
• In the same session, apply data-saving settings and explain roaming on personal lines
• Before departure, have everyone test by turning off Wi-Fi and loading a page
• Give the team lead the spare profiles and the emergency contact list
• Agree in advance how the team communicates if the network fails during the event

Keeping spend predictable

The uncontrolled costs on jobs like this rarely come from the price of the plans. They come from mid-trip repurchasing after a low estimate, and from individuals buying their own and claiming back at different prices. Buying once, centrally, before departure fixes both, and makes the finance paperwork considerably simpler.

The other thing that helps is a review afterwards. Record what each role actually used, and size the next job from those numbers. Similar jobs produce similar usage patterns, and real figures from the last event beat an estimate made from impressions every time.

Contact us with the details of your job

The mistakes crews repeat

From the questions that reach us, the repeated mistakes have a clear shape, and nearly all of them are prevented by preparation before travel day rather than by a larger plan.

1. Waiting to install on arrival, then finding no usable Wi-Fi at the airport or hotel
2. Sizing from the trip total instead of from the busiest hours
3. Skipping the carrier-lock check until it is too late to do anything about it
4. Holding no spare profiles, when last-minute crew changes happen on almost every job
5. Not telling the team to disable roaming on their personal lines
6. Depending on venue Wi-Fi that was never tested beforehand
7. Not recording real usage afterwards, so the next job starts from guesswork again