Rapid Response to Emerging and Re-emerging Pest and Disease Events Across Food and Agricultural Systems (A1713): Urgent USDA NIFA Funding

Rapid Response to Emerging and Re-emerging Pest and Disease Events Across Food and Agricultural Systems (A1713): Urgent USDA NIFA Funding

If your lab, extension unit, or applied team is only effective when a threat is active, this is one of the few federal funding windows designed around that reality. NIFA’s A1713 opportunity is part of the USDA Agriculture and Food Research Initiative (AFRI) and explicitly focuses on rapid response to urgent shocks in agricultural systems.

NIFA describes it as a program area priority built to deploy strategies and fill knowledge gaps when there is an emerging or re-emerging pest or disease problem affecting animal production, plant production, or food and ecosystem health. The wording is unusual for a federal funding program: instead of asking for long-cycle, abstract “future significance” narratives, it asks for work anchored to a real event, with immediate relevance.

This is why A1713 reads more like an operational research-and-response mechanism than a conventional planning-only research grant. In practical terms, it is most meaningful when you can define:

• a clear trigger event (new outbreak, resurgence, or invasion),
• a direct pathway from science to mitigation or risk reduction, and
• a realistic plan you can execute within a short but substantial project window.

Because your current request included the goal years 2026–2027, it is worth noting that this program is listed as accepted on a continuing basis and is explicitly tied to the FY 2026 AFRI FAS framework, making it relevant for applicants monitoring 2026/2027-cycle opportunities.

Key details table

What this opportunity is and why it is distinctive

Most federal opportunities with a “rapid response” label still use ordinary proposal workflows with fixed deadlines that are far in the future or far in the past by the time an event occurs. A1713 differs because it is explicitly structured for event-driven urgency. NIFA does not ask for “if this might happen” research proposals. It asks for proposals that respond to effects already present in a production system or supply chain.

That affects strategy in three ways:

1. Relevance is judged quickly. Proposal ideas must connect to an actual, verifiable event, not just a hypothetical scenario.
2. Timing is part of quality. The project narrative must justify why the timing is critical.
3. Operational fit matters. A good A1713 concept often has shorter decision loops and stronger deliverables than a broad, multi-year research theory paper.

The emphasis areas are intentionally broad but specific enough to prevent vague climate-generalist proposals. A team proposing field surveillance, diagnostic tool development, resistant variety options, disease spread modeling, or extension actions still needs to map to One Health, Plant/Animal Health, or Ecosystem Health with an explicit relevance statement.

A1713 also supports integrated work beyond “pure research.” On NIFA’s page, project types include Research, Extension, and Integrated formats. That means your package can combine evidence generation with adoption and communications pathways, which can improve real-world resilience faster than a publication-only approach.

Eligibility and fit: who this is for, and who should pass

NIFA does not publish an overly long exclusion list in the program landing page, but it does give strict scope constraints that effectively define fit:

• your proposal must directly address effects of emerging or re-emerging pests and/or disease, including plant, animal, food, and/or ecosystem impacts,
• you must show the event’s urgency through a dedicated statement on timing, relevance, and impact,
• and your work should be centered in One Health, Plant/Animal Health, or Ecosystem Health themes.

At this stage, the strongest mismatch is common and costly: teams with excellent science but no event tie-in. If your proposal is mostly “important, but not urgent,” it tends to underperform. If your target problem is a broad climate trend with no discrete triggering incident and no clear 180-day applicability, it is better matched to another AFRI topic.

Institutional eligibility details are in the broader AFRI/FAS NOFO references (and can differ by organization type, role, and compliance requirements), so you should verify institutional status and sponsor rules with NIFA resources and your internal grants office before submission. In practical planning, teams often fail here by waiting too late to confirm whether they can submit as a principal institution or through required partner structures.

Funding mechanics: continuous intake, 180-day clock, and budget shape

The most important mechanics from the official page are clear:

• The opportunity is accepted on a continuous basis (event-driven intake rather than one fixed cycle date in the classical sense).
• Applications are submitted within 180 days of effects associated with the qualifying emergence/re-emergence.
• Project durations are 12–24 months.
• The maximum award is $500,000 including indirect costs.
• Grant types include Standard and FASE (Strengthening Standard).

Treat these as hard controls in your planning sheet:

• The 180-day rule acts like a clock, not a theme.
• “Urgent” must be backed by evidence, not narrative style.
• Indirect costs are part of the maximum.

For applicants used to proposals with fixed annual deadlines, this requires a different project management rhythm:

• keep a near-real-time event tracker (what changed, where, when),
• keep a pre-approved proposal skeleton so you are not starting from zero on day one,
• involve data and extension leads in advance so the response package is complete quickly,
• and align partner letters/commitments with speed.

For budget planning, the $500k ceiling is significant but modest enough that you should resist adding long-term infrastructure ambitions unless necessary for the rapid-response objective. Use funds for deliverables that reduce threat impact quickly: surveillance analytics support, trial designs, extension briefs, validation assays, rapid dissemination workflows, or targeted field/bench work.

Application components and preparation sequence

NIFA’s page highlights the single most important non-negotiable: your proposal narrative must clearly state timing, relevance, and impact of the specific event. Everything else should be in service of that requirement.

A practical application sequence for this program:

1. Define the qualifying event in one paragraph

   • what emerged or re-emerged,
   • when and where effects were observed,
   • what populations, systems, regions, or sectors are affected.

2. Choose the emphasis area and keep it dominant

   • One Health (human-animal-environment overlap),
   • Plant/Animal Health (crop and livestock protection context),
   • Ecosystem Health (supply-chain or landscape-level effects).

3. Select project type early

   • Research, Extension, or Integrated (research + extension/outreach).
   • If integration is chosen, your work plan should include both generation and uptake actions.

4. Write the rapid-response statement explicitly

   • mention why this matter is time-sensitive,
   • describe who is affected now,
   • and describe measurable near-term outcomes.

5. Map timeline against 12–24 months and the 180-day event window

   • if your response window is already near, trim scope to deliverable-first milestones.

6. Prepare institutional approvals in parallel

   • because these opportunities are intake-driven, internal routing must be faster than normal.

7. Package proposal quality around implementation

   • include methods that can be started quickly,
   • include a simple communication and transfer pathway,
   • provide a realistic staffing plan and data acquisition path.

For many teams, the hardest part is the reverse problem: they have good methods but not a clear “why now” narrative. A1713 reverses the typical order of proposal writing.

Reviewer expectations: what makes a credible rapid-response submission

Reviewers for this program are not only scoring technical merit; they are also screening whether the proposal matches the rapid-response intent. The strongest applications generally show:

• Event specificity: not generic risk language but a concrete outbreak/regrowth event in scope.
• Actionable outputs: results that can influence management or policy in a practical period.
• Cross-ecosystem awareness: how the problem moves through animal, plant, and/or food-chain systems.
• Reasonable execution design: clear tasks, data flow, and deliverables that match available time.

Weak submissions often fail in predictable places:

• treating the funding call as a standard open-ended program and missing the urgency framing,
• submitting broad baseline research disconnected from any specific emergence/re-emergence event,
• or proposing too broad a scope for a 12–24 month window while claiming rapid-response intent.

Given the emergency orientation, an excellent strategy is to include a simple “event-to-output” logic chain: event => risk pathway => knowledge gap => deliverable => expected impact. If you can show this in one page, reviewers can process feasibility more quickly.

Timeline planning and 2026/2027 readiness

Because A1713 is event-linked and continuously accepted, opportunities do not arrive as one clean annual deadline. A practical preparation cycle for 2026/2027 looks like this:

• Before an event (standing readiness, weeks/months)

  • maintain current baseline protocols and partner contacts,
  • pre-align extension messaging pathways and data systems,
  • maintain template budget and governance documents.

• When a qualifying event appears (days 1–14)

  • confirm eligibility against A1713 scope,
  • assign lead investigator and co-applicants,
  • identify whether the project is standard or FASE fit.

• Days 14–60

  • draft the event statement, objectives, and milestones,
  • align timeline to 12–24 month deliverables,
  • collect letters and internal approvals.

• By day 180 from qualifying effects

  • submit a complete application package that is still tightly scoped and clearly responsive.

This is not a rigid official timeline for every action, but it reflects the constraint implied by NIFA’s 180-day submission rule and the fixed project length limits. In 2026 and 2026/2027 planning cycles, the main operational advantage is keeping this process pre-primed.

Teams that do this well can often turn new threats into coherent proposals during the event window, instead of treating “urgent” as a reason to delay planning.

Preparation strategy for a first-class A1713 proposal

Below is a practical playbook you can use for your first draft:

1) Build around problem statements, not methods-first narratives

Start with the event, then select methods. If the event is unclear, you are not yet writing a rapid-response proposal.

2) Keep scope within the accepted budget and timeline

A $500,000 cap and 12–24 month duration force prioritization. A simple design with fewer methods and stronger decision outputs often beats a technically broader one.

3) Pair science with uptake

Because this is about protecting supply chains and stakeholder populations, include a path to uptake: how findings will be used by producers, extension offices, diagnostics labs, or sector groups.

4) Use emphasis areas as organizing headings

If your application spans multiple disciplines, do not make One Health or Plant/Animal/Ecosystem Health an afterthought. Use them as section headers in your objectives.

5) Make the 180-day submission logic explicit internally

Many applicants underestimate how fast this window closes. Build an internal checklist with hard dates for event verification, partner commitments, narrative finalization, and budget sign-off.

6) Ask for technical guidance early

The program provides FAQs and additional AFRI resources (including project type and proposal format guidance). If timing is tight, use official communication paths and ask pointed questions early.

7) Preserve reviewability

Use plain causal flow and outcome metrics. Your evaluator should quickly see: if supported, this reduces risk in this threat window.

Common mistakes and fixes

• Mistake: Vague event linkage

  • Fix: include the exact emergence/re-emergence context and why this qualifies.

• Mistake: Overpromising scope

  • Fix: narrow objectives to 2–4 outcomes that can be achieved within the timeline.

• Mistake: Missing urgency statement

  • Fix: include a short dedicated section on timing, relevance, and immediate impact.

• Mistake: Ignoring integrated route when needed

  • Fix: if extension or adoption is central, choose Integrated and document it clearly.

• Mistake: Late institutional routing

  • Fix: start internal approval planning before writing starts.

• Mistake: Confusing research intent with delivery intent

  • Fix: articulate end users and expected use of results.

FAQ (based on official scope)

Is this still open?

The NIFA page is maintained with event-based acceptance and identifies this A1713 priority as open for ongoing submissions under rapid-response timing rules.

Do I need a fixed submission date?

Not in the usual annual sense. The requirement is event-based: submissions should be within 180 days from effects linked to the pest/disease trigger.

What are the project types?

Research, Extension, and Integrated (Research + Extension/Outreach).

Which grant type can I use?

Standard and FASE (Strengthening Standard).

What is the grant size?

NIFA lists the maximum award as $500,000 including indirect costs.

How long can this project run?

12–24 months.

Can teams with mixed disciplines apply?

Yes, if the project remains in One Health, Plant/Animal Health, or Ecosystem Health emphasis and remains tightly connected to a qualifying event.

Who should I contact for quick questions?

Program contact listed on the page: [email protected].

Official links and next steps

For official details and current instructions, use the program page directly:

• https://www.nifa.usda.gov/grants/programs/agriculture-food-research-initiative-afri/rapid-response-pests-diseases-A1713

Before submitting, verify any linked NOFO references and application-format notices on NIFA because those pages can carry additional technical requirements such as page limits or required forms.

A1713 is not a broad “good idea” fund. It is a readiness-and-response mechanism. That is why it can feel demanding: your team has to be disciplined, fast, and specific. If you are already monitoring plant and animal biosecurity risks, this can be one of the most useful federal channels for urgent, practical funding in 2026 and into 2027.