The Contract Mistake That Taught Me to Always Get It in Writing
Early in my career, I took a job on the strength of a warm phone call and a handshake-equivalent email exchange, the kind of casual back-and-forth that felt friendly enough that formalizing it seemed almost insulting to the relationship. The scope changed twice during production, the delivery timeline shifted without ever being renegotiated on paper, and when it came time to invoice, the client and I discovered we had two entirely different understandings of what had actually been agreed to.
Nobody acted in bad faith. That's the part that still sticks with me. It wasn't a scam or a dishonest client, it was two reasonable people who had genuinely different memories of a verbal conversation, with nothing written down to settle the disagreement. That single experience changed how I run every client relationship since, and if you want the fuller framework I now use for contracts and scope management across an entire client roster, I lay it out in The Adventure Travel Photographer's Playbook. Here, I want to walk through exactly what went wrong and what I do differently now.
What the Verbal Agreement Actually Covered
The original conversation covered the basics well enough: a day rate, a general subject, a rough delivery window. What it didn't cover, because neither of us thought to raise it explicitly, was exactly how many final images were included, what usage rights came with the fee, and what would happen if the client wanted additional shooting days added mid-project.
At the time, none of those gaps felt significant. The conversation had a clear, friendly tone, and I assumed reasonable good faith would fill in any details we hadn't explicitly spelled out. That assumption turned out to be the actual mistake, not any specific term we disagreed on later.
Looking back, the verbal agreement covered maybe sixty percent of what actually mattered to the project's outcome. The other forty percent, the part that ended up causing the dispute, simply never came up in conversation at all, because neither of us knew to ask about it until it became relevant mid-shoot.
Where the Scope Actually Drifted
The drift started small. The client asked, mid-shoot, for one additional setup that hadn't been on the original discussion, framed casually as a quick add rather than a real scope change. I said yes, because saying no to a small, reasonable-sounding request felt unnecessarily rigid in the moment, and because nothing on paper existed to define where the original scope actually ended.
That one small addition made the next one easier to ask for, and the one after that easier still. By the end of the shoot, the actual deliverable list had grown considerably beyond what either of us had discussed on that original call, without either of us consciously deciding to renegotiate the fee to match.
None of these individual asks felt unreasonable in isolation. The problem was cumulative, and without a written scope document to check each new request against, there was no natural point where either of us flagged that the project had quietly become a different, larger project than the one we'd originally discussed.
The Moment the Disagreement Actually Surfaced
The disagreement came out at invoicing, which is one of the worst possible times for a scope misunderstanding to surface, since by then the work is already done and the relationship is already strained by the mismatch. I invoiced based on the expanded scope that had actually occurred. The client pushed back, genuinely surprised, expecting the original day rate to cover everything.
We were both right, in a sense. I had genuinely delivered more than the original conversation covered. The client had genuinely never agreed, explicitly, to pay more for that additional work. Without anything written down, there was no neutral reference point either of us could point to, just two competing memories of a conversation that had happened weeks earlier.
We eventually settled on a compromise that satisfied neither of us completely, and the relationship never fully recovered its earlier warmth. That outcome, a client who probably won't rebook and a fee that didn't reflect the actual work delivered, has stuck with me far longer than the specific dollar amount in dispute.
Why "It Felt Too Friendly to Formalize" Is a Trap
The reason I skipped a written agreement in the first place wasn't laziness, it was a specific and, I now think, misguided instinct that formalizing a friendly conversation with a contract would somehow signal distrust. I've since concluded that instinct has it exactly backwards, and I think it's a genuinely common trap for photographers early in a client relationship.
A written agreement doesn't signal distrust of a specific person, it signals professionalism and protects both parties equally from the very real problem of imperfect memory. Two people can leave the same phone call with two different honest impressions of what was decided, and a written document exists specifically to eliminate that gap before it matters.
I've found that most professional clients actually expect a written agreement and read its absence as a red flag rather than a sign of trust. The clients who've pushed back on formalizing terms in writing have, in my experience, been the ones most likely to cause a scope or payment dispute later.
What Goes Into My Agreements Now
Every project now gets a written agreement before a single frame is captured, regardless of how warm or informal the relationship feels. At minimum, it specifies the exact deliverables, the usage rights included in the fee, the timeline, the payment terms, and explicitly how additional requests beyond the original scope will be priced.
That last point, how scope changes get handled, is the piece I was missing entirely in the original mistake, and it's now one of the most important lines in any agreement I sign. It doesn't need to be complicated: a simple stated rate for additional shooting time or additional deliverables beyond what's specified, agreed to before the work happens rather than negotiated after the fact.
I also specify what happens if a shoot gets rescheduled, canceled, or cut short by weather or circumstances outside anyone's control, since those situations come up constantly in adventure and outdoor work specifically. Having those terms settled in advance means neither of us is negotiating fairly during an already stressful moment.
Handling Scope Creep in the Moment, Not After
The real lesson from that early mistake wasn't just "get it in writing" as a one-time step before a project starts, it was learning to flag scope changes the moment they happen during a shoot, rather than accumulating them silently and sorting it all out at invoicing. Now, when a client asks for something beyond the agreed scope mid-shoot, I say so directly, in the moment.
That doesn't have to be an awkward conversation. A simple, direct acknowledgment, that this specific request is beyond what we originally scoped and here's what it would add to the fee, keeps both of us aligned in real time rather than storing up a disagreement for later. Most clients respond well to that kind of directness, especially when it's framed matter-of-factly rather than defensively.
I've found that addressing scope changes immediately, rather than letting politeness delay the conversation, actually strengthens the relationship rather than straining it. Clients tend to respect a photographer who manages scope proactively far more than one who stays quiet in the moment and then delivers a surprising invoice later.
What a Simple Agreement Actually Looks Like
I want to be clear that a written agreement doesn't need to be a dense legal document that requires a lawyer to draft or a client to review for a week before signing. My standard agreement now runs a page or two, in plain language, covering deliverables, usage, timeline, payment terms, and the scope-change clause, and most clients sign it within a day of receiving it.
Keeping it simple and readable has actually made clients more comfortable signing quickly, compared to earlier drafts I tried that leaned too heavily on formal legal language borrowed from templates that weren't really built for photography work specifically. Plain, direct terms that any client can understand on a first read get signed faster and disputed less often.
I revisit and refine this template periodically, usually after learning something new from a project that didn't go the way I expected, adding a clause here or tightening language there. It's a living document that's improved steadily over the years rather than something I got perfectly right on the first attempt.
Trusting a Client Doesn't Mean Skipping the Paperwork
The hardest mental shift for me was separating trust in a person from the practice of getting terms in writing. I genuinely liked and trusted the client from that early mistake, and for a long time I associated a written contract with a lack of trust rather than understanding it as a completely separate, complementary practice.
I now think of a written agreement as protecting the relationship itself, not as a hedge against a client's character. Good terms in writing mean a friendly, trusting relationship has less material to actually disagree about later, which keeps the relationship friendly for longer rather than putting it at risk the first time a misunderstanding surfaces.
Some of my longest, most repeat-booking client relationships are with people I trust completely, and every one of those relationships still runs through a written agreement for every project. Trust and paperwork aren't in tension with each other. In practice, I've found they reinforce each other.
What I'd Tell a Newer Photographer Before Their First Client Call
I'd tell them that a friendly tone on a call is not the same thing as an agreement, no matter how clear the conversation felt in the moment. Memory is unreliable, even honest memory, and a written document exists specifically to remove that unreliability from the relationship before it has a chance to cause a problem.
I'd also tell them not to wait for a dispute to learn this lesson the hard way, the way I did. A simple, plain-language agreement covering deliverables, usage, timeline, and how scope changes get priced takes less time to draft than it takes to resolve even one disagreement after the fact, and it protects a relationship that's worth protecting.
Building a Template Instead of Starting From Scratch Every Time
One practical change that made the whole habit sustainable was building a genuine template rather than drafting a fresh agreement for every new client from a blank page. A blank page invites shortcuts under time pressure, and a rushed job booked on short notice is exactly the situation where skipping the paperwork feels most tempting.
My template now has clearly marked fields for the specifics of each job, deliverable count, usage rights, timeline, and fee, dropped into a structure that otherwise stays consistent from project to project. That consistency means drafting an agreement for a new client takes minutes rather than being a task substantial enough to justify skipping when a booking comes together quickly.
Having this template ready also removed the psychological friction of introducing paperwork into a conversation that had felt purely friendly up to that point. Sending a short, familiar-looking document rather than drafting something that feels newly formal for this specific client has made the whole process feel like a normal, expected step rather than an unusual request.
I'd encourage any photographer who's been skipping written agreements out of inconvenience rather than principle to build this kind of reusable template first. Removing the friction of drafting from scratch each time addresses the actual reason most photographers skip this step, which is rarely a considered decision and usually just a matter of not wanting to slow down a promising conversation.
What Happens When a Client Pushes Back on Signing
Occasionally a client has pushed back on formalizing terms in writing, treating the request as unnecessary given how well the working relationship was already going. I've learned to hold firm on this rather than treating pushback as a signal to accommodate, since in my experience that specific reaction has been a more reliable warning sign than almost anything else in the early stages of a client relationship.
I explain, directly and without apology, that a written agreement protects both parties equally and isn't a reflection of any doubt about the specific person I'm working with. Most clients accept this explanation without further resistance once it's framed as standard professional practice rather than a personal judgment call about their trustworthiness.
The clients who continue pushing back even after that explanation are, in my experience, disproportionately likely to be the ones who'd cause exactly the kind of scope or payment dispute a written agreement is meant to prevent. I now treat continued resistance to a simple, reasonable agreement as genuine information about how the rest of the relationship is likely to go.
Revisiting Old Agreements When a Repeat Client Comes Back
Repeat clients present a specific version of the same risk that caused my original mistake, since familiarity can tempt both parties into treating a new project with a returning client as an informal continuation of the last one rather than a fresh agreement needing its own written terms. I've had to resist that temptation deliberately, even with clients I've worked with for years.
Every new project, even with the most trusted repeat client, gets its own written agreement now, reusing the template but updating the specifics for that exact engagement. Rates change, scope changes, and usage needs change from project to project, and assuming the old agreement's terms still apply by default has the same potential for quiet misalignment that caused the original dispute in the first place.
I've found that repeat clients actually appreciate this consistency rather than finding it redundant or overly formal. It signals that the professionalism of the relationship hasn't slipped just because familiarity has grown, and it gives both of us a clean, current reference point rather than relying on a patchwork of assumptions built up across several past projects with slightly different terms each time.
Getting the business fundamentals right, contracts included, isn't the exciting part of this career, but it's what actually lets the creative work continue long-term without a single misunderstanding derailing an otherwise good client relationship. I go deeper into the full set of business practices that keep a photography career stable in The Adventure Photographer's Playbook.
Reflection Questions
- Do your current client agreements explicitly cover what happens when scope changes mid-project, or does that get handled informally?
- Has a friendly tone on a client call ever led you to skip formalizing terms you'd normally put in writing?
- What's the simplest version of a written agreement you could put in place before your next shoot?
- How would you handle a client mid-shoot who asks for something reasonable-sounding that falls outside the agreed scope?
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.