Program design: writing the methods, activities, and timeline

The program design section (also called methods, approach, project description, or implementation plan) is where you prove you can turn money into results. It is usually the longest section, and in federal applications it typically carries a large share of the points. Candid's guidance sums up the expectation: explain exactly how, when, and by whom the project will be carried out.

A reviewer finishing this section should be able to picture a week in your program: who walks in the door, what happens, who is leading it, and why it should work.

What reviewers look for

The core elements

Participants: who, how many, and how you'll reach them

Restate your target population precisely, consistent with your statement of need, and give the number you will serve. Then describe recruitment and retention concretely. "We will recruit through our partners" is a placeholder; "school counselors will refer students who score below grade level on the fall benchmark, and our site coordinators will call every referred family within five school days" is a plan.

Activities and dosage

Describe each major activity with enough specificity that someone could replicate it. Dosage, meaning how much of the intervention each participant receives, is the detail most often missing and most often questioned. Reviewers compare dosage with your objectives: an hour a month is unlikely to raise reading levels a full grade.

Staffing

Describe who does the work, their time commitment, and their qualifications. A staffing table is efficient:

(Fictional illustration.) If a key position is unfilled, describe the hiring plan, timeline, and the qualifications you will require. Every role in this table should appear in the budget, and leadership qualifications should be consistent with your organizational capacity section.

Partners

For each partner, state what they will do, not just that they "support" the project. Back key partnerships with letters of commitment or memoranda of understanding that describe specific contributions: space, referrals, data sharing, staff time.

The evidence base: why should this work?

Reviewers want a reason to believe your approach will produce the outcomes you promise. There are three main kinds of support, and the strongest proposals combine them:

1. Published evidence for your model or its key components. If you are implementing an established model, name it and cite the research. If your program is locally developed, cite the research behind its core components (for example, small-group instruction or structured phonics).
2. Your own results. Outcome data from prior years of the same program is persuasive, especially if you describe how you collected it.
3. Community input. How participants and community members shaped the design.

Evidence clearinghouses

Clearinghouses review research and rate programs or practices. They are useful both for choosing a model and for citing its evidence. Status as of October 2026:

Federal evidence tiers

Some federal programs score or require evidence. The U.S. Department of Education defines four levels in 34 CFR 77.1: strong evidence, moderate evidence, promising evidence, and demonstrates a rationale. The first three depend on the design and findings of studies of your key project components; "demonstrates a rationale" means a key component in your logic model is supported by citations of high-quality research or evaluation findings suggesting it is likely to improve relevant outcomes. If a NOFO references evidence levels, match your citations to its definitions precisely. See how to read a NOFO.

Fidelity and adaptation

If you use an established model, explain how you will maintain fidelity (training, coaching, observation checklists) and any adaptations you will make for your population, with reasons. Funders understand that adaptation is often necessary; they want to see it is deliberate.

The timeline

A timeline shows a reviewer that you have thought through sequencing and start-up. A table formatted like a simple Gantt chart is the most readable option.

Some funders prefer a milestone table instead: list each milestone, its target date, and the person responsible. Use whichever the funder's template asks for.

Risks and contingencies

A short paragraph on what could go wrong, and what you'll do about it, reads as competence, not weakness.

Federal applications: organizing the approach

In a federal project narrative, this content typically falls under a heading such as "Approach," "Project Design," or "Implementation Plan," as set by the NOFO's review criteria. HHS's applicant guidance notes that the budget narrative should justify the proposed cost per activity, service, or product, so make sure activities in your design are described in units you can cost. Use the NOFO's exact headings and address each sub-criterion explicitly, in order.

Writing tips

• Be concrete. Replace "a variety of engaging activities" with what actually happens.
• Use the same numbers everywhere. Participants, sessions, sites, and staff should match the objectives, logic model, and budget.
• Use tables for staffing, timeline, and partner roles. They save space and are easier to score.
• Write in the future tense with confidence: "Tutors will...", not "We hope to..."
• Show the participant's perspective. One sentence describing a participant's week can make the design vivid.
• Connect back to the need. A sentence explaining how each major activity addresses a cause named in your need statement strengthens the logic.

Common mistakes

• No dosage. Reviewers can't judge whether outcomes are realistic.
• Recruitment assumed, not planned. Under-enrollment is one of the most common reasons programs miss targets.
• Staff named without time commitments, or time commitments that don't match the budget.
• Partners listed without roles.
• No start-up period in the timeline.
• Evidence overstated or cited without specifics.

Next, plan how you'll measure results in the evaluation plan, and cost every activity in the grant budget.