Every NIH Clinical Study Would Owe Its Participants a Plain-Language Summary. NOT-OD-26-113 Is the Sleeper Compliance Cost of 2027 — Comments Close October 26.

Ask a clinical research coordinator what happens to a participant after the last study visit and you will usually get an honest answer: nothing.

The participant goes home. Two or three years later a paper appears in a journal they do not read, behind a paywall they will not pay, written in a register they were never meant to parse. The registry entry on ClinicalTrials.gov eventually fills with outcome tables that are technically public and functionally unreadable — arm-by-arm adverse event counts and least-squares means, formatted for regulators and meta-analysts. Nobody sends the participant anything. Nobody ever promised to.

On August 27, 2026, NIH proposed to end that. NOT-OD-26-113 requests information on a Draft NIH Policy on Sharing Summary Level Study Results with Clinical Research Participants. Responses are due October 26, 2026.

The policy is short, unglamorous, and almost certain to be finalized in some form. It is also going to cost more than any research office currently has in a budget line, for a reason that has nothing to do with the writing.

What the draft would require

Four requirements, each with a sharp edge.

One: offer summary results to every participant. Investigators receiving NIH support for clinical studies must share aggregate results in plain language, and must offer them to all participants regardless of whether an individual participant chooses to accept. The obligation attaches to the offer, not the uptake — which means it is auditable, and which means "we assumed they weren't interested" is not a defense.

Two: meet a deadline that varies by study type. Clinical trials: within one year of study completion, or on the ClinicalTrials.gov timeline where that applies. Other clinical research: by the end of the funding period.

Three: send a status update if the analysis is not done. If results are not ready when the clock runs out, participants get told that, rather than nothing.

Four: request an exception if returning results would be inappropriate, and expect that request to be reviewed rather than assumed.

The draft defines summary level results as a concise overview of the study after data are compiled and analyzed — objectives, methodology, cumulative findings, and limitations — presented in language that is understandable, meaningful, accessible, and appropriate for the audience. Scope is all NIH-supported clinical research, including clinical trials, regardless of funding level or mechanism, effective six months after the final policy publishes.

The scope is the story

The instinct in most research offices will be to file this next to ClinicalTrials.gov results reporting and assume the existing machinery absorbs it. That instinct is wrong in both directions.

Registry results reporting under FDAAA 801 and the 2016 NIH dissemination policy applies to applicable clinical trials — a defined, relatively narrow category, mostly interventional studies of drugs, biologics, and devices. It produces a structured data submission aimed at a scientific and regulatory audience. It is a database transaction.

This draft applies to clinical research, which is a far larger set: observational cohorts, natural history studies, behavioral and prevention trials, community-based participatory research, health services research, and studies with no intervention and no product at all. Enormous swaths of the NIH clinical portfolio have never had a results-return obligation of any kind. They would now.

And the output is not a data submission. It is a document written for a human being with no scientific training, which is a genuinely different production process requiring a genuinely different skill.

It is also worth being precise about what the draft is not. This is summary level — aggregate — results. It is not individual results return, which implicates CLIA certification, clinical actionability, and a much harder ethical calculus. An institution that conflates the two will scope its response wrongly and comment on the wrong problem.

The four costs nobody has budgeted

Contact information you did not keep. This is the sleeper, and it is the reason the policy costs more than it looks like it costs.

You cannot send a summary to a participant whose current address you no longer have. Many protocols destroy or de-link identifiers at study close by design — it is good privacy practice, and IRBs have encouraged it for years. Retaining contact information for two or three years past the last visit specifically so results can be mailed is a change to the data management plan, the consent form, and the IRB approval. For an ongoing study enrolled under a consent form that promised identifier destruction, it may not be retroactively fixable at all.

Institutions should be pricing this against their open portfolio, not their future one. Every study currently enrolling that will still be running when the policy takes effect has a consent form that says nothing about results return and a retention plan that may actively prevent it.

Consent language, everywhere. Template consent forms need a results-return section: that a summary will be offered, roughly when, and how the participant would like to receive it. Collecting a delivery preference at enrollment is the only cheap way to satisfy the offer requirement three years later. Retrofitting it through amendments across an entire institutional portfolio is not cheap.

Plain-language writing as a line item. Producing a health-literacy-appropriate summary — the working standard is roughly a sixth-to-eighth-grade reading level — is a specialist skill. Study teams are staffed with people trained to write the opposite. Multiply by the languages your study enrolled in, because a summary that is "accessible and appropriate" for a Spanish-speaking cohort is not an English PDF. Nothing about this is in a modular budget submitted in 2024.

The end-of-funding-period trigger. For non-trial clinical research, the deadline is the end of the funding period — and that is the provision most likely to break in practice. Analysis routinely finishes after the money does. Papers are written on unfunded effort during no-cost extensions and after. A deadline pinned to the funding period puts the obligation precisely at the moment the staff who would discharge it have rolled to other projects. The status-update fallback softens this, but a status update is itself work, performed by someone, paid by something.

What the RFI is actually asking

NIH is not asking whether to do this. The three questions posed are about participant preferences and delivery methods, low-burden best practices for producing clear and culturally appropriate summaries, and — the one to answer at length — the resources, tools, and cost estimates needed to implement effectively.

That third question is an invitation, and most institutions will waste it. NIH is explicitly soliciting cost data for a policy it intends to finalize. A comment that says "this will be burdensome" contributes nothing. A comment that says "we ran the numbers across 214 open clinical protocols; 61 percent have consent forms that do not permit post-study contact; re-consenting them costs X and takes Y months" changes what the final policy says about transition.

Central production is the other thing worth arguing for. If every study team writes its own summary, quality varies wildly and cost is maximized. If NIH funds or publishes templates, a controlled vocabulary, and translation resources — the way it eventually did for consent language and data management plans — cost drops by an order of magnitude. That resource does not exist unless people ask for it during a comment period.

This is not new anywhere except here

The United States is following on this, not leading. Under EU Regulation 536/2014, sponsors of clinical trials in the EU must post a lay-language summary of results within twelve months of trial end — six months for pediatric trials. The requirement has been in force through the EU Clinical Trials Information System, the templates exist, and the sky did not fall.

That precedent cuts two ways in a comment letter. It undercuts arguments that lay summaries are impossible or unsafe; multinational sponsors have been producing them for years, and your institution may already have staff who do. It also supplies concrete evidence about what actually goes wrong — the EU experience is a real dataset on production cost, translation burden, and template quality that NIH would benefit from hearing about.

There is a further wrinkle worth naming: any institution running trials with an EU footprint is already producing lay summaries on a twelve-month post-trial-end clock. A US policy that pins non-trial research to the end of the funding period creates two different deadlines for two different regulators over one research portfolio. Harmonizing those triggers is a legitimate, specific, and winnable comment.

What to do in the next eight weeks

Count your exposure. Pull every open and planned clinical protocol. For each, answer two questions: does the consent form permit post-study contact, and does the retention plan preserve contact information past the last visit? The percentage that fails both is the number your comment should lead with.

Fix the template now, not after the final rule. New consent forms should already include a results-return section and a delivery-preference field. The policy takes effect six months after final publication; every study you consent between now and then under an old template is a study you may have to re-consent later.

Decide who writes them. Centrally, in a communications or community-engagement office, or study by study. Make that call at the institutional level before 200 teams each invent an answer. The centralized model is cheaper and produces defensible consistency; the distributed model produces 200 documents of wildly varying quality, some of which will be wrong about the science.

Ask for the exception process in writing. The draft permits exceptions where returning results would be inappropriate, subject to approval — but an approval process with no stated standard, no timeline, and no named decision-maker is a source of delay rather than relief. Comment on the mechanics.

Respond by October 26, 2026, through the NIH Office of Science Policy comment form.

The underlying idea here is not controversial and does not deserve to be resisted. People who enroll in research, accept risk, and give their time are owed an account of what came of it, and the profession's failure to provide one is a genuine embarrassment that trial participants have named for decades. The argument worth having is not about whether. It is about the funding-period trigger, the consent-form transition, and whether NIH pays for the templates — three specific, fixable things that will be decided by whoever bothers to write in.

For other NIH policy changes reshaping research administration this year, see our analyses of the draft biosafety policy replacing the NIH Guidelines and the proposed cap on simultaneous Research Project Grants.