The Brief That Told Me Everything About a Client Before We Even Talked
A creative brief is supposed to describe a project. In practice, it also describes the client sending it, often more accurately than any discovery call that follows. The level of detail, the tone, the questions it anticipates versus the ones it leaves wide open, all of that tells you something about how organized, how respectful of your time, and how ready to actually move forward the client on the other end really is.
Over enough years of reading briefs, I've learned to trust that first read more than I used to. A brief that's vague, rushed, or clearly copy-pasted from a template with the details half-filled in usually predicts exactly the kind of project that follows, and a brief that's specific, thoughtful, and clearly written by someone who's done the internal work before reaching out usually predicts the opposite. If you want a fuller framework for evaluating client fit before you're deep into a negotiation, the Adventure Travel Photographer's Playbook covers how I think about qualifying opportunities early.
Why the Brief Matters More Than the Discovery Call
A discovery call is a performance, at least a little. Both sides are putting their best foot forward, being polite, staying vague about budget, and generally trying to make a good first impression. A brief, especially one written before any call happens, is closer to the client's actual internal thinking, because it wasn't written with me in the room.
That makes a brief a more honest signal than a lot of what gets said out loud in an early conversation. Someone can sound enthusiastic and easy to work with on a call while their actual brief reveals a project with an undefined scope, an unrealistic timeline, or budget expectations nowhere close to what the ask actually requires.
I've started treating the brief as the first real test of a potential project, before a single word gets exchanged live. It's not a perfect predictor, but it's a far better one than I gave it credit for earlier in my career, when I mostly skimmed briefs on the way to the more exciting part, the actual conversation.
What Vague Language Actually Signals
A brief full of vague language, "something dynamic," "lifestyle vibes," "authentic storytelling," without any concrete direction underneath those phrases usually signals that the internal team hasn't fully agreed on what they actually want yet. That's not automatically disqualifying, but it does tell me the project is likely to involve more back-and-forth clarification than a well-defined one.
Vague language can also signal a rushed process on the client's side, a brief assembled quickly to meet an internal deadline rather than one built thoughtfully over time. Rushed briefs tend to produce rushed decision-making later in the process too, which affects everything from feedback timelines to how firmly a scope actually holds once work begins.
I don't dismiss every vague brief outright, because sometimes genuinely exciting, more open documentary-style projects are intentionally less defined by design. But I read the vagueness differently depending on context: intentional openness reads very differently than an unfinished internal thought process dressed up as a creative brief.
What a Highly Specific Brief Tells You
A brief with a clear shot list, a defined deliverable count, a stated timeline, and an actual budget range, even a rough one, signals a client who's done real internal work before reaching out. That kind of preparation usually correlates with a smoother process overall, because the hard internal alignment questions have already been worked through before I'm even in the conversation.
Specificity also tends to predict a client who respects the collaborative process rather than expecting me to guess what they want. A brief that anticipates likely questions, weather contingencies, model release needs, usage rights expectations, shows a level of experience working with photographers before, which usually makes the actual working relationship smoother too.
The exception worth noting is a brief that's specific but rigid to the point of leaving no room for creative judgment. Extremely prescriptive briefs sometimes signal a client who wants an executor, not a collaborator, which isn't automatically a problem, but it is worth knowing going in so expectations on both sides match reality.
What Missing Budget Information Really Means
Almost every brief either omits budget entirely or hedges around it, and I've learned that this specific gap isn't necessarily a red flag on its own, brands and agencies often already have a number in mind and just don't share it upfront as a matter of process, not evasiveness.
What matters more is how a client responds when I ask directly. A client who answers a direct budget question with a real range, even a wide one, is signaling genuine intent to move forward. A client who deflects the question repeatedly, or answers with something that doesn't actually contain a number, is signaling something closer to a fishing expedition than a real project.
I've learned not to rush this part of the process, since rushing tends to be exactly what leads to getting ghosted later. Asking clear questions and giving the client room to answer honestly, without pressure, has consistently worked better than trying to force an early commitment before either side has enough information.
How I Read the Requested Turnaround Time
A brief's timeline tells you almost as much as its content. An unusually tight turnaround relative to the scope described often signals either poor internal planning on the client's side or a lack of understanding of how much production and post-production actually take, and both of those are worth knowing before agreeing to anything.
A generous, realistic timeline, on the other hand, usually signals a client who's worked with photographers or production teams before and understands the actual mechanics of a shoot, from pre-production through delivery. That understanding tends to carry through into how reasonable they are during the actual project too.
I factor my own rule of thumb into this read as well: roughly one day of shooting requires about two days of editing before selects are ready. A brief's proposed timeline that doesn't leave room for that basic math is a brief written without a clear sense of the real production process.
Reading Between the Lines on Usage and Licensing
Licensing is the area I've found requires the most active questioning, since every brand handles it differently and a brief rarely spells it out completely on its own. A brief that mentions usage rights at all, even briefly, tells me the client has thought about this ahead of time, which usually means a smoother negotiation later.
A brief that's silent on usage entirely isn't necessarily a problem, but it does mean this becomes one of the first things I raise directly, since assuming usage terms rather than confirming them upfront is exactly the kind of gap that creates disputes well after a project has already wrapped and been delivered.
I've come to see licensing questions as a genuine test of a client relationship early on. A client who answers licensing questions clearly and directly is signaling transparency I can build a project around. A client who stays vague on this specific point, even after being asked directly, is signaling something worth taking seriously before committing further time to the pitch.
The RFP Problem and How a Brief Reveals It
Unpaid RFPs, requests for a full creative proposal without any compensation for the proposal work itself, are common enough that I've built a standing policy around them: I don't respond unless the proposal work itself is paid. A brief structured as an unpaid RFP tells me a lot about how that particular client, or that particular industry norm, values a photographer's time before a contract even exists.
This isn't a hard, universal rule against every RFP, since some are legitimate and some organizations simply operate that way as standard practice. But a brief that asks for substantial creative and strategic thinking without acknowledging that work has value on its own, separate from the eventual project, is a signal worth taking seriously.
Declining to respond to an unpaid RFP does mean occasionally losing a job I might have won by playing along. That's an accepted trade-off, not an oversight. Bandwidth spent on unpaid proposal work is bandwidth not spent on paid work already in the pipeline, and a brief that asks for that trade without acknowledging it is telling me something true about the relationship before it's even started.
How This Shapes My Actual Response to a New Brief
My response to a new brief now starts with reading it slowly, twice, before drafting any reply. The first read is for content, what's actually being asked for. The second read is for signal, what the brief's structure, tone, and gaps say about the client and the project beyond the literal request.
I ask direct questions early rather than assuming I'll get clarity later in the process. Budget, timeline, usage rights, and decision-making structure all get addressed as early as reasonably possible, because rushing past those questions to seem accommodating has, in my experience, led to more ghosting and misalignment than asking them upfront ever has.
I also give myself permission to pass on a brief that reads poorly, even before a full conversation happens. Not every opportunity is worth pursuing, and a brief that predicts a difficult, unclear, or disrespectful process is often right about that prediction, which makes it worth trusting more than the instinct to chase every inbound lead regardless of the signals it's already sending.
What a Brief Reveals About a Client's Decision-Making Structure
A brief that clearly states who has final creative approval, one named decision-maker versus a vague committee, tells me a lot about how smoothly the actual project will run once it's underway. Projects with a single clear approver almost always move faster and involve fewer contradictory rounds of feedback than projects where approval authority is left ambiguous from the start.
I've learned to ask directly, early, who signs off on selects if the brief doesn't already answer that question clearly. The answer, or the lack of a confident answer, tells me whether I'm dealing with an organization that's already resolved its internal alignment or one that's going to work through that alignment live, during the project, at my expense in terms of time and revision rounds.
This connects directly back to a pattern I've seen play out more than once: a creative director approving direction on set, only for someone who wasn't present to demand contradictory changes later. A brief that names a clear, single decision-maker upfront is one of the better predictors I've found for avoiding that exact scenario before it happens.
How I Respond to a Brief That's Almost Right
Not every brief falls cleanly into "clearly a good fit" or "clearly a poor fit." Plenty land somewhere in between, strong in some areas and vague or concerning in others, and how I respond to that middle ground has become its own skill worth developing deliberately.
My approach is to respond with specific, direct questions targeting exactly the gaps rather than either declining outright or accepting the ambiguity and hoping it resolves itself later. A brief that's vague on budget but otherwise well-organized gets a direct budget question. A brief that's specific on deliverables but silent on usage rights gets a direct usage question. Targeted follow-up usually resolves more uncertainty than a generic "can you tell me more about the project" ever does.
How a client responds to those targeted questions often tells me more than the original brief did. A thoughtful, specific answer to a pointed question is a strong positive signal, even if the original brief itself was underwhelming. A vague or defensive response to a direct, reasonable question is a signal worth taking just as seriously as anything in the original document.
Comparing Agency Briefs to Direct Brand Briefs
Briefs that come through an agency read differently than ones that come directly from a brand's internal marketing team, and I've learned to adjust my expectations accordingly rather than judging both against the same standard. Agency briefs are often more polished and better structured, since agencies write them professionally as part of the job, but that polish doesn't always translate into a client with the direct decision-making authority a brand contact might have.
Direct brand briefs can be rougher around the edges, less formally structured, but sometimes come from someone with more genuine authority to make final calls quickly once the project is underway. I weigh a slightly less polished direct brief more generously than I might weigh the same level of polish gap in an agency document, since the underlying signal being measured is different in each case.
I've also found that agency-mediated projects introduce an extra layer of communication that can slow feedback and create the exact kind of contradictory notes problem that a brief's own clarity can't fully prevent on its own. Knowing which type of brief I'm dealing with helps me calibrate expectations for how many rounds of clarification a project is likely to need before things are genuinely settled. Neither structure is inherently better across the board, and treating that distinction as useful context rather than a strict hierarchy has made me a better judge of what a specific project actually needs from me before we've even had a real conversation. Reading a brief well, in the end, is really just an extension of reading people well, and that skill has only sharpened the more deliberately I've paid attention to it project after project. It's a skill I wish I'd taken seriously much earlier in my career, back when I treated every inbound brief as an opportunity to chase rather than a document worth genuinely evaluating on its own terms first. These days, a few extra minutes spent reading closely before replying has saved far more time, and far more frustration, than it has ever cost me in a slower response to a client genuinely waiting on the other end of that conversation, and I honestly don't expect that particular math to change anytime soon, no matter how much faster communication tools get in general.
Reflection Questions
- What does the last brief you received tell you about the client, separate from the project itself?
- Are you asking direct budget and licensing questions early, or waiting and hoping clarity arrives on its own?
- How do you currently distinguish between an intentionally open brief and an unfinished one?
- Do you have a standing policy for unpaid proposal work, or are you deciding case by case under pressure?
For more on how I evaluate and qualify new opportunities before committing real time to them, the Adventure Photographer's Playbook covers the client relationship decisions that shape a sustainable photography business.
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.