NIH’s Draft Results-Sharing Policy Makes Study Closeout a Participant-Facing Workflow

What NIH is proposing

The proposal covers clinical trials as well as other NIH-supported patient-oriented, epidemiological, behavioral, outcomes, and health-services research. NIH defines the expected deliverable as a concise overview of the study’s objective, conduct, methods as appropriate, aggregate findings, relevance, limitations, and potential implications. It specifically distinguishes these summaries from participant-specific laboratory values or other individual research results. ([federalregister.gov](https://www.federalregister.gov/documents/2026/09/25/2026-19706/draft-nih-policy-on-sharing-summary-level-study-results-with-clinical-research-participants))

For clinical trials, the proposed deadline is no later than one year after the primary completion date or the applicable ClinicalTrials.gov reporting deadline, whichever is later. For extramural clinical research that is not a clinical trial, results would generally be due by the end of the award’s period of performance if the analysis is complete. When results are not ready, participants would receive a status update explaining when, where, and how the findings will be shared.

The proposal would also require confirmation to NIH that results or a status update were provided. An exception would require NIH approval and generally should be requested before the first participant enrolls. In other words, a research team could not reach closeout, decide that returning results is impractical, and quietly remove the obligation.

The workflow starts at consent, not database lock

A site cannot reliably contact participants after study completion unless the study establishes that capability from the beginning. Consent materials should explain whether participants will be offered aggregate results, how they can indicate their preference, the likely timing, available delivery methods, and how to update their contact information.

The participant tracking system also needs to separate permission from delivery. A participant may agree to receive results but later withdraw that preference. Another may change an email address, move, lose portal access, or ask that information be sent to a legally authorized representative. Pediatric, caregiver-supported, and long-duration studies introduce additional questions about who should receive the summary years later.

Operationally, this means the results-return preference should be a structured field, not a note buried in a source document. Sites and coordinating centers need a defined process for updating the field, recording the participant’s preferred language and communication channel, and retaining only the contact information that the approved plan permits them to retain.

Five questions feasibility should answer before enrollment

The draft policy places responsibility on NIH-supported researchers and institutions, but multisite studies still need a precise division of labor. Without it, the coordinating center may assume sites will distribute the summary while sites assume the sponsor or lead institution will contact participants directly.

• Who owns the participant-facing deliverable? Identify who drafts the summary, validates scientific accuracy, completes health-literacy review, obtains required IRB or institutional approval, and authorizes release.
• Who maintains contactability? Define whether sites, the coordinating center, or a central platform will maintain participant preferences and current contact details after active follow-up ends.
• Who pays for the work? Budget for writing, participant review, translation, formatting, mailing, portal configuration, staff time, returned mail, undeliverable email, and responses to participant questions.
• Who documents completion? Establish the evidence needed to show that a participant was offered results, received them, declined them, or could not be reached after defined attempts.
• Who handles questions? Participants may ask whether the findings change their care, which treatment they received, or why their experience differed from the overall outcome. Staff need an approved response pathway that distinguishes aggregate research findings from medical advice.

Plain language is a quality requirement

A scientifically correct summary can still fail if it is written like a manuscript abstract. NIH’s proposal defines plain language as communication that is clear, concise, organized, culturally and contextually appropriate, and free of unnecessary jargon and acronyms. That standard requires more than applying a readability score after medical writing is complete. ([federalregister.gov](https://www.federalregister.gov/documents/2026/09/25/2026-19706/draft-nih-policy-on-sharing-summary-level-study-results-with-clinical-research-participants))

A 2025 scoping review found a strong participant desire to receive aggregate findings, but it also identified recurring barriers including limited funding and staffing, outdated contact information, digital-literacy gaps, and inadequate support for multilingual or lower-literacy populations. Preferences also varied by context. Digital-only distribution should therefore not be treated as universally participant-centered. ([doi.org](https://doi.org/10.1136/bmjopen-2025-107270?utm_source=openai))

Useful summaries usually answer practical questions: Why was the study conducted? Who participated? What did researchers compare or observe? What were the main findings? What were the important limitations? What happens next? The MRCT Center’s return-of-results resources also recommend thanking participants and clearly explaining that the document summarizes one study and that later research may produce different information. ([mrctcenter.org](https://mrctcenter.org/project/aggregate-results/?utm_source=openai))

Multilingual communities need more than translation at the end

For sites serving communities such as South Florida and Puerto Rico, language planning should be included in startup. A Spanish summary translated after English approval may be grammatically accurate but still use unfamiliar terminology, awkward descriptions of uncertainty, or wording that does not match the language participants heard throughout the study.

The better approach is to establish target languages during feasibility, budget for translation and quality review, and involve speakers familiar with the local participant population. The same principle applies to delivery channels. Some participants may prefer email or a secure portal, while others may be better served by mail, a telephone explanation, or a community-based dissemination session.

Equity also requires a plan for participants who discontinued early. The MRCT Center recommends that results be offered to people who consented to participate, including those who were not ultimately randomized or did not complete the trial, if they opted to receive them. That population is easy to lose when results distribution is built from a list of completers rather than the full consent log. ([mrctcenter.org](https://mrctcenter.org/wp-content/uploads/2023/04/2017-11-27-Return-of-Aggregate-Results-Principles.pdf?utm_source=openai))

Do not leave the cost in an unfunded closeout period

NIH explicitly acknowledges that returning results will require resources and is asking stakeholders for information about reasonable implementation costs. Previous research has identified financial, logistical, systems, regulatory, and investigator-capacity barriers to sharing findings with participants. ([federalregister.gov](https://www.federalregister.gov/documents/2026/09/25/2026-19706/draft-nih-policy-on-sharing-summary-level-study-results-with-clinical-research-participants))

A realistic budget should include work occurring after the primary endpoint is collected and potentially after routine site payments have slowed or stopped. If a site is expected to contact participants, answer questions, document delivery, or manage returned communications, those tasks need funded line items and an invoicing mechanism that remains available during closeout.

Contract language should also address what happens if the study ends early, the analysis is delayed, a site closes, the investigator leaves, or the institution can no longer maintain participant contact information. Results-return obligations should survive personnel changes without creating indefinite, unsupported responsibility for an individual coordinator.

Why commercial sponsors should pay attention

The draft policy is limited to NIH-supported research, but the underlying operational problem is broader. Participants do not experience research according to its funding mechanism. They remember whether the study team stayed in contact, explained delays, and told them what their contribution helped researchers learn.

Sponsors that already produce plain-language summaries should evaluate whether those summaries consistently reach participants through a documented process. Posting a document online is not the same as returning it to the people who enrolled. Sites, meanwhile, should avoid promising a result-delivery process that has not been funded or approved.

The most practical response is to add results return to protocol and feasibility discussions now. Define ownership, participant preferences, contact-data retention, translations, delivery channels, escalation pathways, documentation, and cost before enrollment. When those decisions are postponed until database lock, even a well-intentioned commitment can become an improvised closeout project.

NIH’s proposal frames returning results as part of the research obligation, not an optional courtesy. Whether the final policy changes after public comment, that is the operational lesson worth keeping.