See the Glossary for more terms.
NIH issued several recent Guide notices that affect fellowships, training grants, and career development awards. In case you missed them, here’s a recap.
New Page Limits for Ks
Starting with the February 12, 2011, due date, investigators should follow the new page limits outlined in the December 7, 2010, Guide notice.
Heads up for those applying for the January 7, 2011, AIDS due date: when you submit your application, you will get a warning related to the new page limits. Disregard it. You don’t have to take any action.
Keep in mind, however, that you still have to address warnings about other issues.
On the Table: Revised Tables for Ts
NIH has revised the SF 424 Data Tables for training grants, which must be used starting May 25, 2011. See the December 2, 2010, Guide notice.
How does this affect our T32 and T35 applicants?
Use the revised Tables for NIAID’s annual submission dates: September 25 for non-AIDS and January 7 for AIDS-related applications.
Reminder: Full Steam Ahead for xTrain
We’ve written about this before, so it shouldn’t come as a surprise.
Use the eRA Commons’ xTrain module to submit NRSA forms, like fellowship terminations and training appointments.
Read more at Submitting Your Fellowship Forms, Contacting NIAID and Submitting Your Training Grant Forms, Contacting NIAID in our Advice on Research Training and Career Awards.
For the official word, see the December 8, 2010, Guide notice.
If you’re pondering your next food allergy research project, get inspiration from NIAID’s clinical guidelines for food allergy research.
Though designed for healthcare providers, the report identifies gaps in food allergy research, provides new research data, and establishes consistent terminology and definitions. It also contains a thorough review of scientific literature.
That information could help you because reviewers tend to be enthusiastic about research that opens up a new area of discovery or develops a new approach to a major problem. You can expect them to have brushed up on the most recent literature, so make sure you understand the current state of various research problems.
The guidelines also highlight NIAID’s priorities, and they’ll be the basis for our future food allergy initiatives. When you submit an investigator-initiated application, applying with a project that meets our priorities can give your application a leg up on the competition.
Go to Guidelines for the Diagnosis and Management of Food Allergy in the United States to read the recommendations, see NIAID’s literature review, and view public presentations.
For our advice on picking topics and planning your application, read the articles in our New Investigator Series, especially How to Pick a Project and Application Approach: What Are Your Choices?
Get general background on how we plan funding opportunities at Planning Research Opportunities.
To continue the discussion of the future of the HIV/AIDS and Infectious Diseases Clinical Trials Networks, NIAID will host a second public Town Hall meeting on Monday, March 7, 2011, in Bethesda, Maryland.
The meeting provides a forum to discuss the proposed development of a network for non-HIV/AIDS infectious diseases with the larger infectious disease community.
It will be held at the Bethesda Marriott, 5151 Pooks Hill Road, Bethesda, MD. We will post registration and other important information soon.
The first Town Hall meeting, held on October 26, 2010, examined restructuring the HIV/AIDS clinical trial networks. You can read more at Town Hall Meeting to Examine the Restructuring of the NIAID Clinical Trials Networks.
In this series, we have delved into what it takes to get independent support, how to pick a project, and steps to start planning your application. In this article, we explore how to write the core of the Research Plan, the Research Strategy.
Before you start writing, be sure you have completed the planning steps described in the Related Articles listed below.
At this point you should have defined your hypothesis, prepared your Specific Aims, and determined which experiments you will do to support those aims. To learn more about those steps, read "Laying the Groundwork for Your Research Plan" in our October 27 issue and "Start Writing Your Application" from January 5.
Our advice is geared mainly to the R01, NIH's standard research grant.
As you read this text, look at our new Sample R01 Applications and Summary Statements to get an idea of the different strategies used by PIs whose applications scored in the exceptional range.
There are many ways to write a great Research Plan, so explore your options.
Our PIs keep reviewers' eyes on the ball by bringing them back to the main points they want to make.
Your application's Research Plan is the map that shows your reviewers how you plan to test your hypothesis. It not only lays out your experiments and expected outcomes, but must also convince your reviewers of your likely success by allaying any doubts that may cross their minds.
Notice in the sample applications how the writing keeps reviewers' eyes on the ball by bringing them back to the main points the PIs want to make.
The big three. So as you write, put the big picture squarely in your sights. When reviewers read your application, they'll look for the answers to three basic questions:
Use these questions as a litmus test for deciding what to include. Most everything you write should elucidate—and quell potential concerns—on these topics.
Spread the news. Savvy PIs create opportunities to drive their main points home. They don't stop at the Significance section to emphasize their project's importance, and they look beyond their biosketches to highlight their team's expertise.
Don't take a chance your reviewer will gloss over that one critical sentence buried somewhere in your Research Strategy or elsewhere. Write yourself an insurance policy against human fallibility: if it's a key point, repeat it, then repeat it again.
Add more emphasis by putting the text in bold, or bold italics (in the modern age, we skip underlining—it's for typewriters).
Here are more strategies from our successful PIs:
Spot the Sample
You can see many of these principles at work in the Approach section of Boris Striepen's application, "Biology of the apicomplexan plastid."
Aim your antennae. Our applicants not only wrote with their reviewers in mind they seemed to anticipate their questions. You may think: how can I anticipate all the questions people may have? Of course you can't, but there some basic items (in addition to the "big three" listed above) that will surely be on your reviewers' minds:
Address these questions; then spend time thinking about more potential issues specific to you and your research—and address those too.
Use graphics. For applications, a picture can truly be worth a thousand words. Graphics can illustrate complex information in a small space and add visual interest to your application.
Look at our sample applications to see how the investigators included schematics, tables, illustrations, graphs, and other types of graphics to enhance their applications.
Consider adding a timetable or flowchart to illustrate your experimental plan, including decision trees with alternative experimental pathways to help your reviewers understand your plans.
Know your audience's perspective. Though there's no guarantee exactly who will review your application, it's a good idea to see who may be on the review committee, so you can learn their possible perspectives on your area of science.
In the top notch applications we reviewed, organization ruled but followed few rules. While you want to be organized, how you go about it is up to you.
Nevertheless, here are some principles to follow:
The Research Strategy's page limit—12 for R01s—is for the three main parts: Significance, Innovation, and Approach and your preliminary studies (or a progress report if you're renewing your grant). Other sections, for example, research animals or select agents, do not have a page limit.
As we did in our previous article, we give you advice to use as you work. Each section starts with general background that you use to create an initial draft. Then use our checklists under the Checkpoint headers to critique your draft and improve it.
Check each point, analyze your text, revise—and repeat until perfect!
Although you will emphasize your project's significance throughout the application, the Significance section should give the most details. Don't skimp—the farther removed your reviewers are from your field, the more information you'll need to provide on basic biology, importance of the area, gaps, and new findings.
When you describe your project's significance, put it in the context of 1) the state of your field, 2) your long-term research plans, and 3) your preliminary data. (Read more about choosing a highly significant topic in "May the Force Be With Your Application".")
In our sample applications and summary statements, you can see that both investigators and reviewers made a case for the importance of the research to improving human health as well as to the scientific field.
Look at the Significance section of Adam Ratner's application: "Gardnerella vaginalis: toxin production and pathogenesis" to see how these elements combine to make a strong case for significance.
Checkpoint. After conveying the significance of the research in several parts of the application, check that:
Innovation can be tricky. Be sure to read the advice in our earlier articles: "Your Project's Scope: Plot Your Boundaries" and "May the Force Be With Your Application"." Though they discuss application planning, the same concepts can help guide your writing too.
The main point for a new PI: be cautious about seeming too innovative. Not only is innovation just one of five review criteria, but a paradigm shift can be as dangerous as an earthquake! A reviewer may take a challenge to the status quo as a challenge to his or her world view.
When you look at our sample applications, you see that both the new and experienced investigators are not generally shifting paradigms. They are using new approaches or models, working in new areas, or testing innovative ideas.
In your Approach, you spell out a few sets of experiments to address each aim. As we noted above, it's a good idea to restate the key points you've made before on your project's significance, its place in your field, and your long-term goals.
You're probably wondering how much detail to include. Look at our sample applications as a guide. You can see very different approaches though in general people used less detail than you'd see in a publication.
Look at the applications from Adam Ratner cited above and the one from Carolina Wahlby "Image analysis for high-throughput C. elegans infection and metabolism assays" to see how two new investigators handled the Approach section—and got a perfect score!
As a new investigator, you need enough detail to convince reviewers that you understand what you are undertaking and can handle the method.
Be sure to lay out alternative experiments and approaches in case you get negative or surprising results. Show reviewers you have a plan for spending the four or five years you will be funded no matter where the experiments lead.
See Colin Parrish's application "Structural controls of functional receptor and antibody binding to viral capsids" for strong sections on potential problems and difficulties and alternative approaches, for example, on page 37.
Here are some pointers for organizing your Approach:
Trim the fat—omit all information not needed to make your case. If you try to wow reviewers with your knowledge, they'll find flaws and penalize you heavily. Don't give them ammunition by including anything you don't need.
Jotting this information down will help you prepare your budget justification and other sections later.
Checkpoint. After finishing a draft Approach section, check that:
Your preliminary studies show that you can handle the methods and interpret results. Here's where you build reviewer confidence you are headed in the right direction by pursuing research that builds on your accomplishments.
Give alternative interpretations to your data to show reviewers you've thought through problems in-depth and are prepared to meet future challenges.
Reviewers use your preliminary studies together with the biosketches to assess the investigator review criterion, which reflects the competence of the research team.
Give alternative interpretations to your data to show reviewers you've thought through problems in-depth and are prepared to meet future challenges. If you don't do this, the reviewers will!
Though you may include other people's publications, focus on your preliminary data or unpublished data from your lab and the labs of your team members as much as you can.
As we noted above, you can put your preliminary data anywhere in the Research Strategy that you feel is appropriate, just make sure your reviewers will be able to distinguish it. Alternatively, you can create a separate section with its own header.
Throughout your Research Plan, you will reference all relevant publications for the concepts underlying your research and your methods.
References show your breadth of knowledge of the field. If you leave out an important work, reviewers may assume you're not aware of it.
Cite publications that are current and relevant to the project or show that you or your collaborators used your proposed methods. In general, you do not include a copy of publications in the application.
Checkpoint. After finishing the draft, check that:
You will list all citations in your Other Project Information Form: Bibliography and References Cited form.
Look over what you've written with a critical eye of a reviewer to identify potential questions or weak spots.
Enlist others to do that too—they can look at your application with a fresh eye. Include people who aren't familiar with your research to make sure you can get your point across to someone outside your field.
As you finalize the details of your Research Strategy, you will also need to return to your Specific Aims to see if you must revise. Stay tuned: we'll give you more pointers in our next article.
See the full list of articles in the new investigator series on the Early-Stage and New Investigators portal.
Interact with NIH staff and learn about a host of topics, including the ins and outs of writing an application and the peer review process.
Before your calendar fills up for the new year, you might want to leave space for one of NIH's two annual Regional Seminars on Program Funding and Grants Administration.
These are your chances to interact with NIH staff and learn about a host of topics, including the ins and outs of writing an application and the peer review process.
The 2011 seminars will take place as follows:
Optional eRA computer workshops will be held in both locations the day before. This year's sessions will offer additional IC representation with one-on-one meeting opportunities, sessions on NIH niche programs and initiatives, and more.
Be sure to reserve your spot before space fills up. Sign up at the Attendee Registration Page.
For more information, go to NIH Regional Seminars on NIH Regional Seminars on Program Funding and Grants Administration.
Our Division of AIDS ushered in 2011 with a new acting director and deputy director for its Vaccine Research Program (VRP).
Familiar Face Takes the Helm
Alan Fix, M.D., is the interim head, taking over from the retired Dr. Peggy Johnston. His effective management skills and in-depth knowledge of clinical trial design and implementation will serve both VRP and the Division well.
No stranger to DAIDS, Dr. Fix joined the Division in 2002 and became a branch chief in 2006. In that position, which he still holds, he has overseen the HIV Vaccine Trials Network and coordinated and harmonized protocols across the HVTN, U.S. Military HIV Research Program, and International AIDS Vaccine Initiative.
Deputy Returns to NIAID
New Deputy Director Kevin Ryan, Ph.D., will play a key role in providing scientific leadership and direction for planning, managing, and evaluating VRP's national and international programs.
Dr. Ryan spent five years as program officer and deputy chief of NICHD's Pediatric, Adolescent, and Maternal AIDS Branch, Center for Research for Mothers and Children. Before his tenure at NICHD, he was a program officer and chief of DAIDS' Prevention Sciences Branch. He brings extensive knowledge of extramural research program management as well as scientific expertise in molecular virology and clinical trials for AIDS prevention.
If you want to join the conversation about NIH's long-term planning and development as a federal agency, go to Feedback NIH, an interactive community resource NIH created to engage you and your colleagues directly.
You can ask questions, make comments, or get the scoop on some of NIH's biggest topics.
Current features include proposals to establish a national center for translational sciences and a new institute devoted to research on addiction and substance use and abuse.
Feel free to send us a question at firstname.lastname@example.org. After responding to you, we may include your question in the newsletter, incorporate it into the NIAID Research Funding site, or both.
"Can a subaward on an NIH grant receive more funding than the grantee?"—Joan Eaton, University of Colorado at Boulder
Yes, though the grantee has to play a substantive role in developing the research and not simply channel funds to the subawardee.
"When I attempt to follow the links in the NIAID Funding Newsletter, why do I get a message 'this URL is not syntactically valid'?"—several readers
The links you see go through our email service provider, which is why they have an unusual structure. Unfortunately, we can't change that, and most people have a browser and email reader that work with this approach.
If the links do not work for you, first try contacting your local tech support people for help. If they cannot resolve the problem, try copying the spelled-out link at the top of the email to find the newsletter online, or use the emails as a tickler to read the newsletter at NIAID Funding Newsletter.
See these and older announcements at NIAID Funding Opportunities List.
back to top
Last Updated July 08, 2011
Last Reviewed January 19, 2011