How to Prevent Scope Creep Before It Starts

The project that was supposed to be a one-day interview shoot. Then the client mentioned they also wanted b-roll. Then product shots. Then a testimonial from a second person they hadn't mentioned. Then a "quick version" for social. Then a revision to the version you already delivered.

Every one of those additions felt small in the moment. Taken together, they turned a $4,500 job into a $9,000 job that billed at $4,500.

This is scope creep. It is not a client being malicious. It is what happens when nobody defines what done looks like before the work begins.

Where Scope Creep Actually Starts

Not on set. Not in post. It starts in the first conversation, when the brief is still loose and everyone is optimistic.

Clients describe what they want in general terms. Production companies quote in general terms. Nobody pins down the specific deliverables, the specific revision count, the specific turnaround window, or the specific definition of a "finished" project. Both sides assume the other shares their mental model of what was agreed.

They don't. They never do.

The gap between what the client pictured and what the production company priced is where every scope creep problem lives. The shoot day happens inside that gap. The revision cycle happens inside that gap. The "one more thing" happens inside that gap, over and over, until the budget is gone and the relationship is strained and nobody is sure exactly how it got here.

The solution is not to be more suspicious of clients. It is to close the gap with documents before the camera goes anywhere near a card.

The Three-Document System

Professional production companies run on three documents that together eliminate most scope disputes. Not reduce. Eliminate.

Document One: The Discovery Questionnaire

This is a structured intake form completed before a single number is put on paper.

The discovery questionnaire forces both the client and the production company to think through the job before it has a price on it. Typical fields include:

• What is the primary deliverable, and what platform will it appear on?
• How many total deliverables are expected, including cutdowns and format variations?
• Is this a union or non-union production?
• What is the approval chain on the client side, and how many people have sign-off authority?
• How many rounds of revisions are expected in post?
• What is the broadcast/distribution window after delivery?
• Are there any existing brand guidelines, legal review requirements, or regulatory considerations that affect content?
• Has a budget range been discussed internally?

None of these questions is gotcha. They are the questions any producer needs answered to build an accurate estimate. When clients fill out a discovery form, they often discover aspects of the project they hadn't thought through either, which is exactly the point. The friction of the form is the value of the form. It reveals complexity before anyone has committed to a number.

When GLM sends a discovery form before an estimate, it signals to the client that this is a professional operation that thinks in systems, not gut-feel quotes. That perception matters for every conversation that follows.

Document Two: The Scope of Work

The scope of work (SOW) is the most important document in a production relationship. More important than the contract in most practical situations, because the contract references the scope and the scope defines what was actually agreed.

A production scope of work answers seven questions:

What is being produced? Not "a video." A :60 hero brand film, a :30 cutdown, and three 9:16 social derivatives. Named formats, named platforms, named durations.

How many shoot days? Including prep days, the production date, and any scheduled wrap time. If there is a weather day or a built-in contingency day, state it explicitly.

Where does the work happen? Location, or studio. If location is TBD, note what the pricing assumed and what happens if the actual location differs.

Who is responsible for what? What does the production company supply versus what does the client supply? Props, talent, food, transportation, location access. This is where the "I thought that was included" conversations come from when it is missing.

How many revision rounds are included in post? This number matters more than almost anything else in the document. Two rounds is standard. Three is generous. "Until the client is happy" is not a number and should never appear in a scope of work.

What is the delivery format? Not just file type. Codec, resolution, frame rate, audio spec, color space, naming convention. The client who asks for "a 4K file" and the post team who delivers a ProRes master when the platform needed H.264 are both following the instruction. The scope should make this unambiguous.

What is explicitly excluded? This section gets skipped or softened by production companies who do not want to seem difficult. It is the most valuable section in the document. Music licensing, voiceover recording, motion graphics beyond lower thirds, any additional locations beyond those listed, any deliverables not named above. If it is not included in the scope, say so. Not aggressively. Just clearly.

The SOW does not need to be long. The best ones are a single page. What they need to be is specific.

Document Three: The Change Order Protocol

A change order protocol is simply a written agreement, made before the job starts, about how changes to the scope will be handled when they arise.

The key elements:

• Any addition to the agreed scope requires a written change order before the work begins.
• Change orders include the cost of the addition and any impact on the delivery timeline.
• Verbal approvals do not authorize scope changes. Written approval does.
• The client has a stated number of business days to approve or reject a change order. After that window, the work either proceeds under the original scope or pauses until approval arrives.

The reason this needs to be established before the project starts is that mid-project is a terrible time to have the procedural conversation. When a client asks for something additional during a shoot day, the moment is charged and the relationship is in motion. If the production company says "that will be a change order," and the client has never heard that term before in this relationship, it reads as antagonistic. If the protocol was established in the SOW and signed off at the start, the same conversation is just following the process everyone agreed to.

What Kill Fees and Revision Limits Actually Protect

Kill fees and revision limits are not punitive clauses. They are compensation structures for real costs that clients sometimes forget are being incurred.

Kill fees compensate the production company for work completed before a client cancels a project. A standard kill fee schedule runs: 25% of total if cancelled before prep begins, 50% if cancelled after prep but before principal photography, 100% if cancelled on or after the shoot day. These reflect the real costs: prep labor, booked crew, reserved equipment, location deposits, materials purchased.

Without a kill fee clause, a production company that has locked crew, reserved gear, and spent two days in prep has no recourse when a client calls the morning of the shoot and says "we're putting this on hold." The work that happened was real. It should be compensated.

Revision limits protect two things: the editor's time and the editorial integrity of the cut. Three rounds of revisions on a :60 commercial is a meaningful amount of feedback time. By round four, what typically happens is not that the work is getting better. It is that a new stakeholder entered the approval chain, or a client who approved the cut in round two changed their mind, or the original creative brief shifted underneath the project.

Revision limits create a structure where clients consolidate feedback seriously before submitting it. The limit is not "you only get to improve it twice." It is "you get two organized rounds of meaningful feedback, after which additional rounds are change orders." The client who understands this turns in better notes, because they know the clock is running.

How to Have the Scope Conversation Without Sounding Defensive

The mistake most production companies make is framing scope documents as protection against bad clients. That framing makes the conversation adversarial before it needs to be.

A better frame: these documents are how professional production works. They protect both parties.

When presenting a scope of work, the language is collaborative. "Here is exactly what we are making together. Here is what each side is responsible for. Here is how we handle changes if the project evolves." That is a confident production company explaining its process, not a nervous one pre-emptively defending against a problem that hasn't happened.

When the revision limit comes up, the framing is practical. "We include two rounds of feedback in the post budget. After that, additional rounds are billed at our standard post rate, which I can give you in writing. Most projects close within the included rounds. If yours needs more, we handle it, we just price it accordingly."

No apology. No defensiveness. Just process.

The production company that presents a clear scope document early in the relationship is signaling expertise. Clients are paying for someone who knows how this works. A well-structured SOW is proof of that knowledge before a frame is shot.

The Real Cost of Skipping This

The project that runs over scope without documentation is not just a money problem. It is a relationship problem.

By the time the production company realizes the job has grown past its budget, two things are true: the work is too far along to renegotiate cleanly, and the client has no idea there was ever a problem. From the client's side, they asked for reasonable things and got them. From the production company's side, they absorbed costs they were never paid for.

The resentment that builds on the production company's side in that situation corrupts the relationship. Clients can feel it even when it is never said. The work that should generate a repeat booking does not.

The three-document system does not guarantee that every project goes smoothly. Jobs have surprises. Clients change their minds. That is production. What the system does guarantee is that when something changes, both sides know exactly what changed, what it costs, and what the options are.

That conversation, had clearly and early, is the difference between a client relationship that compounds over years and one that ends at delivery with mutual frustration on both sides.

Define done before the job starts. It is the most valuable thing a production company can do for its clients, and for itself.