WGA AI Rules for Screenwriters: What Applies to You

Published by StoryNotes. We make an AI screenplay tool — one of the things this article is about. It names, plainly, the line our own category should not cross, and the places these rules don't reach you at all. Weigh it accordingly.

"The WGA banned AI" is the version that traveled. It is not what the agreement says. The rule most writers are afraid of — the one they picture switching on the moment they open a chatbot next to their draft — governs studios and the writers they employ. It has almost nothing to say about the script sitting on your laptop. The confusion is fair, because the actual document is a labor contract written for members and their representatives, not a permission slip written for you. This is the plain-language version.

TL;DR: You can use AI on a script you own and haven't sold — no guild rule reaches it. The rules that matter switch on at the sale or the job: AI can't take your writing credit, no one can force you to use it, and any AI-generated material you're handed has to be disclosed. And a tool that reads your finished pages and gives notes is feedback, not a co-writer — a different thing from the AI-as-author the credit rules are built to catch. This is a translation, not legal advice; for your situation, the guild is the source of record.

No. The 2023 Minimum Basic Agreement — the contract that ended the strike — did not prohibit writers from using AI. What it did was fence in how signatory companies can use AI in covered writing work: it blocks a studio from treating an AI as a credited writer, from forcing AI onto a writer who doesn't want it, and from quietly passing off machine-generated pages as assignment material. Those are limits on the company, not on you.

The "ban" framing spread because AI was one of the fights the strike was actually about, so the settlement's AI language got reported as a crackdown. It is a crackdown — on the studios' ability to use AI against writers' pay and credit. Read as a rule aimed at the individual writer, it points the wrong way.

One concrete fix: Before you assume a rule applies to you, ask who the contract is between. If you are not being employed by, or selling to, a signatory company, most of what you've read about "the AI rules" describes a relationship you are not in yet.

AI was a core issue in the 2023 strike, which ran 148 days — the writers walked on May 2 and the strike lifted on September 27 after a tentative deal (Forbes, 2023). AI landed in a labor contract for a concrete reason: the fear that studios would use generative tools to undercut what a writer is paid and credited for — generate a draft with a machine, hire a writer cheaply to "polish" it, and call the human a rewriter instead of the author.

So the deal drew its lines around the company's behavior. In the guild's own summary, generative AI is not a writer, so nothing it produces counts as literary material; a company can't require a writer to use it; and a company that hands a writer AI-generated material has to disclose that (WGA, retrieved July 2026; The Hollywood Reporter, 2023). Every one of those is a constraint on the employer.

The sentence that unlocks the rest is simple: the agreement is a deal between the guild and the companies that sign it. Whether any provision touches you depends entirely on whether you're inside that relationship — employed by, or selling to, one of those companies. Which is why the honest answer isn't one rule. It's three situations.

One concrete fix: Read the AI provisions as answers to the question "what can a studio do to a writer it's paying?" — because that's the question they were written to answer. Your own drafting isn't in the frame.

No. There is no guild rule against using AI on a script you own and have not sold. The MBA governs employment and the sale of material to signatory companies; a writer drafting a spec at their own desk, for no one yet, is outside its scope. Nothing in the agreement regulates the tools you point at a page you own.

Day to day, that means brainstorming with a chatbot, asking it for structural notes, or running coverage on your own draft aren't violations of anything — because there's no "anything" there to violate yet. Guild membership doesn't change this for an unsold spec; a member writing on spec is still writing on spec. The contract activates around the job, not around the person.

Two honest caveats. First, "no guild rule" is not "no consequences" — a future buyer may have preferences, and some writing communities are openly hostile to AI use, which is a social fact even where it isn't a contractual one. Second, this is guild rules, not craft: permission doesn't make the pages good. And to be plain — this is a translation, not legal advice. For your specific situation, wga.org and the guild are the source of record.

One concrete fix: Treat your unsold draft as what it is — yours. If a tool helps you see the structure, use it; the rule you're worried about doesn't switch on until you try to sell what you've written.

This is where the provisions actually engage — and they run in the writer's favor. Once you're being employed by, or selling to, a signatory company, four things hold, in plain language (WGA, retrieved July 2026):

• Your credit is protected. AI isn't treated as a writer, and AI-generated material isn't "literary material." If a company hands a writer unpublished AI-produced pages, those pages don't count as assigned material for pay or as source material for credit — and can't be used to deny separated rights. The machine can't be slotted in ahead of you to shave your credit.
• You can't be forced — or refused. A company can't require you to use AI to perform writing services. Use is your choice, made with the company's consent and under its policies; declining isn't grounds to pass you over.
• Disclosure runs to you. If a company gives you materials that were generated by AI or contain AI-generated material, it has to tell you. You're entitled to know whether the pages you're building on came from a person or a program.
• Training is contested. The guild reserved the right to assert that using writers' material to train AI is prohibited under the agreement or other law. This one is unsettled — treat it as an open front, not a closed rule.

A quick map of what's actually inside the contract's reach:

One concrete fix: If a sale or an assignment is in play, get the AI question in writing — what you were handed, what was disclosed, and that no one required you to use it. The protections are real, but they're only useful if you can point to them.

No — and it's the distinction most worth understanding, because the rules are about AI-generated writing, not about feedback. A tool that reads a finished draft and returns notes doesn't produce material that could ever displace your credit. It isn't writing anything. It's reading.

Draw the line clearly. A generative co-writer produces pages — new scenes, new dialogue — and that output is exactly what the credit and disclosure provisions are built to track. An analysis tool goes the other direction: you give it your completed pages, and it gives back an assessment — a graded read, the way a reader's report or a set of studio notes always has. One makes text that competes with yours; the other evaluates text you already wrote. The contract's machinery is aimed at the first kind.

This is the honest place to say where our own category sits. An analysis tool of this sort returns a six-stage report, from genre and tone through character and plot structure to theme and scene-level craft — a diagnosis of the draft you handed it, not a rewrite of it. That's the notes side of the line. It's also why the sequencing writers already use — a cheap first-pass read before you pay for a human one — sits nowhere near the authorship question the WGA provisions police.

One concrete fix: When you weigh any AI tool against "the rules," ask one question — does it write pages, or read them? If it reads, you're looking at feedback, and feedback was never what the credit rules were about.

Yes, mapped to the three situations you might be in. On your own unsold spec: yes, with no guild rule in the way. Selling it, or working under a contract: yes, within the protections — consent, disclosure, and a credit the machine can't touch. And on tool choice: analysis is feedback, generation is the thing the rules watch, so know which one you're reaching for.

If you want to run that cheap first-pass read, there are several ways to do it — including free options worth trying before you pay for anything, a range of paid tools tested side by side, and our own tool, StoryNotes ($20, one-time), which sits squarely on the notes side of the line — a read of your pages, not a co-writer. See what that kind of report looks like and judge it for your own drafts. None of these is the answer to "is it allowed"; that answer is the three situations above.

One last time, plainly: this is a translation, not legal advice, and the guild — not a blog — is the source of record for your specific case. But the fear that started you reading, the one where the WGA reaches across your desk and forbids the draft you own, isn't in the document.

One concrete fix: Before you take your script anywhere, run one cheap structural read on the draft you already own. The permission was never the problem — the rewrite is, and that's the part a first-pass read actually helps.