Skip to content

How to Write a Grant Management Plan (With Examples)

Updated 17 official sources

Quick Answer: A grant management plan names who runs the project, how federal money is controlled under 2 CFR 200.302 and 200.303, how data gets collected, and what happens when something goes wrong.

Full answer and how we checked it

Reviewers score it directly: SAMHSA's FY2026 CCBHC-PDI notice gives 25 points to organizational experience and staffing and 20 to data collection. Most run 3 to 5 pages and should match your budget line by line.

Data note: Amounts may shift with annual appropriations.

Source review by Grantsights, October 17, 2026: Grantsights checked the management-plan advice here against the current eCFR text of 2 CFR 200.302 (financial management), 200.303 (internal controls), 200.308 (extensions), 200.329 (performance reporting), and 200.332 (subrecipient monitoring); the 2024 Uniform Guidance revision published at 89 FR 30046; the scoring criteria in SAMHSA's FY2026 CCBHC-PDI notice (SM-26-014); ED's management-plan criterion in 34 CFR 75.210(g); and NIH's simplified review framework. Grantsights also pulled the 475 Certified Community Behavioral Health Clinic awards (Assistance Listing 93.696) with FY2025 activity from USAspending.gov (opens in a new tab) to see how grantees actually structure these projects. Where a NOFO sets a stricter rule than 2 CFR 200, follow the NOFO.

In this guide

If you're a grant writer drafting a management section, a program director organizing a multi-site project, or a finance lead checking that a proposal covers federal oversight rules, this guide covers what reviewers look for and what the regulations require.

Applicants often pour most of their drafting time into the program narrative and treat the management plan as "everything else." That's a mistake. Plenty of proposals describe strong programs but fall apart on the operational details. Your management plan is where you prove you're not one of those applicants.

Here's the thing about federal grant reviewers: they're reading dozens of proposals in a short window. They've seen plenty of organizations win funding and then struggle to hire staff, track spending, collect data, or submit reports on time. The management plan is the section where experienced reviewers separate organizations that can execute from those that can't.

This guide walks through every component of a strong management plan, explains what reviewers actually look for, and shows you how to connect your management approach to your budget justification so the two sections reinforce each other.

What Reviewers Actually Look for in a Management Plan

In SAMHSA's FY2026 CCBHC-PDI notice, 45 of the review points sit in two management-heavy sections, so read the Notice of Funding Opportunity (NOFO) scoring criteria before writing a single word. The NOFO's review criteria spell out what reviewers are required to evaluate, and the Grants.gov applicant resources page (opens in a new tab) explains how a notice is organized.

Federal review criteria for management usually cover some mix of these five dimensions:

  • Organizational capacity to implement the proposed project
  • Adequacy of staffing and qualifications of key personnel
  • Soundness of the management approach including oversight, monitoring, and quality assurance
  • Reasonableness of the timeline and milestones
  • Adequacy of systems for tracking progress and managing finances

Point values vary by program, so check the criteria in your notice. Here's how three agencies handle it:

Agency and sourceWhere management is scoredWeight
SAMHSA, FY2026 CCBHC-PDI NOFO (SM-26-014) (opens in a new tab)Section D, Organizational experience and staffing (about 3 pages); Section E, Data collection and performance measurement (about 2 pages)25 points and 20 points
ED, 34 CFR 75.210(g) (opens in a new tab)"Quality of the management plan," when a competition selects itSet in each competition's notice
NIH, simplified review framework (opens in a new tab)Factor 3, Expertise and Resources (investigator and environment)Rated sufficient or not; no numeric score

According to ED's selection criteria in 34 CFR 75.210(g), reviewers can weigh whether the plan will meet objectives "on time and within budget," with clearly defined responsibilities, timelines, and milestones, and whether time commitments of the project director and other key staff are adequate. According to NIH's review framework, for most research project grants due on or after January 25, 2025, reviewers judge Factor 2 (Rigor and Feasibility) on a 1 to 9 scale and Factor 3 only as sufficient or not. A reviewer who marks resources insufficient has to explain why in writing, so a thin description of your environment still costs you.

The common thread across agencies: reviewers want evidence, not promises. Saying "we have strong financial management systems" means nothing. Describing your specific accounting software, your monthly reconciliation process, and your segregation of duties policy means everything.

Looking for your next grant?

About once a week, we email a short list of open grant calls with real deadlines from different funders. It lists open calls only.

No spam. Unsubscribe anytime.

The Organizational Capacity Section

This section answers one question: does your organization have the track record, infrastructure, and institutional knowledge to pull this off? SAMHSA makes that concrete. Its FY2026 CCBHC-PDI notice asks applicants to show experience delivering at least 5 of the 9 required CCBHC services and to affirm in Attachment 1 that the clinic served at least 200 unduplicated people with a mental health or substance use disorder in the prior calendar year. Other notices are less specific, but reviewers are asking the same question.

What to Include

Start with a brief organizational overview that's directly relevant to the proposed project. Don't recite your entire history. Focus on:

  • Similar projects you've successfully managed. Name the funder, the award amount, and the outcome. "We managed a $1.2 million SAMHSA grant from 2022 to 2025, serving 450 participants and achieving a 78 percent program completion rate" is specific and verifiable.
  • Relevant infrastructure. Office space, technology systems, existing relationships with the target population, and community partnerships that you'll use for this project.
  • Compliance track record. If you've had clean Single Audits, say so. Under 2 CFR 200.501 (opens in a new tab), an organization that expends $1,000,000 or more in federal awards during its fiscal year needs one; the single audit guide covers which fiscal years use that threshold. If you've had clean monitoring visits from federal agencies, mention them.

What Reviewers Flag as Weaknesses

  • Vague statements about organizational experience without naming specific grants or outcomes
  • No mention of financial management infrastructure
  • Claiming capacity you can't document (reviewers sometimes check)
  • Ignoring organizational challenges that are obvious from your size or location

If your organization is newer and doesn't have extensive federal grant experience, be honest about it and describe the specific steps you're taking to build capacity. That's more convincing than pretending you have experience you don't.

The Staffing Plan: Who Does What and When

In SAMHSA's FY2026 CCBHC-PDI notice, the Project Director and the Project Evaluator must each be at least 50 percent of a full-time position, and neither role can be split among more than 2 people. That's the kind of hard rule a staffing plan has to meet before any reviewer judges its quality. The staffing plan is often the most scrutinized part of the management section. Reviewers want to know that you've thought carefully about who will do the work and whether the proposed level of effort is realistic.

Building a Strong Staffing Table

Create a table that shows each position, the person's name (if hired), their qualifications, their FTE or percent effort on the project, and their primary responsibilities.

PositionNameFTEKey QualificationsPrimary Responsibilities
Project DirectorJane Smith0.75 FTEMSW, 8 years program managementOverall project oversight, funder reporting, staff supervision
Program CoordinatorTo Be Hired1.0 FTEBA required, bilingual preferredDay-to-day operations, participant enrollment, data entry
EvaluatorDr. Robert Chen0.20 FTEPhD, 12 years evaluation experienceDesign evaluation framework, analyze data, write reports
Fiscal ManagerMaria Lopez0.15 FTECPA, 6 years grant accountingBudget monitoring, drawdowns, audit preparation

The names in this table are placeholders. Check the effort levels against your notice before you copy the format: a 0.20 FTE evaluator works for many programs, but it would fail the 50 percent minimum in the CCBHC-PDI notice. SAMHSA also asks for each position's role, level of effort as a percentage of employment, and qualifications, so a table with those columns maps straight onto its Section D.

Key Principles for the Staffing Plan

Match effort to workload. If you're proposing to serve 200 participants with one full-time coordinator, reviewers will question whether that's realistic. Show your math: how many participants per month, how many contact hours per participant, how much time for documentation.

Name existing staff when possible. Positions listed as "To Be Hired" are weaker than named individuals because there's no guarantee you'll find the right person. If the position is vacant, describe your recruitment plan, timeline, and the qualifications you'll require.

Include supervisory relationships. Who supervises the project coordinator? Who does the project director report to? An organizational chart helps reviewers understand the chain of accountability.

Account for turnover. Staff turnover is one of the biggest risks in grant-funded projects. Describe your succession plan. If the project director leaves, who steps in? How will you maintain continuity?

Your staffing plan should align precisely with your budget. If you list a position at 0.75 FTE in the management plan, your budget categories should reflect the same percentage. Inconsistencies between the narrative and the budget are among the most common reviewer complaints.

Financial Management Systems

2 CFR 200.302 (opens in a new tab) lists 7 things every recipient's financial management system must provide, and the financial part of your management plan should show you've got each one. For organizations that have managed federal grants before, this is a chance to describe your proven systems. For first-time applicants, it's where you show you've done your homework on federal grant compliance requirements.

What 2 CFR 200.302 and 200.303 Require

Grantsights checked the current eCFR text of both sections (as of October 15, 2026). Here's what they require and what a management plan should say about each:

RequirementRuleWhat to write in the plan
Identify every federal award, with Assistance Listing number, award number, year, and agency200.302(b)(1)Your chart of accounts sets up a separate fund or class for each award
Accurate, current, complete financial results for reporting200.302(b)(2)Who prepares the SF-425 and how often you reconcile to the general ledger
Records of the amount, source, and spending of federal funds, backed by source documents200.302(b)(3)Where invoices, timesheets, and approvals are kept
Effective control over all funds, property, and assets200.302(b)(4)Asset tagging and inventory for equipment
Comparison of spending with the budget for each award200.302(b)(5)Monthly budget-to-actual review and who signs off
Written payment procedures (200.305)200.302(b)(6)How drawdowns are timed to match actual costs
Written procedures for deciding whether costs are allowable200.302(b)(7)Who reviews a questionable charge before it posts
Documented internal controls aligned with GAO's Green Book or COSO200.303(a)Segregation of duties and approval limits
Reasonable cybersecurity measures to protect personally identifiable information200.303(e)Access controls on participant data and case files

What to Cover

Accounting system. Name your accounting software and confirm it can track expenses by grant, budget category, and cost center. Federal grants require you to maintain records that distinguish between allowable and unallowable costs under 2 CFR 200.

Internal controls. Describe your segregation of duties. Who approves expenditures? Who processes payments? Who reconciles accounts? The same person shouldn't be doing all three. According to 2 CFR 200.303(a), those controls should align with either the Comptroller General's "Standards for Internal Control in the Federal Government" or the COSO Internal Control-Integrated Framework, so name the one you follow.

Drawdown procedures. Explain how you'll request funds from the federal payment system. HHS awards are paid through the Payment Management System, and many other agencies use Treasury's ASAP system. Describe your process for ensuring drawdowns match actual expenditures.

Cost principles compliance. Reference your understanding of allowable costs under the Uniform Guidance. For equipment, which 2 CFR 200.1 now defines as items costing $10,000 or more per unit (or your lower capitalization threshold), describe your procurement and inventory procedures. For indirect costs, state your negotiated indirect cost rate or the de minimis rate you'll use; 2 CFR 200.414(f) (opens in a new tab) allows up to 15 percent of modified total direct costs. The 2 CFR 200 guide lists the other thresholds the 2024 revision changed.

Audit readiness. If your organization expends $1,000,000 or more in federal awards during its fiscal year, 2 CFR 200.501 requires a Single Audit. Describe your audit history and how you address findings. If you're below the threshold, describe your financial review procedures.

Example Language

"ABC Nonprofit uses QuickBooks Enterprise with a customized chart of accounts that tracks expenditures by funding source, budget category, and program activity. The Finance Director approves all expenditures over $500, and the Executive Director approves expenditures over $5,000. Monthly budget-to-actual reports are reviewed by the Project Director and Finance Director, with variances exceeding 10 percent investigated and documented. Our organization completed Single Audits for FY 2023, FY 2024, and FY 2025 with no findings or questioned costs."

The Data Collection Plan

SAMHSA's CCBHC-PDI notice gives data collection and performance measurement 20 points on its own, and it asks applicants to describe the Project Evaluator's role in using that data to manage the project. Reviewers need to know how you'll track progress and measure results. The data collection plan connects directly to your evaluation plan, but it focuses specifically on the operational mechanics: what data you'll collect, who collects it, how often, and where it's stored.

Components of a Data Collection Plan

Data elements. List every piece of data you'll collect, tied to your objectives. If Objective 1 is "Increase participant employment by 25 percent within 12 months," your data elements include employment status at intake, employment status at 3-month intervals, job type, wage level, and hours worked.

Collection methods. Specify the instruments. Are you using validated surveys? Pre/post assessments? Administrative data from partner agencies? Case management notes? Name the specific tools.

Collection schedule. When does data collection happen? At enrollment? Monthly? Quarterly? At exit? At follow-up? Create a data collection calendar that shows the timing.

Responsible staff. Who enters the data? Who checks it for accuracy? Who runs reports?

Data management system. Describe your database or case management system. Many federally funded programs require specific data systems. HUD homeless assistance grantees use HMIS. According to SAMHSA's FY2026 CCBHC-PDI notice, grantees must enter client-level data in SAMHSA's Performance Accountability and Reporting System (SPARS) no later than 30 days after collection, at intake, 6 months after intake, 12 months after intake and annually after that, and at administrative closeout. That's a fixed reporting rhythm your staffing and data plan have to support. Identify the required system and confirm you have access and training.

Data quality procedures. Describe how you'll ensure accuracy. Monthly data quality checks? Supervisor review of a random sample of records? Cross-referencing between data systems? Reviewers want to know you've planned for the reality that data entry errors happen.

Connecting Data to Reporting

Explain how your data collection feeds into your required reports. Under 2 CFR 200.329 (opens in a new tab), performance reports come no less often than annually and no more often than quarterly unless the agency imposes a specific condition. Quarterly or semiannual reports are due within 30 days after the period ends, annual reports within 90 days, and the final report within 120 days after the period of performance. If you're collecting the right data on the right schedule, report writing becomes straightforward. If you're not, you'll be scrambling at every reporting deadline.

Most federal grant reporting requirements include both financial reports (SF-425 Federal Financial Report) and programmatic performance reports. Your data collection plan should support both.

Quality Assurance and Continuous Improvement

The quality assurance section shows reviewers that you won't just launch the program and hope for the best. You'll actively monitor quality and make adjustments.

Building a QA Framework

Define quality standards. What does "good" look like for your program? Set specific benchmarks. "90 percent of participants will complete intake within 48 hours of referral." "Case managers will meet with participants at least twice monthly." "All staff will complete 20 hours of annual training."

Monitoring methods. How will you check whether you're meeting those standards? Options include:

  • Supervisory review of case files (monthly sample of 10 to 20 percent)
  • Participant satisfaction surveys (quarterly)
  • Fidelity assessments for evidence-based practices (semi-annual)
  • Staff observation and feedback sessions
  • Dashboard tracking of key performance indicators

Corrective action process. What happens when something isn't working? Describe your process for identifying problems, determining root causes, developing solutions, and tracking whether the fix worked. Reviewers know that every program hits obstacles. They want to see that you have a system for responding.

Continuous quality improvement meetings. Describe a regular meeting (monthly or quarterly) where project leadership reviews performance data, identifies trends, and makes operational adjustments. Name who attends, what data they review, and how decisions are documented.

Why This Section Matters for Scoring

Quality assurance is one of the easiest sections to write generically, which is why many applicants lose points here. Reviewers can tell the difference between a boilerplate QA description and one that's targeted to your specific program model. Tie your QA activities to the actual risks and challenges of your proposed project. If you're implementing a new evidence-based practice, your QA plan should include fidelity monitoring. If you're serving hard-to-reach populations, it should address engagement and retention tracking.

The Communication Plan

Communication plans describe how information flows between staff, partners, participants, and the funder. This section is especially important for collaborative grants involving multiple organizations.

Internal Communication

  • Staff meetings. How often does the project team meet? What's the agenda structure? Who supports?
  • Supervisory conferences. How often do supervisors meet one-on-one with direct service staff?
  • Information sharing. How do staff access project updates, policy changes, and client information? Shared drives? Project management software? Email protocols?

External Communication

  • Funder communication. How will you stay in touch with your federal program officer? Many program offices hold periodic check-in calls or monitoring visits, and your award terms will say what's expected. Note these in your plan, along with who's responsible for telling the program officer about problems that affect milestones.
  • Partner communication. If the project involves partner organizations, describe the meeting schedule, information sharing protocols, and escalation procedures for resolving disagreements.
  • Community communication. How will you share program information with the community? Referral partners? Advisory boards?

Advisory or Governance Boards

Many federal grants require or encourage an advisory board. If applicable, describe the board's composition, meeting frequency, and role. Clarify whether the board is advisory or has decision-making authority. Include community members, people with lived experience, and content experts as appropriate.

Timeline and Milestones

The timeline translates your management plan from concept to schedule. It should cover the entire grant period, with milestones for each quarter or reporting period.

Structuring the Timeline

Use a Gantt chart or milestone table rather than a paragraph of text. Reviewers need to quickly see what happens when.

QuarterMilestoneResponsible
Q1 (Months 1-3)Hire staff, finalize MOUs, configure data systems, conduct staff trainingProject Director
Q2 (Months 4-6)Begin participant enrollment, launch services, first data quality reviewProgram Coordinator
Q3 (Months 7-9)Reach 50% enrollment target, mid-year performance review, submit semi-annual reportProject Director, Evaluator
Q4 (Months 10-12)Reach 100% enrollment, conduct participant satisfaction survey, annual reportFull Team

Common Timeline Mistakes

Underestimating startup. Plan for 2 to 4 months before services are fully running. You need to hire staff, negotiate subawards, set up data systems, and train everyone before you can serve your first participant. Reviewers get suspicious when you show full enrollment in month one.

Ignoring reporting deadlines. Build federal reporting deadlines into your timeline. If semi-annual reports are due April 30 and October 30, your data collection and analysis need to be complete at least two weeks before those dates.

Missing the no-cost extension window. If you might need extra time, know that most agencies require you to request a no-cost extension before the grant end date. Under 2 CFR 200.308(g)(2) (opens in a new tab), a recipient whose award terms allow a one-time extension of up to 12 months must notify the agency in writing, with a justification and revised end date, at least 10 calendar days before the period of performance ends. The extension can't be used only to spend leftover funds, and some agencies set earlier internal deadlines in their award terms. Build a decision point into your timeline well ahead of that.

Front-loading all activities. Spread major activities across the full grant period. A timeline that shows everything happening in the first two quarters and nothing in the last two raises questions about sustainability and planning.

How the Management Plan Connects to the Budget

Your management plan and budget should read like two versions of the same story. Every staff position mentioned in the management plan should appear in the budget. Every data system, training event, travel cost, and contracted service referenced in the management plan should have a corresponding budget line.

Alignment Checklist

  • Does the FTE for each position match between the staffing plan and the budget?
  • Are consultant or contractor costs in the budget supported by descriptions in the management plan?
  • Does the budget include costs for data collection tools, software licenses, or assessment instruments mentioned in the data collection plan?
  • Are travel costs for advisory board meetings, partner convenings, or site visits reflected in both documents?
  • If you pass funds to partner organizations through subawards, does the budget show subaward costs and does the management plan describe subrecipient risk assessment and monitoring per 2 CFR 200.332 (opens in a new tab)? This applies to every subaward; the $50,000 figure only limits how much of each subaward counts toward indirect costs.

This cross-referencing isn't just good practice. It's where reviewers catch inconsistencies. A management plan that describes monthly partner meetings but a budget with zero travel funds tells reviewers you haven't thought this through. A budget with a $200,000 subaward but no description of subrecipient monitoring tells them you don't understand the compliance requirements.

How CCBHC Grantees Actually Structure the Money

Grantsights analysis of USAspending.gov (opens in a new tab) award data found 475 grants under Assistance Listing 93.696 (Certified Community Behavioral Health Clinics) with transactions in FY2025 (October 1, 2024 to September 30, 2025). Method: Grantsights pulled every grant award (types 02 to 05) under that listing from the USAspending award search API, then checked each award's federal subaward reporting.

What the award records showCountShare
Awards with FY2025 activity475100%
Awards with total obligations of exactly $4,000,00025654%
Awards reporting at least 1 subaward173.6%

The $4,000,000 cluster matches the structure in SAMHSA's FY2026 CCBHC-PDI notice: up to $1,000,000 a year for up to 4 years. One organization in Montana, AWARE Inc., received award H79SM089470 for $4,000,000 to run a CCBHC planning, development, and implementation project from September 30, 2023, to September 29, 2027. Most grantees report no subawards at all. Federal reporting under 2 CFR Part 170 only covers subawards of $30,000 or more, so smaller ones won't appear, but the pattern still suggests most CCBHC grantees deliver services through their own staff and partner agreements rather than passing federal money through. When a grantee does use subawards, the plan has to cover them: Casa Esperanza Inc. in Massachusetts (award H79SM086841, $4,000,000) reports 5 subawards totaling $721,763, and every one of those triggers the pass-through duties in 2 CFR 200.332. The practical rule: decide early whether a partner is a subrecipient or a contractor, because that choice decides how much monitoring your management plan has to describe. The subrecipient monitoring guide walks through the 200.332 steps.

Common Mistakes That Cost Points

Common management plan errors:

1. Copy-pasting from a previous application. Reviewers notice when your management plan references a different grant program, a different timeline, or staff who left three years ago. Tailor every management plan to the specific NOFO.

2. Describing the program, not the management. The management plan isn't a second program narrative. It's about systems and processes, not services and outcomes. If you're describing what you'll do for participants, you're in the wrong section.

3. Ignoring the scoring rubric. If the NOFO says the management plan is worth 15 points and lists five criteria, address all five criteria explicitly. Use headers that mirror the NOFO language so reviewers can easily find your response to each criterion.

4. Understaffing the project. A $500,000 grant with one full-time staff person and no administrative support signals that you haven't thought through the actual work involved. Be realistic about the effort required.

5. No contingency planning. What happens if your PI goes on medical leave? What if a partner organization drops out? What if enrollment is slower than projected? Reviewers want to see that you've considered the "what ifs" and have a plan.

6. Generic quality assurance. "We will monitor program quality on an ongoing basis" is meaningless. Name the specific activities, the frequency, the responsible person, and the benchmarks.

A Section-by-Section Template

Here's a structure you can adapt for most federal grant management plans:

Section 1: Organizational Capacity (0.5 to 1 page)

  • Relevant organizational history and mission
  • Similar grants successfully managed (name funder, amount, outcomes)
  • Infrastructure relevant to this project
  • Compliance and audit history

Section 2: Staffing and Organizational Structure (1 to 1.5 pages)

  • Staffing table with positions, FTE, qualifications, responsibilities
  • Organizational chart
  • Recruitment plan for vacant positions
  • Succession and turnover contingency plan

Section 3: Financial Management (0.5 to 1 page)

  • Accounting system and internal controls
  • Budget monitoring and reconciliation process
  • Procurement procedures for equipment over $10,000
  • Indirect cost rate (negotiated rate or 15% de minimis)
  • Audit history and compliance procedures

Section 4: Data Collection and Management (0.5 to 1 page)

  • Data elements tied to objectives
  • Collection instruments and schedule
  • Data management system
  • Data quality assurance procedures
  • Connection to reporting requirements

Section 5: Quality Assurance (0.5 to 1 page)

  • Quality benchmarks and standards
  • Monitoring methods and frequency
  • Corrective action process
  • CQI meeting structure

Section 6: Communication and Governance (0.5 page)

  • Internal communication schedule (staff meetings, supervision)
  • External communication (funder, partners, community)
  • Advisory board composition and role

Section 7: Timeline and Milestones (0.5 to 1 page)

  • Quarterly milestone table or Gantt chart
  • Key decision points and reporting deadlines

The Staffing Plan Inconsistency That Kills Otherwise Strong Applications

The most common management plan failure isn't vague language or missing sections. It's a staffing plan that doesn't match the budget. Reviewers catch it every time, and it costs points even when the program narrative is excellent.

Here's a hypothetical pattern: an applicant proposes a $500,000 behavioral health grant to serve 200 participants over 24 months. The management plan describes a project director at 1.0 FTE, a case manager at 1.0 FTE, and a data coordinator at 0.5 FTE. The budget shows the project director at 0.75 FTE. The case manager salary is budgeted at a rate $12,000 below the market wage in that metro area. The data coordinator is listed as "to be hired" with no recruitment timeline. In a case like this, reviewers can mark the section down heavily because the staffing plan describes a project that can't be delivered with the staff the budget actually funds. A staffing inconsistency like this can drop the management section score low enough that the total falls below the funding threshold.

Applicants also often understaff administrative functions. Program staff are easy to budget because the work is visible. But someone still has to handle drawdowns and financial reports, someone has to own the data, and many projects need a quality assurance lead. Many NOFOs also set key personnel rules. SAMHSA's FY2026 CCBHC-PDI notice, for instance, requires the Project Director to have decision-making authority for the project and sets a 50 percent minimum effort for both the Project Director and the Project Evaluator. If you don't read those sections and your proposed staff don't meet the stated qualifications, you're flagged before the reviewer even reads your management approach. As a hypothetical, an application might propose "clinical supervision by a licensed professional" without naming the licensure type when the notice requires a specific license. That kind of gap can cost points or, if the rule is an eligibility requirement, sink the application.

Subrecipient monitoring also belongs in the plan. Under 2 CFR 200.332, if you're passing funds to any partner organization through a subaward, your management plan needs to describe how you'll assess subrecipient risk, conduct site visits or desk reviews, and document findings. Even experienced organizations sometimes describe partnership activities in detail but don't mention subrecipient monitoring at all, treating it as a post-award administrative detail. Subrecipient monitoring is a federal requirement, so describing it at the application stage shows you've planned for it.

One practical change: treat the management plan as a mirror of the budget justification, not as a separate section. Write them together. Every position in the staffing plan gets a corresponding line in the budget. Every data collection tool mentioned in the management plan has a budget line for the license or subscription cost. Every partner meeting described in the communication plan has a travel budget line. Reviewers who see that level of internal consistency read it as evidence of real planning, not just template completion. That's the difference between an 8-out-of-10 management score and a 10-out-of-10.

What Federal Grant Handbooks Don't Tell You About Management Plans

The 2 CFR 200 sections cited here run to thousands of words, and none of them tell you how to turn those rules into a 3-page plan a reviewer will score well. That's the gap. The management plan is where reviewers assess whether you can actually do what you proposed. A management plan that reads like an organizational chart with titles and lines won't score well. Reviewers want to see who does what, when, with what authority, and what happens when something goes wrong. Include decision-making processes, escalation paths, and contingency plans for key staff turnover.

Data security belongs in the plan too. 2 CFR 200.303(e) requires recipients to take reasonable cybersecurity and other measures to protect personally identifiable information and anything the agency marks as sensitive. If your project collects participant records, say who has access and how it's controlled. A management plan that handles programmatic oversight but ignores fiscal controls or data protection signals that your organization treats compliance as an afterthought.

The project timeline in your management plan should include administrative milestones, not just programmatic ones. IRB approval, subcontract execution, hiring timelines, procurement of equipment, and first report submission dates all belong in the management plan. A startup period is normal; an unexplained one isn't. A red flag for reviewers is a timeline that shows services starting in month one and then quietly slips because hiring and contracts weren't planned.

Finally, the plan only matters if the program is a good fit in the first place. Before you write one, check which grants match your organization before you apply, so the management work goes into an application you can win. If the notice's staffing minimums or data rules are a bad fit for your current team, that's a reason to skip the round or build capacity first.


Sources

Frequently Asked Questions

How long should a grant management plan be?

Most federal grant management plans run 3 to 5 pages, though the required length depends on the funder's page limits and how many components they ask you to address. SAMHSA's FY2026 CCBHC-PDI notice (SM-26-014), for example, suggests about 3 pages for organizational experience and staffing and about 2 pages for data collection, inside a 15-page narrative. If the funder doesn't give a page limit for the management plan specifically, aim for 10 to 15 percent of your total narrative. Reviewers want enough detail to confirm you've thought through implementation, but they don't want filler. Every sentence should answer a specific operational question: who does what, when, how, and what happens if something goes wrong.

What's the difference between a management plan and a work plan?

A work plan lists the specific activities, responsible staff, and deadlines for completing project objectives. A management plan is broader. It describes the organizational systems and processes you'll use to oversee the entire grant, including financial management, quality assurance, communication protocols, and risk mitigation. Think of the work plan as the 'what' and the management plan as the 'how.' Many funders ask for both, and some combine them into a single section. If the NOFO uses the term 'project management plan,' it usually means they want elements of both.

Do all federal grants require a management plan?

Not all federal grants use the term 'management plan,' but virtually every competitive federal grant asks you to demonstrate organizational capacity and describe how you'll manage the project. NIH research grants cover it through the Facilities and Other Resources attachment, key personnel, and the budget justification; under NIH's simplified review framework, reviewers rate investigator expertise and environment only as sufficient or not. Department of Education competitions often use the 'Quality of the management plan' criterion in 34 CFR 75.210(g), and SAMHSA notices score organizational experience, staffing, and data collection as separate lettered sections. Even when a funder doesn't require a standalone management plan, describing your management approach somewhere in the narrative strengthens your application.

Should the management plan include the budget?

The management plan should connect to the budget but doesn't replace it. Reference specific budget line items when you describe staffing levels, data collection tools, or contracted services. For example, if your management plan describes a half-time project coordinator, the budget should show that position at 50 percent FTE with the correct salary and fringe. Reviewers check for consistency between the two sections. If your management plan promises weekly data collection but your budget doesn't include the software license or staff time to do it, that's a red flag.

How do you write a management plan for a collaborative grant with multiple organizations?

Collaborative grants need a management plan that clarifies governance, decision-making authority, and communication across all partner organizations. Include an organizational chart showing reporting relationships, name a lead fiscal agent, describe how subawards or subcontracts will be managed, and explain how you'll handle disagreements between partners. Specify who attends which meetings, who has final authority on budget modifications, and how you'll ensure consistent data collection across sites. For every subaward, regardless of size, you'll also need to describe your subrecipient risk assessment and monitoring procedures per 2 CFR 200.332.

Last updated October 17, 2026. Corrected October 17, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.