FY 2027 Multistate Conservation Grant Program (F27AS00009)

FY 2027 Multistate Conservation Grant Program (F27AS00009)

The FY 2027 Multistate Conservation Grant Program (F27AS00009) is a federal conservation funding line managed by the U.S. Fish and Wildlife Service (FWS) with AFWA partnership. It is intended for projects that are regional in scale, involve cross-jurisdiction coordination, and address conservation needs that are too large for one state or institution to handle alone.

Unlike many programmatic grants where scoring mostly measures scientific quality alone, this opportunity is built around regional benefit and strategic fit. The published notice of funding opportunity is explicit that the program is for work tied to one of the 2027 AFWA Strategic Priorities, focused on wildlife restoration, sport fish restoration, habitat or management needs, and related recruitment/retention public benefit efforts (R3). In practical terms, this is a “big picture” resource grant: it supports groups of partner organizations that can show why one state or one campus cannot reasonably carry this work alone.

As of the source dates available to this article, the first-step submission deadline is July 14, 2026 at 11:59 PM ET. That makes this one of the most relevant opportunities in the current cycle, because it is still usable within 2026 planning windows and feeds into a second-stage full application process in September if your concept is selected.

Key details

What the program is actually funding

The NOFO defines this as a multistate conservation mechanism, not a laboratory-only or narrowly disciplinary research grant. Its core purpose is to fund efforts that respond to “needs beyond the scale, scope, and capabilities of a single State.”

The activity areas listed in the official text include:

• wildlife restoration,
• sport fish restoration,
• habitat management,
• conservation and management,
• habitat and resource improvement,
• eligible R3 activities tied to recruitment, retention, and reactivation in hunting, target shooting, and angling.

It is important that this is interpreted as a collaborative instrument. The program rewards consortium logic because the AFWA/FWS process explicitly includes technical review and priority-list ranking across states and associations, then final selection through additional FWS review layers.

What this means for applicants:

• a well-structured single-state proposal that does not create regional spillover is a weak fit;
• a proposal that can demonstrate cross-jurisdiction outcomes and coordinated implementation is much stronger;
• the project logic should connect clearly to 2027 AFWA Strategic Priorities.

Who should apply and who should not

The list of eligible applicants in the official record includes:

• state governments,
• public and state-controlled institutions of higher education,
• private institutions of higher education,
• nonprofits (with and without 501(c)(3) status, excluding most higher-education nonprofits in that category),
• additional applicants described in additional eligibility notes.

This is broad on paper, but “broad” should not be confused with “easy.” In practice, the program is built for entities that can coordinate at scale. A small nonprofit with no state or regional role would not automatically be competitive unless it is attached to a stronger implementing structure.

Also note:

• non-U.S. jurisdictions are not eligible;
• U.S. territories and states are eligible only as defined in the NOFO and counted for benefit calculations;
• projects must address at least one of the 2027 AFWA Strategic Priorities;
• the benefit area must meet the regional threshold (26+ states or majority of defined regional groupings).

Because regional benefit thresholds are explicit, teams that cannot prove “why this is multi-state, and why this scale is necessary” often fail even with solid ecological content. Build your justification on scale logic first, technical details second.

Deadline structure and the two-stage submission model

This opportunity has a staged process that is easy to miss if you only read headlines.

1. Stage 1: Grant Proposal package by July 14, 2026 (11:59 PM ET)

   Applicants submit a Grant Proposal without federal forms through the AFWA MSCGP portal.

   Confirmed required components include:

   • Project Narrative
   • Budget Narrative
   • Budget Table
   • No federal forms in this stage (as stated by the NOFO).

2. Stage 2: Complete application invitation

   If the stage-1 proposal is selected for further consideration, the team is invited via email in late September 2026 to submit a complete Grant Application through a directed announcement in GrantSolutions.gov.

   At that point, the package becomes fuller and includes:

   • Project Narrative
   • Budget Narrative
   • Budget Table
   • Required Statements
   • Negotiated Indirect Cost Rate Agreement (if applicable)
   • Federal forms.

3. Important administrative detail

   The NOFO states clearly that complete Grant Applications should not be submitted in Grants.gov for this NOFO.

The immediate implication is that a team can move toward a quality stage-1 packet without waiting for all federal reporting infrastructure, but must preserve strict continuity so the second-stage transition is not a rebuild exercise.

Registrations and system prep you must complete early

The submission system requirement is technical and can become the primary bottleneck if started late. The official materials require:

• UEI and SAM.gov registration for almost all non-individual applicants;
• registration completion before submission; SAM.gov Financial Assistance General Representations and Certifications checked and current;
• GrantSolutions registration and user role setup.

At minimum, the GrantSolutions process requires:

• a new-organization request with required metadata,
• ADO and PI/PD role assignment,
• Login.gov account setup for GrantSolutions users,
• role management and approval structure aligned to your administration path.

In practical terms, applicants that treat this as a writing task often stall here and lose time. Treat registrations as a pre-submission deliverable, not a back-end administrative chore.

Practical pre-check sequence (recommended)

• Confirm your jurisdiction and entity eligibility, including whether your group naturally contributes to multistate benefit metrics.
• Reserve a timeline: registration done at least 4–6 weeks before July 14.
• Build a document tree before writing:
  • draft narrative,
  • budget with clear line-item logic,
  • partner agreements,
  • cost-share explanation (if applicable even though not required).
• Establish state/territory benefit matrix with clear evidence per requirement:
  • name the regions,
  • map state coverage,
  • show how benefits are distributed.

Review logic: what reviewers are likely to prioritize

The program’s review framework includes eligibility checks, merit review, and a national-level review chain. The published material describes a two-step technical/recommendation flow where AFWA priority process supports project ranking before FWS-level decisions.

You should therefore write in a way that satisfies both technical and governance reviewers:

• Eligibility reviewers need to see clear applicant legitimacy and jurisdictional fit; if they cannot verify threshold eligibility quickly, the packet can be removed from deeper scoring.
• Merit reviewers need measurable logic tied directly to strategic priorities and regional necessity.
• FWS/portfolio reviewers need confidence that the project is administratively executable, with realistic budgeting and partner responsibilities.

A conservative, strong proposal shape is:

• start every section with a regional problem statement,
• map each activity to a defined priority,
• assign each activity to a lead entity and partner,
• show benefit across required state count conditions,
• include monitoring metrics at the start of the narrative.

Money and budget expectations

The published summary lists:

• total funding: $11,000,000,
• 45 expected awards,
• award ceiling up to $1,000,000,
• cost sharing not required.

The page also separates estimated allocations between the two track types:

• Traditional Multistate Conservation Grants: $6,000,000 with per-application request ceiling $625,000.
• R3 Multistate Conservation Grants: $5,000,000 with per-application request ceiling $1,000,000.

This matters for budget strategy:

• if your project is purely Traditional conservation outcomes, budget and timeline should align with the corresponding ceiling,
• if R3-related objectives are central, you can model within the higher T-MSCG and R3-MSCG allowance structure as applicable.

No match is required, which is unusual relative to many conservation lines and lowers one common barrier. However, it does not remove the need for transparent financial logic. A weakly justified budget still loses against clear, well-explained cost realism.

A strong budget section should include:

• per-activity cost breakdown,
• shared costs across participating entities,
• in-kind or contribution assumptions clearly labeled,
• administrative overhead not overrun.

Avoid “full generic budgets” that appear copied across states or partnerships. The review committee expects the budget narrative to be tied to the regional implementation design.

Project design guidance for this specific NOFO

Because this is a multistate mechanism, applicants often underperform by writing like a local plan. A more competitive submission should be designed around three technical pillars.

Pillar 1: Strategic-priority alignment

Start with the applicable AFWA priority(s), cite exactly why the project maps to them, and include evidence sources for need. Don’t leave this to a single concluding paragraph.

Pillar 2: Regional benefit proof

Use the requirement thresholds directly:

• 26+ states, or
• majority of one FWS region, or
• majority of one regional association of fish and wildlife agencies.

For each claim, list the affected states and briefly describe expected outcome by state bloc. Don’t rely on generic “regional collaboration” language; use explicit geography.

Pillar 3: Governance and implementation realism

Each partner’s role needs an operational assignment:

• who leads data collection,
• who handles permits and compliance,
• who manages partner deliverables,
• who is responsible for milestone monitoring and reporting.

This is a long-cycle portfolio (implementation is usually not a one-month initiative), so governance matters as much as technical quality.

Common errors that can invalidate an otherwise good proposal

1) Ignoring first-stage and second-stage logic

Submitting a comprehensive narrative without preserving a clean stage-1-to-stage-2 transition causes duplication and inconsistency. The stage-1 materials should already contain architecture clean enough to scale.

2) Weak regional scale explanation

The NOFO is explicit that projects should have multistate impact. If your draft can be rewritten as “one state with a few partner letters,” it will likely fail review.

3) Incomplete administrative readiness

Many teams have excellent technical narratives but lose because SAM.gov and GrantSolutions role setup is incomplete. Since the call has hard system-specific requirements, that is a preventable error.

4) Ambiguous benefit-counting method

If you claim 26+ state impact, the proposal should include enough detail for the reviewer to check where and how each state benefits.

5) Submission channel confusion

The NOFO states that complete applications are not submitted in Grants.gov. Confirm this before submission. Use the correct channel at each stage.

FAQ

Is this a recurring grant, or only one cycle?

The listing shows the FY 2027 funding window, with archive date shown as Jan 1, 2027. In that framework, it is a cycle-specific opportunity for FY 2027 multistate grants.

Do I need federal matching funds?

No, the NOFO states no cost sharing is required for this opportunity.

Can a nonprofit apply?

Yes, certain nonprofits may apply depending on 501(c)(3) status categories and exclusions described in the official eligibility text.

Is there any way to apply after July 14, 2026?

The initial submission deadline in the public materials is July 14, 2026 at 11:59 PM ET. Late submissions are not expected to be accepted.

What happens after stage-1 submission?

Selected proposals are notified by email in late September and then move into a complete Grant Application cycle via a directed announcement in GrantSolutions.

Can foreign entities apply?

The source defines U.S. states and related U.S. jurisdictions and treats non-U.S. jurisdictions as not eligible applicants, with only limited roles in partnerships allowed for benefit-counting context.

Final preparation timeline

Because deadline management determines competitiveness, use a backward-planning matrix:

• Now through mid-March: confirm applicant consortium and strategic-priority fit.
• Late March to April: complete SAM.gov and internal registrations; identify AFWA regional priority alignment with evidence.
• April to May: draft all stage-1 core text and budgets.
• May to early June: partner validation and benefit-counting table built.
• Mid June: first internal review across technical, admin, and compliance checks.
• First two weeks of June-end/July: final packaging, file conversions, submission readiness check.
• Before July 14: submit at least one day early to absorb any portal issues.

This avoids exactly the type of delay that turns a good proposal into “incomplete or late.”

Official sources to use while applying

• Official opportunity listing (grants search and key metadata): simpler.grants.gov opportunity page
• Full PDF NOFO (authoritative): Foa_Content_of_F27AS00009.pdf
• FWS regions reference cited in the NOFO: FWS regions
• AFWA regional associations referenced in the NOFO: AFWA regional associations

The grant is best treated as a high-complexity coordination opportunity, not a simple science concept grant. If your team can prove regional relevance, partner accountability, and clear staged execution, you should be competitively positioned for consideration in this cycle.