Paying Collaborators Fairly on a Shared Project
When I bring a second shooter, an assistant, or a co-director onto a project, how I pay them isn't separate from how the shoot itself goes. Someone who feels shorted on a rate shows up distracted, or worse, disengaged at exactly the moment I need them sharpest.
I didn't always think about collaborator pay this carefully. Early on it was whatever was left after my own rate was covered, which is backwards, and it took years of running my own pricing through a more honest process to see it. If you're building out how you structure a shared project from the ground up, the Adventure Travel Photographer's Playbook walks through how I think about budgeting a full production, collaborators included, before a client ever sees a number.
Why Fair Pay Is a Production Decision, Not Just an Ethical One
When I bring a second shooter, an assistant, or a co-director onto a project, how I pay them isn't separate from how the shoot itself goes. Someone who feels shorted on a rate shows up distracted, or worse, disengaged at exactly the moment I need them sharpest. I've come to treat fair pay the same way I treat a light kit or a rental car: it's part of the production, not an afterthought I settle after the fact.
Early in my career I didn't think about it this way. I was still figuring out my own pricing, working off what I personally needed to make rather than what a job actually cost to produce, and collaborator pay got whatever was left over after my own rate was covered. That's backwards. The people helping me deliver the work are part of the cost of doing the work, and they need to be budgeted for from the start, not squeezed in at the end.
The shift for me came at the same time I moved from guessing a flat number to itemizing every real cost on a job: memory cards, hard drives, monitors, rigs, even the folding chairs on set. Collaborator pay became its own clean line item instead of something absorbed into my own fee. That single change did more for how fairly I pay people than any specific rate card ever has.
Line-Item Estimating Applies to Collaborators Too
Once I started building full line-item estimates for clients, it became obvious the same discipline had to apply internally. If a second shooter's day rate, a drone operator's fee, or an assistant's travel costs aren't broken out clearly in my own planning, I end up guessing at what's fair the same way I used to guess at my own rate. Guessing is where underpayment creeps in, usually without anyone intending it.
I now build a collaborator budget line before I ever quote a client, based on the actual scope of what I'm asking someone to do: how many days, what gear they're bringing, whether travel is involved, whether the terrain or conditions carry real physical demand. That number gets locked in before the job starts, which means I'm not scrambling to figure out what's fair once we're already on location and the pressure of the schedule is working against careful math.
It also means collaborators get a real answer when they ask what a job pays, instead of a vague range that shifts depending on how the budget shakes out. Clarity up front is its own form of fairness. People can decide whether a rate works for them before they've committed their time, not after.
Day Rate vs. Project Rate: Picking the Right Structure
Most of my own work has moved toward project-based pricing rather than a straight day rate, because a day rate doesn't reward efficiency and it doesn't protect against a job running long. Collaborators face the same tension, and I've learned to ask which structure actually fits the role before defaulting to whatever's easiest to write into a contract.
A second shooter or assistant whose hours are genuinely tied to my schedule, someone I'm directing minute to minute, is usually fairest to pay on a day rate, because their time is fully mine for that day regardless of what gets produced. A collaborator contributing a distinct deliverable, like a drone operator handling their own aerial sequence, often makes more sense on a flat project fee tied to that specific output, since their workload doesn't track hour for hour with mine.
Neither structure is inherently more fair than the other. What's unfair is picking whichever one benefits me most in a given moment rather than whichever one actually matches how the person's time and output are structured on that job.
Paying for Skill Level, Not Just Hours in the Field
Two people can spend the same number of hours on a shoot and bring wildly different value to it. An experienced second shooter who anticipates a moment before I call it out, or an assistant who knows how to keep a set moving without being told, is worth more than someone doing the same tasks with less instinct for the work. I try to price for that difference honestly rather than pretending every hour on a call sheet is interchangeable.
This gets harder with newer collaborators who are still building experience, since undervaluing their time just because they're early in their career isn't fair either. My approach is to be transparent about where a rate sits relative to more seasoned help, and to be clear that the number will move as their skill and reliability on set grow. Nobody should be surprised, in either direction, once they've worked with me more than once.
I also try to pay a premium for specific skills I don't have myself, like a drone pilot's certification or a water housing specialist's experience, rather than treating those as generic labor. Specialized skill that fills a real gap in what I can produce alone deserves a rate that reflects the gap it's closing, not just the hours logged.
What to Do When a Collaborator Is Also a Friend
The messiest pay conversations I've had were with friends, not strangers, because the instinct is to skip the formal structure entirely and just wing it based on the relationship. I've learned that's actually where things go wrong fastest. A stranger expects a written rate and a contract. A friend often doesn't ask for one, which means the burden falls on me to bring it up anyway, even when it feels awkward to formalize something that started casually.
My rule now is that friend collaborations get the same itemized, written approach as anyone else, just delivered with more context and more conversation up front. I'll explain the budget, walk through what the job actually pays and why, and give them room to negotiate the same way a stranger would. Treating the friendship as a reason to skip that conversation almost always backfires later, once money and expectations have quietly diverged without either person noticing.
It's also fair to acknowledge that some friend collaborations genuinely aren't about market rate, they're about trading skills or building something together outside client work. That's a legitimate arrangement, but it only stays fair if both people agree to it explicitly rather than one person assuming a market rate and the other assuming a favor.
Licensing and Usage: Who Gets Paid When the Work Gets Reused
Licensing is genuinely the area I still spend the most time thinking through, because every brand handles it differently and there's no single formula that covers every situation. When a collaborator's work, a drone shot, a specific angle, an assistant-operated second camera, ends up in the final licensed deliverable, that reuse has value beyond the original day rate, and I try to account for it rather than assuming the flat fee covers everything forever.
My approach is to ask more questions upfront rather than defaulting to a fixed policy: how is the client planning to use the material, for how long, and across what channels. Once I have real answers, I can decide whether a collaborator's contribution warrants a usage bump on top of their base rate, especially if their specific footage or frames end up carrying real weight in the final campaign rather than just supporting my own work.
This is an area where I'd rather over-communicate than assume. A collaborator who finds out months later that their shot became the hero image of a national campaign, without any conversation about what that meant for their pay, has a legitimate grievance even if the original day rate was fair at the time it was agreed.
Getting Agreements in Writing Before the First Frame
I never start a shared project without a written understanding of the rate, the scope, and what happens if the day runs long. It doesn't need to be a formal legal contract for every collaborator, sometimes it's genuinely just a clear message or a one-page agreement, but it needs to exist somewhere both people can point back to if a disagreement comes up later.
This matters most in the moment things go sideways, when a shoot runs three hours over or the scope quietly expands mid-day. Without something written down, those conversations turn into a negotiation happening under pressure, which almost never favors the person with less leverage. With something written down, it's a quick reference check instead of a fight.
I ask collaborators the same thing I ask clients: do you get paid if you work overtime. If the honest answer is no, under the current agreement, that's the moment to fix the agreement, not after the overtime has already happened and someone's decided whether to bring it up.
Handling Scope Creep on a Shared Project
Scope creep doesn't just hit me on a client job, it hits collaborators too, and I think it's my responsibility to catch it before they have to raise it themselves. If a shoot day expands past what was planned, or I ask a second shooter to take on something outside the original agreement, that's extra work and it should be treated as extra pay, named on the spot rather than absorbed silently.
The move that's worked for me with clients applies here too: name the extra work in the moment, agree on what it's worth right then, even informally, and follow up with something in writing before the day is over. Waiting until after a project wraps to sort out whether extra work should have been compensated puts the collaborator in the position of having to ask, which isn't a fair position to put someone in.
I'd rather over-flag scope changes and occasionally get told it's fine than let a collaborator quietly absorb work that wasn't part of what we agreed to. That habit protects the relationship far more than it costs in the moment.
How I Handle Payment Timing and Upfront Deposits
Fair pay isn't only about the number, it's also about when the money actually arrives. I collect roughly half of a project's total fee upfront from clients specifically to cover production costs, and that same principle carries through to how I pay collaborators: I don't ask someone to front their own travel, gear rental, or living expenses for a week and then wait a month past the shoot to get reimbursed.
Where possible, I pay collaborators a deposit before travel-heavy jobs, especially if I'm asking them to book flights or cover costs before we've even met on location. Making someone float real money on my behalf isn't fair just because the final total will eventually balance out. Cash flow matters to a freelance collaborator the same way it matters to me, and I try to remember that instead of assuming everyone has the same runway I do.
On the back end, I try to pay out final balances within days of a job wrapping, not weeks. A collaborator who did the work shouldn't be the one absorbing my own slow invoicing cycle with a client. If my payment from a brand is delayed, that's a cash flow problem I need to manage on my end, not something I pass down to the person who showed up and did the job on schedule.
Setting Expectations About Credit and Portfolio Use
Money isn't the only currency on a shared project. Credit and portfolio rights matter too, and I've learned to talk about both explicitly rather than assuming a collaborator's only concern is the rate on the invoice. Some collaborators, especially earlier in their career, will genuinely value a clear credit line or permission to use select frames in their own portfolio as much as an extra few hundred dollars.
I try to ask rather than assume. Some clients restrict how imagery can be shared before a campaign launches, and I make sure collaborators understand those restrictions clearly rather than finding out after the fact that a frame they were proud of can't go up on their own site yet. Being upfront about those limits, and about when they'll lift, is part of treating someone's professional interests as seriously as their pay.
When a collaborator's specific contribution, a striking angle, a technical setup only they could pull off, becomes something they want to show future clients, I try to make that easy rather than treating it as a favor I'm reluctantly granting. People remember who made it easy to build their own career alongside working for someone else's.
A Quick Gut-Check I Run Before Every Shared Project
Before I finalize any collaborator arrangement, I run through a short mental checklist: would I be comfortable if this rate and these terms were posted publicly, would I accept this exact deal if our roles were reversed, and does the person know everything about the scope and pay that I know myself. If any answer makes me uneasy, that's a sign the terms need adjusting before the job starts, not after.
This gut-check has saved me from a few arrangements that looked fine on paper but felt off once I actually imagined being on the other side of them. It's a simple test, but it catches the kind of quiet unfairness that doesn't show up in a spreadsheet, the stuff that only becomes obvious once you picture yourself accepting the same deal.
I'd rather catch that discomfort in planning than have a collaborator raise it mid-project, when fixing it costs more, takes longer, and puts strain on a relationship I want to keep for future jobs.
What Fair Pay Actually Buys You Long Term
The collaborators I've worked with most consistently over the years aren't necessarily the ones I pay the most, they're the ones who trust that the number I quote them is honest and that it won't quietly shrink once we're on location. That trust is worth more to a working relationship than any single rate, because it means I can call someone for a hard job on short notice and know they'll say yes.
Underpaying a collaborator once might save money on a single job, but it costs something bigger: the willingness of good people to work with me again. Adventure and travel photography runs on a small circle of reliable collaborators who show up in tough conditions and do good work under pressure. That circle only stays intact if people feel like the arrangement was fair the first time.
I think about fair pay less as generosity and more as an investment in the team I want to be able to call on for the next ten years of projects, not just the next one.
Reflection Questions
- Is your collaborator pay a real line item in your budget, or whatever's left over after your own rate is covered?
- Have you ever had a friend collaboration go sideways because the pay conversation never got formalized?
- Do your collaborators know how licensing and usage might affect their pay beyond the original day rate?
- What would change about your next shared project if every agreement was in writing before the first frame?
If you're rethinking how you structure pay across a shared project, the Adventure Photographer's Playbook covers how I approach budgeting, contracts, and collaborator relationships as part of running a full-service studio.
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.