The twelve-cut rule
- Limit
- Exactly 12 cuts in 30 seconds.
- Suits
- A process: cooking, repairing, packing a bag.
- Ask
- “Where did a shot outstay its welcome?”
An open timeline invites the same moves you always make: the familiar music bed, the favourite transition, the reflexive speed ramp. A constraint takes one of those options away. Suddenly you have to look at the footage again and ask what it can do on its own. That is where most editors find their next skill.
The best constraints are small and specific. “Make it cinematic” is a mood, not a limit. “Use only straight cuts” or “no shot longer than two seconds” are limits, because you can check whether you met them and reviewers can judge the result against them. A clear limit also protects feedback. When a reviewer knows you were not allowed music, they stop suggesting music and start commenting on rhythm and sound design instead.
Constraints also level the field for editors with different experience. Someone in their first month on CapCut and someone with years in Avid Media Composer can take the same brief and both learn something, because the limit is about thinking, not about owning a plugin.
Each brief names a constraint, the footage it suits and one question for reviewers. Adapt freely; the reviewer question matters more than the exact numbers.
Not sure where to begin? Press the button to draw a random constraint. If it does not suit your footage, draw again. Nothing is saved or sent anywhere; the picker runs in your browser.

A challenge should stretch everyone without excluding anyone. Rather than splitting editors into leagues, keep the same core constraint and change one variable.
| Level | Twelve-cut rule variation | Focus for reviewers |
|---|---|---|
| Starting out | 12 cuts in 45 seconds, any order | Does each shot show something new? |
| Building | 12 cuts in 30 seconds, with one J-cut | Is the sound lead smooth? |
| Experienced | 12 cuts in 20 seconds, last shot rhymes with first | Does the rhyme add meaning? |
Notice that the reviewer question changes with the level. Feedback on a first edit should help the editor see; feedback on an advanced edit can debate nuance. Neither is more important. If you notice a reviewer judging a beginner by advanced standards, point them back to the brief.
When you are done, take your cut to the feedback guide, or check the export FAQ before you share it.