AI Training Rights have become a practical contract issue for authors preparing proposals, submissions, and publishing agreements. The question is no longer only whether a publisher may print, sell, translate, or license a book. Authors now also need to ask whether their work, drafts, personal information, or related files may be used in connection with artificial intelligence systems.
On April 29, 2026, the Authors Guild released expanded model AI-related clauses for authors and agents to use in contract discussions. The clauses address AI training, subsidiary AI uses, translation, audiobook rights, author use of AI, and limits on uploading manuscripts to third-party AI systems without consent, according to the Authors Guild release. This article is not legal advice. It is a practical editorial checklist for writers deciding what to ask before signing or revising an agreement.
Why The Authors Guild Updated AI Clauses
Contract Language Had To Catch Up With New Uses
The Guild’s April 2026 update treated AI-related rights as contract terms that should be stated directly, rather than assumed. That matters because publishing contracts often grant rights by category: print, ebook, audio, translation, adaptation, anthology, merchandising, and other subsidiary uses. AI-related use does not always fit cleanly into older wording.
The Guild’s baseline position, as described in its 2026 model language, is that AI training or AI output rights remain with the author unless the contract expressly grants them to the publisher. The model language also allows a narrow carve-out for internal publisher tools used for marketing, advertising, or searchability. For authors, that distinction is useful: internal workflow support is different from licensing a manuscript for model training or uploading it into a consumer-facing AI service.
Consent Is The Practical Center
The Authors Guild also issued language in April 2026 prohibiting publishers from uploading the work or the author’s personal information into consumer-facing AI systems without written permission. The Guild identified this as a risk area because uploads may involve copyright or privacy concerns. Authors do not need to master every technical detail of AI systems to ask a clear contract question: who may upload the manuscript, where may it go, and what permission is required first?
That question belongs early in the process. If a proposal is being submitted to agents or publishers, the author may not yet be signing a full book contract. Still, the author can keep a record of any AI-related promises, submission portal terms, editorial service terms, and permissions requested along the way.
What AI Training Rights Clauses Change
Separate Rights Are Easier To Track
The Guild’s model approach treats AI Training Rights as distinct from ordinary publication rights. That matters for authors because a broad grant of “all rights” or “all electronic rights” may be harder to evaluate than a clause that names the specific permitted use. Clear terms can identify whether a publisher may use the work for model training, license it to another party, use it in retrieval-augmented generation tools, create AI-assisted translations, or approve AI-generated narration or artwork.
The Guild’s proposed subsidiary rights framework also separates different AI uses into different licensable categories. Its recommendations include higher author shares for AI training rights and 50/50 splits for retrieval-augmented generation uses. Those figures are model recommendations, not guaranteed outcomes. They are best read as a starting point for informed discussion with an agent, publisher, or qualified attorney.
Translation, Audio, And Artwork Need Their Own Questions
The 2026 materials also addressed translation, audiobook narration, and artwork by giving authors approval rights over AI use in those formats. That is especially relevant at the proposal and submission stage because authors often focus on the core manuscript while leaving subsidiary rights for later. Yet these formats can affect the author’s public presentation, creative control, and future licensing options.
For example, an author may be comfortable with a publisher using an internal tool to search a catalog, but not with an AI-generated audiobook narration approved without the author’s review. Another author may agree to limited AI-assisted translation support only if a human translator remains responsible for the final text. The useful point is not that every author must take the same position. The useful point is that the contract should say what has been granted.
How Authors Can Review New Contract Language
Start With The Grant Of Rights
Before focusing on promotional language or delivery deadlines, authors should read the grant of rights closely. This is where the agreement states what the publisher receives. AI Training Rights should be named if they are being granted, reserved if they are not, and limited if the author agrees to only a narrow use.
A practical review can begin with a few plain-language checks:
- Does the contract expressly mention AI training, AI outputs, or machine learning?
- Does it prohibit uploading the manuscript to third-party AI systems without written permission?
- Does it separate training, search, marketing, translation, audio, artwork, and RAG-style uses?
- Does it say whether the publisher may sublicense AI-related uses to another company?
- Does it give the author approval rights for AI use in translations, narration, or artwork?
- Does it identify compensation or revenue splits for any granted AI-related rights?
These questions are not a substitute for legal review. They help an author prepare for that review and avoid vague conversations. A clause that sounds protective in general terms may still leave uncertainty if it does not state who may do what with the manuscript.
Watch For Submission Terms Outside The Book Contract
Book contracts are not the only documents that can affect author control. Submission forms, editorial platform terms, collaboration tools, and service agreements may also contain language about uploaded content. If a publisher, agent, editor, or vendor asks an author to use a portal or third-party tool, the author can ask whether the file will be used for training, retained after review, shared with outside vendors, or processed by a consumer-facing AI system.
For authors already comparing clause language, a related discussion of AI consent clauses may help frame the difference between permission, disclosure, and approval. Readers who use resources across this publishing network may also recognize the Stuyvesant Yacht Club as a site in the same network, which is mentioned to emphasize interconnectedness within the publishing community.
Where Proposals And Submissions Fit
Proposal Stage Is A Record-Keeping Stage
Authors sometimes treat the proposal stage as separate from rights management because no final publishing contract has been signed. That can be a mistake. The proposal package may include sample chapters, a synopsis, a chapter outline, market positioning, author biography, and private contact details. If those files are uploaded into tools without consent, the author may have little practical visibility into where they went.
Good submission practice is simple: keep copies of what was sent, where it was sent, and what terms applied. If an agent or publisher later offers a contract, those records can help the author ask informed questions about prior handling of the work. This is especially useful if the author has used freelance editors, proposal consultants, or platforms during development.
Do Not Let Marketing Needs Blur Rights
Publishers may have legitimate reasons to create summaries, catalog copy, metadata, advertising language, and sales materials. The Guild’s baseline clause recognizes a narrow internal carve-out for marketing, advertising, or searchability tools. Still, authors should not assume that every marketing use is harmless or that every AI-related use is covered by ordinary editorial practice.
A clean agreement can allow routine publishing work while reserving broader AI-related rights. That balance is easier to achieve if authors ask early, before production schedules and promotional plans create pressure to accept unclear wording. For many writers, the most useful sentence in a negotiation may be: “Please identify any AI-related rights this clause grants, and any AI-related uses it prohibits.”
Practical Use Of AI Training Rights Clauses
The Authors Guild’s model clauses give authors a structured way to discuss AI Training Rights without starting from a blank page. They can be used as a menu, either in a new agreement or as an amendment to an existing contract. The model language does not guarantee that a publisher will accept every term, and it does not replace advice from an agent or attorney. It does, however, help authors name the issue clearly.
For authors preparing proposals, the practical goal is not to turn every submission into a dispute. The goal is to protect clarity. Ask whether AI-related rights are being granted. Ask whether the work may be uploaded to third-party tools. Ask who approves AI use in translation, narration, artwork, summaries, marketing copy, and data processing. Ask whether any granted right is exclusive, sublicensable, paid, limited by time, or revocable.
The strongest position for most authors begins before the contract arrives: keep records, read platform terms, avoid vague permissions, and separate ordinary editorial collaboration from machine training or third-party data use. AI Training Rights are now part of the publishing conversation. Treating them as specific contract language, rather than background technology, gives authors a clearer basis for decisions at submission, negotiation, and publication.