How to Check Film Festival Submission Rules for an AI Short Film

An AI short film can be ready to screen while its submission plan is still vague. A listing site may show a category that sounds suitable, a discussion may mention that a festival screened a generated film, and a friend may remember a programmer saying submissions were welcome. None of those tells you what the current edition requires of your specific film. Before paying an entry fee or cutting a festival version, I would build a small verification sheet for each event.

The first row is the official entry page for the current edition. Record the date you checked it, the relevant category, the deadline, runtime limits, premiere or prior-publication conditions, delivery format, and any question about generated footage or synthetic performance. If a rule is unclear, mark it unresolved. Do not fill the blank with a confident answer from an old forum thread. Submission platforms are useful for discovery and logistics, but the event’s own current instructions and a direct answer from its team should settle an ambiguous point.

The second row describes the film accurately. Was the story written by people? Are some backgrounds generated while performances were filmed? Is the whole picture generated? Are any voices synthetic? Does the film depict real people or events? Those distinctions matter because “AI film” can describe very different production methods. A concise production note makes it easier to answer a festival’s form consistently and avoids a last-minute scramble over what the team can honestly claim. Keep the note separate from the marketing blurb so a change in promotional language does not quietly change the production facts.

The third row is about the reason for submitting. Are you looking for an audience, a conversation with other filmmakers, a portfolio credit, or feedback from programmers? A screening in a relevant small room can be more useful than an expensive long-shot application, depending on the goal. Think about the likely audience as well as formal eligibility. People disagree strongly about generated film, and a category label alone does not guarantee a friendly reception. That uncertainty should shape expectations and the presentation plan, not invite anyone to hide how the film was made.

I would also keep an asset and rights checklist before final export: music, effects, voices, footage, artwork, and any material supplied by collaborators. The checklist is a record of what the team actually used and what it has permission to submit. It is not a substitute for reading the event’s rules or for professional advice on a difficult rights question. If a requirement is uncertain, ask the organizer a narrow question with the relevant production facts and save the reply with the submission record.

Finally, avoid turning a single acceptance or rejection into a universal rule about festivals. Selection involves programming taste, available slots, audience fit, and the quality of the film itself. A practical tracker can show which questions recur and which destinations are worth the work. For filmmakers submitting generated or hybrid shorts, what question tends to stay unclear longest: eligibility, disclosure wording, asset documentation, or where the film fits in the program?

The distinction between a hybrid film and a fully generated one should be in the production note. A single checkbox rarely captures it.

I would save a PDF or screenshot of the official rules on the day I submit. Pages can change between the deadline and screening.

That is sensible record keeping. I would also keep any direct reply from the organizer with the same entry.

Do you think a filmmaker should email before submitting whenever the AI language is missing, or only if the film is heavily generated?

If the missing rule could change whether you submit or how you describe the film, I would ask. Keep the question short and factual.

The goal row is useful. I have seen people judge a screening only by prestige when the actual value they wanted was a real discussion afterward.

Asset documentation is a separate task from eligibility. The organizer may welcome the film while a music or voice permission is still unresolved.

存档这招好,规则页中途改过的情况我碰到过

One rejection does not reveal a universal policy. A tracker with the exact category and edition would prevent that overgeneralization.