Building a Communication Plan for Shoots With No Cell Service
Some of my best work happens in places with no cell service at all, and that's not a coincidence. The locations that make for genuinely compelling adventure photography are often the same ones with nothing resembling a signal for days at a time.
That tradeoff is worth it, but only if the communication plan for those stretches is built deliberately beforehand, not improvised once I'm already out of range. If you're planning shoots that take you off the grid, the Adventure Travel Photographer's Playbook covers how I plan logistics for remote work before ever leaving cell coverage behind.
Why a Plan Matters More Than the Technology Itself
It's tempting to think the solution to no cell service is simply buying the right piece of satellite gear and calling the problem solved. Technology is part of it, but the harder, more important part is the plan around it: who needs to know what, how often, and what specifically happens if something actually goes wrong while I'm unreachable by normal means.
A satellite communicator without a clear plan for how it's actually used just becomes an expensive piece of equipment that gets checked occasionally instead of a reliable system. The plan has to exist independently of the specific tool, since tools fail, batteries die, devices get left in a bag at the wrong moment, and the plan needs to hold up even when the primary technology doesn't.
I build this plan the same way for every remote shoot, regardless of which specific device I'm carrying that trip, because the plan is really about clear expectations and defined check-in points, not about any particular piece of hardware.
Who Needs to Know the Plan, and What They Need From It
Before heading somewhere with no service, I make sure at least two people, usually a client contact and someone in my personal circle, have the same information: where I'm going, roughly how long I expect to be unreachable, and what a genuine emergency response should look like if I don't check in when expected.
Giving this information to just one person creates a single point of failure if that person is unreachable themselves when it matters. Two people with the same information, ideally who don't depend on each other to relay it, means the plan holds up even if one contact is temporarily unavailable when a check-in is missed.
I also make sure both contacts know specifically what "no update" should and shouldn't trigger. A missed daily check-in on a shoot where that's expected and planned for is very different from a missed check-in on a trip where I said I'd have reliable signal the whole time. Context prevents an unnecessary emergency response to something that's actually just the plan working as expected.
Setting a Clear Check-In Cadence Before Leaving Service
I agree on a specific check-in schedule before ever losing signal, not a vague "I'll update when I can." A defined cadence, once daily at a set rough time, for instance, gives both me and my contacts a clear baseline for what normal looks like, which makes any actual deviation from that baseline meaningfully informative instead of just more silence in a pattern of already-uncertain silence.
This cadence has to be realistic given the actual conditions of the trip, not aspirational. Promising a daily check-in on a route where satellite coverage is unreliable in narrow canyons or dense tree cover sets an expectation the terrain itself might not let me keep, and a broken promise about check-ins causes more worry than an honest, more conservative cadence would have from the start.
I'd rather commit to a cadence I'm confident I can hold to reliably, even if it's less frequent than ideal, than promise something ambitious that then creates false alarm the first time terrain or weather interferes with it.
What a Satellite Communicator Actually Solves, and What It Doesn't
A satellite communicator solves the basic problem of sending a short message with no cell coverage, a check-in, a location ping, a brief status update. It doesn't solve the harder problem of nuanced communication, explaining a complex scope question, walking through a creative decision, the kind of back-and-forth a client conversation might normally involve.
I try to set expectations with clients before a remote shoot that satellite communication during the trip will be limited to short, functional updates, not detailed conversation, and that any complex decisions get deferred until I'm back in range, unless something is genuinely urgent enough to warrant working through it in short, expensive, low-bandwidth satellite messages.
This limitation is worth naming explicitly rather than letting a client assume satellite coverage means normal communication just continues uninterrupted. It doesn't, and setting that expectation before the trip prevents frustration if a client tries to have a detailed conversation that the technology genuinely can't support well.
Pre-Loading Information Before Losing Signal
Right before heading out of range, I make sure anything I might need is downloaded and accessible offline, maps, permits, emergency contact numbers, the shot list, since assuming I can look something up later assumes a connection that won't exist for the length of the trip. This preparation happens as a deliberate final check, not an afterthought.
I also send a final, more detailed update right before losing signal, similar to what I'd send before an international time-zone gap, laying out the plan, the expected return-to-service date, and anything the client or my personal contacts should know in the meantime. That message becomes the reference point everyone works from during the gap, reducing the number of things anyone has to guess at while I'm unreachable.
This final pre-departure update takes real intention to get right, since it has to anticipate questions that would normally just get asked and answered in real time, and answer them preemptively instead.
Handling a Genuine Emergency With No Service
The plan for a genuine emergency has to be simple enough to execute under real stress, not a complicated multi-step process that's hard to remember when something's actually gone wrong. My emergency plan is deliberately basic: use the satellite device's dedicated emergency function if one exists and is warranted, or send the clearest possible short message to my established contacts if the situation is serious but not immediately life-threatening.
I've also made sure my contacts know, in advance, exactly what to do if they receive an emergency signal or a genuinely concerning missed check-in, who to call, what information to provide, so precious time isn't lost to them figuring out the right response in the moment. That advance planning on their end matters just as much as my own preparation on the ground.
Having this simple, pre-agreed plan removes decision-making under pressure, which is exactly when clear thinking is hardest and mistakes are most likely.
Balancing Client Expectations Against Realistic Remote Conditions
Clients booking a remote shoot don't always intuitively understand what "no cell service" actually means for communication during the trip, especially if they haven't worked on a similarly remote project before. I try to walk through this explicitly during planning, not just mention it in passing, since a client who fully understands the communication limits going in is far more patient with them than one who's surprised once the trip is already underway.
This conversation also covers what happens on the client side if they urgently need to reach me. Setting a realistic expectation, a message might take a day or more to actually reach me depending on terrain and conditions, prevents a client from assuming a shorter response time is possible and then reading normal remote conditions as a problem.
Why I Still Choose These Locations Despite the Complexity
Given how much extra planning this all requires, it would be easier to stick to locations with reliable cell service. I don't, because the genuinely remote locations are often where the most compelling adventure photography actually happens, places that feel real and unfiltered specifically because they haven't been made convenient and connected.
The communication plan exists to manage the real risk of that choice responsibly, not to talk myself out of making it. A well-built plan means the tradeoff of going somewhere disconnected is a manageable, deliberate one, rather than a reckless gap in judgment that happens to also produce good photos.
What Years of Remote Shoots Have Taught Me About This
The plan has gotten simpler over time, not more complicated, as I've learned which parts actually matter and which were just adding process without adding real safety or communication value. A realistic check-in cadence, two informed contacts, pre-loaded essential information, and a simple emergency protocol covers the vast majority of what's actually needed, and everything beyond that tends to be more effort than it's worth.
The goal was never to eliminate the discomfort of being unreachable for stretches of time. It's to make sure that discomfort is planned for, understood by everyone who needs to understand it, and backed by a clear protocol if something genuinely goes wrong, rather than an anxious, undefined gap that leaves everyone guessing.
Testing the Plan Before It Actually Matters
A communication plan that's only ever been thought through on paper is a different thing than one that's actually been tested, and I try to run through mine, at least mentally and sometimes literally, before relying on it for a genuinely remote trip. That might mean confirming the satellite device actually connects reliably from a similar type of terrain before the trip that really depends on it, rather than assuming it'll work the same way it did in a different environment.
I've caught real gaps this way, a device with a firmware update pending that I hadn't noticed, a contact who'd misunderstood part of the plan when I asked them to repeat it back to me. Catching these gaps during a low-stakes test is enormously better than discovering them during an actual emergency, when there's no time left to fix a misunderstanding or a technical issue.
What Batteries and Backup Power Mean for a Communication Plan
None of this plan matters if the device itself is dead when it's actually needed, and power management for communication equipment gets the same seriousness I apply to camera batteries on a remote trip. I carry backup power specifically allocated to the communication device, separate from what's budgeted for camera gear, since running both off a shared, limited power source risks the communication device losing out during a long, demanding shooting day.
I also test the device's battery life under conditions similar to the actual trip beforehand, cold temperatures in particular can drain batteries far faster than their rated performance suggests, rather than trusting a manufacturer's estimate that was likely tested under far more forgiving conditions than a multi-day trip in genuinely remote terrain.
How This Plan Has Evolved Across Different Kinds of Trips
The core structure of my communication plan has stayed consistent over years of remote work, but the specifics have adapted as the trips themselves have varied, a solo backcountry shoot requires a different level of detail than a multi-day trip with a small crew, where more people need to be looped into the same plan and the failure of any single person's device isn't necessarily catastrophic the way it would be traveling alone.
I've also adjusted the plan based on genuine lessons from past trips rather than treating the first version I built as permanent. An early plan that worked fine for a domestic backcountry trip needed real adjustment for international remote work, where local emergency response systems, language barriers, and unfamiliar terrain all add complexity that a simpler domestic plan never had to account for. Treating the plan as something to keep refining, rather than a template to reuse unchanged, has made it more reliable with every trip it's been tested against.
What I'd Pack Even on a Trip I Expect to Have Signal
I carry basic off-grid communication capability even on trips where I genuinely expect reliable cell service most of the time, since terrain, weather, and infrastructure failures can turn an expected-to-be-connected trip into an unexpectedly disconnected one with little warning. Treating off-grid communication readiness as standard kit, rather than something reserved specifically for trips I already know will be remote, has caught more than one situation where signal dropped out for longer than anticipated in a spot I hadn't planned around.
This isn't about assuming the worst on every trip. It's a small amount of extra weight and cost against a real, if occasional, gap between what a trip's connectivity is expected to look like on paper and what it actually turns out to be once I'm on location and conditions don't cooperate the way a map or a forecast suggested they would.
The trips where this backup readiness has actually mattered were never the ones I expected. A short domestic assignment with supposedly reliable coverage turned into a full day of no signal because of an unexpected dead zone nobody had flagged in advance. Having the same basic plan and equipment ready, even for a trip I genuinely didn't expect to need it on, meant that day was a minor inconvenience rather than a moment of real uncertainty for the people waiting to hear from me.
That experience shifted how I think about the whole category of trips I'd previously treated as low-risk simply because coverage maps suggested reliable signal throughout. Coverage maps describe an average expectation, not a guarantee, and the gap between the two is exactly where an unprepared communication plan turns a minor inconvenience into genuine, avoidable worry for the people counting on hearing from me on schedule, which is reason enough to keep the basic version of this plan in place on essentially every trip, remote or not, rather than reserving it only for the assignments that look obviously disconnected on paper before I've actually arrived and seen the real conditions for myself, since paper and reality don't always agree once I'm standing somewhere the map simply couldn't have predicted with any real precision or confidence, and I'd rather carry the extra preparation on a trip that turns out not to need it than be caught without it on the one that genuinely does.
Reflection Questions
- Do at least two people, who don't depend on each other, know your plan for your next remote shoot?
- Have you set a realistic check-in cadence, or an aspirational one that terrain might not actually let you keep?
- Do your clients understand what satellite communication can and can't support during a remote trip?
- Is your emergency protocol simple enough to actually execute under real stress?
If remote and off-grid locations are part of your work, the Adventure Travel Photographer's Playbook covers how I plan communication and logistics for shoots well beyond cell coverage.
Dalton Johnson is a professional adventure and editorial photographer with over a decade of experience creating images on all seven continents. His client work includes Patagonia, GoPro, Arc'teryx, Four Seasons, Nike, Rivian, Big Agnes, Ford Bronco, and 160+ other brands. He runs Dalton Johnson Media as a full-service studio, from pre-production through post and distribution.