Most Asked Questions About Client Work

If you have ever walked away from a “quick project” feeling underpaid, overworked, or weirdly responsible for someone else’s chaos, this is for you.

I opened this episode with a gut punch scenario: you are still owed $3,700, and on top of that you lost other opportunities because you were counting on the work. That is the part people forget. It’s not just the invoice. It’s the opportunity cost.

So I pulled together 10 questions I see constantly in the photo and video world and answered them in a way you can actually use on your next gig.

_ _ _

Quick note: the contract and licensing parts are US-based and not legal advice. They are practical guardrails, not courtroom ready.

_ _ _

Why these questions matter

Most client problems are not “creative problems.” They are expectation problems.

The camera work can be solid and you can still get burned if the scope is fuzzy, the feedback is late, six people are “just chiming in,” or someone asks for raw footage without understanding what that even means.

This article is meant to be a checklist you can copy, paste, and build into your process. Without further ado, let’s get into it!

1) How do I stop scope creep without sounding rude?

Scope creep usually starts as “one small ask.” Then it grows teeth.

What I do, especially with a new client, is keep it professional and calm:

• “That’s not really part of our scope.”

• “I’ll do it this time, but going forward that would be an additional charge.”

• “If we need to add that, we’ll do a change order.”

You are not being difficult. You are protecting the agreement you both made.

Pro Insight
If someone balks at basic boundaries, that is useful information about whether you want them as a repeat client.

2) How many revision rounds do you include and what happens after?

I keep this simple: three rounds.

• Draft 1

• Draft 2

• Final

Anything after “final” becomes hourly (or whatever your additional work rate is). If you cannot get aligned by round three, it usually means there was a miss earlier in communication, not a “client being annoying” problem.

A practical way to prevent revision chaos: ask for references up front. A Pinterest board. A video they like. Something that helps you understand taste and intent before you ever edit.

3) What needs to be in a simple contract, even for small gigs?

_ _ _

Quick note: the contract and licensing parts are US-based and not legal advice. They are practical guardrails, not courtroom ready.

_ _ _

I do not care if it’s a small job. A simple contract is still your best friend.

Here’s what I make sure is included, big or small:

Parties and project summary

Who is hiring who, and what the project is. Define “client” and “contractor” clearly.

Scope and deliverables

Be specific:

• Formats (MP4, PNG, etc.)

• Length (3 minutes? 20 minutes?)

• Quantity (one photo? 500 photos?)

• Delivery method (Dropbox, Google Drive, etc.)

Timeline and key dates

Include:

• Shoot date

• Draft delivery date

• Review windows

• Final delivery date

Also spell out call time expectations. If the shoot is at 9:00, and you need to arrive at 6:30 to set up properly, that needs to be clear.

Review windows and what happens if the client is late

This line matters: If review is delayed, the timeline shifts.
Because you are not sitting there frozen in time waiting for an email. You have other work scheduled.

Client responsibilities

Spell out what they must provide:

• Access permissions (site access, locations, etc.)

• One point of contact

• Releases if needed

• Brand assets (logo, fonts, guidelines)

• Approvals on time

Fees and payment terms

Include:

• Total cost

• Deposit amount and due date

• Due dates (Net 15/30/60)

• Late fees if you use them

• Accepted payment methods

My personal line in the sand: I do not step on site without a cleared deposit in my account.

Revision policy

Define:

• Number of revision rounds included

• What counts as a revision vs a new request

• Rate for additional work

Final approval and what “complete” means

How final signoff happens, what “delivered” means, and when the project is officially complete.

4) How do you price quick jobs when the ask is vague?

“Quick” plus “vague” is where people accidentally donate their time.

My move: probe first, then think, then price. I do not give a range on the spot. Not because I want to be dramatic, but because I need time to process what the job actually is.

Questions that change the price fast:

• What are you actually delivering?

• What is the approval process? One decision maker or 15 people?

• How much back and forth is likely?

Then consider opportunity cost. If you race to the bottom to win a “quick job,” you might lose out on better work that week.

5) What do you do when the client is slow to give feedback and the timeline slips?

This is where you protect the project with a paper trail.

Before the deadline slips, send a reminder:

• “Just a reminder, I need feedback by the 14th so we stay on track.”

If they miss it, document it clearly and reset the timeline:

• “No worries. When do you think you can get feedback to me so we can restructure the timeline?”

Key point: do not sign up to “still hit the deadline” because they dropped the ball. If you can pull off a miracle sometimes, cool. But do not make miracles your default business model.

6) What do you do when multiple people are giving notes and nobody can decide?

I have lived this. Six people send feedback individually. Nobody talks to each other. Suddenly you are doing “six revisions” that were never agreed to.

This gets solved with one requirement: a single point of contact who consolidates feedback.

You can call it whatever you want, but the concept is the same:

• Who is collecting notes?

• Who is sending the final, distilled list?

• Who is the head chef?

Put it in the contract. Save yourself.

7) What if the client asks for all the raw footage or project files?

First, clarify what they mean. Most clients do not understand “raw.” They often mean:

• “All the clips, unedited”

• Or “All the Photos that were tak”

Raw files also come with reality:

• They take time to organize and transfer

• They can include rejects you would normally filter out

• Many clients cannot even open RAW photos without the right software

If I provide raw footage, I treat it as a separate deliverable and I set a clear boundary:

• I’m happy to help you get what you need, but edits made by others should not be presented as my work

That last part is critical. If someone slaps a terrible grade on it, that is their choice. Don’t let it reflect poorly on your name.

8) Who owns the work and what do rights or licensing mean?

In most cases (again, US-based context), the person hired to capture photo or video owns the work, and the client is granted licensing rights.

Licensing can vary a lot:

• Unlimited use

• Limited use

• Time-limited use (example: 30 days)

The important part is not the perfect legal language. It’s that both sides understand what the client can do with the work after delivery.

9) How do you keep versions organized so you do not lose your mind?

Part of my naming convention helps keep this clear:

• Use Drafts for iterations within the same direction

• Use Versions only when the direction changes significantly

Example structure: “Dave’s Awesome Video File D1.mp4”

• D1, D2, D3 for drafts

• If it becomes a new direction: Version 2, Draft 1 (V2 D1)

10) How do you handle deliverables and exports so clients do not get confused?

When the final file has been approved make sure to rename it “Dave’s Awesome Video File D3-FINAL.mp4”

This lets you and the client easily know which version got the nod for publication.

If You Remember One Thing

A contract is not about being cold. It’s about being clear.

Clear scope, clear revision rules, clear timelines, clear decision makers, and clear deliverables. That is how you protect the relationship and protect your time.

Until next time, Be Good to Each Other.

-Dave