A Practical AI Risk Check for Film Teams

Before a film team uses an AI tool, answer a narrower question than “Is AI good or bad?” Identify the exact file, task, service, and decision. A script excerpt, call sheet, casting image, and public press release carry different rights and privacy risks.

This is a workflow check, not legal advice. A contract, union agreement, employer policy, or rights-holder instruction takes priority over a general checklist.

  <h2>1. Check who can authorize the use</h2>
  <p>Find the person or organization that controls the material. Check the production agreement, confidentiality terms, client instructions, and applicable workplace policy before sending it to a tool. A person’s access to a file does not automatically grant permission to upload it to another service.</p>
  <p>Rules can be agreement-specific. For example, the <a href="https://www.wga.org/contracts/contracts/mba/2026-mba-contract-changes-faq">WGA’s 2026 MBA FAQ</a> describes a notice requirement when a company licenses writers’ work to train a commercial generative AI system. That applies to covered agreements; it is not a rule for every writer, production, or service. Check the current agreement and ask the relevant representative when coverage is unclear.</p>

  <h2>2. Classify the material before sharing it</h2>
  <ul>
    <li><strong>Public:</strong> already released or approved for public distribution.</li>
    <li><strong>Internal:</strong> schedules, budgets, contact sheets, or drafts meant only for a team.</li>
    <li><strong>Restricted:</strong> unreleased scripts, likeness or voice material, personal data, confidential client work, or anything under an NDA.</li>
  </ul>
  <p>When the category or permission is unclear, do not upload the file. Removing names may reduce exposure, but it does not make a distinctive script, image, or story anonymous.</p>

  <h2>3. Read the service terms for this use</h2>
  <p>Check the exact account and product settings for retention, model training, human access, subprocessors, deletion, and who can retrieve the output. Do not assume that a paid plan, a “private” label, or an account login answers those questions. If the terms do not support the project’s requirements, choose an approved service or keep the material out.</p>

  <h2>4. Limit the task and keep a human decision-maker</h2>
  <p>Write down what the tool may do and what it may not decide. A team might test whether an approved tool can format already-approved production notes. That does not authorize it to invent schedule facts, judge a performer, rewrite a writer’s material, or make a hiring decision.</p>
  <p>For a hypothetical unreleased screenplay summary, first confirm the project permits the upload and the service terms fit. Use only the minimum useful excerpt if the task allows it. Then compare every plot point against the source; do not use the generated summary as coverage or a recommendation. If the task cannot be done without exposing restricted material, stop.</p>

  <h2>5. Pilot, record corrections, and set a stop rule</h2>
  <p>Start with a low-risk, approved sample. Record the source version, tool and settings, reviewer, corrections, and time spent checking the output. Count review and cleanup as part of the workflow. A shorter first draft is not a gain if it takes longer to verify or introduces errors.</p>
  <p>Stop the pilot if the output invents facts, exposes material to an unapproved party, cannot be traced to its source, or requires a person to make a decision the tool should not make. Keep the original file as the authority and make responsibility for approval explicit.</p>

  <h2>Two useful boundaries</h2>
  <p>The <a href="https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf">U.S. Copyright Office’s report</a> says copyrightability of AI-assisted output depends on human authorship and is assessed case by case; prompts alone do not establish enough control under the Office’s analysis. This is a U.S. copyright discussion, not a promise about every work or jurisdiction. Keep records of human-created material and substantial creative decisions, and get qualified advice for rights questions.</p>
  <p>Audio can be one way to access text, but it should not erase the text or the screenplay’s visual information. <a href="https://www.w3.org/WAI/media/av/transcripts/">W3C’s guidance</a> says prerecorded audio-only content needs a transcript to meet WCAG Level A. Keep the original and an accessible text alternative available when a workflow creates audio-only material.</p>

  <h2>Before the next upload</h2>
  <ol>
    <li>Who approved this exact use?</li>
    <li>What information leaves the team, and under which service terms?</li>
    <li>What may the tool produce, and what decision stays with a person?</li>
    <li>Who checks the result against the source?</li>
    <li>What condition makes the team stop?</li>
  </ol>
  <p>If you cannot answer these questions, pause. A useful workflow makes the permission, risk, and review path clear before anyone uploads the work.</p>