Setting Expectations Before a Shoot Even Starts

The worst client conflicts I've had in my career almost never traced back to bad weather, a missed flight, or a genuinely difficult shoot day. They traced back to a mismatch between what a client thought they were getting and what I actually delivered, a gap that existed from the very first phone call and simply hadn't been surfaced until delivery day, when it was far too late to fix cheaply or gracefully.

Setting expectations properly before a shoot starts has become one of the most valuable, and least glamorous, skills in my business, more valuable in practice than almost any technical skill I've built. If you're refining how you manage client relationships across a full project lifecycle, I cover that framework in The Adventure Travel Photographer's Playbook. Here's exactly how I set clear expectations with a client before a shoot even starts.

Why Vague Expectations Cause More Problems Than Bad Weather

Bad weather is a known, expected variable that most clients accept as part of outdoor work, and it rarely becomes a genuine relationship problem because everyone understands, going in, that weather is unpredictable. Vague expectations are different, because a client usually doesn't realize their assumption was ever unstated until it collides with reality.

A client who assumes "a few final images" means fifty finished files, when I was planning to deliver fifteen, doesn't discover that mismatch during a rainstorm, they discover it during delivery, when the relationship is already strained by a number that feels like a letdown regardless of how good the actual images are.

I've learned that nearly every client conflict I've had traces back to an assumption that went unstated on one side or the other, not to an external circumstance neither of us controlled. That realization is what pushed me to build a deliberate expectation-setting process rather than relying on general goodwill to smooth over gaps.

The Pre-Shoot Call: What I Actually Cover Every Time

Every project, regardless of size, gets a dedicated pre-shoot call rather than relying purely on email threads, since a live conversation surfaces misunderstandings far faster than back-and-forth messages that can each be read differently by each side. I treat this call as non-negotiable, even for smaller assignments where it might feel like overkill.

On that call, I walk through the shot list, the schedule, the deliverable count and format, the timeline for delivery, and any specific brand or usage requirements, asking the client to actively confirm each point rather than just presenting the plan and assuming silence means agreement. Genuine confirmation, not passive acceptance, is the actual goal of the call.

I also use this call to surface anything I'm uncertain about myself, an ambiguous brief detail, an assumption I'm making about location access, rather than guessing quietly and hoping I guessed correctly. Clients consistently tell me they appreciate this kind of direct question far more than a photographer who seems to be guessing.

Written Confirmation: Putting Verbal Agreements in Writing

A verbal agreement on a call, however clear it felt in the moment, fades in both parties' memory and can get remembered slightly differently by each side weeks later. I follow every pre-shoot call with a written summary email covering every point discussed, specifically asking for written confirmation rather than assuming silence equals agreement.

This written record has saved more than one relationship when a disagreement arose later about what was actually agreed to. Being able to point to a specific written confirmation, rather than relying on competing memories of a conversation, resolves a potential conflict quickly and keeps it from becoming a larger trust issue.

I've also learned to keep this written summary genuinely readable rather than burying it in dense contract language, since a client who actually reads and confirms a plain-language summary provides far more real protection than a client who skims past a long legal document without absorbing the specific details that actually matter for that project.

Shot Lists as an Expectation-Setting Tool, Not Just a Checklist

A shot list is often treated purely as a working document for the shoot day itself, but I've come to see it as one of the most powerful expectation-setting tools available, since a specific, detailed shot list makes a client's mental image of the final deliverable concrete rather than left to assumption.

I build shot lists collaboratively with a client whenever possible, rather than presenting a finished list for approval, since the back-and-forth of building it together surfaces disagreements about priorities and feasibility while there's still time to adjust, rather than discovering a mismatch on shoot day itself.

I also flag, directly within the shot list conversation, anything that seems logistically unrealistic given the timeline or conditions, rather than agreeing to an ambitious list and hoping it works out. A client who hears "this specific shot may not be achievable given the light window" before the shoot day is a client who isn't blindsided by its absence later.

Weather, Timing, and Contingency Plans Discussed Upfront

Outdoor adventure work carries genuine weather risk, and I discuss contingency plans explicitly before a shoot rather than only addressing weather once it actually becomes a problem. What happens if the light window closes early, what happens if a planned location becomes inaccessible, what the actual backup plan looks like, all get covered before the shoot day itself.

This conversation also covers realistic timing expectations, how many setups are actually achievable in a given day given travel time between locations, subject availability, and light conditions, rather than letting a client assume an ambitious shot list and a compressed timeline can both be honored simultaneously without some compromise.

I've found that clients respond well to this kind of upfront honesty about constraints, even when it means adjusting their original vision, because it demonstrates that I'm planning realistically rather than simply agreeing to everything and hoping it works out on the day itself.

Setting Expectations Around Deliverables and Turnaround

Deliverable expectations get specific numbers and specific formats confirmed in writing before the shoot, not vague language like "a good selection of final images," since "a good selection" means something different to every client and every photographer, and that gap has caused real friction for me before I tightened this practice.

Turnaround timing gets the same specific treatment. I quote a realistic delivery window based on my actual current workload rather than an optimistic estimate meant to sound impressive during the sales conversation, since an optimistic timeline that slips damages trust far more than a longer, honestly quoted timeline that gets met exactly as promised.

I've also learned to build a small buffer into every quoted timeline rather than promising the fastest theoretically possible turnaround, since unexpected delays, a corrupted card, a slower-than-expected edit pass, happen often enough that a buffer protects the relationship far more than it costs in perceived speed.

What Happens When a Client's Expectations Are Unrealistic

Sometimes a client's expectations, once surfaced during the pre-shoot process, are genuinely unrealistic given budget, timeline, or physical conditions, and I've learned that addressing this directly and early is far better for the relationship than quietly trying to exceed an impossible standard and inevitably falling short.

I frame these conversations around tradeoffs rather than flat refusals, explaining specifically what would need to change, more budget, more time, a different location, to make an ambitious request achievable, rather than simply saying no without offering the client a clear picture of what the actual constraints are.

Most clients respond well to this kind of honest tradeoff conversation, and I've found that being the photographer willing to have it, rather than the one who agrees to everything and struggles silently later, builds more long-term trust than any single perfectly executed shoot day would on its own.

Expectations Around Usage Rights and Scope Creep

Usage rights are one of the most common sources of expectation mismatch I've encountered, since a client's assumption about how broadly they can use delivered images, across which platforms, for how long, sometimes differs significantly from what was actually contracted, and that gap can turn into a genuine legal and financial problem if it isn't clarified upfront.

I now spell out usage rights in specific, plain language before a shoot, not just in dense contract language, covering exactly which platforms, which duration, and which specific uses are included, and what falls outside that scope and would require a separate conversation and separate compensation.

Scope creep during a shoot, a client asking for "just one more setup" repeatedly through the day, gets addressed with the same upfront clarity. I set expectations before the shoot day about how additional requests beyond the agreed shot list will be handled, which has prevented a number of awkward on-the-day conversations about unplanned extra work.

Setting Expectations With the Talent or Subject, Not Just the Client

Expectation-setting doesn't stop with the paying client, since the actual subject in front of the camera, an athlete, a model, a brand ambassador, has their own set of assumptions about the shoot day that need addressing separately. A subject who doesn't know how long a day will realistically run, or what specific activities will be asked of them, can become fatigued or frustrated in ways that show up directly in the final images.

I now hold a brief, separate conversation with any subject before a shoot day starts, covering the general schedule, what specific shots or activities are planned, and roughly how physically demanding the day will be, since a subject who understands the plan tends to perform more consistently through a long day than one who's simply following instructions without any sense of the bigger picture.

This matters especially for physically demanding adventure shoots, where a subject repeating a climbing move or a paddle stroke multiple times for the camera needs to understand that repetition is coming, rather than assuming a single take will suffice. Setting that expectation upfront has noticeably improved subject energy and cooperation across a full shoot day compared to shoots where I skipped this conversation.

Documenting Expectations for Multi-Day and Recurring Projects

Longer, multi-day assignments and recurring client relationships need expectation-setting that extends beyond a single pre-shoot call, since priorities and circumstances can shift meaningfully across a multi-day shoot in ways that a single upfront conversation can't fully anticipate. I build in brief daily check-ins on longer projects specifically to catch and address any expectation drift before it becomes a larger problem.

For recurring clients, I've learned not to assume expectations from a previous project automatically carry over to a new one, even when the client and general type of work are the same. A brand's priorities, budget, or creative direction can shift between projects, and re-confirming expectations at the start of each new engagement, rather than assuming continuity, has prevented misunderstandings that would otherwise resurface repeatedly across an ongoing relationship.

I keep a simple written record of expectations set for every project, client, subject, and deliverable details together, that I can reference quickly at the start of a new engagement with a returning client. This record has proven valuable for catching subtle expectation changes I might otherwise have missed by relying purely on memory of how a previous, similar project went.

Handling a Mismatch When It Happens Anyway

Even with careful upfront expectation-setting, a mismatch sometimes still surfaces, and how I handle that moment matters as much as the prevention work itself. I address a surfaced mismatch directly and promptly rather than hoping a client won't notice or letting an uncomfortable conversation drift unaddressed, since a quickly acknowledged gap is far easier to resolve than one that's allowed to fester.

I've learned to lead these conversations with genuine ownership rather than defensiveness, acknowledging clearly where a miscommunication happened on my end even when the client also shares some responsibility for an unstated assumption. Clients remember how a problem gets handled far more than they remember the problem itself, and a photographer who handles a mismatch honestly and fairly often ends up with a stronger relationship than one who never had a mismatch to navigate in the first place.

Offering a concrete, specific resolution, rather than a vague apology, has consistently repaired these situations faster. Whether that means an additional round of edits, an adjusted timeline, or a clear explanation of what actually happened and why, giving the client something specific to respond to moves the conversation toward resolution rather than leaving it to linger unresolved.

I also treat every genuine mismatch as useful information about a gap in my own process, updating my pre-shoot call checklist or written summary template afterward so the same specific misunderstanding is less likely to recur with a future client. This habit of turning an uncomfortable moment into a concrete process improvement has meaningfully reduced how often similar mismatches resurface over time, and it's turned what used to feel like isolated failures into a steadily improving system instead, one that gets a little more reliable with every single project rather than quietly repeating the exact same avoidable gaps year after year on client after client, which is ultimately a far better use of an uncomfortable conversation than simply moving on and hoping it doesn't happen again.

What I'd Tell Myself Before My Early Client Shoots

I'd tell myself that a dedicated pre-shoot call, even for a small project that feels too simple to need one, prevents more problems than any amount of talent or hustle on the actual shoot day. Most of my early client friction came from skipping this step because a project seemed straightforward enough not to need it.

I'd tell myself to put every verbal agreement in writing immediately afterward, and to ask for actual confirmation rather than assuming silence means agreement, since competing memories of a conversation have caused more strain in my client relationships than any technical mistake I've ever made on a shoot itself.

Mostly I'd tell myself that setting clear expectations isn't about being overly formal or bureaucratic with clients, it's about genuinely respecting their time and money enough to make sure we're both picturing the same outcome before either of us commits real resources to it. If you want a deeper framework for managing client relationships through an entire project, I lay that out in The Adventure Photographer's Playbook.

Reflection Questions

1. Do you hold a dedicated pre-shoot call for every project, or only for the ones that feel complex enough to need it?
2. Have you ever had a client conflict that, in hindsight, traced back to an unstated assumption rather than an external circumstance?
3. Are your deliverable counts and turnaround timelines specific numbers in writing, or vague language both sides interpret differently?
4. How do you currently handle scope creep or "just one more setup" requests during a shoot day?

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.