SNAP-Ed Application & State Plan Guide

The SNAP-Ed State Plan Process

Unlike competitive federal grants where individual organizations submit applications through Grants.gov, SNAP-Ed operates through a state plan model. Each state SNAP agency submits a single comprehensive SNAP-Ed plan to its FNS regional office for approval. This plan covers all SNAP-Ed activities that will occur in the state during the federal fiscal year (October 1 through September 30), including activities conducted by every implementing agency in the state.

The state plan is the controlling document for all SNAP-Ed activities within the state. If an activity is not described in the approved state plan, it cannot be funded with SNAP-Ed dollars. This means that implementing agencies must work closely with their state SNAP agency to ensure their programming is accurately reflected in the state plan before the fiscal year begins.

Annual Timeline

The SNAP-Ed plan cycle follows a predictable annual rhythm tied to the federal fiscal year. While specific dates vary by FNS region and state, the general timeline is:

This timeline means implementing agencies typically need to begin preparing their proposals 6 to 9 months before the programming year starts. Agencies new to SNAP-Ed should engage with their state SNAP agency well in advance to understand the state's specific submission requirements and deadlines.

The SNAP-Ed Guidance Document

FNS publishes the SNAP-Ed Guidance document annually, and it is the authoritative federal policy reference for all SNAP-Ed activities. The Guidance specifies what must be included in state plans, defines allowable and prohibited activities, establishes target population criteria, details reporting requirements, and sets fiscal policies. State plans must align with the current year's SNAP-Ed Guidance, and implementing agencies are expected to be familiar with its requirements.

Key sections of the SNAP-Ed Guidance that directly affect plan development include:

• Needs assessment requirements: How states and implementing agencies must document the nutrition education needs of SNAP-eligible populations
• Evidence-based programming: Requirements for using SNAP-Ed Toolkit interventions or documenting equivalent evidence standards
• Evaluation expectations: How implementing agencies should plan for outcome measurement and program evaluation
• Coordination requirements: Mandatory coordination with EFNEP and other nutrition education programs to avoid duplication

Becoming an Implementing Agency

The process for becoming a SNAP-Ed implementing agency varies by state, but generally follows one of two models:

Competitive RFP Process

Many states use a competitive Request for Proposals (RFP) or Request for Applications (RFA) process to select implementing agencies. The state SNAP agency publishes an RFP that specifies the programming priorities, geographic areas of need, eligible activities, budget parameters, and evaluation requirements. Organizations respond with proposals describing their qualifications, proposed programming, target populations and sites, staffing plans, and budgets. The state reviews and scores proposals, selects implementing agencies, and negotiates contracts or subgrant agreements.

RFP cycles may occur annually or on a multi-year basis (typically 3 to 5 years) with annual renewals contingent on performance. New agencies may be able to enter the system between full RFP cycles if the state identifies unmet needs in specific geographic areas or populations.

Direct State Agency Selection

Some states use a direct selection model, particularly for established implementing agencies such as the state's cooperative extension service or the state public health department. In these cases, the state SNAP agency may negotiate directly with the implementing agency without a competitive RFP. This model is common in states where a single land-grant university extension service delivers the majority of SNAP-Ed programming statewide.

State Plan Components

Whether you are responding to a state RFP or developing your portion of the state plan through direct negotiation, the following components are typically required. Understanding these components helps implementing agencies prepare stronger proposals and ensure their programming aligns with state and federal requirements.

Needs Assessment

Every state SNAP-Ed plan must include a needs assessment that identifies the nutrition education and obesity prevention needs of SNAP-eligible populations in the state. Implementing agencies typically contribute to this assessment by providing data and analysis specific to their service areas. A strong needs assessment includes:

• SNAP participation data: Number of SNAP participants in the service area, demographic breakdown, trends over time
• Health and nutrition data: Obesity prevalence, diet quality indicators, food insecurity rates, chronic disease rates linked to nutrition (diabetes, hypertension, cardiovascular disease)
• Food environment analysis: Healthy food access indicators, food desert mapping, SNAP-authorized retailer density, farmers market availability
• Gap analysis: Identification of populations and geographic areas with unmet nutrition education needs, considering existing SNAP-Ed, EFNEP, and other nutrition education resources
• Community input: Qualitative data from community stakeholders, partner organizations, and target population representatives about perceived nutrition education needs

Program Design

The program design section describes the specific interventions, delivery methods, target populations, and sites that the implementing agency will use to address the identified needs. A strong program design connects directly to the needs assessment and includes:

• Intervention selection: Specific SNAP-Ed Toolkit curricula and PSE change strategies to be used, with justification for why each intervention addresses identified needs
• Delivery plan: Number of education series planned, session frequency and duration, anticipated reach (number of participants), and delivery modality (in-person, virtual, hybrid)
• Site list: Specific schools, community sites, and other locations where programming will be delivered, with eligibility documentation for each site
• PSE change objectives: Specific policy, systems, or environmental changes the implementing agency will work toward, with measurable indicators of progress
• Staffing plan: Number and qualifications of nutrition educators, supervisors, and support staff, including training plans for curriculum fidelity

Evaluation Plan

FNS expects implementing agencies to evaluate the effectiveness of their programming and contribute to the national SNAP-Ed evidence base. The evaluation plan should describe:

• Outcome indicators aligned with the SNAP-Ed Evaluation Framework priority areas (dietary quality, physical activity, food resource management, food safety, food security)
• Data collection methods and instruments (pre/post surveys, behavioral checklists, observation protocols for PSE changes)
• Process evaluation methods to assess delivery quality, fidelity to curricula, and participant satisfaction
• How evaluation findings will be used to improve programming in subsequent years

For detailed information on evaluation indicators and EARS reporting, see the Reporting & EARS Guide.

EFNEP Coordination Plan

FNS requires that every state SNAP-Ed plan include a description of how SNAP-Ed and EFNEP activities will be coordinated to avoid duplication. At the implementing agency level, this is particularly important for universities and extension services that administer both programs. The coordination plan should address:

• Geographic delineation of service areas to minimize overlap
• Differentiation of target populations and recruitment strategies
• Shared referral systems between SNAP-Ed and EFNEP staff
• Clear cost allocation procedures to ensure no costs are double-charged
• Regular communication protocols between SNAP-Ed and EFNEP program staff

Budget Development

Implementing agencies must submit detailed budgets as part of their plan submissions. Because SNAP-Ed is 100% federally funded with no match requirement, the budget must accurately reflect all costs that will be charged to SNAP-Ed. Budget development for SNAP-Ed follows 2 CFR 200 cost principles, and all costs must be necessary, reasonable, allocable, and adequately documented. See the Budget & Financial Management section for comprehensive budget guidance.

Writing a Strong Implementing Agency Proposal

Whether responding to a state RFP or developing your plan section through direct negotiation, the following practices strengthen your proposal:

• Lead with data: Ground every program element in specific needs assessment data. States and FNS want to see that programming decisions are driven by documented need, not organizational preference or historical practice.
• Select high-tier interventions: Choosing Tier 1 and Tier 2 interventions from the SNAP-Ed Toolkit demonstrates commitment to evidence-based practice and reduces compliance risk.
• Balance direct education and PSE: FNS has increasingly emphasized PSE change. Proposals that incorporate both direct education and complementary PSE strategies demonstrate a comprehensive approach to nutrition improvement.
• Document site eligibility upfront: Include specific data for each proposed delivery site showing that it meets the low-income population threshold.
• Plan for realistic reach: Overestimating participant reach is a common mistake. Base your projections on actual organizational capacity, site availability, and historical delivery data.
• Address EFNEP coordination explicitly: If your organization or service area overlaps with EFNEP, describe your coordination plan in detail.

Plan Amendments

The approved state SNAP-Ed plan is a living document, but changes require formal amendment approval. Implementing agencies cannot unilaterally modify their programming, sites, budgets, or staffing from what was described in the approved plan without going through the amendment process.

When Amendments Are Required

Plan amendments are typically required when:

• Adding new implementing agencies or removing existing ones from the plan
• Changing curricula or interventions from those described in the approved plan
• Significant budget reallocations between line items or implementing agencies
• Adding new geographic service areas not covered in the original plan
• Substantial changes to evaluation methodology or outcome indicators

Amendment Process

The amendment process typically involves three steps:

• Implementing agency notification: The implementing agency identifies the need for a change and submits a written request to the state SNAP agency with justification and revised plan details
• State agency review: The state SNAP agency evaluates the proposed change for compliance with SNAP-Ed Guidance requirements and determines whether FNS approval is needed
• FNS approval: For significant amendments, the state submits a formal plan amendment to the FNS regional office. The implementing agency should not implement changes until the amendment is approved.

Implementing changes before amendment approval is a compliance risk. If FNS or the state does not approve the amendment, costs incurred under the unapproved activities may be disallowed. Plan ahead to avoid last-minute amendment requests that cannot be processed before the programming change must occur.

Common Application Pitfalls

Based on common findings from state reviews and FNS management evaluations, these are the most frequent issues in SNAP-Ed plan submissions:

• Weak needs assessment: Generic statements about nutrition needs without specific data for the proposed service area. Use local SNAP data, BRFSS indicators, and food environment metrics to make the case.
• Non-Toolkit curricula: Proposing curricula that are not in the SNAP-Ed Toolkit without adequate evidence documentation. Always check the Toolkit first and provide evidence equivalence documentation if using alternative curricula.
• Missing EFNEP coordination: Failing to address EFNEP coordination, especially when the implementing agency or service area overlaps with EFNEP activities.
• Unrealistic reach projections: Overestimating participant numbers without grounding projections in organizational capacity and historical delivery data.
• Vague PSE strategies: Describing PSE change goals in general terms without specific, measurable objectives and a clear implementation timeline.

For more detailed coverage of compliance pitfalls, see the Common Mistakes & How to Avoid Them section.