Edition 004 | October 21, 2026

AI Manuscript Review and the Next EPUB Production Standard
This edition connects two October developments with two supporting guides already in the Publishing Standards library.

A publishing policy becomes useful when an editor can apply it to an actual manuscript. A technical specification becomes useful when a production team knows what to test, what to document, and which existing files can remain in service. Both questions are central to this edition.

Our new Authors Guild implementation guide addresses the decisions that arise when a manuscript is questioned for AI use. Our EPUB 3.4 guide addresses the practical response to a developing ebook specification. Two supporting reference guides connect those decisions to accurate disclosure and title-level rights records.

The working standard: identify the authority behind the decision, assign a responsible person, and preserve enough evidence to explain the result. Industry guidance, contract terms, draft specifications, and applicable law have different roles.

1. Authors Guild AI Best Practices: Put Manuscript Review in Writing

New implementation guide. The Authors Guild published its publisher AI best practices on October 13. These are voluntary industry recommendations, not a new regulation. Our full guide explains their significance and develops a practical house workflow for independent presses and professional publishing teams.

Start with the question the editor can actually investigate. An inaccurate citation, repetitive prose, and a suspected violation of an AI-use agreement are different concerns. A useful review identifies the relevant passages and policy, controls manuscript handling, invites the author’s explanation, and records a supported outcome.

The guide includes a ten-step manuscript-review procedure, a proposed consent record, an adaptable author-facing policy, original contract discussion language, and a publisher checklist. Those implementation tools are Publishing Standards proposals rather than additional Guild mandates.

Action for publishers: select one current submission and confirm which policy version applies, who may authorize external processing, and who reviews a disputed decision. Resolve gaps before the next concern becomes an urgent acquisition or publication problem.

Read the Authors Guild AI best practices implementation guide →

2. EPUB 3.4: Test Relevant Changes Before Rebuilding Books

October production development. W3C’s October 12 update describes EPUB 3.4 as being in the candidate stage and emphasizes backward compatibility. It says previously conforming EPUB books do not need to be changed merely because of this update. The announcement also introduces roll layouts for fixed-layout vertical comics.

The publishing task is to decide which changes serve the actual catalog. A comics imprint may have a useful layout pilot. A prose publisher may get more immediate value from checking its validation and release records. Neither decision should rest on a general claim that a file is “ready” without a defined test.

Our existing EPUB 3.4 guide separates specification status, validation, reading-system behavior, accessibility, and retailer acceptance. These checks answer different questions. Document the file, tool version, result, and delivery environment so a later production decision can be traced to evidence.

Action for publishers: choose one representative ebook. Review its validation record and intended reading environments. Pilot new features only where they meet a reader or production need, and preserve the approved release file.

Read the EPUB 3.4 implementation and validation guide →

3. Supporting Reference: Make AI Disclosure Describe the Work

Evergreen guide, not a new announcement. A manuscript-processing permission and a reader-facing disclosure are different records. Permission documents an authorized task. Disclosure explains relevant production contributions to the intended audience.

Use the existing disclosure guide when reviewing a book’s credits, production notes, or article disclosures. Then use the new manuscript-review guide for the underlying authorization and investigation workflow. Together, the two help a team avoid making a public claim that its production records cannot support.

Action for publishers: review one publication’s disclosure alongside its actual production history. Identify the function performed, responsible reviewer, and final approved wording. Correct vague or inaccurate descriptions before export and republication.

Use the AI content disclosure standard →

4. Supporting Reference: Connect Permissions to the Title’s Rights File

Evergreen guide, not a new announcement. The manuscript, its publishing agreement, and its permissions should be easy to connect. A separate processing approval is much less useful if a later editor cannot determine which work, version, service, and task it covered.

Use the existing rights-provenance guide as the title’s wider recordkeeping framework. Add the new guide’s consent and review records to that structure. Keep a distinction between authorization to perform a limited editorial task and a negotiated right to exploit the work in another format or service.

Action for publishers: open one active title’s rights file and check whether an unfamiliar team member could retrieve the governing agreement, contributor permissions, current source files, and any authorized external manuscript processing.

Build the title-level rights-provenance record →

Edition 004: Four Actions for the Next Production Meeting

1. Editorial: identify the manuscript AI policy and review owner.
2. Production: record the EPUB file, validation environment, and release decision.
3. Disclosure: reconcile public wording with what actually happened.
4. Rights: link task-specific permissions to the title’s governing records.

Choose a real title for each action rather than creating an empty policy folder. Record any gap, assign responsibility, and set a review date. A small press can maintain these controls in a compact title log; a larger house can distribute the work while keeping one accountable coordinator.

Start here: use the new manuscript-review procedure and sample publisher AI policy.

Sources and Scope

Primary announcements checked October 21, 2026: Authors Guild publisher AI best practices, dated October 13, and W3C’s EPUB 3.4 update, dated October 12. The linked full guides provide additional references and implementation details. The final two sections are supporting library references, not additional October news releases.

This edition provides general publishing information and operational recommendations. Contractual and legal decisions require review of the relevant agreement and applicable law.