How I Build a Shot List Before an Adventure Trip
A shot list built before a trip isn't about scripting every frame in advance, adventure photography by nature involves too much unpredictability for that to work well. It's about giving myself and any client a shared reference point for what the trip needs to deliver, while leaving enough room to actually respond to what happens once we're on location.
Getting this balance right has taken real trial and error over the years. For the fuller planning system I use before every trip, it's part of a bigger framework in The Adventure Travel Photographer's Playbook.
What a Shot List Is Actually For
A shot list serves a few distinct purposes that are worth separating out, because conflating them leads to a document that doesn't actually do any of them well. First, it's a planning tool, forcing me to think through what the trip actually needs to deliver before I'm standing in the field trying to figure it out in real time. Second, it's a communication tool, giving a client a clear sense of what to expect and a way to confirm we're aligned on priorities before the trip happens. Third, it's a safety net, a checklist to work through so a critical shot doesn't get missed simply because something else was distracting in the moment.
What a shot list is not, in my approach, is a rigid script that gets followed regardless of what's actually happening on the ground. Adventure photography depends heavily on responding to real conditions, weather, light, the actual behavior and energy of subjects, and a shot list that's too rigid actively works against capturing the best possible content when reality doesn't match the plan.
Balancing those purposes means building a list detailed enough to be genuinely useful for planning and communication, while treating it as a flexible guide rather than a fixed requirement once the trip is actually underway.
I've also come to see the shot list as a tool for managing my own mental load during a demanding trip. Adventure photography often happens under real physical and cognitive strain, fatigue, altitude, weather stress, and trying to hold an entire trip's priorities purely in memory under those conditions is asking for something to slip through the cracks. Having it written down externalizes that load in a way that frees up mental capacity for the actual creative and technical decisions happening in the moment.
How I Actually Build the List
I start with the confirmed deliverables and client priorities, working backward from what actually needs to exist at the end of the trip to what needs to be captured to make that possible. This includes both the specific hero shots a client has explicitly requested and the supporting content, wide establishing shots, detail shots, portraits, that a finished gallery or story typically needs even if the client hasn't explicitly asked for each piece.
I then research the specific location and activity as thoroughly as I can before the trip, looking at what's actually possible there, known viewpoints, likely conditions, the general shape of how the activity unfolds, so the shot list reflects genuine possibilities rather than generic assumptions that might not fit the actual location or subject.
I organize the list loosely by priority rather than by chronological order, since the actual sequence of a trip rarely matches a neat plan, and I want to be able to glance at the list at any point and know immediately what the highest-value remaining shots are, regardless of when during the trip that moment happens to occur.
I also try to explicitly flag which items on the list are genuinely unrepeatable, a specific weather window, a specific stage of an expedition, versus which ones could reasonably be captured on a different day or even a future trip if conditions don't cooperate this time. That distinction matters enormously for how I prioritize limited time and energy once actually in the field, since treating every item as equally urgent leads to poor triage decisions under time pressure.
How I Use the List Once the Trip Starts
Once actually in the field, the shot list becomes more of a background reference than an active script. I check it during natural lulls, waiting for light, traveling between locations, rather than trying to consult it constantly during active shooting, since that constant referencing pulls attention away from actually seeing and responding to what's happening in front of me.
I treat unplanned, unexpected moments as having priority over the shot list whenever something genuinely compelling happens that wasn't anticipated. The list exists to make sure nothing important gets missed by oversight, not to prevent capturing something better than what was planned. Some of the strongest images from past trips came from moments that weren't on any list at all.
Toward the end of a trip, I do a more deliberate review against the list, checking what's been captured against what was planned, and using any remaining time to specifically target anything still missing rather than assuming everything important has naturally been covered. This final check has caught real gaps more than once, a specific angle or moment that felt like it would obviously happen naturally but hadn't actually been captured yet.
On multi-day trips, I also do a brief daily check-in against the list, not a full formal review, just a quick mental or written pass at the end of each day, so gaps get identified while there's still time within the trip to address them, rather than only discovering a significant miss during the final review when it's too late to do anything about it.
Sharing the List With Clients
For client projects, I usually share a version of the shot list, sometimes simplified, during the proposal or pre-trip planning phase, both to confirm we're aligned on priorities and to manage expectations about what's realistic given the trip's actual timeline and conditions. This conversation surfaces misalignments before the trip happens, when they're still easy to address, rather than after delivery, when they're much harder to fix.
I'm also honest with clients that the shared list represents priorities and intentions, not guarantees, since weather, access, and countless other real-world factors can affect what's actually achievable on any given day. Setting that expectation upfront avoids disappointment if conditions genuinely prevent capturing something on the original list, while still giving the client confidence that the trip is being planned deliberately rather than left to chance.
I've also found it useful to revisit the shared list with clients mid-trip on longer projects, giving a brief update on what's been captured relative to the plan and flagging early if any priority item looks genuinely at risk due to conditions. That proactive communication, rather than waiting until final delivery to surface any gaps, tends to be received far better and keeps the client feeling informed rather than anxious about an unknown outcome.
What I've Learned Refining This Process Over Time
The biggest shift in how I build shot lists over the years hasn't been in the format itself but in how much I trust the list to hold priorities versus how much I lean on in-the-moment instinct. Earlier in my career, I built exhaustive, highly detailed lists partly out of insecurity, wanting a document that felt thorough enough to guarantee good results. Over time, I've learned that an overly detailed list can actually become a distraction, competing with genuine attentiveness to what's unfolding in front of me.
The lists I build now are considerably leaner than what I built early in my career, focused on the handful of genuinely essential priorities rather than an exhaustive catalog of every possible shot. That leanness makes the list faster to reference in the field and easier to hold in mind even without constantly checking it, which has actually improved both my planning discipline and my ability to stay present and responsive once shooting.
Building a shot list this way, detailed enough to genuinely guide planning and communication, flexible enough to not fight against what actually happens in the field, has become one of the most consistently useful habits in how I approach every trip.
Adapting the Shot List Format to the Trip Type
A shot list for a tightly scheduled single-day client shoot looks and functions differently than one for an extended personal expedition, and I've learned to adapt the format to actually match what the trip needs rather than using a single rigid template for every situation. A single-day client shoot benefits from a more detailed, hour-by-hour structured list, since the compressed timeline leaves less room to improvise a plan on the fly.
A longer expedition or multi-day trip benefits from a looser, more thematic list, organized around broad narrative beats, the departure, the grind of the middle days, the arrival or summit, rather than a rigid shot-by-shot schedule that would almost certainly need to be abandoned given how much can shift over multiple days in the field. Trying to apply a single-day level of scheduling detail to a multi-day expedition tends to produce a document that's abandoned within the first few hours simply because it can't keep up with how the actual trip unfolds.
For trips involving other collaborators, an assistant, a second shooter, a crew, I also build a slightly more formal version of the list specifically to communicate priorities across the team, since a shot list that only lives in my own head doesn't help anyone else on a shoot understand what matters most if we get separated or need to divide coverage responsibilities during a busy day.
Planning trips that balance real preparation with genuine flexibility is part of the bigger system I cover in The Adventure Travel Photographer's Playbook.
Tools I Actually Use to Build and Track the List
I've tried a range of different tools over the years for actually building and referencing shot lists in the field, from simple paper notebooks to dedicated apps, and I've settled on the simplest option that reliably works rather than the most feature-rich one. A basic digital notes app, accessible offline and synced across a phone and a backup device, has proven more reliable in the field than more elaborate dedicated planning software, which often assumes a level of connectivity or screen interaction that isn't practical mid-shoot.
For trips where I'm working entirely alone in remote conditions, I still keep a physical paper backup of the core list, since electronics can fail, batteries can die, and a laminated or simply durable paper copy of the highest-priority items provides a reliable fallback that doesn't depend on any device working correctly.
Whatever the tool, I try to keep the actual reference format extremely simple and fast to scan, short phrases rather than long descriptions, organized so the highest priorities are immediately visible without scrolling or searching. The goal is always speed and low friction when checking the list in the field, since anything that takes real time or attention to reference defeats the purpose of having a quick, reliable planning tool in the first place.
Debriefing Against the List After a Trip Wraps
The shot list's usefulness doesn't end once a trip is over, I also use it as a structured tool for reviewing how the trip actually went, comparing what was planned against what was captured and, more importantly, understanding why any gaps occurred. That honest debrief has taught me more about my own planning weaknesses than almost any other single practice I've built into my workflow.
Some gaps trace back to genuinely unpredictable factors, weather, access issues, subject availability, that no amount of better planning could have prevented. Other gaps trace back to planning mistakes I can actually learn from and correct, underestimating how long a specific sequence would take, or failing to account for a logistical constraint that should have been anticipated. Distinguishing between these two categories honestly, rather than treating every gap as equally unavoidable, is what actually improves planning over successive trips.
I keep a simple running log of these debrief notes across trips, which over time has built a genuinely useful reference for planning future projects, patterns in what tends to get missed, what kinds of trips consistently run over their planned timeline, and other recurring lessons that a single trip's debrief alone wouldn't reveal but that become clear looking across many trips together.
Why I Keep Every Old Shot List
I never delete or discard old shot lists once a trip is complete, even long after the project has been delivered and closed out. Archived shot lists from past trips to similar locations or activities have become one of the most useful planning resources I have, giving me a real starting reference rather than building every new list entirely from scratch each time a broadly similar project comes up.
Reviewing an old list before building a new one for a similar trip type also serves as a useful reminder of past lessons, reminding me of specific challenges or gaps that came up previously so I can proactively address them in the new plan rather than potentially repeating the same oversight. This accumulated library of past lists, effectively a growing internal knowledge base built entirely from my own direct field experience, has become genuinely valuable in a way that would be hard to replicate through research or advice from other sources alone, and it grows more valuable with every additional trip added to it. I'd encourage any photographer who currently discards old planning documents to start keeping them, even informally, since their value compounds in ways that aren't obvious until you actually have a few years of them to draw from. A simple folder of past lists, organized loosely by location or activity type, is enough to start building this resource without any special system or software required. What matters is starting the habit now rather than waiting until some future point when the archive would already be more valuable had it been kept from the beginning. The best time to start was years ago, and the second best time is the next trip you plan.
Building a shot list this way, informed by direct accumulated experience rather than built fresh from theory every time, has become one of the quieter but most valuable parts of how I plan every new trip, adventure photography included.
Reflection Questions
- Does your shot list function as a flexible guide, or does it become a rigid script you feel locked into?
- Do you share a version of your shot list with clients to confirm alignment before a trip?
- How do you decide when an unplanned moment should take priority over your planned list?
- Do you do a deliberate final review against your shot list before a trip wraps?
Dalton Johnson is a professional adventure and editorial photographer with over a decade of experience shooting 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.