The New COPE Code Needs an Evidence File

A code of conduct rarely changes the work on the morning it is published. Editors still open the same manuscripts, reviewers still miss deadlines, authors still dispute decisions, and production still asks whether a correction can wait until next week. The change arrives later, when someone asks a sharper question: show me how the journal knows it followed the rule.

That is the useful way to read COPE's July 2026 update. COPE has published a new Code of Conduct for members, replacing the Core Practices that were retired in 2024, with a 12-month transition period before full adherence becomes a condition of membership: https://publicationethics.org/membership/code-of-conduct. COPE's own history page records the lineage from the 1999 Guidelines on Good Publication Practice, through the Code of Conduct for Editors, through the 2017 Core Practices, and now to the new member Code: https://publicationethics.org/about/what-we-do/our-story/history-code-conduct.

For journal leaders, the important shift is not that ethics suddenly matters more in July 2026 than it did in June. The shift is that a familiar reference framework has become a membership standard that should be demonstrable across day-to-day editorial operations. A PDF policy page is not enough if the actual evidence sits in private email, unstructured notes, old decision letters, or the memory of one managing editor.

Do Not Start With A Rewrite

The first instinct will be to update public pages: publication ethics, complaints and appeals, conflicts of interest, authorship, peer review, corrections, retractions. That work is necessary, but it is the wrong starting point. If the team begins by rewriting web copy, it may produce cleaner language without discovering whether the journal can actually prove what the language says.

Start instead with a small evidence file. Pick five recent cases that touched ethics or governance: a disputed authorship change, a conflict-of-interest question, a rejected appeal, a suspected image issue, and a correction or withdrawal request. For each case, ask what the journal promised publicly, what happened internally, who had authority, what the author or reviewer was told, and where the record now lives.

This exercise usually exposes a different problem from the one leadership expected. The issue may not be that the policy is absent. It may be that the policy is scattered across submission guidelines, reviewer instructions, editor onboarding slides, publisher contracts, society bylaws, and staff habits. The journal has standards, but no reliable map from standard to action.

A Membership Standard Needs Owners

Old ethics frameworks were often treated as editorial background reading. A member Code should be treated more like an operating requirement. That means every major obligation needs an owner who can answer for process, not just values.

Authorship and contributorship cannot belong vaguely to "the editorial office." Someone must decide when a change after acceptance needs every author's confirmation, when an institution should be contacted, and which documents are preserved. Complaints and appeals cannot belong vaguely to "the editor." Someone must define what counts as an appeal, who reviews it independently, how conflicts are screened, and how the outcome is recorded.

The same is true for peer review. The jointly maintained Principles of Transparency and Best Practice in Scholarly Publishing say journals should clearly state who conducts peer review, what type of review is used, how decisions are made, and what exceptions apply: https://doaj.org/apply/transparency/. That is public-facing guidance, but it implies internal evidence. If a commentary, editorial, data paper, registered report, or invited article follows a different review path, the article record and editorial file should be able to explain the exception without a forensic search through inboxes.

Where The Evidence Usually Breaks

Most journals can point to a policy. Fewer can show the chain that connects policy, decision, communication, and published record. The breaks tend to be small and familiar.

• A conflict disclosure is collected at submission but not visible to the handling editor at reviewer invitation.
• A guest editor conflict is handled informally, with no recusal note tied to the manuscript.
• An author appeal is answered from a shared inbox, but the grounds for rejection and the reviewer of the appeal are not coded anywhere.
• A correction request is discussed in email, while the production system only records the final text change.
• A reviewer concern about data availability is resolved by author correspondence that never reaches the article metadata or editorial summary.
• A special issue uses a modified screening process, but the public journal page still describes only the standard route.

None of those failures requires bad faith. They are ordinary workflow gaps. They become governance failures when a journal cannot reconstruct them after a complaint, indexer query, member review, institutional investigation, or media inquiry.

Public Pages And Machine Records Are Converging

The COPE update is also arriving in a metadata environment that is becoming less forgiving. Crossref's 2026 public data file announcement said the snapshot includes nearly 180 million records and described richer metadata across abstracts, ORCID identifiers, ROR identifiers, grant identifiers, Crossmark, and Retraction Watch retractions: https://www.crossref.org/blog/2026-public-data-file-now-available/. The precise fields differ from a journal ethics file, but the direction is relevant: trust is increasingly expressed through records that other systems can inspect.

That does not mean every ethics decision should be made public or pushed into DOI metadata. Many cases require confidentiality. It does mean journal managers should stop treating public policy, editorial workflow, correction notices, retraction records, author communications, and metadata deposits as separate worlds. They are becoming different views of the same accountability system.

A journal that says it follows a transparent correction process should be able to connect the correction request, editorial assessment, author response, notice text, publication date, Crossmark or update signal where applicable, and final article page. A journal that says editorial decisions are not influenced by fees should be able to separate waiver and billing records from editorial decision authority. A journal that says peer review exceptions are disclosed should not need staff memory to find them.

A 30-Day Transition Sprint

The 12-month transition should not become an 11-month delay followed by a policy sprint. A practical first month can be narrow.

Week 1: build the obligation map

List the new Code headings or obligations your journal must satisfy. Next to each one, name the current public page, internal procedure, system field, template letter, and accountable owner. Leave blanks visible. They are the point of the exercise.

Week 2: sample live cases

Review recent manuscripts and post-publication cases against the map. Do not ask whether the outcomes felt reasonable. Ask whether another competent editor could reconstruct the process from the record without interviewing the people involved.

Week 3: fix the handoffs

Most gaps will appear between teams: editorial to production, editor to ethics lead, society office to publisher, guest editor to editor-in-chief, support inbox to manuscript record. Fix those handoffs before polishing public language.

Week 4: update public wording last

Once the workflow is known, update author instructions, reviewer guidance, ethics pages, correction and retraction policies, and appeal language so they describe what the journal can actually do. Clear wording is valuable only when it matches operational capacity.

The Takeaway For Journal Leaders

Treat the new COPE Code as an evidence-mapping project. By the next governance meeting, ask for one table that connects each major ethics obligation to an owner, public statement, workflow step, system record, template communication, and audit location. If the table is thin, the journal does not yet have a Code implementation problem. It has an evidence problem.

That is a solvable problem, but only if leadership resists the comforting version of compliance. The test is not whether the journal can quote COPE. The test is whether it can show, case by case, how publication ethics becomes editorial practice.