Clinical Research Grant Writing: What IRBs and Funders Both Need to See

The Federal Policy for the Protection of Human Subjects — the "Common Rule," codified at 45 CFR 46 — governs human subjects research conducted or supported by 20 federal departments and agencies. Its 2018 revision substantially updated requirements for informed consent documentation, IRB review categories, and continuing review obligations. The FDA's parallel regulations at 21 CFR Parts 50 and 56 apply to research involving FDA-regulated products. Together, these frameworks create a regulatory environment in which clinical research proposals must satisfy two distinct audiences: scientific reviewers assessing the merit of the research and ethics reviewers assessing the protection of research participants.

These two audiences are not simply different — they read the same documents with different questions and different consequences for what they find. A scientific reviewer assessing an NIH R01 application is asking whether the research is significant, innovative, and feasible. An IRB reviewer assessing the same protocol is asking whether the risks are minimized, whether the benefits justify them, whether consent will be meaningful and voluntary, and whether vulnerable populations are appropriately protected. The writing that satisfies one audience is often insufficient for the other, which creates a dual-audience problem that many clinical research proposals do not successfully navigate.

What IRBs Look For That Scientific Reviewers Don't Weight

The IRB's primary regulatory responsibility, established in 45 CFR 46.111, is to evaluate research against specific criteria before approval. These criteria include risk-benefit analysis, equitable subject selection, informed consent adequacy, and appropriate additional safeguards for vulnerable populations. Scientific merit — the question of whether the research will produce valuable knowledge — is relevant to the risk-benefit analysis only insofar as greater scientific value may justify greater risk. Scientific excellence does not offset ethical concerns about participant protection.

The specific elements that IRB reviewers assess most carefully, and that are most often inadequately addressed in proposals written primarily for scientific audiences:

Risk-benefit analysis specificity. The Common Rule requires that "risks to subjects are reasonable in relation to anticipated benefits, if any, to subjects, and the importance of the knowledge that may reasonably be expected to result." IRB reviewers assess whether the protocol adequately identifies and mitigates each specific risk — not risk categories, but the specific interventions, procedures, and data collection activities in this protocol and the specific risks they create for this population. A protocol that describes "minimal risk" without specifying which procedures are minimal risk and why has not provided the analysis IRBs need.

Vulnerable population identification. The Common Rule establishes additional protections for pregnant women, human fetuses, neonates, prisoners, and children (Subparts B, C, and D of 45 CFR 46). IRB reviewers identify whether any study population is or may include members of these groups and assess whether the additional protections required by the applicable subpart are addressed in the protocol. A protocol that recruits from a population where a significant percentage are likely to be pregnant, or that recruits adults who may include incarcerated individuals, must address the applicable subpart requirements explicitly.

Data safety monitoring. For clinical trials, IRB reviewers assess whether appropriate data safety monitoring is in place — a Data Safety Monitoring Board (DSMB) for Phase III trials with significant risk, or a data safety monitoring plan for lower-risk trials. NIH's guidance on data safety monitoring (published in 1998 and updated subsequently) requires all NIH-supported Phase III clinical trials to have an independent DSMB. The protocol should describe the monitoring mechanism and its authority to stop the trial early for safety or futility reasons.

Writing Informed Consent Documents That Meet Legal Standards and Remain Ethically Readable

The informed consent document serves two purposes that create competing writing pressures. As a legal document, it must include all elements required by 45 CFR 46.116 and, where applicable, 21 CFR 50.25. As an ethical document, it must enable prospective participants to make genuinely informed, voluntary decisions about whether to enroll in research — which requires that it be readable, comprehensible, and complete enough to give participants a realistic picture of what participation involves.

The required elements of informed consent under the revised Common Rule include the statement that the study involves research, the expected duration of participation, a description of the procedures, the reasonably foreseeable risks or discomforts, the potential benefits, disclosure of alternatives, confidentiality protections, and information about compensation and treatment for injury. For research involving identifiable private information or biospecimens, the 2018 revision added requirements for disclosure of how data may be used in future research.

The readability problem with consent forms is well-documented. Research published in the Journal of Clinical Oncology and elsewhere consistently finds that consent forms for clinical trials are written at reading levels significantly above the average reading level of the intended participants. The National Cancer Institute's guidelines for consent form development recommend a sixth-to-eighth grade reading level for documents intended for a general adult population. Forms written at a 15th-grade reading level — which is common — are not providing meaningful informed consent to participants who cannot understand them.

The writing approaches that produce consent forms that meet legal requirements while remaining readable:

• Use the second person — "You will" rather than "Participants will" — to make the document personally relevant
• Use concrete specificity over vague generality — "You will visit the clinic 4 times over 6 months, each lasting about 2 hours" rather than "Participation involves multiple study visits"
• State risks in plain language before legal qualifications — "This drug can cause liver problems, which can be serious in some people. We will monitor your liver function with blood tests every 3 months" rather than leading with regulatory boilerplate
• Separate what is "research" from what is "standard care" explicitly — participants often do not understand this distinction without being told explicitly which procedures are done only for the study

Protocol Sections That Create Friction in IRB Review

IRB reviewers identify specific protocol sections that consistently generate the most questions, requests for clarification, and required modifications. Understanding these friction points allows investigators to invest writing effort where it produces the most value in reducing review time.

Inclusion and exclusion criteria. Criteria that are ambiguous — "significant medical conditions," "clinically appropriate," "investigator discretion" — require IRB reviewers to ask how the discretion will be exercised consistently and whether the criteria could exclude populations in ways that raise equity concerns. Criteria should be specific enough that two investigators would apply them identically to the same patient.

Recruitment procedures. The IRB evaluates whether recruitment will be coercive or will create undue influence. Recruitment through the treating physician — where the patient-physician relationship creates an implicit pressure to participate — requires specific discussion of how the therapeutic misconception will be addressed and how voluntary participation will be ensured. Online recruitment and social media recruitment raise screening and privacy questions that must be addressed explicitly.

Data storage and confidentiality. HIPAA's research provisions (45 CFR Parts 160 and 164) and the Common Rule's data confidentiality requirements apply to identifiable private information. IRBs assess whether the proposed data security measures — encryption standards, access controls, retention periods, data sharing provisions — are appropriate to the sensitivity of the data being collected. Proposals involving genetic data, mental health information, or substance use data face heightened scrutiny because of the specific harms that could result from disclosure.

Addressing HIPAA Compliance in Clinical Research Protocols

HIPAA's Privacy Rule (45 CFR Part 164) intersects with human subjects research in ways that create documentation requirements beyond those imposed by the Common Rule. Research use of protected health information (PHI) requires either patient authorization, a waiver of authorization approved by the IRB, or a certification that the proposed use qualifies as a limited data set or de-identified data.

Clinical research proposals that involve accessing existing medical records, collecting data that will be linked to medical records, or conducting follow-up using medical record data must address the HIPAA authorization or waiver requirements explicitly. Proposals that do not address HIPAA compliance — or that assume IRB approval subsumes HIPAA authorization — create problems at the institutional level even when IRB review is completed successfully.

The HIPAA authorization form, when required, must include the specific PHI to be used, the specific people or organizations who will access it, the specific purpose of the use, and the participant's right to revoke authorization. These requirements are parallel to but distinct from the informed consent requirements, and both documents must be present when participant-level data is involved.