Writing the Project Design

The project design section explains how the work will be done and why that work will produce the promised results. It specifies activities, sequence, dosage, staffing, and participant flow, cites the evidence behind the chosen approach, and traces every objective to activities, a named person, and a budget line.

Current figures — verified 2026-08-11

Item	Value	Source
Correlation between the NIH Approach criterion score and overall impact score	Usually around 0.8, higher than Significance, Innovation, Investigator, or Environment	NIA, The Approach criterion
NSF Project Description page limit	15 pages, including all visual materials	NSF PAPPG, Chapter II
Share of NSF proposals rated not competitive	Approximately two-thirds	UC Irvine, How NSF Makes Awards

These figures change. Verify against the linked source before relying on them. Report an outdated figure

Key takeaways

• Reviewers score the plausibility of the mechanism, not enthusiasm.
• Unspecified dosage is where designs stop being checkable.
• Every activity needs a person, a date, and a budget line.
• Naming alternatives considered strengthens the chosen approach.
• A design with no contingency reads as one that has not been run.

What is the project design section of a grant proposal?

The project design section describes the activities that will be performed, in what order, by whom, at what volume, for which participants — and argues that those activities can mechanically produce the outcomes promised elsewhere. Funders call it the approach, the methodology, the work plan, the scope of work, or the research strategy.

The section carries more weight than its page count suggests. At NIH, the average of reviewers’ Approach scores tracks the final overall impact score more closely than any other criterion, and the agency’s own analysis notes that Investigator and Environment “lag a long way behind” (NIA, The Approach criterion); the correlation figure appears in the current figures above. NSF encodes the same priority as a merit review element: “Is the plan for carrying out the proposed activities well-reasoned, well-organized, and based on a sound rationale? Does the plan incorporate a mechanism to assess success?” (NSF PAPPG, Chapter III).

What reviewers are grading is the plausibility of a mechanism. Enthusiasm, mission language, and the importance of the problem belong to other sections; within the writing the proposal hub, the design section is where a reader should be able to follow a causal path from a scheduled activity to a measured change without being asked to assume a step.

Winthrop University’s proposal guidance lists the components a complete methodology section covers: it “clearly describes activities, resources, processes,” “describes qualified personnel and tasks to be performed,” “includes a timeline with milestones,” “discusses expected outcomes,” and addresses “constraints, limitations, potential challenges” (Winthrop University, Proposal Development). A design missing any of the five has a hole a reviewer will find.

How do you build the work plan for a project design?

A project design work plan is built objective by objective, not chronologically. Start from the commitments in the goals and objectives section, decompose each into the activities required to deliver it, then assign each activity a responsible role, a start and end point, and a resource requirement.

There are seven steps:

• Step 1 — List each objective and the activities it requires. An activity that serves no objective is either budget padding or an objective you forgot to state.
• Step 2 — Specify dosage for every direct-service activity. How many sessions, how long, how often, delivered by whom, to how many people. Dosage is where designs become checkable and where fantasy becomes visible.
• Step 3 — Assign a responsible role, not a person’s enthusiasm. Name the position, the percentage of effort, and the supervisory line.
• Step 4 — Sequence by dependency. The University of Michigan’s guide asks the operative questions directly: “When will the first step be completed? When can subsequent steps be started? What must be done before what else, and what can be done at the same time?” (University of Michigan, Proposal Writer’s Guide).
• Step 5 — Locate the measurement points. Baseline collection before implementation, interim data at defined checkpoints, and final measurement inside the period of performance.
• Step 6 — Attach every activity to a budget line. The Office of Justice Programs states the requirement plainly: “Your budget should justify all expenses and be consistent with the program narrative” (OJP, Develop a Budget).
• Step 7 — Scale the plan down until it is deliverable. Michigan names over-reach as a category error rather than an ambition problem: “A frequent comment made by reviewers to new investigators is ‘the work is too ambitious,’” and being too ambitious “is a common rookie mistake.”

The work plan is also where a first year spent on setup should be declared rather than disguised. Michigan’s advice is to label it: “If your first year must be spent developing an analytical method or laying groundwork, spell that out as Phase 1.” Reviewers penalize hidden ramp-up far more than acknowledged ramp-up.

What should a grant project timeline show?

A grant project timeline should show sequence, dependency, duration, responsibility, and milestones — not just a list of months with activities beside them. A timeline that could describe any project of that length is decoration; one that shows what must finish before what else can start is evidence of planning.

The University of Michigan’s guide states the reason a timeline earns points at all: “A Timeline detailing the projected sequence and interrelationship of major tasks often gives the sponsor assurance that the investigator is capable of careful step-by-step planning, and that the work will be accomplished in an efficient and feasible manner.” The operative word is interrelationship. Gantt-style charts encode dependency visually, which is why Winthrop lists “Gantt charts, Logic Models” among the visual aids a methodology section may use, and Swarthmore advises applicants to “include a chart or graph to illustrate the timeline” (Swarthmore College, Develop Your Proposal).

Four elements distinguish a scoring timeline from a filler timeline. Milestones with completion criteria, so “curriculum developed” becomes “curriculum reviewed and approved by the advisory committee.” Dependencies marked, so a reviewer can see that recruitment must close before cohort one begins. Responsibility named per task, tying the timeline to the staffing plan. Reporting and evaluation checkpoints included, so data collection appears as scheduled work rather than as an assumption.

Timelines consume page limits, and visuals are not always free. NSF counts visual materials inside the Project Description page limit; see the current figures above (NSF PAPPG, Chapter II). Where space is tight, a compact table with a dependency column outperforms a decorative chart.

How do you describe participant flow and dosage in a project design?

Participant flow describes how a person enters a program, moves through it, and leaves it; dosage describes how much of the intervention that person actually receives. A project design that omits either has not specified the thing being funded, however well it describes the intent.

Participant flow has five stages that each need a stated method. Outreach — how eligible people learn the program exists. Eligibility and selection — the criteria, who applies them, and what happens to people who do not qualify. Enrollment — consent, intake, baseline measurement, and expected time from referral to first service. Service delivery — the dosage schedule, caseload ratios, and the mechanism for handling people who fall behind. Exit and follow-up — completion criteria, planned attrition rate, and the follow-up window.

Dosage is the specific place where reviewers catch designs that cannot work. A tutoring program promising a full grade level of gain on one 30-minute session per month has an arithmetic problem no prose can conceal. State frequency, duration, group size, and total contact hours per participant, and state the expected retention rate rather than implying that everyone enrolled receives everything scheduled.

Two numbers make participant flow verifiable. The first is target enrollment expressed as both unduplicated participants and total service units, which prevents the common inflation of counting repeat visits as people. The second is expected attrition, stated in advance with the plan for it. A design that assumes zero attrition is a design that has not been operated, and reviewers who have run programs read it that way.

Recruitment feasibility deserves its own sentence when the population is hard to reach. Naming the referral partners, the existing agreements, and the historical conversion rate from referral to enrollment converts an assumption into a claim with evidence behind it.

How do you justify the chosen approach over the alternatives?

Justifying an approach means naming the evidence behind it, naming the alternatives considered, and explaining why the chosen approach fits this population and this setting. A design presented as the only option reads as a design that was never compared to anything.

Evidence citation has a regulatory shape in federal competitions. Education Department rules define a project component as “an activity, strategy, intervention, process, product, practice, or policy included in a project,” and set the lowest evidence tier — demonstrating a rationale — as a component “included in the project’s logic model that is supported by citations of high-quality research or evaluation findings” (34 CFR 77.1). The unit of evidence is the component, not the whole project, so cite per component and state the design, sample, setting, and effect direction of each study rather than the title alone.

Population and setting match is the qualifier that separates a credible citation from a decorative one. A study conducted in urban elementary schools supports a rural high school program only with an argument about transferability, and making that argument explicitly is stronger than hoping no reviewer notices. Where the fit is imperfect, say so and describe the adaptation.

Alternatives should be named and dismissed in one or two sentences each. Michigan’s guide extends the same logic to unconventional choices: “If you are proposing new, risky or unorthodox methods, be sure to include adequate justification, e.g., references in literature about success of these methods in similar studies.” NIMH’s list of common application mistakes reads as an inventory of what happens when this discipline is skipped, including “no discussion of alternative models or hypotheses,” “no discussion of potential pitfalls,” and “not enough detail on approaches, especially untested ones” (NIMH, Common Mistakes in Writing Applications).

How does a project design align with the rest of the proposal?

Project design alignment is demonstrated by tracing every objective forward through activities, staffing, budget, and measurement, and showing the reader that nothing appears in one place without appearing in the others. A synthesis of NSF decline reasons lists misalignment as its own failure category: “Sound theoretical framework, solid methodology, but they don’t align with each other” (UC Irvine Research Development, How NSF Makes Awards).

The table below shows the alignment trace for a single objective in a hypothetical workforce training program; every value is invented to illustrate the structure, not drawn from a real project.

Trace element	Content
Documented need	Regional employer demand exceeds credentialed applicants in the target occupation
Objective	Increase annual credential completions from a stated baseline to a stated target by Year 3
Activities	Cohort-based training, two cohorts per year, with employer-hosted work experience
Staffing	Program manager at 0.5 FTE; two instructors at 1.0 FTE; job developer at 0.5 FTE
Budget lines	Salaries and fringe for the four positions; instructional supplies; participant transportation stipends
Measurement	Credential attainment from the college registrar; employment from state wage records at two follow-up points

Running the trace in both directions is what makes it useful. Forward from each objective, ask whether the activities are sufficient to produce it. Backward from each budget line, ask which activity requires it and which objective that activity serves. Anything that fails both directions should be cut before a reviewer cuts points for it.

Federal criteria reward the trace explicitly. Education Department selection factors include “the quality of the logic model or other conceptual framework underlying the proposed project, including how inputs are related to outcomes” (34 CFR 75.210), and the Kellogg framework supplies the if-then language the trace runs on: “If you accomplish your planned activities to the extent you intended, then your participants will benefit in certain ways” (W.K. Kellogg Foundation, Logic Model Development Guide).

How do you handle risk and adaptation in a project design?

Risk handling in a project design means naming what could go wrong, stating the threshold at which you would notice, and describing what you would do. A design with no contingency section reads as one that has never been operated, and reviewers who have run programs discount it accordingly.

Four risks appear in almost every service or research design. Recruitment shortfall — enrollment below target, which threatens both service volume and statistical power. Staffing gaps — a vacancy in a specialized role in a thin labor market. Partner non-performance — a referral source, data provider, or host site that does not deliver. Data access failure — records the design requires that no agreement yet covers.

Each one becomes credible when written as a decision rule rather than a reassurance. “If enrollment is below 80 percent of target at month nine, the program will add a second referral pathway through the named partner and document the change in an amended implementation plan” tells a reviewer that someone has thought about the number, the moment, and the authority to act. “We anticipate strong enrollment” tells them nothing.

Adaptation has a timing constraint worth respecting. The National Institute of Justice notes that outcome evaluation “is difficult when a program is too new because program elements, strategies or procedures often still are being adjusted and finalized,” and belongs “at the end of the program’s development, when the program is stable and unlikely to change in fundamental ways” (NIJ, Plan a Program Evaluation from the Start). A design that promises both a rigorous impact study and continuous redesign of the intervention has promised two incompatible things.

Michigan’s framing is the shortest guidance available on tone: “Try to imagine the questions or objections of a hostile critic and show that the research plan anticipates them.” Anticipated objections score better than unaddressed ones.

What goes wrong in a project design section?

Project design sections fail in a small number of mechanical ways, each visible before submission. Seven recur:

• A design that cannot produce the stated outcomes. The volume of service is too small, or too short, or reaches too few people for the promised change. Repair: do the arithmetic before writing the objective.
• Unspecified dosage. Activities named without frequency, duration, or group size. Repair: state contact hours per participant.
• Magical intermediate steps. A jump from activity to outcome with no stated mechanism. Repair: write the intervening sentence, or cut the claim.
• Staffing that does not appear in the budget. A named coordinator, evaluator, or partner with no line and no letter. Repair: reconcile roles, effort, and lines before submitting.
• No risk contingency. No thresholds, no triggers, no alternative pathway. Repair: convert each assumption into a decision rule.
• Insufficient methodological detail. The NSF decline-reason synthesis cited above names “flawed research design OR failure to specify research methods in sufficient detail” among the primary reasons, adding that “often, plans for data analysis are insufficient.” Repair: specify the analysis, not just the collection.
• Over-scope. More activities than the budget, period, or staff can deliver, which reads as inexperience rather than ambition.

The category worth internalizing is scale. Roughly two-thirds of NSF proposals are rated not competitive, and the agency’s own breakdown splits that group between weak proposals and good ideas that are not yet ready, usually because of methodological flaws; see the current figures above. Most declines in that second group are design problems, not idea problems, and design problems are the ones a writer can fix without a new idea.

Frequently asked questions

How long should the project design section be?

In proportion to its scoring weight. Where a competition publishes point values, allocate pages to match. Where it does not, the design section is usually the longest part of the narrative, since it carries the mechanism reviewers grade most heavily and must accommodate a work plan, a timeline, and a staffing description.

What is the difference between a work plan and a timeline?

A work plan lists activities, responsibilities, and resources organized by objective. A timeline places those activities in sequence with dependencies and milestones. Most competitive proposals include both, because the work plan proves completeness and the timeline proves feasibility.

Does the project design section need a logic model?

Often. Human-services competitions at many federal agencies require one explicitly, while research competitions generally expect the equivalent logic in prose. The logic model is the compact form of the same causal argument the design section makes at length.

How specific does the staffing plan need to be?

Specific enough to reconcile with the budget. Name the position, the percentage of effort, the qualifications required, and the supervisory relationship. Where a key person is already hired, name them and attach the résumé; where the position is to be filled, state the hiring timeline and the qualifications.

Should you describe alternatives you rejected?

Yes, briefly. One or two sentences per alternative showing why the chosen approach fits this population and setting better. Reviewers read the absence of alternatives as evidence that none were considered, and NIMH lists the lack of discussion of alternative models among common application mistakes.

How do the project design and evaluation plan relate?

The design supplies what will be measured; the evaluation plan supplies how. Baseline collection must be scheduled in the design before implementation begins, or the evaluation loses its comparison point and the two sections contradict each other on the page.

Related topics

• Writing the Proposal — the hub for section-by-section proposal craft
• The Anatomy of a Grant Proposal
• Writing a Statement of Need
• Demonstrating Organizational Capacity
• Writing a Budget Narrative

Sources

1. National Institute on Aging. The Approach criterion: why does it matter so much in peer review? NIA Blog, 2013-07-31. https://www.nia.nih.gov/research/blog/2013/07/approach-criterion-why-does-it-matter-so-much-peer-review (accessed 2026-08-11)
2. U.S. National Science Foundation. PAPPG 24-1, Chapter III — Proposal Processing and Review. https://www.nsf.gov/policies/pappg/24-1/ch-3-proposal-processing-review (accessed 2026-08-11)
3. U.S. National Science Foundation. PAPPG 24-1, Chapter II — Proposal Preparation Instructions. https://www.nsf.gov/policies/pappg/24-1/ch-2-proposal-preparation (accessed 2026-08-11)
4. Winthrop University. Proposal Development. Office of Sponsored Programs and Research. https://www.winthrop.edu/grants/proposal-development.aspx (accessed 2026-08-11)
5. University of Michigan Office of Research and Sponsored Projects. Proposal Writer’s Guide. https://sites.lsa.umich.edu/nextprof-science/wp-content/uploads/sites/130/2018/04/3-University-of-Michigan-Proposal-Writers-Guide.pdf (accessed 2026-08-11)
6. Swarthmore College Sponsored Programs. Develop Your Proposal. https://www.swarthmore.edu/sponsored-programs/develop-your-proposal (accessed 2026-08-11)
7. Office of Justice Programs. Develop a Budget. U.S. Department of Justice. https://www.ojp.gov/funding/grants101/develop-budget (accessed 2026-08-11)
8. National Institute of Mental Health. Common Mistakes in Writing Applications. https://www.nimh.nih.gov/funding/grant-writing-and-application-process/common-mistakes-in-writing-applications (accessed 2026-08-11)
9. U.S. Department of Education. 34 CFR 77.1 — Definitions that apply to all Department programs. eCFR. https://www.ecfr.gov/current/title-34/subtitle-A/part-77/section-77.1 (accessed 2026-08-11)
10. U.S. Department of Education. 34 CFR 75.210 — General selection criteria. Cornell Legal Information Institute. https://www.law.cornell.edu/cfr/text/34/75.210 (accessed 2026-08-11)
11. UC Irvine Research Development. How NSF Makes Awards: Insights from Inside the Black Box. https://www.researchdevelopment.socsci.uci.edu/files/documents/2021/How%20NSF%20Makes%20Awards.pdf (accessed 2026-08-11)
12. W.K. Kellogg Foundation. Logic Model Development Guide (2004). Hosted by NACCHO. https://www.naccho.org/uploads/downloadable-resources/Programs/Public-Health-Infrastructure/KelloggLogicModelGuide_161122_162808.pdf (accessed 2026-08-11)
13. National Institute of Justice. Plan a Program Evaluation from the Start. https://nij.ojp.gov/topics/articles/plan-program-evaluation-start (accessed 2026-08-11)