Day rate and project rate get talked about like they're just two ways of arriving at the same number, but they actually protect you against two completely different risks — and picking the wrong one for a given job is one of the more common ways photographers end up underpaid without quite understanding why.
What each one actually protects against
Day rate protects your time. You're charging for the day itself, regardless of how much or how little the client asks of you within it. If the shoot runs efficiently and wraps in four hours, you still made your full day rate. If it drags into overtime because the client kept adding shots, that's covered separately or built into the rate you quoted going in.
Project rate protects your scope. You're charging for a defined deliverable — a certain number of final images, a specific type of coverage, a finished product — regardless of how many hours it actually takes you to get there. If you're fast and it takes half the time you budgeted, you keep that upside. If it takes longer than expected, that's a cost you absorb unless the scope itself changes.
Neither one is inherently better. The question is which risk you'd rather be exposed to for a given type of job.
When day rate is the better fit
Day rate makes the most sense when the client controls the pace, not you — shoots where you're on someone else's schedule and the value you're providing is availability and expertise for a block of time, not a fixed, easily-scoped deliverable. This describes a lot of commercial and editorial work: you show up, shoot what's needed within the day, and the client directs a meaningful amount of what happens during it.
It's also the better fit when the shot list is genuinely unpredictable going in — event coverage, documentary-style work, anything where you can't fully scope the deliverable in advance because you're responding to what happens in real time rather than executing a pre-planned shot list.
When project rate is the better fit
Project rate works best when you control the process and the deliverable is genuinely definable upfront — a portrait session with a known number of final edited images, a product shoot with a defined list of items, a wedding package with a specific set of deliverables (ceremony, reception, a certain number of edited images, an album). If you can write the scope down clearly enough that both you and the client would agree on what "done" looks like before you start, project rate is usually the cleaner structure.
It's also the better choice when efficiency is actually your edge. If you're fast — if your workflow lets you deliver the same quality in less time than a lot of other photographers — day rate quietly punishes that skill, because you're capped at the day rate regardless of how efficiently you worked. Project rate lets your speed translate directly into a better effective hourly return.
The risk of picking the wrong one for the job
Using project rate on a shoot where the scope is genuinely unpredictable is how photographers end up doing three times the agreed work for the agreed price — the client keeps adding "just one more setup," and because the quote wasn't tied to time, there's no natural point where that starts costing them anything. This is exactly the territory covered in our post on handling scope creep — a lot of scope creep problems actually trace back to a project-rate quote that should have been a day rate, or a day rate with clearer boundaries on what's included.
The reverse problem happens too: using day rate on a job where you're genuinely fast and efficient means you're leaving money on the table relative to what a well-scoped project rate would have paid for the same deliverable.
A practical way to decide
A useful gut check: if you can write the deliverable down in one clear sentence before you start — "12 edited images, delivered within two weeks" — project rate probably fits. If the honest answer is "we'll see what we get," day rate protects you better, because you're being paid for your time and availability rather than for a specific outcome you can't fully control.
Whichever structure you use, being specific about it on the invoice and the original quote matters more than the label itself. "Day rate" without a stated number of hours or an overtime policy is just as vague as an unscoped project rate — the protection comes from the specifics, not the category.
Once you've settled on a structure, keeping the invoice consistent with what was actually agreed to — the day, the deliverables, or both — makes disputes far less likely down the line. CreateCollect's invoice templates let you itemize exactly what a rate covers, whether that's a day and its terms or a defined set of deliverables, so the scope lives on the paperwork itself rather than in a conversation nobody wrote down.