What Happens When a Brand Ghosts You Mid-Project
People ask me this question more than almost any other, usually with a specific fear behind it: what do you do when a brand just stops responding halfway through a project. My honest answer surprises them. It hasn't happened to me, not in any project that actually mattered financially, and that's not luck. It's the direct result of a small set of habits I built into every contract and every payment structure long before the question ever needed to come up.
That's not me dodging the question, either — it's the actual answer, and I think it's more useful than a horror story would be. If you want the specific contract language and payment structure I use to prevent this exact scenario, it's laid out in full in The Adventure Travel Photographer's Playbook. But the underlying logic is simple enough to walk through here.
Why This Almost Never Actually Happens to Me
The honest starting point is that going quiet mid-project is rare, and it's rare because most reasonably professional brands and marketing teams have their own internal accountability that makes disappearing mid-project a genuinely unusual move on their end. The bigger risk isn't malicious ghosting — it's slow internal approval processes that feel like silence from the outside but are really just bureaucracy.
What actually protects me from both scenarios, malicious or bureaucratic, is the same system: a signed contract before any work begins, and a payment structure that never leaves me financially exposed if communication does break down. I credit the fact that this has never turned into a real financial problem almost entirely to those two things being non-negotiable on every project.
It's worth separating the emotional experience from the financial one here. Even a well-protected photographer can feel frustrated by a quiet client. But frustration and financial exposure are two very different problems, and the systems I use are built to solve the second one specifically, which usually takes most of the sting out of the first.
The Signed Contract Comes Before Anything Else
I don't start meaningful production work without a signed agreement in place, full stop. That contract does more than formalize the relationship — it sets clear expectations for both sides about deliverables, timeline, and what happens if either party doesn't hold up their end. A brand that's signed a real agreement has a different relationship to the project than one that's still operating on a verbal understanding.
This isn't about distrust of any specific client. It's about removing ambiguity before ambiguity has a chance to cause a problem. A lot of photographers skip this step with brands that feel established or reputable, assuming a big name is inherently lower risk. Company size has very little to do with whether a specific project moves smoothly through an organization's internal approval chain.
The contract also gives me something concrete to point back to if a project does slow down. Instead of an emotionally charged conversation about why someone's gone quiet, I can reference specific terms both sides already agreed to, which keeps the conversation practical instead of personal.
Why I Take Roughly Half Upfront
The other piece that removes most of the financial risk is collecting a substantial deposit before production begins, generally around half of the total project fee. That deposit covers real production costs — travel, gear, time — regardless of what happens with the rest of the relationship after the shoot itself wraps.
This isn't an unusual ask in commercial photography, and clients who balk at a reasonable deposit are often telling you something useful about how the rest of the project is likely to go. A deposit signals that both sides are genuinely committed before either one invests significant time or resources, and it protects the photographer from being the only party carrying financial risk in the relationship.
Structuring payment this way also changes the emotional stakes if a client does go quiet during editing or delivery. The production costs are already covered. What's left outstanding is the value of the finished work, which is a different, less urgent kind of exposure than having fronted everything with nothing collected.
Deliverables Stay Withheld Until the Final Invoice Clears
The other structural piece is straightforward: final, high-resolution deliverables don't go out until the final invoice is paid in full. Low-res proofs or a limited preview gallery might go out earlier in the process to keep the project moving, but the actual usable assets a brand needs for their campaign stay withheld until payment is complete.
This single practice removes most of the incentive for a client to simply stop responding once they've seen the work. There's nothing to gain by going quiet if going quiet means the deliverables they actually need never arrive. It shifts the leverage back toward the photographer in a way that a lot of freelancers never build into their process.
It's a simple rule, but it only works if it's applied consistently, every project, without exceptions made for clients who feel too big or too reputable to need it. The moment you make an exception for one client, you've told yourself the rule was optional, and optional rules don't protect you when you actually need them to.
What I'd Actually Do If It Happened
Even with these systems in place, I've thought through what I'd do if a project genuinely went quiet with real money and real deliverables on the line. The first move would be a direct, professional follow-up referencing the specific contract terms and next payment or milestone due, rather than a vague check-in. Specificity tends to get a faster response than an open-ended "just checking in."
If that didn't produce a response within a reasonable window, the next step would be escalating through whatever channel actually gets attention — a different contact at the company, a written notice referencing the contract's terms around non-payment or breach. Most agreements include language for exactly this scenario, which is another reason the contract has to exist before the work starts, not after a problem shows up.
Beyond that, it becomes a business decision about how much time and cost it's worth to pursue further, weighed against the size of the project and the relationship's future value. Having runway in the business, something I've written about elsewhere, is part of what makes that decision calmer rather than desperate.
Internal Silence Isn't Always Ghosting
It's worth distinguishing true ghosting from the much more common experience of a project going quiet because of internal approval delays on the client's side. Marketing and brand teams often move through layers of internal sign-off that have nothing to do with the photographer or the quality of the work, and a slow week of silence is frequently just that process running in the background.
I try not to assume the worst the moment a response is a few days late. A brief, low-pressure check-in referencing the next expected milestone usually clarifies which situation you're actually in — genuine internal delay, or an actual communication breakdown worth escalating. Jumping straight to an aggressive follow-up over normal internal lag can damage a relationship that was never actually at risk.
This distinction matters because the response should look different depending on which one you're facing. Internal delay calls for patience and a light touch. A genuine breakdown calls for the more formal, contract-referencing escalation described above. Confusing the two in either direction tends to make things worse.
How This Changes the Way I Scope New Clients
Because I've built these protections into every project, I don't approach new or unfamiliar clients with extra suspicion just because they're new. The systems are the same regardless of who I'm working with, which means I don't have to make a judgment call about which clients are trustworthy enough to skip a deposit or a contract. Nobody skips it, so trust never has to be guessed at upfront.
This has the side benefit of making early client conversations more straightforward. Explaining a standard deposit and contract process to a new client is much easier than explaining why this particular client needs extra protections that others don't. Consistency removes an awkward conversation that a lot of photographers end up having anyway when they try to assess risk case by case.
It also means I don't waste energy trying to predict which clients might eventually cause a problem. The protections exist regardless of that prediction, so I can focus my judgment on whether a project is a good fit creatively and financially, rather than trying to guess at a brand's internal reliability in advance.
Why the System Matters More Than the Instinct
A lot of advice about handling difficult clients focuses on reading people well — trusting your gut about who might flake or go quiet. I don't discount that instinct entirely, but I've come to trust systems more than instinct, because systems protect you even when your read on a person or company turns out to be wrong.
Instinct is useful for deciding whether to take a project at all. It's a much less reliable tool for protecting you financially once you're already committed. A signed contract, a real deposit, and withheld final deliverables do the protecting regardless of whether your instinct about a specific client happened to be accurate.
That's ultimately the mindset shift that's kept this from ever becoming a real problem in my business: build the protection into the process itself, not into your ability to correctly judge every client you take on. Judgment fails sometimes. Process doesn't, as long as you actually follow it.
How This Plays Out With Agencies Instead of Direct Brands
Working through an agency adds a layer between the photographer and the actual brand paying for the work, and that extra layer changes how a communication gap tends to show up. An agency contact going quiet doesn't always mean the underlying brand relationship or budget has disappeared, it can just as easily mean an internal handoff or personnel change happened on the agency side without anyone thinking to loop the photographer in.
The same contract and deposit protections apply regardless of whether the paying party is a brand directly or an agency acting on their behalf, but I've learned to ask, at the very start of an agency relationship, who the actual point of continuity is if my primary contact changes roles or leaves. Getting that answer upfront makes a mid-project handoff far less disruptive if it happens.
I also make sure the contract itself is with an entity that will still exist and be accountable regardless of which individual person is currently the day-to-day contact. A contract tied to a company, not a single person's ongoing involvement, holds up better if a project spans a personnel change on the client or agency side partway through.
Why I Don't Treat This as Purely a Legal Problem
It would be easy to think of contract terms and deposits as purely a legal safety net, something that only matters if a dispute actually escalates. In practice, I think their bigger value is behavioral rather than legal. Clients who've signed a clear, fair agreement tend to behave differently throughout a project than clients operating on a looser, more informal understanding, even when no dispute ever actually happens.
A signed contract creates a shared, explicit reference point that both sides can return to without it feeling personal or accusatory. Referring back to an agreed deliverable date feels like project management. Referring back to a vague verbal understanding that one side remembers differently than the other feels like conflict. That distinction alone prevents a lot of the friction that could otherwise turn into something resembling ghosting.
I think this is why the practice has worked as well as it has for me over the years. It's not really about winning a hypothetical future dispute. It's about removing the ambiguity that makes disputes, and communication breakdowns, more likely to happen in the first place.
How I Handle the First Few Days of Genuine Silence
There's a specific window, usually the first few days after an expected response doesn't arrive, where the right move is patience rather than escalation. Jumping straight to a formal, contract-referencing message the moment a reply is a day late tends to read as disproportionate, and it can damage a relationship that was never actually at risk of a real problem.
I use that early window for a single, low-pressure check-in, framed around the next concrete step rather than the silence itself. Something as simple as confirming an upcoming date or asking whether feedback is still on track keeps the tone collaborative rather than confrontational, while still creating a written record of outreach if the situation does eventually need to escalate.
Only once that early, patient window has passed without any response do I treat the situation as a genuine communication breakdown rather than normal, forgivable delay. That sequencing protects relationships that are actually fine from an overreaction, while still leaving room to escalate firmly if the silence turns out to be real.
Documenting the Relationship as It Happens, Not After a Problem Starts
One habit that's quietly protected me more than any single contract clause is keeping a running written record of key decisions and approvals as a project moves forward, not just at the signing stage. A quick email summarizing what was agreed on a call, or confirming a scope change in writing the same day it's discussed, means there's never a scramble to reconstruct what actually happened if a question comes up later.
This isn't about building a legal case preemptively against every client. It's a genuinely low-effort habit that pays off disproportionately the rare times a project does hit friction, since the record already exists rather than needing to be assembled defensively after the fact, which tends to feel adversarial in a way that a routine, ongoing habit never does.
I treat this the same way I treat the contract and deposit, as infrastructure that exists quietly in the background on every project, doing its job whether or not it's ever actually needed. Most projects never require any of it. The ones that do are exactly why the habit is worth keeping consistent.
These are the exact deposit structures, contract clauses, and delivery terms I use on every project, laid out step by step in The Adventure Photographer's Playbook, if you want to build the same protection into your own workflow.
Reflection Questions
- Does every one of your current projects have a signed agreement in place before production work begins?
- What percentage of your project fee do you collect before you start incurring real production costs?
- Are your final, high-resolution deliverables ever released before the final invoice is actually paid?
- How would you tell the difference between normal internal delay and a genuine communication breakdown with a client?
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.