Correction, 2026-10-01: an earlier version counted the example deliverables as nine files. Five videos (a master, three cutdowns and a bumper), each delivered captioned and silent, plus a caption file for each, is fifteen files: ten videos and five caption files. The count is corrected throughout, and an unsourced claim that most timelines slip on the client side is softened.
Every creative overrun traces back to one of three ambiguities: what exactly is being delivered, how many times it can be changed, and who can say yes. Fix those three in writing and most scope creep disappears, because scope creep is rarely a client acting badly. It is two people who agreed on a project and never agreed on the same project.
The six lines a scope needs
1. The deliverables, enumerated. Not "a brand video." One 30-second master at 16:9, three 15-second vertical cutdowns, one 6-second bumper, all with burnt-in captions plus separate caption files, and a silent version of each. That is fifteen files (ten videos and five caption files), and the difference between that sentence and "a brand video" is the difference between a profitable project and an argument. See what is a deliverables list.
2. Rounds, and what counts as one. Two rounds included is normal. Define a round: one consolidated set of feedback, delivered once, from the named decider. Six people sending notes separately over four days is not one round even though it feels like it to them.
3. The decider, by name. One person who can approve. If the real approver is someone who has not been in a meeting yet, the project has an unfunded round in it already.
4. Timeline with client-side dates. Not just your delivery dates. Feedback due dates too, with the stated consequence that a late round moves delivery. Timelines often slip on the client side and get blamed on the supplier.
5. What is excluded. The most valuable line and the one everyone omits. Naming what you are not doing (localisation, additional formats, ongoing edits, usage beyond the agreed term) prevents the assumption that it was included.
6. Usage and rights. Where the work runs, in what media, for how long. Priced separately from making it. See what is a usage licence.
The three ambiguities, in detail
"A video." Every deliverable has an invisible tail of format versions, and clients picture one file while suppliers quote fifteen. Enumerate at quote stage, always.
"Some revisions." Unbounded revision destroys per-deliverable pricing. Two rounds, defined, then priced.
"The team will review." A team does not approve; a person does. Committees generate contradictions and the supplier ends up refereeing them, which is unpaid work with no upside.
What AI changed about scoping, and what it did not
Changed: the volume clause. Scopes used to cap variants because producing them was expensive. Now a scope can reasonably promise fifteen tested variants where it used to promise three, and that is a competitive advantage worth writing in. Using canon 8frame prices, a credit being $0.01 in a top-up pack, fifteen drafted video variants as 8-second Veo 3.1 Lite clips with sound is 810 credits, roughly $8, so the constraint is your judgment time, not the render budget.
Changed: when discovery can happen. Style frames at 6 to 21 credits mean the "what does this look like" question can be answered during scoping rather than in round one. A scope agreed against a picture overruns less than a scope agreed against adjectives.
Did not change: rounds. Cheap regeneration makes it easier to say yes to one more version, which makes an unbounded revision clause more dangerous than it used to be, not less. Hold the two-round line harder than before.
Did not change: approval structure. No tooling fixes an unnamed decider.
A scope that fits on one page
Project: Refill launch campaign Deliverables: 1x 30s master (16:9), 3x 15s (9:16), 1x 6s bumper, captions burnt-in and as SRT, silent versions of all. 15 files (10 videos, 5 SRT). Included: concept, 3 directions at style-frame fidelity, production, 2 rounds of consolidated feedback, format versioning. Excluded: localisation, additional formats, paid media management, usage beyond 12 months organic and paid social. Decider: [name]. Dates: directions [date], feedback due [date], rough cut [date], feedback due [date], delivery [date]. Late feedback moves delivery by the same number of days. Rights: 12 months, organic and paid social, worldwide. Change orders: additional rounds or deliverables quoted before work begins.
Boring, short, and it prevents most of what goes wrong.
FAQ
How many revision rounds should a creative scope include? Two. A third is survivable; a fourth means the brief was wrong, and the fix is upstream in the creative brief rather than in more rounds.
How do I handle a client who adds deliverables mid-project? Quote them as a change order before starting. Saying yes informally once establishes that the scope is negotiable throughout.
Should the scope say we use AI? Yes, at quote stage, alongside anything the client needs disclosed downstream. See how to price creative work in the AI era.
Sources
- 8frame prices (Veo 3.1 Lite 54 credits for 8 seconds with sound; stills from 6 credits on Nano Banana Classic or Seedream 5 Lite to 21 on Nano Banana Pro at 1K or 2K) and credit value ($0.01 at pack rate): 8frame back tool registry cost functions, origin/main, read 2026-10-01, and 8frame pricing
Scope creep is a definition problem, not a discipline problem. Define the fifteen files, the two rounds, and the one decider.
Try it without signing up: the 8frame canvas opens on a real board. The canvas is free and unlimited; generation is paid from $19/month.