The AI Disclosure Standard Needs Change Control

The next fight over AI disclosure will not be about whether journals need a sentence in the manuscript. Most serious publishers already know they do. The harder problem is what happens when that sentence changes shape three times between submission and publication, differs by article type, collides with reviewer confidentiality rules, and then has to be understood by readers, editors, institutions, indexers, and future metadata systems.

That is why the second consultation round for a global AI disclosure standard deserves operational attention. On July 28, 2026, STM highlighted the renewed consultation toward a Global Reporting Standard for AI Disclosure in Research, a joint initiative involving STM, COPE, the International Science Council, the Global Young Academy, and the World Conference on Research Integrity Foundation: https://stm-assoc.org/ai-disclosure-in-research-towards-a-global-reporting-standard/. The consultation is open through October 16, 2026, and asks participants to weigh in on thresholds, placement, taxonomy, mandatory non-empty disclosure, and responsibility or accountability signaling.

The International Science Council project page gives the broader timeline: a first round from December 2025 to February 2026, the current July-to-October round on when, where, and how AI use should be disclosed, and a final round expected from late 2026 into early 2027 to refine what it calls the Vancouver Standard: https://council.science/our-work/ai-disclosure-in-research/. That schedule creates a practical window for journals. The standard is not finished, but the implementation questions are visible enough to start preparing.

The Consultation Is Really About Workflow States

The five consultation questions sound like policy questions. Which AI use should be disclosed? Where should the disclosure appear? How should it be structured? Should a non-empty disclosure be mandatory? How should responsibility be signaled? Each one also implies a workflow state that has to be captured somewhere before the final article exists.

A threshold rule is not enforceable if submission forms only ask authors to paste a paragraph. Placement is not stable if production receives a manuscript with one statement in Methods, another in acknowledgements, and a different answer in the cover letter. A taxonomy is not useful if staff cannot distinguish language editing, translation, code generation, literature summarization, image creation, statistical interpretation, or AI-assisted peer review from one another. Accountability cannot be signaled if the journal never records who verified the disclosure or when it changed.

This is the part journal managers should take seriously now. A global standard will not remove local judgment. It will make weak local implementation more visible. The journals that treat disclosure as a final-text problem will spend the next year reconciling manuscripts by hand. The journals that treat disclosure as a versioned workflow state will be able to adapt without rewriting the whole editorial system.

A Disclosure Is Not One Moment

Consider a plausible manuscript. At submission, the authors disclose that AI was used for language polishing. During revision, they add an AI-assisted statistical explanation after a reviewer asks for clearer interpretation. Before acceptance, production notices that the graphical abstract was generated using a tool that the journal allows only with explicit labeling. After publication, an institution asks whether the AI-generated figure source file was retained.

A journal with only one free-text disclosure box is already in trouble. Which version is the record? Who approved the change? Did the reviewer see the relevant information? Did production? Did the article page? Did the XML? If the answer is buried in email, the journal does not have a disclosure policy. It has a disclosure memory test.

The solution is not to make authors fill out a long bureaucratic form for every spelling correction. It is to separate low-risk language support from uses that affect interpretation, evidence, presentation, data handling, or evaluation. Then the journal can define which changes require editor review, which require author responsibility language, which require production labeling, and which should be preserved only internally.

The Metadata Lesson Is Arriving From Another Direction

Crossref is a useful parallel even though AI disclosure is not simply a DOI deposit issue today. Its July 2026 Schema 5.5 announcement added support for CRediT contributor roles, along with other updates such as blog and poster record types: https://www.crossref.org/blog/schema-5.5-now-available-adding-credit-new-record-types-for-blogs-and-posters-and-more/. The direction is clear: statements that once lived as prose are increasingly expected to become structured, exchangeable information.

AI disclosure is likely to follow the same pressure. A human-readable statement will still matter, but downstream systems will want more than a paragraph. They will want to know whether a disclosure exists, what class of use it describes, whether authors accepted responsibility, and perhaps whether the statement was verified or updated. Even if the eventual standard is deliberately modest, journals will need cleaner internal data than most have now.

This does not mean publishers should invent private metadata schemes that nobody else can read. It means they should avoid locking AI disclosure into places that cannot be migrated later. Free text can be part of the record. It should not be the whole record.

What Journal Leaders Should Decide Before October

The October 16 consultation deadline is a useful forcing function. Instead of sending one policy specialist to answer the survey alone, convene a short working group with editorial, ethics, production, metadata, platform, and author-support representation. Ask for a response that reflects how the journal would actually implement the standard, not only what it would prefer in principle.

• Name the AI-use categories the journal can distinguish today without reading a manuscript manually.
• Identify which categories are author assistance, which touch research interpretation, and which may create confidentiality or integrity risk.
• Choose the authoritative disclosure location at submission, revision, acceptance, article page, and export.
• Define what counts as a material change to the disclosure after submission.
• Decide who can approve disclosure changes: handling editor, ethics editor, production editor, or publisher staff.
• Record how author responsibility is expressed when AI has contributed to analysis, images, code, or interpretation.
• Test whether the disclosure can survive transfer between editorial system, production files, hosting page, and metadata deposit.

Those answers will also make the consultation response better. Standards fail when they are designed around abstract consensus and then meet messy systems too late. Publishers, societies, and universities can help by bringing implementation evidence to the process: where ambiguity costs time, where authors misunderstand thresholds, where small journals lack platform support, and where a structured taxonomy would reduce rather than add work.

Do Not Wait For The Perfect Standard

Some journals will be tempted to wait until the final reporting standard appears. That is understandable and still risky. The current consultation already shows the implementation surface: thresholds, placement, taxonomy, mandatory disclosure, and accountability. None of those topics requires a final global text before a journal can inspect its own workflow.

Run a small test this month. Take five recent manuscripts with any AI-related statement or author query. Trace the disclosure from submission to decision letter to production file to article page. Note every place where the information is duplicated, rewritten, lost, contradicted, or visible to the wrong role. Then ask whether the journal could handle the same path across a portfolio of titles with different editors and article types.

That test will reveal whether the journal has an AI disclosure policy that can survive contact with publishing operations. If it cannot, the answer is not another paragraph in the author guidelines. The answer is change control.

Practical Takeaway For Journal Leaders

Before responding to the AI disclosure consultation, build a one-page disclosure change map. Show the initial field, allowed AI-use categories, material-change rule, approval owner, author responsibility language, production destination, article-page destination, metadata/export destination, and audit location. Bring that map to the consultation response and to your next platform meeting.

The emerging standard will help align the industry. It will not, by itself, make a journal operationally ready. Readiness means that when the disclosure changes, the record changes with it and the journal can show why.