Practical production resource
Video production scope of work template
A scope of work describes the boundaries of the production. It should be specific enough that the client and the team can recognise both the agreed output and a new request.
Describe the finished outputs
List the number of films, approximate duration, aspect ratios, captions, language versions and delivery formats. Distinguish a different export from a separately edited film when the difference affects effort.
Describe the production allowance as well as the output. A final runtime does not say how many filming days, locations, contributors or editing rounds are included.
Make approvals and dependencies explicit
Name the person who consolidates feedback, the included review rounds and the expected response dates. Record the assets, access and approvals the client provides. Explain how a delay or change will be discussed.
Keep usage rights, releases, payment obligations and legal terms in your company’s appropriate agreements. This template is a scope-planning aid, not a complete contract.
Keep changes visible after acceptance
When a new request arrives, compare it with the accepted scope before estimating additional work. Record what changes, its effect on price or dates and who has approved it.
The CRM preserves the accepted scope and supports priced variations from the job. Describe the changed or additional work, enter the deliverables and price, then copy the proposal for the client. Record approval or decline with evidence. Approval creates extra delivery tasks; the original agreement remains unchanged. Client communication and any signatures stay in your existing process.
Use the template
Adapt the fields to your own production and review the details before sharing it with a client.
Download text templateVIDEO PRODUCTION SCOPE OF WORK Production reference / quote version: [Details] DELIVERABLES [Repeat for each distinct Film / Live stream / Shoot only item] Name / type / duration: [Details; duration not required for shoot-only] Delivery versions: [Each version name and format, including captions/languages] Raw-footage handover for shoot-only: [Named output and format] PRE-PRODUCTION [Planning, scripting, meetings and approvals included] FILMING [Days/hours, locations, contributors and crew assumptions, or filming not required] POST-PRODUCTION [Editing, graphics, audio, captions and exports included] REVISIONS [Included rounds or not required, feedback coordinator and review deadlines] CLIENT RESPONSIBILITIES [Assets, access, contributors, approvals and required dates] EXCLUSIONS [Additional outputs or services outside the price] TIMELINE AND DEPENDENCIES [Milestones and what each depends on] CHANGES [Original accepted quote reference and version] [Client request, additional outputs and any explicit replacements] [Additional price, currency, tax and due date] [Decision, who approved/declined, when and evidence] [Review affected original tasks if work is replaced] RELATED AGREEMENTS [References to the applicable commercial terms]
Common questions
Should revision rounds be in the scope?
Yes. Define the review process and allowance clearly so both sides can recognise when a request changes the agreed work.
Does the CRM automatically detect scope creep?
No. Producers compare the request with the original agreement. Required-field checks help complete a quote, and variations record priced changes and decisions, but the app does not interpret emails or detect scope creep automatically.