The methods section is where many proposals win or lose. Learn how to write a compelling methods (approach) section that shows funders you can deliver.

If the statement of need tells the funder why the work matters, the methods section tells them how it will actually happen. It’s the part of the proposal where promises become a plan, and where many proposals quietly fall apart.

A weak methods section is the most common reason a proposal with a strong need section still loses. The funder believes the problem; they just don’t believe this organization will solve it. Strong methods writing closes that gap by showing exactly what you’ll do, with whom, on what schedule, and why.

This guide covers how to write a methods section that earns the funder’s confidence.

TL;DR: Quick Answers

What is the methods section? The part of the proposal that describes the approach, activities, schedule, and team that will deliver the project’s goals.
What does it need to include? A clear approach, specific activities, a workplan and timeline, key personnel, and the evidence base behind your design.
What does it need to avoid? Vague activities, disconnects from your goals and budget, and an unrealistic schedule.
How does it tie to the rest of the proposal? Tightly, the methods section is where your logic model, goals, evaluation plan, and budget operationalize.

What the Methods Section Does

The methods section answers four core questions:

What approach will you use to achieve the goals? What model, framework, or evidence base informs the design?
What specific activities will happen? Who does what, with whom, where, and when?
What’s the timeline? What’s done in months 1–3, 4–6, etc.?
Who’s responsible? Which roles and people will deliver each piece?

Some funders explicitly score the methods section heavily, especially federal funders like HRSA, CDC, NSF/NIH, ED, and DOJ. Even where it isn’t explicit, it’s where reviewer confidence is built or lost.

Structure: A Strong Methods Section in Order

A defensible methods section usually moves through these elements:

1. Overall approach. A short, clear opening that names the model or framework you’re using and why. If it’s evidence-based, cite the evidence. If it’s an adaptation or innovation, explain the rationale.

2. Major activities. Describe each major activity, what it is, who participates, what happens during it, what comes out of it. Tie each activity to a goal or objective from your SMART goals.

3. Workplan and timeline. A clear schedule, often as a Gantt-style chart or quarter-by-quarter table, showing when each activity happens and how they sequence.

4. Key personnel and partners. Who’s leading the work and what qualifies them. Name key staff and partners; tie them to specific roles. See letters of support.

5. Recruitment, engagement, and outreach. How participants come to the program. Recruitment plans often get less attention than they deserve and are a common point of skepticism.

6. Cross-cutting strategies. Cultural responsiveness, language access, equity, trauma-informed design, harm reduction, whatever cross-cuts apply to your work.

7. Risks and adaptations. Some funders expect a brief, honest mention of likely challenges and how you’ll respond, see risk-and-mitigation in grant proposals.

What Funders Actually Want to See

Across funders, a few things consistently signal a strong methods section:

Specificity. “We will deliver weekly tutoring sessions to 60 third-graders at three Title I schools, using the [named curriculum], facilitated by 6 trained tutors recruited from local community college partners.” That’s specific. “We will provide tutoring services” is not.

Coherence with the rest of the proposal. Methods activities map cleanly to your logic model. The budget funds each activity. The evaluation plan measures the outcomes. A drift between any of these is a red flag.

Realism. A timeline that reflects how programs actually start (hiring, ramp-up, recruitment) rather than assuming day-one full operation.

Evidence base. Methods grounded in research, prior performance, or a credible logic, not invented from scratch.

Cultural and community fit. For community-facing work, evidence that the approach was designed with, not just for, the community.

Common Methods Section Mistakes

Vague activities. “Provide services” is not a method. Name the services, the format, the dosage, and the participants.
Mismatched timeline. A 12-month grant timeline that assumes hiring happens on day one and impact emerges by month three.
No mention of recruitment. Funders are skeptical of “if we build it, they will come.” Show how participants actually arrive.
Disconnected from goals. Activities that don’t clearly lead to the SMART goals you set.
Generic templates. Reviewers can tell when a methods section came from a template; specific organizational and local detail beats every template every time, see training AI on your past proposals.
Skipping personnel. Reviewers fund teams as much as plans. Name the people.

How Methods Connect to the Rest of the Proposal

The methods section is the spine that connects every other piece:

Activities flow from the statement of need.
Each activity ladders to a SMART goal and the logic model.
The evaluation plan measures what these activities produce.
The budget funds each activity line.
The sustainability plan describes what continues.

Before you submit, walk a reviewer’s mental path through the proposal: need → goal → method → measurement → cost → future. If any link breaks, the methods section probably needs to fix it.

How Grantboost Helps

A coherent methods section is impossible to write in isolation; it depends on the rest of the proposal being aligned. Grantboost helps you build the whole proposal as one connected piece, drafted in your organization’s voice (see training AI on your past proposals), structured around the specific funder’s requirements, so the methods section sits coherently inside the rest of the application.

Try Grantboost free and build proposals where every section fits.

How to Write the Methods (Approach) Section of a Grant Proposal