FY 2026 SNAP Process and Technology Improvement Grants (PTIG)

FY 2026 SNAP Process and Technology Improvement Grants (PTIG)

The Food and Nutrition Service (FNS) posted the FY 2026 Process and Technology Improvement Grants (PTIG) opportunity to support operational upgrades to SNAP certification, application, and eligibility systems. This is not a general-purpose digital transformation voucher. It is a competitive federal grant with a tight due date and strict administrative controls. The competition is open to a broad set of public and nonprofit entities, but the rules are specific enough that many technically strong applicants fail on compliance basics.

This guide is built from the FY 2026 PTIG listing and RFA text. Dates and requirements can change on update, but as of 2026-05-31 15:05:34Z the publication reflected a June 29, 2026 due date and the funding profile below.

Key details at a glance

Why this is genuinely useful for teams working on digital public-services programs

If your team is already operating in public-assistance workflows, this opportunity is useful because it funds exactly the infrastructure and process friction points that slow families, caseworkers, and program integrity teams.

In practical terms, PTIG funds can support:

• automation where appropriate,
• case processing efficiency improvements,
• verification process redesign,
• cross-program integration between SNAP and local support systems,
• and modernized citizen-facing communication and service journeys.

It is not a general technology modernization grant where any software project qualifies. The language in the solicitation is explicit: the proposal must address SNAP certification and eligibility functions and align with one or more of the three fiscal-year objectives. If your proposal reads like a broad civic-tech project with no SNAP operational anchor, your application is at high risk of being removed early.

Because the solicitation includes post-award reporting obligations and explicit compliance gates, successful teams usually come from organizations that already have grants management discipline, not from first-time digital startups trying this style of federal competition alone.

What FY 2026 PTIG is and is not funding

The solicitation describes PTIG funds as support for improving how SNAP is delivered, not for creating a generic tech stack for unrelated programs. The funding is also bounded by legal eligibility and fiscal controls.

The grants are designed around these three operational themes:

1. Customer and applicant experience modernization

   • improve how households interact with application and eligibility systems,
   • increase transparency and communication quality,
   • make status and case-management flows easier to understand.

2. Administrative and process modernization

   • reduce delays,
   • improve data handling quality,
   • increase operational consistency in eligibility operations.

3. Inter-program process coordination

   • integrate SNAP systems with related benefit and assistance workflows,
   • support better verification and case integrity,
   • reduce redundant effort across agencies.

The funding is for new projects. That is important. Proposals must not be a wrapper around routine operational costs that were already underway. The budget needs to reflect incremental activity with clear new outcomes in the SNAP context.

What the grant explicitly excludes

The solicitation and application guidance also make exclusion lines clear:

• No pre-award costs cannot be charged or recovered.
• Pre-existing operational maintenance is not the primary target unless the activity is clearly part of a new PTIG project.
• Outreach-only activities have limits and pure application help efforts cannot consume funds.
• No more than 25% of requested grant funds can go to SNAP outreach.
• Borrowed budget categories must reflect SNAP-only share when project benefits multiple programs.

This is a serious funding opportunity for program modernization, not a broad capacity-building grant with flexible spend.

Eligibility: who should apply and who should pass this one

PTIG is structured to prioritize eligible SNAP-related entities and organizations that can demonstrate implementation capacity.

Eligible entity types

The following can be eligible leads (subject to full submission requirements):

• one of the 53 State SNAP agencies,
• state or local governments,
• public or private health/welfare organizations,
• public health or educational entities,
• Indian Tribal Organizations,
• private nonprofits with relevant service alignment (including food banks and community/faith-based organizations).

For non-State applicants that are not applying directly as a State agency, a letter of commitment or State endorsement is required. The rules are enforced at package level, and letters must be included in the submitted package.

Practical filters that remove applicants quickly

Even if your mission is a good fit, one of these filters can remove your proposal:

• Missing required State letter for non-state lead applicants.
• Ineligible lead entity due to FY 2024 or FY 2025 PTIG award status.
• Late application (even by seconds).
• Failure to address requirements in all required sections and attachments.
• Incomplete letters for partner commitments when partnering.

The ineligibility statement is straightforward and strict. Read it as: eligibility is a hard gate, and the gate is checked before scoring in many cases.

Application flow: what to submit and when

The opportunity is hosted via Simpler.grants for listing and documents, but the actual submission is via Grants.gov. The key deadline date is June 29, 2026 at 11:59 PM EDT.

Required preconditions (minimum)

Before you draft the narrative, make sure this list is done:

1. UEI registration.
2. SAM.gov registration maintained and valid.
3. Grants.gov registration and roles configured.
4. Internal signature and role approvals aligned.
5. If not a State lead, draft both partnership letter and State endorsement language.

Treat this as your submission readiness checklist. Missing one here can derail the rest of your work.

Core submission package components

From the solicitation and checklist, the core materials include:

• SF-424,
• SF-424A,
• SF-424B,
• FNS-906 (financial capability if needed),
• mandatory narrative sections,
• budget narrative (with spreadsheet alignment),
• Activities/Indicators tracker,
• required letters.

Applicants should map each budget figure across SF-424 and SF-424A before upload, because discrepancies are treated as evaluation risks.

Timing strategy for a June 29 deadline

A realistic internal planning rhythm:

• Now through early May: eligibility and governance confirmation, no narrative writing before the decision tree is clear.
• Mid-May to early June: draft the full narrative around the three objective areas and tie each activity to a measurable output.
• Early June: budget narrative pass, all forms, signatures, letter review.
• By the final week of June: final compliance audit + dry run submission path in Grants.gov.

This is not a “submit right before deadline” workflow. Grants.gov transmission errors, portal issues, and file packaging mistakes are common near the deadline.

How applications are evaluated

The review criteria are competitive and numerically explicit:

• Project design: 35 points
• Impact and evaluation: 30 points
• Budget and economic efficiency: 20 points
• Organizational experience, staff capability, management: 15 points
• Bonus points: up to 9 points

This is a meaningful spread. It rewards coherent project design and execution plans, not only technical ambition.

What reviewers look for in project design

Your proposal should be built as a problem-to-outcome chain:

1. identify the SNAP process pain point,
2. describe the proposed intervention,
3. show why it works in the applicant’s operational context,
4. show alignment with State SNAP modernization priorities,
5. show a realistic timeline.

Good proposals often spend more effort on this chain than on abstract narrative. The score is not about complexity for its own sake. It is about demonstrated impact in a constrained public service environment.

Impact and evaluation quality matters as much as architecture

The evaluation section expects measurable impact:

• timeliness improvements,
• reduced processing friction,
• improved accuracy/quality in determinations,
• better program integrity outcomes,
• documented evidence plan with indicators.

Projects that cannot explain how they will measure success against these dimensions often fail even with polished technical plans. A good PTIG proposal should be evidence-first: build measurable claims, define indicators, and show how the proposal changes baseline operations.

Budget and economic efficiency

The budget is not a filing exercise. Reviewers expect alignment between request and activities:

• whole-dollar requests,
• clear line items,
• realistic staffing assumptions,
• explicit handling of shared-program activities,
• evidence of not funding routine overhead-only work.

Because the grant total is only $5 million and awards are only 12, budget clarity has a direct influence on perceived feasibility. If your budget appears inflated, disconnected, or inconsistent across forms, reviewers infer weak management capacity.

Bonus-point areas

Bonus points are limited but useful when your main sections are already strong. They are intended for projects that can clearly demonstrate additional technical or programmatic value tied to the solicitation objectives. In PTIG language, this usually means stronger innovation framing and clear modernization outcomes that are harder to replicate by incremental upgrades.

Budget restrictions and compliance details that change strategy

The PTIG RFA has rules that affect technical architecture choices. These details directly shape project design:

• Budget requests are between $20,000 and $2,000,000 per applicant.
• Equipment over $10,000 or with multi-year life usually needs prior approval and justification.
• Pre-award costs are not allowed.
• If project costs tied to larger systems exceed threshold limits, an APD may be required.
• No more than 25% of grant funds for SNAP outreach.
• Cost-sharing is not required, but post-award sustainability still must be explained.

Also note the explicit restriction for larger, multi-entity projects: if costs benefit multiple programs, you must allocate costs so that SNAP only pays SNAP’s share.

This is a frequent pitfall for agencies that run shared systems. If you submit a unified workstream that also supports education, welfare, or local service functions, the entire budget must still pass this SNAP-only audit logic.

Governance and compliance after award

Even if selected, the work continues under close reporting.

Core reporting architecture

Grantees are expected to submit progress via FNS forms on a quarterly cadence and provide a final report after period end. The period of performance spans three years in this solicitation (September 2026 to September 2029), which means governance planning is long-horizon, not a one-year pilot.

Common post-award burdens

• Quarterly SF-425-like financial reporting sequence through FNS systems.
• 30-day progress cadence after quarter end.
• Final report with results, lessons learned, and outcome evidence.
• Alignment of reported activities with declared objectives.

Teams planning this as a short pilot often fail when reporting architecture is not built into the proposal.

Common mistakes and how to avoid them

Mistake 1: treating this as a general digital transformation grant

PTIG is tightly tied to SNAP process and eligibility functions. A proposal that is too broad tends to be scored weak in pre-screening or the first review pass. Anchor everything in SNAP outcomes.

Mistake 2: using the wrong letters or wrong letter routing

Letters of commitment and endorsement must be submitted through the Grants.gov application package. Submitting separately or via email does not satisfy submission instructions. This is a frequent source of nonresponsive status.

Mistake 3: forgetting ineligibility carryover from prior fiscal years

Lead entities that received FY 2024 or FY 2025 PTIG funding are disqualified from FY 2026 leadership. This rule changes the feasibility of coalition structures, especially where organizations are used to rotating leads every year.

Mistake 4: underinvesting in partnership cost allocation

If you are proposing partner entities and shared execution, your cost allocation must be explicit. Reviewers and post-award teams expect clear attribution of roles, costs, and FTE commitments.

Mistake 5: packaging budget figures inconsistently

All financial forms must agree on funding request totals and categories. If the SF-424 total differs from SF-424A or the budget narrative, the proposal can be penalized, and in some cases disallowed.

Mistake 6: weak post-award planning

Even a compelling concept can fail if implementation continuity is weak. The solicitation expects a timeline, sustainability approach after grant period, and a realistic risk posture for integration into existing agency operations.

FAQ for first-time federal PTIG applicants

1) Is this grant only for State agencies?

No. It is broader, but non-State applicants must include required commitment or endorsement mechanisms from State SNAP agencies.

2) Can a nonprofit lead without a State partnership?

No. A direct relationship to State SNAP leadership is required in the way the filing documents define for non-state entities.

3) Is matching or cost sharing required?

No matching is required for this solicitation.

4) Are existing projects eligible for enhancement?

Yes, but only if new activities and outcomes are clearly defined. Continuing an existing maintenance project without new implementation is generally not acceptable.

5) Can applicants self-assess AI use in drafting?

The solicitation asks for disclosure where AI is used. If AI-assisted drafting is used, that involvement should be acknowledged and explained.

6) Is the grant available to foreign applicants?

The opportunity is structured for U.S. entities connected to SNAP-related administration and is not designed as an international grant channel.

Strategic positioning guidance: who this is best for

The best PTIG applicants are usually:

• State SNAP agencies ready to modernize workflows.
• Local governments coordinating public assistance data and operations.
• Nonprofits that work with SNAP administration and can show durable execution capacity.
• Delivery partners that can provide technical depth and compliance support while staying secondary to the lead entity.

A weak PTIG application is often a strong idea with weak federal format. A strong PTIG application is usually a good idea plus disciplined structure:

• clear problem statement,
• measurable outcomes,
• explicit workload and staffing,
• clean budget logic,
• partner letters compliant with format and timing,
• and post-award reporting realism.

Official links

• Official opportunity page: https://simpler.grants.gov/opportunity/e1bc457a-bf73-4070-b141-bc5421c9eb9a
• FY 2026 PTIG RFA PDF: https://files.simpler.grants.gov/competitions/f0f0d7e4-b080-4a00-a6ea-eba9a436a637/instructions/d347ca8d-fe0a-4ba6-bbd9-41265f8e1b37/PKG00292865.pdf

If you are applying, open and read the full solicitation sections on your final preparation checklist day—especially application content and score criteria sections. Use this page as a planning model, then align your package line by line to the official form requirements.