What I Do When Two Clients Want the Same Week

Eventually, if your business is working, this happens: two clients want you for the exact same week, and you can only be in one place. It's a good problem to have, but it's still a problem, and how you handle it says a lot about how you run your business.

Here's how I actually approach it when it comes up. If you want the full system I use for managing clients and scheduling, it's part of a bigger framework in The Adventure Travel Photographer's Playbook.

This is a situation nearly every working photographer eventually faces, but it rarely gets discussed as its own topic worth thinking through deliberately. Most of the advice out there focuses on landing clients in the first place, and comparatively little addresses what happens once you're successful enough that demand starts genuinely outpacing your availability. That's exactly the gap I want to fill here.

The First Move: Try to Shift a Date

Before treating this as a conflict that requires choosing one client over another, my first move is always to see if either date actually has flexibility. A lot of the time, a shoot week feels fixed because nobody has asked whether it actually is. Client schedules often have more give than they initially present, especially if a project doesn't hinge on a specific seasonal window or event.

Asking this question directly, and early, solves the problem more often than people expect. It also signals to both clients that you're being proactive and transparent rather than just picking whoever seems more important and letting the other one figure it out on their own.

I've found it helps to ask about flexibility in a specific, low-pressure way rather than a vague one. Instead of asking generally whether a date could move, I'll ask about the actual constraint behind it: is this tied to a product launch, a seasonal window, another vendor's availability, or is it more of a preference. Understanding the real reason behind a date often reveals room to move that wouldn't have come up from a general question.

I've also learned to ask this question as early as possible, the moment a second inquiry for an overlapping date comes in, rather than waiting until both are further along in planning. The earlier a potential conflict surfaces, the more options everyone actually has. Waiting until contracts are close to signed before raising the possibility of a date shift puts unnecessary pressure on a conversation that could have been simple if it happened a few weeks sooner.

I also keep my calendar genuinely up to date and visible to myself at a glance, which sounds obvious but is easy to let slip during a busy season. A tentative hold that never got formally confirmed or released, sitting quietly on a calendar, has caused more than one near-miss where I almost double-booked a date because an old placeholder wasn't cleared out. A clean, current calendar is a small piece of infrastructure that prevents a meaningful share of these conflicts from happening in the first place.

I've also started building in a standard policy around how long a tentative hold can sit unconfirmed before it automatically releases. Without that kind of rule, it's easy to let a soft hold linger indefinitely out of a reluctance to push a client for a firm answer, which is exactly how a date ends up double-booked in the first place. A clear, upfront policy on hold duration, communicated to the client when the hold is first placed, keeps this from becoming a recurring problem.

When Neither Date Can Move

If shifting isn't possible for either client, and I actually have to choose, my default tiebreaker is simple: whoever approached first gets priority. It's a fair, defensible rule that doesn't require judging the relative value of either relationship, and it's easy to explain to the client who doesn't get the slot without it feeling personal.

That said, I don't treat "whoever came first" as an absolute rule that overrides every other consideration. There are situations where portfolio value or the overall size and scope of a project genuinely matters more to where the business is heading, and in those cases, I'll factor that in honestly rather than pretending fairness is the only variable that matters. Running a business means making real tradeoffs sometimes, and pretending otherwise doesn't actually serve either client well.

What I try to avoid is letting the decision drag out while I quietly weigh both options against each other for too long. The longer a decision sits unresolved, the less time either client has to make their own alternate plans if they need to. I'd rather make the call promptly, even if it's not a perfectly optimized decision, than let indecision cost both clients time they could have used elsewhere.

I also think it's worth being honest with yourself about your own biases before applying any tiebreaker. It's easy to unconsciously favor whichever client feels more exciting or prestigious in the moment, even when a fair, previously-agreed rule points the other way. Naming the tiebreaker rule for yourself before a conflict actually happens, rather than deciding in the moment when a more appealing option is sitting right in front of you, makes it much easier to actually follow it consistently.

There's also a version of this conflict that's less obvious: two projects that don't fully overlap on dates but that would still stretch me too thin if I tried to do both, back-to-back travel with no recovery time, or overlapping pre-production windows that would compromise the quality of planning for either project. I try to apply the same honest evaluation to these near-conflicts as I do to true double-bookings, rather than only treating an exact date overlap as worth this level of consideration.

I also weigh recovery time specifically, since adventure photography is physically demanding in a way that a lot of other photography work isn't. Accepting back-to-back trips with no rest between them might be technically possible on the calendar, but it can compromise the quality of work on the second trip in ways that aren't always obvious until you're in the middle of it, exhausted and running on depleted reserves. That physical reality is a legitimate factor in scheduling decisions, not just an excuse to say no to work.

How I Actually Communicate the Decision

Whichever way the decision goes, how you communicate it matters as much as the decision itself. I try to be direct and honest rather than vague. If a client isn't getting the date, they deserve to know clearly, as early as possible, so they have real time to adjust their own plans instead of finding out at the last minute.

I also try to offer something concrete when I have to turn a date down: an alternative week if one exists, a referral to another photographer if that's genuinely useful to them, or at minimum an honest, specific explanation of why the scheduling conflict happened. Clients respond far better to a clear, respectful no than to a vague maybe that eventually turns into a no anyway.

A referral, in particular, tends to leave a much better impression than people expect. Recommending another photographer whose work you trust, even for a client you had to turn away, signals that you care about the client's project succeeding, not just about your own calendar. That kind of goodwill has come back around more than once in the form of a client returning for a future project once their original date conflict was no longer an issue.

I try to deliver this kind of news over a call or a real conversation rather than a short message whenever the relationship and the situation allow for it. A scheduling conflict handled over a quick, impersonal text can come across as dismissive even when that's not the intent at all. A few minutes on the phone, explaining the situation directly and answering any questions on the spot, tends to leave the relationship in a much better place than the same information delivered in a single line of text.

I also try to follow up in writing after that conversation, a short email confirming what was discussed and any alternative dates or referrals offered. This isn't about covering myself legally so much as making sure nothing gets lost or misremembered on either side. A quick written summary after a difficult conversation has more than once clarified a detail that could have otherwise turned into a miscommunication down the line.

I try to give the disappointed client a real answer to the obvious next question too: what happens now. Whether that's a concrete alternative date, a name and introduction to another photographer, or an honest timeline for when I might have availability again, leaving that question unanswered is what turns a professional no into a frustrating dead end for the client on the other side of it.

Why This System Matters Beyond Just the Calendar

The way you handle a scheduling conflict is a small moment that says a lot about how seriously you take your business and your relationships. A photographer who juggles conflicting commitments carelessly, or who overcommits and then scrambles, damages trust in a way that's hard to rebuild. A photographer who handles it transparently, even when the answer disappoints someone, builds a reputation for being straightforward to work with, which matters as much as the actual photography over a long career.

Scheduling conflicts are also a useful signal about demand. If you're regularly running into competing requests for the same weeks, that's real information about where your business is heading and whether it's time to think about raising rates, bringing on help, or being more selective about which projects you take on in the first place. It's worth actually tracking how often this happens rather than treating each conflict as an isolated event. A pattern of repeated conflicts in the same season, for example, might tell you something specific about when demand peaks for your type of work, information that's genuinely useful for planning the following year.

I've started keeping a simple running note of every scheduling conflict I encounter, including the rough dates involved and which client ultimately got the slot. Looking back over a year of that record has told me more about seasonal demand patterns in my specific niche than any amount of general industry advice could have, since it's built entirely from my own actual business rather than someone else's averages.

I'd also say that being willing to say no, clearly and without excessive apology, is a skill that took time to build. Early in my career, every scheduling conflict felt like a crisis I needed to fully solve for both clients somehow. Over time I've come to see that a clean, honest no, delivered with genuine care for the client who doesn't get the date, is a completely normal and healthy part of running a business that has more demand than a single photographer can personally fulfill.

The photographers I respect most in this business are the ones who handle a full calendar gracefully rather than either overcommitting to please everyone or turning scheduling conflicts into a source of constant stress. It's a genuinely learnable skill, and it gets easier the more you accept that a certain amount of scheduling tension is simply what a healthy, in-demand business looks like, not a sign that something's going wrong.

I'd also say this entire approach only works if it's applied consistently rather than selectively. Bending the rules for a client who pushes back hard, while holding firm with a more agreeable one, undermines the fairness of the whole system and tends to become obvious to clients over time even when they don't say so directly. Treating every scheduling conflict with the same honest process, regardless of how much pressure a given client applies, is what actually builds the reputation for fairness that makes this whole approach worth the effort in the first place.

I'd also point out that this whole system depends on having clear terms established up front, before a conflict ever arises, not improvised in the moment under pressure from two clients who both genuinely want the same week. A simple line in a contract or booking confirmation about how scheduling conflicts get resolved, first-come priority with room for exceptions in the photographer's discretion, sets expectations before any tension exists. Clients rarely object to a policy stated plainly and fairly at the outset. What actually damages a relationship is discovering, after the fact, that a process existed that they were never told about, especially if it feels like it worked against them without explanation. Building that clarity into the very first conversation with a client, long before any scheduling pressure ever materializes, is a small piece of contract language that has saved a lot of awkward conversations down the line, and it's one of the cheapest pieces of business infrastructure a growing photographer can put in place, especially relative to the goodwill it protects and the awkward conversations it quietly prevents down the road, long after the specific conflict itself has been completely forgotten by everyone involved and the working relationship has simply moved forward, unbothered, without any lingering resentment on either side.

Building a business that can handle growth without falling apart at the seams is exactly what I cover in The Adventure Travel Photographer's Playbook.

Reflection Questions

1. The next time you have a scheduling conflict, will you ask about flexibility before assuming the dates are fixed?
2. Do you have a consistent, fair rule for breaking ties, or does it change case by case?
3. How do you currently communicate a scheduling no to a client, and does it leave them with anything concrete?
4. How often are you running into competing requests, and what does that tell you about where your business is heading?

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.