Disorders A - Z:   A    B   C    D    E    F    G    H    I    J    K    L    M    N    O    P    Q    R    S    T    U    V    W    X    Y    Z

Skip secondary menu

Writing a Grant Application: A "Technical" Checklist



ESSENTIALS:

  • Significance
  • Sound hypotheses
  • Productivity and demonstration of feasibility -- high quality results and figures
  • Logical development of experimental design

Before you start:

  • Is it really time to write this grant? Is it premature?
  • Should you write that paper first?
  • Plan ahead and don't rush -- give yourself 2-3 months to prepare the grant.
  • Arrange with colleagues or mentors to review a first draft of your specific aims EARLY (6 weeks or so) just to make sure you are on the mark.

Specific Aims

  • Do the aims address interesting and significant issues?
  • Are they hypothesis-based?
  • Are they "win-win" - i.e., will an outcome consistent with the null hypothesis still be a contribution to the field?

Background

  • Clear, well organized -- use subheadings where possible. Make sure the significance of the topic is EXPLICITLY stated.
  • State CLEARLY where the gaps in knowledge exist in the field that your results will address.
  • Make sure your references reflect an updated knowledge of the field.

Preliminary Results

  • Draw as much as possible on your past productivity; emphasize how your previous work leads up to the present proposal or at least demonstrates feasibility of methods to be used.
  • DO NOT show preliminary results that are not of high quality -- this is your chance to represent yourself.
  • Show detailed numbers and representative raw data where necessary, especially if this is work that is unpublished.
  • Make sure that the major methods to be used in the proposed work are reflected by preliminary results. (If you do not have expertise or preliminary results with a technique, make sure you list a solid, experienced consultant or collaborator and include a letter agreeing to the collaboration.)
  • Put time and effort into preparing METICULOUS figures, graphs, or tables; this is your chance to demonstrate rigor and organization that will increase the reviewer's confidence that you can carry out the project.

Experimental Design

  • This IS one of the most common places where the text is insufficient. This is NOT just a place to tediously list group sizes, detailed methods, etc. This IS the place to demonstrate your ability to think knowledgeably and logically.
  • DEVELOP your aims; of all the sections this may well be the part of the grant upon which you spend the most time.
  • One method that often works is to divide this section into subheadings after each specific aim is restated, as follows:

    Specific Aim #.

    1. Rationale: how does this design relate to your hypotheses? What is your reasoning (IN DETAIL)?
    2. Methods: list general approaches first, explaining why the methods you propose are the best available for your questions. (Caveat: If you realize that you do not have the best, most direct methods for your questions, you need to rethink your aims or incorporate collaborators or new preliminary data showing feasibility with the necessary techniques.) **Don't forget to address statistical analysis.
    3. Anticipated results: you need to spend a great deal of thought as to potential outcomes and their likelihood. Explain how you will interpret the different outcome scenarios and how these results relate back to your hypotheses. This is an opportunity to demonstrate creativity and enthusiasm for the data to be obtained, and show that they will be competently addressed.
    4. Problems and pitfalls: be honest with yourself. If this section feels horribly uncomfortable, it is because you are probably trying an experiment that is not feasible. All experiments have pitfalls, but extraordinarily large pitfalls are likely to be unreasonable; hence, this section should serve as a reality test. Explain the pitfalls, and how alternate approaches will be used to overcome them if they occur. Do not think that avoiding mentioning a pitfall is a good strategy - it usually doesn't work. The reviewer will very likely notice the pitfall and believe that you are not aware of it, decreasing confidence in your ability to manage the data.

Timetable

Not a futile exercise, although it does not need to take up an inordinate amount of space. The idea is here to take it seriously and use it as a reality check for yourself.

Last updated July 17, 2006