When a creative request is blocked, pause and review the underlying brief against the current policy. Do not assume the block is a mistake, and do not repeatedly disguise the same request to try to obtain a different result.
Record what you actually know
Separate the intended creative goal from the observed response. Record the non-sensitive brief, the response wording available to you and the stage at which work stopped. Do not infer an exact policy trigger unless the available explanation establishes it.
Runway's supplied policy passage describes automated systems and internal human review that detect and block harmful inputs and outputs. It does not explain every block or establish a guaranteed review or appeal route.
Complete a legitimate brief-review form
Use these fields to decide whether the concept can responsibly continue:
- Communication goal: What should the audience learn or understand?
- Literal depiction: What people, actions and circumstances does the request actually describe?
- Harmful ambiguity: Could the request imply coercion, deception, humiliation or another harmful context you did not intend?
- Identity and permission: Does it involve a real person or material whose use has not been approved?
- Policy question: What exact uncertainty needs checking in the current documentation?
- Substantive alternative: Can the goal be met by removing the problematic depiction rather than concealing it?
- Decision owner: Who can stop or redesign the project?
Keep secrets, customer records and private reference materials out of this review exercise.
Hypothetical example: a safety-training scene
Suppose an Indian training studio wants a fictional workplace-safety explainer. Its draft asks for a dramatic confrontation between a supervisor and a worker, but the educational objective is simply to teach how to report a hazard.
Assume the request is blocked; the example does not identify why. Review whether the confrontation adds necessary instruction or merely spectacle. A substantive redesign could use an illustrated hazard, a reporting checklist and a neutral adult narrator, without identifiable workers or invented accusations.
Evaluate the redesign by checking whether all three reporting steps remain clear and whether the threatening interaction has genuinely been removed. Changing spellings or hiding the same scene in coded language would not be a legitimate editorial revision.
Decide whether to stop or seek clarification
Stop if the objective depends on harmful depiction or if a significant policy question remains unresolved. Next, consult current documentation and use only any clarification options actually documented there. Do not assume a particular support route exists or promise that a revised request will succeed.
If comparing future access, inspect the AI tools catalog, checking access format and saving terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence; alternate access is not a policy workaround.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Runway's Usage Policy establishes the bounded moderation-process description, not the reason for a hypothetical block. The form and redesign exercise are editorial advice, not filter-evasion instructions or a promised appeal process.