NIH Alternative Approaches: Writing the Subsection Reviewers Notice When It's Missing
There is a subsection required in every NIH Research Strategy that most applicants write in five minutes, with one sentence, as an afterthought. Experienced reviewers have learned exactly what that sentence looks like. When they find it, they mark Approach down — not always dramatically, but reliably. This guide is about what to write instead.
Table of Contents
What the Alternative Approaches Subsection Is and Where It Lives
The NIH Research Strategy has three main sections: Significance, Innovation, and Approach. Inside Approach, the agency instructs applicants to discuss "potential problems and alternative approaches." That phrase appears in NIH's own application guide and in every FOA that follows the standard R-series format. It is not optional language. It is a required element.
In practice, most applicants embed this subsection at the end of each aim's experimental plan, under a small bolded header that says "Potential Problems and Alternative Approaches" or just "Alternative Approaches." Some put a single consolidated version at the end of the entire Approach section. Either structure can work, but the per-aim placement is more common and is usually easier for reviewers to follow, because they read each aim sequentially and want to see your contingency thinking while the experimental details are still in front of them.
What the subsection is not is a confession that your project might fail. That is how many applicants treat it, and it is why the typical version reads as defensive and thin. The subsection is actually a demonstration of scientific maturity — evidence that you have thought carefully about the boundary conditions of your approach and have already identified the path forward if those boundaries are reached. Reviewers have been doing this work a long time. They know the boundary conditions of your methods better than you might expect. Showing that you know them too changes the conversation.
Why Reviewers Actually Read This Subsection
The Approach criterion is where reviewers assess feasibility. That word — feasibility — is doing a lot of work. It encompasses whether your experimental plan is coherent, whether your timeline is realistic, whether your preliminary data is sufficient, and whether you have the personnel and resources to execute. Alternative Approaches feeds directly into the feasibility read.
When a reviewer is preparing their critique, they often start with the places where the science feels thin or risky. The usual suspects are preliminary data gaps, over-ambitious timelines, untested reagents, and aims that depend on a technique the lab has not demonstrably used. If those concerns arise during the read, the reviewer goes looking for evidence that the applicant has already anticipated them. Alternative Approaches is where that evidence lives — or doesn't.
There is also a reviewer psychology element here that is worth naming. When reviewers find a thorough Alternative Approaches section, it shifts their posture from critic to collaborator. Instead of writing "what happens if X doesn't work?" as a critique, they can write "the applicant has addressed the X contingency; the proposed alternative is reasonable." That is a materially different sentence in a summary statement, and it points toward a different discussion at the panel meeting.
What to Write: A Framework That Works
The most useful way to think about this subsection is as a three-part structure for each major experimental risk in the aim: identify the risk, explain why it is genuine, and describe the alternative you would execute. That is it. Most applicants either skip the middle step (the "why it is genuine" part) or collapse all three into a single vague sentence.
Step 1 — Name the Specific Risk
Not "if the experiment does not work," but "if the antibody fails to immunoprecipitate the target under native conditions," or "if the mouse model does not recapitulate the human phenotype at six weeks." Specific risks tell the reviewer that you have actually thought about failure modes, not that you have inserted boilerplate. The more specific, the better. The reviewer can evaluate a specific risk; they cannot evaluate a generic one.
Step 2 — Acknowledge Why the Risk Is Real
A single sentence explaining the basis for the risk is enough. "Antibody cross-reactivity under denaturing conditions has been reported with three commercially available clones targeting this epitope." Or: "The six-week phenotype window is based on our preliminary data, which used a different transgenic background." This sentence accomplishes two things: it signals scientific literacy, and it pre-empts the reviewer from writing the same sentence in their critique without attribution.
Step 3 — Describe a Concrete Alternative
The alternative must be something you can actually do, not something you would do in a different grant five years from now. "We would switch to proximity ligation assay, which we have validated in our lab for three related targets." Or: "We would extend the window to twelve weeks based on published literature for the knockout background." One concrete sentence is better than three vague ones. If you can name a technique, a timeline adjustment, or a collaborator, do it.
Two or three such three-part structures per aim is usually the right number. Cover the risks that a reviewer in your field would independently identify — not every conceivable failure mode, which would be unreadable — and cover the ones where you have a credible alternative ready. If a risk exists and you genuinely do not have a good alternative, that is a project design problem, not an Alternative Approaches problem. Redesign the aim.
How Much Space to Give It
There is no NIH-mandated length for this subsection, which is part of why it gets so little attention. A reasonable rule of thumb for an R01 with a 12-page Research Strategy: aim for roughly one paragraph of Alternative Approaches for every three to four pages of experimental detail in the aim. If an aim occupies four pages, a single well-written paragraph covering two or three contingencies is probably appropriate. If an aim is lean — two pages of methodologically straightforward experiments — one or two contingency pairs may be enough.
The floor is not a sentence. The single-sentence version ("If the experiments do not produce the expected results, we will troubleshoot and explore alternatives") is what reviewers have seen so many times that they read it as the applicant having given up on this section. It might as well be blank, from a scoring perspective.
The ceiling is around half a page per aim for most proposals. Beyond that, the section starts to crowd out your experimental plan — which is the primary basis for the Approach score — and can read as defensive overcompensation. If you feel like you need more than half a page to handle contingencies for a single aim, that aim may be carrying too much risk to begin with. Consider whether the experimental plan needs a narrower scope or stronger preliminary data before submission.
Common Failures and How to Avoid Them
The "we will troubleshoot" placeholder
Every reviewer has read this sentence hundreds of times. It signals that the applicant did not think about failure modes. Replace it with at least one specific contingency per aim, even if it is a single three-sentence structure using the framework above.
Alternatives that require a different grant
"If this approach fails, we would apply for a separate R21 to develop the necessary tools." This is not an alternative. An alternative must be executable within the scope and resources of the current grant. If your only alternative requires additional funding, the proposed aim is not ready for submission.
Listing risks without alternatives
Some applicants enumerate three or four risks in careful detail and then do not say what they would do about any of them. This is worse than a placeholder — it flags feasibility concerns without resolving them. Every named risk needs a paired alternative, even if the alternative is brief.
Consolidating everything at the end of the Approach
A single Alternative Approaches block covering all three aims placed at the very end of a 12-page Research Strategy is easy to miss. Reviewers read sequentially, and by the time they reach the end of the document, their critique is already half-formed. Place contingencies at the end of each aim's experimental section, where the reviewer encounters them while the experimental details are still fresh.
Addressing only technical failures, not scientific ones
"If the western blot does not work" is a technical contingency. "If the hypothesized mechanism does not account for the observed phenotype" is a scientific one. Reviewers care about both, but the scientific contingency — what you would do if your central hypothesis were wrong — is what separates a mature proposal from an optimistic one. Most applicants only address the technical side.
Connecting Alternative Approaches to Rigor Requirements
Since NIH's 2016 rigor and reproducibility policy, reviewers are specifically instructed to assess whether applicants have considered scientific rigor in their experimental designs. That assessment happens primarily in the Approach section, and the Alternative Approaches subsection is a natural place to demonstrate it — without having to add dedicated rigor language that can read as formulaic if it is dropped into the wrong place.
Specifically, when you identify an experimental risk in the Alternative Approaches subsection, you can address rigor concerns in the paired alternative. "If our primary antibody shows cross-reactivity, we will switch to a validated secondary detection reagent from a second commercial source, which we have already obtained from [vendor]." That sentence speaks to authentication of key resources — a specific rigor criterion — without requiring a separate paragraph headed "Rigor and Reproducibility." The same logic applies to biological variables like sex: "If the phenotype is not observed at the proposed sex ratio, we will stratify by sex and power each subgroup independently based on the published variance for this strain."
This integration is more elegant than bolting a rigor paragraph onto the end of the Approach, and it tends to land better with reviewers because it shows that you are thinking about rigor as a feature of your experimental design rather than as a compliance checkbox. Whether that is the right read or not, it is how most reviewers experience it.
Frequently Asked Questions
Does Alternative Approaches need its own bolded subheader?
It does not strictly require one, but a bolded "Potential Problems and Alternative Approaches" header makes the section easy to find when reviewers are scanning. Given that this is a required element and reviewers will be looking for it, making it findable is worth the one line of formatting overhead.
Should I address what happens if an entire aim fails?
Yes, briefly — but the larger point is that your aims should be designed so that the failure of one does not collapse the project. If you need to spend significant space explaining what happens when Aim 1 fails entirely, that is usually a sign that the aims are more interdependent than they should be. Fix the design before the aims are submitted; don't patch it with Alternative Approaches text.
Can I use the Alternative Approaches section to introduce new preliminary data?
Only if that data directly supports the feasibility of the alternative you are proposing. A brief reference is fine — "we have used this technique in a related context; see Figure 4" — but the subsection is not a second Preliminary Data section. Data that supports your primary approach belongs in the experimental plan, not in contingency text.
How does this section change for a resubmission?
In an A1 resubmission, reviewers will specifically look at Alternative Approaches to see whether you addressed feasibility concerns they raised in the previous summary statement. If a reviewer wrote "what would the applicant do if X fails?" as a critique, and your A1 now has a clear answer in the Alternative Approaches subsection, that critique goes away. This is one of the highest-return revisions you can make in a resubmission, because it directly closes reviewer concerns without requiring you to change the experimental plan.
Scope the Field Before You Write Your Approach
Understanding what methods and approaches are currently funded in your area helps you anticipate the risks reviewers will flag — and write Alternative Approaches that address them before they appear in a summary statement.
Related Reading
Explore more resources to enhance your NIH funding knowledge
Writing the NIH R01 Approach Section
How to structure experimental plans, preliminary data, and timeline within the 12-page Research Strategy.
Writing the NIH Specific Aims Page: A Structure That Survives Review
The four-paragraph structure that works, common failures, and how to test the page before submission.
NIH Rigor and Reproducibility: A Writing Guide
How to address scientific premise, rigor of prior research, biological variables, and authentication requirements without formulaic language.
Writing NIH Significance and Innovation Sections
Practical guidance on separating what the field lacks from what your approach adds, with common patterns that reviewers score poorly.
Trust & Transparency
How this content is reviewed before it goes live
NIH Grant Explorer combines public NIH records with editorial interpretation. We publish the review structure, methodology, and correction pathways so readers can judge the value of a guide or chart for themselves.
When a topic turns into an official policy question, we point readers back to NIH rather than pretending an independent site can replace the underlying federal guidance.
Contributors & Review Desks
See how data, strategy, and career-focused pages are reviewed.
Editorial Guidelines
How we source, update, and correct articles and tool explanations.
Data & Methodology
Refresh cadence, public-source coverage, and chart caveats.
Corrections & Contact
Send corrections, feedback, or contributor inquiries.
