Worked scenario — illustrative, not a customer result
Illustrative case: one approved master becomes square, vertical, short-form, and subtitled versions. Count each output and its reframing, caption QA, audio, and export checks. One creative direction does not mean every export is already included.
Contract checkpoint before production
Specify master runtime, cut stages, review rounds, aspect ratios, languages, subtitles, and derivative-output counts separately.
Document the actual scope change
Change record: version matrix; runtime and ratio; subtitle language; asset dependencies; reframing and QA estimate; fee; milestone; approval before export work.
Copy-and-customize wording
Use this as a practical starting point. Replace every placeholder with a fact from the approved project.
Free editable sample
No purchase or email required.
The project includes [master cut] and [versions]. Additional aspect ratios, runtimes, or platform cuts are [fee] each; extra edit rounds are [fee].
How to apply it
- Check the approved scope when: one master becomes many formats
- Check the approved scope when: rough-cut feedback arrives late
- Check the approved scope when: runtime changes after approval
- Estimate the changed outcome and obtain written approval of the current version
Use with care
- Match the message to the signed scope
- Estimate hidden review, QA, and coordination time
- Preserve written approval before changing delivery
Frequently asked questions
- When should I use this wording?
- Video editors should define cut stages, revision rounds, runtime, aspect ratios, and derivative versions separately to prevent one edit becoming a content package.
- Is this legal advice?
- No. This is practical business wording, not legal advice. Adapt it to your agreement and ask a qualified lawyer about legal requirements in your jurisdiction.
Continue with the next decision
Scope creep for video editors
Video editors absorb extra cuts, versioning, and format requests. This guide gives video editors triggers, scripts, and delivery checkpoints.
Contract clause libraryRevision Limits Clause for Freelance Contracts
A revision-limits clause defines the number of included rounds, what constitutes one round, and how additional revisions are approved and billed.
Client script libraryAdded Deliverable Request: Fee and Timeline Script
Name the additional deliverable separately from the current package, quote its fee and delivery impact, and preserve the original plan until approval.
Role × problem guidesScope-control solutions by client problem
Solve the exact boundary problem your profession creates. These guides combine role-specific triggers, precise wording, contract checkpoints, and a documented approval path.