Treat an AI-video storyboard as a set of requirements to validate, not a promise that a tool can execute every shot. Run a bounded concept test with rights-cleared, non-private inputs before committing to a delivery method or fixed production scope.
Separate outcomes from production methods
Describe what viewers must understand before naming how a shot will be made. “The parcel arrives intact” is an outcome; “one uninterrupted moving shot follows it through three rooms” is a particular execution.
For an Indian studio quoting a campaign, distinguish mandatory brand facts from optional camera moves. This creates room for approved substitutions without silently changing the brief. Do not infer technical capability from a provider's usage-rights statement.
Draft a concept-validation worksheet
For each shot, record:
- Required outcome and approximate duration.
- Non-negotiable details, such as object identity or readable wording.
- Acceptable substitutions, agreed before testing.
- Input origin and permission status.
- Observable pass criteria and failure conditions.
- Maximum experiment count, review time and budget in rupees.
- Fallback method and person authorised to approve it.
Use invented brands, self-created props and fictional environments for exploratory tests. Do not upload client footage or private briefs. If an intended technique is not established by the supplied documentation, label it “to be validated”, not “supported”.
Hypothetical three-shot plan
Suppose a fictional delivery-service concept lasts nine seconds: a sealed blue parcel on a desk, the parcel crossing a doorway and a final delivery message.
Set an editorial test budget of â‚ą1,500 and a 90-minute review window; these are planning inputs, not platform prices. Allow at most three candidate attempts per uncertain shot. Require the parcel to remain blue and sealed, with no invented text.
The doorway shot is the highest-risk requirement. An agreed substitute could be two static compositions joined by a cut. The final message could use separately prepared, verified lettering rather than depending on generated text.
Evaluate each candidate against the written criteria. Record pass, revise or reject without claiming any test has already succeeded. This example is entirely hypothetical.
Stop before experimentation becomes a promise
Stop testing when the budget or attempt cap is reached, or when a mandatory detail remains unreliable. Choose the approved fallback, revise the brief or decline the execution promise.
Before paying for experimental access, check the AI tools catalog, confirm access format and save offer terms. Marketplace account, code or token offers are not proof of official subscription equivalence. Provider documentation and marketplace access conditions require separate review.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Runway usage rights establishes bounded ownership and absence of provider-imposed non-commercial restrictions. It does not establish shot-level execution capabilities. The worksheet, budget, attempt cap and fallback plan are practical editorial advice, not hands-on findings.