PACM Retirement Turns NIH Compliance Into Manuscript-Status Work

The next NIH public-access problem for journals is not only whether an author deposits the right manuscript. It is whether everyone involved can still see where that manuscript is, what evidence exists, and who needs to act before a compliance problem hardens into a grant-administration problem.

That distinction became sharper at the end of July. The National Library of Medicine posted that, after September 30, 2026, the Public Access Compliance Monitor, usually known as PACM, will no longer be available. NCBI will move institutional compliance-monitoring services into the NIH Manuscript Submission System through the new NIHMS Institutional Monitor: https://www.nlm.nih.gov/pubs/techbull/ja26/ja26_pacm.html.

For institutions, this is an obvious systems change. For journals and publishers, it is a quieter warning. The monitoring layer is moving closer to the author accepted manuscript, not the polished article page. If a journal still treats NIH compliance as something the author or university sorts out after acceptance, the handoff is going to feel late, manual, and brittle.

The 2024 NIH Public Access Policy has been in effect since July 1, 2025. NIH says author accepted manuscripts accepted for publication on or after that date must be submitted to PubMed Central upon acceptance and made publicly available without embargo upon the official date of publication: https://grants.nih.gov/policy-and-compliance/policy-topics/public-access. The policy pressure is not new. What is changing now is the operational surface where institutions will monitor progress.

What Actually Changes After September 30

NLM says PACM will remain available alongside the NIHMS Institutional Monitor through September 30, 2026, so institutions have time to become familiar with the new service and integrate it into their workflows. After that date, PACM goes away. Institutional users with the necessary eRA Commons role can access NIHMS Institutional Monitor, including institutions that currently have PACM access.

The replacement is not one-for-one. NLM states that NIHMS Institutional Monitor does not include information about final published articles submitted directly to PMC by participating publishers, and it does not support API access. In exchange, it gives more timely access to author accepted manuscript submission status and lets institutions act on stalled manuscripts.

That trade matters. PACM was useful because it aggregated compliance status around institution-associated journal articles. NIHMS Institutional Monitor is more closely tied to the manuscript-submission process. For institutions, that may be more actionable. For journals, it means the author accepted manuscript stage becomes harder to ignore.

The Missing API Is An Operations Signal

The line about no API may look like a technical footnote. It is not. Many institutional compliance teams have built local routines around exported reports, scheduled checks, spreadsheet reconciliation, or internal dashboards. When a monitoring service stops offering API access, work that used to happen quietly in the background may become screen-based, role-based, and more dependent on human follow-up.

Journal offices may never log in to either PACM or NIHMS Institutional Monitor. They will still feel the effect when authors, grant managers, or librarians ask for clearer acceptance dates, manuscript-version confirmation, embargo language, publication-date evidence, or proof that the journal route does not block NIH deposit. The institution is losing one kind of automated view and gaining a more direct view into stalled AAM workflows. That will push more questions upstream.

The risk is not that journals must become institutional compliance-monitor operators. They should not. The risk is that journals publish NIH-funded work without keeping the few facts that institutional monitors need to resolve problems quickly. When those facts are missing, staff rebuild the story from decision letters, production emails, author proofs, and platform timestamps.

Final Published Articles Are A Different Lane

One subtle part of the NLM notice deserves attention: NIHMS Institutional Monitor does not include information about final published articles submitted directly to PMC by participating publishers. That does not make publisher-deposited content less important. It means institutions may need a clearer distinction between article routes.

For a journal, there are at least three relevant pathways. The author accepted manuscript may be submitted through NIHMS. A final published article may reach PMC through a publisher arrangement. A citation may appear in PubMed while the compliance-relevant manuscript status remains unresolved. Those pathways are related, but they are not the same record.

Confusion at this boundary creates familiar friction. An author assumes the publisher deposit covers the policy. A university office sees a stalled AAM and asks for action. A production team points to the live article. The editor only has the acceptance email. Each person may be looking at a true fact, while the compliance story remains incomplete.

Acceptance Is The Control Point

NCBI had already updated the NIHMS submission interface in May 2026 to help reviewers apply the correct embargo under the 2024 policy: https://ncbiinsights.ncbi.nlm.nih.gov/2026/05/05/updates-to-nihms-2026/. That update sits in the same pattern as the July PACM transition. Compliance is being organized around the manuscript lifecycle, not around a once-a-year policy reminder.

The practical control point for journals is acceptance. At acceptance, the office knows the article has passed peer review, knows the author accepted manuscript exists, knows whether NIH funding was declared, and can still communicate with the author before production becomes the dominant workflow. Waiting until publication turns compliance into a chase.

That does not mean every acceptance email needs to become a legal memo. It means the journal should preserve a small, consistent record: funding acknowledgement as submitted, grant identifiers if provided, acceptance date, official publication date when assigned, manuscript version delivered to the author, rights or license language relevant to deposit, and any journal-specific route for PMC submission.

The Handoff Should Be Designed, Not Implied

The weakest compliance workflows rely on implication. The author is expected to know the funder policy. The institution is expected to monitor the author. The publisher is expected to know whether a final article deposit resolves the case. The editorial office is expected to answer questions later without seeing the monitoring context. Nobody is exactly wrong, but nobody owns the handoff.

A better handoff is explicit. If the journal accepts NIH-funded work, the acceptance workflow should tell authors which version is relevant, when deposit is expected, whether the publisher has a PMC route, and whom to contact if their institution flags a stalled record. If the journal relies on the author to submit the AAM, say that plainly. If the journal or publisher deposits the final published article for qualifying content, explain what that does and does not cover.

The same clarity belongs in staff tooling. Managing editors should be able to see whether a manuscript has NIH funding, whether acceptance has triggered a compliance notice, and whether the publication date has changed since the author was first instructed. Production should not have to infer policy state from a funding paragraph buried in the manuscript file.

Three Records To Reconcile Before October

Journal leaders do not need a large transformation program before PACM disappears. They need a focused reconciliation exercise across three records that often drift apart.

• The submission record: declared funders, grant identifiers, corresponding author, acceptance date, manuscript version, and staff notes about public-access obligations.
• The production record: official publication date, version of record availability, article URL, license display, and any publisher-to-PMC deposit status known to the journal.
• The author communication record: acceptance instructions, deposit guidance, rights language, responses to institutional queries, and any correction when publication timing changes.

If those three records cannot be connected for a recent NIH-funded article, the journal has an operational gap. The gap may not be visible on the article page. It will become visible when an institution sees a stalled AAM in NIHMS Institutional Monitor and asks the author or journal to resolve it.

Practical Takeaway For Journal Leaders

Before September 30, choose ten NIH-funded manuscripts accepted since July 1, 2025 and trace each one from acceptance to publication. For each manuscript, ask whether the journal can identify the AAM, the acceptance date, the official publication date, the author instruction sent at acceptance, the route to PMC, and the staff owner for institutional questions.

Do not grade the exercise by whether the article eventually looks compliant. Grade it by how quickly the team can explain the path. PACM retirement is a reminder that public-access compliance is becoming manuscript-status work. Journals that keep acceptance, production, and author-communication evidence connected will be easier partners for institutions when the monitoring screen changes.