Testing My Shot List in Runway Before Booking the Shoot
Every shot in my next video got a Runway test render first. Two shots died, one changed completely, and the shoot day got cheaper.
Shoot days are where video budgets die, and they die on shots that seemed fine in the script. My new pre-production step: every ambitious shot on the list gets a Runway test render first. It is not the final look, but it answers the only question that matters: does this shot survive existing at all.
The process is deliberately fast, fifteen minutes per shot maximum. Write the shot as a motion prompt (subject, action, camera move, lighting), generate two or three takes, and make a call: keep, modify, or kill. The point is not beauty; a rough render answers 'does this composition read in motion' well enough to bet money on it.
The test killed two shots from my last list. The drone pull-back through the window I had storyboarded turned out, in motion, to reveal a transition nobody could follow. And the slow push-in on the product existed to hide that there was no second angle; seeing it rendered made that obvious. Both replaced with simple shots that actually serve the cut.
One shot changed rather than died: the overhead flat-lay that rotates was too slow in render and exposed how long three seconds of nothing feels. The fix, a faster half-rotation with a cut mid-move, went straight into the shot list. That is the kind of note you normally get on the day, when the clock is eating money.
The budget argument sells itself: a few hours of Runway credits against a day rate plus location plus crew. But the quieter benefit is that the edit got better, because the shot list now contains only shots proven to work in motion. Storyboards show what you hope; motion tests show what you get.