Set Clear Boundaries for Deliverables, Revisions, Approvals, Reshoots, and Scope Changes

A strong creative project agreement should state exactly what you will deliver, how many revisions are included, who has approval authority, what happens if a reshoot or additional version is requested, and how work outside the original scope is priced and approved. Clear boundaries protect both the client and the creator: the client knows what to expect, and the creator retains control over their process, intellectual property, schedule, and compensation.

Start with a Specific Deliverables List

The most effective way to prevent confusion is to define the deliverables before production begins. Avoid broad phrases such as “final content,” “a campaign,” or “edited assets” unless the agreement also explains what those phrases include. A deliverables list should identify the format, quantity, length, intended use, delivery method, and expected timing for each item. For example, a project may include one primary video, a defined number of cutdowns, a set number of edited photographs, a written article, source design files, or another clearly described output. If raw footage, working files, project files, alternate takes, unused concepts, captions, transcripts, or platform-specific exports are not included, say so directly.

Specificity is not inflexibility. It gives both parties a shared starting point. A client can request work with confidence because they understand what has been purchased. A creator can plan time, crew, equipment, production, post-production, and delivery without assuming that every possible variation is automatically included. If a deliverable depends on information, access, products, locations, talent, brand assets, or approvals supplied by the client, identify those dependencies as well. Delays or missing materials from the client can affect delivery dates, production feasibility, and the final scope.

Deliverables should also distinguish between drafts and final files. A preview, proof, rough cut, low-resolution review link, watermarked image, or internal presentation may be provided only for review and approval. It is not necessarily a final deliverable or a license to publish, distribute, edit, or transfer the work. Final delivery should occur according to the agreed payment and approval terms.

Define What Is Included in the Creative Scope

Scope is more than a list of files. It includes the agreed creative objective, concept, production approach, schedule, number of production days, locations, participants, technical requirements, distribution assumptions, and level of post-production. When these elements are documented, requests can be evaluated fairly: are they part of the original assignment, a reasonable revision to existing work, or new work that requires a change order?

A useful scope description can include a creative brief, treatment, mood board, shot list, outline, or written summary of the approved direction. These materials do not need to eliminate all creative judgment. In fact, the creator should retain control over the professional methods, workflow, artistic decisions, tools, staffing, and techniques used to produce the agreed work. The client may define business goals, required messages, brand standards, legal requirements, and approval criteria. The creator remains responsible for determining how to perform the services in a way that meets the agreed scope.

Creator control matters because creative work is not a mechanical commodity. A client may commission a result, but that does not automatically mean the client controls every unfinished file, every production decision, every alternative concept, or every component of the creator’s process. The agreement should reflect the actual relationship and should not imply rights, ownership, or authority that have not been expressly granted.

Set a Revision Process That Is Practical and Fair

Revisions are often necessary, but unlimited revisions create uncertainty, delay delivery, and can turn a defined project into an open-ended obligation. State the number of revision rounds included in the fee and explain what counts as one round. In many projects, one round means the client gathers consolidated feedback from all internal stakeholders and submits one organized set of comments by the stated deadline. A second round may address the changes made in response to the first round. This process is more efficient than receiving separate, conflicting notes from multiple people over several days.

Revision feedback should be related to the approved scope, brief, brand requirements, or agreed deliverables. Requests that reverse a previously approved direction, introduce a new audience or platform, require a new concept, add substantial content, change the central message, or require major new production are generally scope changes rather than ordinary revisions. For example, changing a title card or correcting a factual error may be a revision. Replacing the storyline, adding a new product, changing the location after production, or requesting a different campaign concept is likely additional work.

Set clear review deadlines. If feedback is late, the creator may need to move the project in the production queue, revise the delivery schedule, or charge for restart work where appropriate. The client should appoint one authorized point of contact whenever possible. Consolidated feedback reduces duplicated effort and helps avoid a situation in which one stakeholder approves a version while another stakeholder requests a contradictory change.

Make Approval Authority and Approval Deadlines Clear

Approval should come from a person or group with authority to make decisions for the client. Before work begins, identify who can approve the brief, draft, final deliverable, budget changes, and any use of the work. If several people need to review, the client should manage that internal process and provide a single consolidated response. The creator should not be expected to resolve disagreements among client stakeholders or continue revising while internal approval remains unsettled.

Approval terms should state when feedback is due and what happens when no response is received. Depending on the project, the parties may agree that the delivery timeline pauses until feedback is received, that the timeline extends by the length of the delay, or that a draft is treated as approved after a stated review period. Any deemed-approval provision should be written clearly and used only where appropriate for the relationship and project.

An approval is meaningful. Once a concept, script, layout, proof, rough cut, or other milestone has been approved, later requests to change that approved element may require additional time and fees. This is not a penalty for changing direction. It is a practical recognition that the creator has relied on the approval to move into the next stage of work. Document approvals in writing, including email or the agreed project-management channel, so both parties have a reliable record.

Treat Reshoots and Rework as Separate Decisions

A reshoot should not be assumed to be included simply because a client would prefer a different result after production. A reshoot may be appropriate when the creator fails to perform the agreed scope, when a technical issue prevents delivery of the promised work, or when the parties agree that the original result does not meet documented requirements. Even then, the cause, remedy, timing, and responsibility for related expenses should be discussed promptly.

A reshoot requested because of a changed brief, new stakeholder preference, revised brand direction, altered product, unavailable location, client-provided materials, weather risk accepted by the parties, talent changes, scheduling delays, or new messaging is ordinarily outside the original scope. It may require a new estimate covering crew, equipment, travel, permits, talent, studio costs, post-production, and schedule changes. The same applies to re-recording, rebuilding, re-editing, re-designing, or recreating completed work when the request is not caused by the creator’s failure to meet the agreed deliverables.

The agreement should avoid promising outcomes that depend on factors outside the creator’s control. Creative work can be planned carefully, but availability, access, third-party participation, client decisions, technical environments, and external conditions can affect production. A clear reshoot policy allows the parties to address real issues without assuming that the creator must absorb every new cost.

Price Extra Versions, Formats, and Platform Requests Separately

A master deliverable is not automatically a complete library of every possible version. Extra aspect ratios, alternate edits, language versions, captioned versions, clean versions, shortened cuts, extended cuts, regional adaptations, resized graphics, additional thumbnails, still-image pulls, audio-only exports, or platform-specific formatting can require meaningful time and review. They should be listed as included only when they are actually part of the agreed scope.

If the client anticipates needing multiple versions, build them into the initial estimate with defined quantities and specifications. For example, the project may include one approved master plus a stated number of cutdowns in designated formats. Any additional versions can then be quoted based on the work required. This approach is more transparent than leaving the phrase “all formats” undefined.

Versioning also raises approval questions. A client should approve the master direction before requesting extensive derivative versions whenever possible. Creating numerous variations before the core content is approved can multiply rework if the message, pacing, graphics, product information, or legal copy later changes. A staged workflow protects the schedule and helps ensure that additional versions are based on a stable, approved source.

Use Written Change Orders for Work Outside the Original Scope

A scope change is any request that materially changes the agreed deliverables, timeline, production requirements, usage assumptions, or level of work. Common examples include adding deliverables, requesting more revision rounds, changing the concept after approval, adding shoot days, changing locations, adding talent or products, expanding usage, requesting source files, requiring expedited delivery, or asking for new versions not included in the original estimate.

The best practice is to document the change before the extra work begins. A written change order can be brief, but it should identify the requested work, adjusted fee, added expenses, revised timeline, payment terms, and any effect on rights or usage. Email confirmation may be sufficient if both parties agree that it forms part of the project record. The important point is that the creator is not required to begin out-of-scope work based on an informal assumption that the details will be sorted out later.

If a client asks for something new during production, the creator can respond constructively: explain whether the request fits the current scope, describe the impact on timing and budget, and provide options. Some changes may be small enough to accommodate. Others may require a revised estimate or a separate project. Respectful scope management is not refusal; it is a way to keep expectations, costs, and deadlines honest.

Protect Payment, Rights, and Legal Boundaries

Project scope and payment are closely connected. The agreement should state the fee, deposit or retainer requirements if any, invoice schedule, reimbursable expenses, payment due dates, late-payment treatment if applicable, and whether final files or usage rights are released only after payment is received. A creator should not be expected to provide additional work, transfer files, or expand rights without an agreed basis for compensation.

Ownership and usage rights should be stated separately from deliverables. Delivering a file does not automatically transfer copyright, assign ownership, grant unlimited usage, or authorize editing by third parties. Any license, assignment, work-made-for-hire arrangement, credit requirement, portfolio permission, confidentiality obligation, or restriction on use should be expressly addressed in the applicable agreement. The creator may retain rights in underlying materials, tools, processes, templates, pre-existing work, unused concepts, and other assets unless a written agreement says otherwise.

Clients are generally responsible for the accuracy and legality of materials they provide, including claims, product information, trademarks, permissions, releases, disclosures, and instructions relating to their business. Creators should not be asked to make legal determinations or guarantee regulatory compliance unless that responsibility has been expressly agreed and appropriately priced. For significant projects, both parties should seek advice from qualified legal, tax, insurance, or other professionals as needed. A project page or proposal can explain working boundaries, but it is not a substitute for a contract tailored to the specific engagement.

Create a Shared Record from Kickoff Through Delivery

Good project management supports good creative work. Keep the approved brief, schedule, estimates, feedback, approvals, change requests, invoices, and final delivery details in a shared written record. This does not require a complicated system. A clear email thread, project platform, or signed statement of work can prevent misunderstandings that are difficult to reconstruct later.

At kickoff, confirm the client contact, deliverables, included revisions, review windows, approval stages, budget, payment schedule, and expected delivery date. During the project, flag potential scope issues early rather than waiting until the final stage. At delivery, identify exactly what is being delivered, any remaining payment conditions, and the rights or permitted uses associated with the completed work.

Clear boundaries make collaboration easier. They allow the client to make informed decisions and give the creator room to deliver focused, professional work. When revisions, approvals, reshoots, extra versions, and scope changes are handled openly, the project can adapt without eroding the value of the original agreement.

Continue with the Deal Negotiation overview and the Revisions And Deliverables collection. Then compare the related creator guide and the next practical resource for the next step in this workflow.

FAQ

What Is the Difference Between a Revision and a Scope Change?

A revision adjusts work within the approved brief and included deliverables. A scope change adds or materially alters the work, such as requesting a new concept, new production day, extra deliverables, major re-edit, additional platform versions, or expanded usage. The agreement should define included revision rounds and require written approval for additional work.

Are Raw Files, Source Files, and Unused Footage Automatically Included?

No. These materials should be included only if the agreement specifically identifies them as deliverables. A final exported file, edited image, or completed design does not automatically include raw footage, layered files, project files, unused takes, alternate concepts, or the creator’s working materials.

Who Should Provide Project Approval?

The client should designate a person with authority to approve the work or submit consolidated feedback on behalf of the client. The creator should be able to rely on documented approvals and should not be responsible for resolving conflicting internal stakeholder requests.

What Happens If the Client Asks for a Reshoot?

The parties should first determine why the reshoot is requested. If the creator did not meet the documented scope, an appropriate remedy can be discussed. If the request results from a changed brief, new preference, new stakeholder input, scheduling issue, product change, or another client-side factor, the reshoot is typically additional work subject to a new estimate and schedule.

Can a Client Request More Versions After Final Delivery?

Yes, but additional versions should be treated as new work unless they were included in the original scope. The creator can provide a quote for new aspect ratios, cutdowns, alternate languages, resized assets, revised messaging, captions, or other requested adaptations.

When Do Usage Rights or Final Files Transfer?

That depends on the written agreement. Many projects provide that final deliverables and any agreed license or rights are released after all required payments are received. Rights, ownership, permitted uses, duration, territory, exclusivity, and editing permissions should be stated expressly rather than assumed.