No-Cost Public Access Needs Better Author Instructions

The author email is usually polite: "Do I need to pay the open access fee for this paper to comply with my grant?" It looks like a billing question. It is really a workflow-design question, because the answer depends on funder policy, manuscript version, repository route, rights language, publication timing, and the way the journal explains those things before the author is under deadline pressure.

That confusion has become harder to ignore after the latest round of U.S. federal grant-rule comments. On July 15, 2026, SPARC said its comments on OMB-2026-0034 focused on a misconception that public access compliance requires paying an article processing charge: https://sparcopen.org/news/2026/sparc-submits-comments-to-omb-on-proposed-revisions-to-federal-financial-assistance-rules/. SPARC pointed instead to no-cost deposit routes through agency-designated repositories such as PubMed Central, DOE PAGES, and NSF-PAR. Whether one agrees with every policy argument in the filing, the operational point is hard to dismiss: authors should not have to infer a compliance route from a price page.

The proposed OMB rule itself is not final. The Federal Register notice, published May 29, 2026, says comments closed July 13 and proposes that publication costs, including APCs and similar open access fees, would be unallowable under federal awards unless required by statute or approved in advance by the agency on a case-by-case basis: https://www.federalregister.gov/documents/2026/05/29/2026-10817/regulation-for-federal-financial-assistance. Journal leaders should avoid writing as if the proposal is already settled law. They should also treat the debate as a useful audit of their author instructions.

The Problem Is Not Only The Fee

A clean APC page does not automatically create a clean compliance path. Many journals still place public access, open access, copyright, self-archiving, waiver, and payment information in separate pages written by different teams. The author sees a mosaic. The research office sees another. The editor may see none of it unless a manuscript is already accepted and payment uncertainty is slowing publication.

The practical risk is that the journal unintentionally teaches authors to equate "publicly available" with "pay this charge." Sometimes paying for immediate open access is exactly what an author wants or what an institution has arranged. Sometimes the compliant route is deposit of the author accepted manuscript in a designated repository. Sometimes the author needs an agency-specific version statement, a license statement, or a final-publication-date record. Those cases should not be hidden behind one commercial choice.

This matters even for journals that oppose the OMB proposal. STM warned in June that the proposed restrictions on publication and dissemination could limit the reach of federally funded research and weaken the systems that make research credible, discoverable, and usable: https://stm-assoc.org/stm-statement-on-proposed-omb-revisions/. A publisher can hold that position and still make its author guidance more precise. Better instructions do not concede the policy argument. They reduce avoidable friction for authors, librarians, funder-compliance staff, and editorial teams.

The Accepted Manuscript Needs Its Own Route

The author accepted manuscript is not just a file sitting between review and production. Under many public access policies, it is the version that moves through the no-cost repository channel. If a journal treats it as an internal artifact, authors will improvise. They will upload the wrong file, wait for the final PDF, ask for retrospective permission, or assume that payment is the only way to avoid noncompliance.

The route should be visible before submission and repeated at acceptance. Which manuscript version may be deposited? Which repository is expected for NIH, DOE, NSF, NASA, USDA, or other agency-funded work? Does the author or publisher deposit? What citation or DOI information will become available later? What embargo, if any, applies under the relevant policy? What license or rights statement should accompany the deposited version? Who answers if the institution reads the policy differently from the author?

GAO described the agency-repository pattern in its May 2026 report on federal public access implementation. The report found that selected agency plans generally described repository-based public access routes, including PMC for NIH, DOE PAGES, NASA PubSpace, NSF-PAR, and PubAg for USDA: https://files.gao.gov/reports/GAO-26-107738/index.html. Those repository names belong in author support materials, not only in funder-policy pages maintained elsewhere.

Payment Pages Need A Compliance Firewall

The simplest cleanup is also the most valuable: separate payment choice from compliance instruction. A journal can say that an APC makes the final version of record openly available under the journal license. It should not leave authors with the impression that APC payment is the only route to comply with a public access mandate unless that is actually true for the policy and manuscript in question.

This is a design problem as much as a policy problem. A payment page should include a short "public access compliance" box that routes authors to agency-specific deposit instructions. A waiver page should say whether waiver requests are financial-support requests, compliance questions, or both. A copyright page should state what authors may deposit and when. The acceptance letter should link the exact page that applies to the manuscript version the author now has in hand.

Avoid vague reassurance. "Authors may comply with applicable funder policies" sounds flexible but tells an anxious corresponding author almost nothing. Better language names the file, the repository path, the timing, and the support contact. It also tells authors when the journal cannot provide legal advice and when they should consult their institution. Precision reduces support burden because fewer authors need one-off explanations.

Acceptance Letters Should Carry The Handoff

The acceptance letter is the natural control point because it is when the accepted manuscript exists and the author is paying attention. It should not be a ceremonial note followed by a maze of links. For funded papers, the acceptance workflow should prompt staff or the system to include the relevant deposit guidance, version language, publication-date expectations, and institutional support route.

A good acceptance handoff does four jobs. It congratulates the author without burying obligations. It identifies the accepted manuscript version. It explains whether the journal, author, or agency submission system handles deposit. It separates optional open access publication choices from mandatory public access compliance steps. That last distinction matters because authors under deadline often interpret any button in the production workflow as a compliance requirement.

Editors do not need to become grant administrators. They do need confidence that authors are not receiving contradictory messages from editorial, production, rights, billing, and support teams. When those messages diverge, the editor becomes the escalation path by default. A better handoff protects editorial independence by moving compliance and payment questions into governed support lanes.

The Risk Is Different For Multi-Journal Publishers

Single-title journals can often fix this with a careful rewrite and a shared inbox. Multi-journal publishers have a harder problem. Different titles may have different licenses, funder mixes, society rules, waiver programs, repository arrangements, and publisher deposit services. Authors moving between journals in a transfer workflow may receive incompatible guidance even when the publisher brand is the same.

That is where governance matters. The portfolio should have a common compliance vocabulary: author accepted manuscript, version of record, repository deposit, optional OA, waiver, institutional agreement, agency approval, and public access mandate should mean the same thing across author-facing materials. Journal-specific differences can remain, but they should be explicit differences, not accidents of page ownership.

A quarterly review is enough to catch many problems. Pick a few recent federally funded accepted papers and trace what the author saw from submission through acceptance, production, payment, and publication. If the route cannot be reconstructed without asking three departments, it is too fragile for the policy environment now forming around public access.

A One-Week Author Guidance Cleanup

• Inventory every page, email template, and form that mentions APCs, open access, public access, self-archiving, copyright, funder compliance, or accepted manuscripts.
• Add a short agency-repository map for the funders that appear most often in your submissions, and link to authoritative agency pages where possible.
• Rewrite payment pages so they distinguish optional OA publication choices from no-cost public access deposit routes where those routes apply.
• Update acceptance letters to name the manuscript version, deposit responsibility, timing, and support contact before the author reaches production billing.
• Create a standard escalation path for research offices, librarians, and authors who ask whether a charge is required for compliance.
• Run a sample manuscript through the process and remove any screen, checkbox, or email that makes payment look mandatory when it is not.

This cleanup does not require a final OMB rule. It is basic author support. It also creates a better record if institutional research offices begin asking journals to justify payment requests, confirm repository routes, or provide language for grant files.

The Takeaway For Journal Leaders

Treat the current OMB publication-cost debate as a stress test for author guidance. The immediate task is not to predict every regulatory outcome. It is to make sure authors can tell the difference between paying for the journal version of record to be open and depositing an accepted manuscript through a no-cost public access route.

If your journal can answer that distinction in one paragraph, with the right file, repository, timing, rights language, and support contact, it is ready for a more confusing funding environment. If it cannot, the next policy shock will arrive first as an author-support queue.