The Difference Between a Fair Ask and a Red Flag Ask

Every negotiation involves asks. Clients ask for a lower rate, a faster turnaround, extra usage rights, or one more look added to the day. Most of these are completely normal, and treating every ask as an attack is a fast way to lose good clients over reasonable requests. But some asks are different in kind, not just degree, and learning to spot that difference early has saved me from a handful of projects that would have gone badly no matter how well I shot them.

The line isn't always obvious in the moment, which is exactly why I've built a rough set of signals I check a request against before deciding how to respond. Some of that framework, along with the pricing structures that make fair negotiation easier in the first place, is laid out in The Adventure Photographer's Playbook, but the short version starts with paying attention to how a request is framed, not just what it's asking for.

The Question I Ask Myself First

When a client makes a request that pushes on scope, price, or timeline, the first thing I check isn't whether I can accommodate it. It's whether the request is being made as an open negotiation or as a demand dressed up as a suggestion. Those two things can sound almost identical on a call, but they lead to completely different working relationships.

An open negotiation invites a trade-off. "Could we do this for less if we cut the second location?" is a negotiation, because it acknowledges that something has to give somewhere. A demand dressed as a suggestion sounds similar on the surface, "could we do this for less," but with no acknowledgment that anything else in the project would need to change to make that work.

That distinction, whether the client is willing to adjust something else in exchange for what they're asking, is the single fastest filter I have for sorting a fair ask from a red flag ask. It doesn't catch everything, but it catches most of it before a call even ends.

What a Fair Ask Usually Sounds Like

Fair asks tend to be specific and grounded in an actual constraint the client is dealing with. "Our budget for this campaign is capped at a certain number, can we find a version of this project that fits" is specific, honest, and gives me something concrete to work with. I can propose a smaller shot list, a shorter day, or a narrower usage window, and we can find a version of the project that works for both of us.

Fair asks also tend to come with context. A client explaining why they need a fast turnaround, because of a launch date or a press deadline, is giving me real information I can use to prioritize the work appropriately. Context doesn't mean I automatically say yes, but it means the request is coming from a real business need rather than a habit of asking for more simply because asking is free.

The clearest sign of a fair ask, though, is that the client accepts a reasonable no. If I explain why something isn't possible within the current scope and they adjust the request accordingly, that's a fair negotiation working exactly the way it should.

What a Red Flag Ask Usually Sounds Like

Red flag asks tend to be vague and framed as non-negotiable, often paired with an implicit threat that the whole deal is at risk if I don't just say yes. "We just need this to include full buyout rights, that's standard for us" with no further explanation, and no willingness to discuss the fee difference between licensed use and a full buyout, is a pattern I've learned to take seriously.

Another consistent signal is a request that expects me to absorb the exact same amount of risk or work for less money, framed as if it's a favor I should be glad to do. "We loved working with you, so we're hoping you can do this one a bit cheaper" sounds like a compliment, but functionally it's asking me to discount my own value based on the strength of the relationship, which is backwards.

The clearest red flag, though, is a request that can't survive a direct question. If I ask "can you help me understand what's driving that ask" and get a vague non-answer or a repeat of the same demand with more urgency, that tells me the request isn't really about a specific need. It's a default posture, and defaults like that rarely change project to project.

The Line-Item Estimate as a Diagnostic Tool

One of the most useful things I've built into my process is presenting a full line-item breakdown of a project's costs rather than a single flat number. It turns out this does double duty as a negotiation tool and as a diagnostic for exactly this fair-versus-red-flag question. When a client sees the itemized breakdown, a fair negotiation usually looks like them picking specific items to cut, an assistant, a second location, a certain number of revision rounds, in exchange for the lower total they need.

A red flag response to the same itemized breakdown looks different. It's a client who wants the same full scope, the same assistant, the same locations, the same deliverable count, but at a lower total, with no specific item identified for removal. That's not a negotiation over what's actually needed, it's just downward pressure on the number itself, and the itemized structure makes that gap obvious almost immediately.

I've come to genuinely appreciate how much clarity this brings to a negotiation that used to feel murky when I quoted flat rates. The line-item format doesn't just help me price accurately, it surfaces exactly the kind of ask I'm dealing with faster than any amount of conversation would on its own.

Scope Requests vs. Fee Requests

A useful distinction I've learned to make is between a client asking for a change in scope and a client asking for a change in fee without touching scope at all. Scope requests, adding a look, extending a shoot day, adding a location, are normal and expected, and I price them as extras rather than treating them as some kind of violation. This is exactly the situation behind the "napkin agreement" approach I use on set: name the extra work, price it against the already-agreed rate, and get it in writing on the spot.

Fee-only requests, where the scope stays exactly the same but the client wants to pay less for it, are a different animal, and they deserve more scrutiny. There are legitimate versions of this, a genuine budget constraint discovered mid-negotiation, but there are also versions that are simply testing whether I'll cave on price if pushed hard enough, with no intention of adjusting anything else about the project.

Separating these two categories in my head before I respond keeps me from reacting emotionally to either one. A scope request gets a straightforward quote for the added work. A fee-only request gets a direct question about what's driving it, and the answer to that question tells me almost everything I need to know.

When "Everyone Else Does It This Way" Is a Red Flag

A specific phrase I've learned to flag immediately is some version of "this is just standard for our industry" or "everyone we work with does it this way," used to justify a request without actually explaining the request itself. Sometimes this is true and genuinely useful information. More often, in my experience, it's a way of making a one-sided ask sound like an objective fact rather than a negotiating position.

My response to this phrase is almost always the same: ask for the specific reasoning behind the standard, not just the claim that it exists. A client who can explain why full buyout rights are standard for their category, insurance requirements, syndication needs, internal legal policy, is giving me real information. A client who repeats the claim without explaining it is usually just hoping I won't push back.

This pattern shows up constantly in usage rights conversations specifically, since usage is genuinely one of the areas where I still find myself asking more questions than I used to, because every brand handles it differently. "Standard" is doing a lot of work in that sentence, and it's worth unpacking every time before accepting it at face value.

The Ask That's Fair on Paper But Wrong for This Client

Not every red flag is about the content of the request itself. Sometimes an ask is perfectly reasonable in the abstract, but wrong for the specific relationship because of everything else going on around it. A request for a faster turnaround is fair on its own, but if it's the fourth timeline change on a project that's already blown past its original scope twice, it stops being a simple scheduling question and starts being a pattern.

This is where I've learned to zoom out from any single request and look at the sequence of asks over the life of a project. One flexible accommodation is just good client service. A string of them, each individually reasonable, adds up to a client relationship that's quietly renegotiating the entire project one small ask at a time, without ever having the direct conversation about what's actually changed.

When I notice this pattern, I address it directly rather than continuing to accommodate one more "small" change. Naming the pattern out loud, "I've noticed the scope has shifted a few times since we started, can we align on what the project actually looks like now," resets the conversation without making any single past accommodation the villain.

How I Respond to a Red Flag Without Burning the Bridge

Identifying a red flag ask doesn't mean the relationship is over, and treating it that way would cost me clients who are simply having an off day or working within pressure I don't fully see. My first response to a red flag ask is almost always a direct, non-accusatory question: what's driving this specific request, and is there flexibility on any other part of the project to make it work.

This does two things at once. It gives the client a genuine opportunity to explain themselves and turn what looked like a red flag into a fair, contextualized ask. And it makes clear, without ever being confrontational, that I noticed the shape of the request and I'm not going to simply absorb it without discussion.

If the direct question gets a non-answer or more pressure instead of clarity, that's when I start protecting myself more deliberately, tightening contract language, requiring more upfront payment, or in some cases declining the project. But I try never to skip the step of asking directly first, because it's saved more than one relationship that just needed a clearer conversation.

Patterns I've Learned to Watch For Over Time

A few patterns repeat often enough that I now treat them as near-automatic flags. A client who wants to skip the contract entirely "since we trust each other" is one, especially on anything beyond a small personal favor. A client who pushes hard for a decision on a call before I've had time to think it through is another, because urgency is sometimes real and sometimes manufactured specifically to prevent careful consideration.

A request to do a discovery call or sample concept for free, framed as "just to see if we're a fit," is a pattern I watch closely too, since unpaid speculative work is one of the more common ways photographers get used without compensation, especially by agencies working through a pitch process on someone else's behalf.

None of these patterns are automatic disqualifiers on their own. Plenty of good clients have asked for one of these things innocently, without any bad intent behind it. But when two or three show up together on the same project, that combination has been a reliable enough signal for me that I now take it seriously every time.

Trusting the Gut Check

After enough years of this, a lot of the fair-versus-red-flag distinction has become something closer to instinct than a checklist, and I've learned to trust that instinct more than I used to. If a request leaves me feeling slightly uneasy even after I can't immediately articulate why, that feeling is usually pointing at something real, some combination of framing, urgency, and lack of reciprocity that my conscious brain hasn't fully catalogued yet.

That said, instinct works best paired with the more concrete checks I've described here, not instead of them. A gut feeling tells me to slow down and look closer. The specific questions, is this a scope ask or a fee ask, is there a trade-off on the table, does "standard" have an actual explanation behind it, are what turn that instinct into a decision I can actually explain to myself and to the client if it comes to that.

The photographers I respect most in this business aren't the ones who never get a red flag ask. They're the ones who've gotten comfortable naming it plainly, asking a direct question about it, and making a clear decision either way, rather than quietly resenting a client while still saying yes to everything.

Documenting the Ask So the Pattern Becomes Visible Later

One habit that's made this whole framework more useful over time is simply writing down unusual requests as they come in, even briefly, rather than trusting memory to catch a pattern across months of client conversations. A quick note after a call, what was asked, how it was framed, whether it came with a trade-off, turns a vague gut feeling into something I can actually review later.

This record has been especially useful with agencies and repeat clients, where a single odd request might mean nothing on its own but a series of them across several projects tells a much clearer story. Without notes, that pattern is easy to miss, since each individual conversation feels unremarkable in isolation and only looks significant once several are lined up side by side.

It's a small amount of extra effort, a few sentences after a call that would otherwise go unrecorded, but it's paid for itself several times over in cases where a client relationship needed a harder conversation and I wanted to be certain I wasn't reacting to a single bad day rather than a genuine pattern.

For a deeper look at how a line-item pricing structure makes these negotiations clearer for both sides, it's covered in the Adventure Photographer's Playbook.

Reflection Questions

1. When was the last time a client request left me uneasy, and what specifically about the framing caused that reaction?
2. Do I currently distinguish between scope requests and fee-only requests, or do I respond to both the same way?
3. How often do I ask a client directly what's driving a request, rather than just accommodating or declining without asking?
4. Have I ever accepted a string of small, individually reasonable changes that added up to a much bigger shift in the project than I agreed to?

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.