USDA-NIFA-DAG2PI-32942: Agricultural Genome to Phenome Initiative - Workshop Grants (FY 2026)
Federal workshop-focused grant under USDA-NIFA’s AG2PI program for interdisciplinary genome-to-phenome workshop projects, with FY 2026 applications due June 29, 2026.
USDA-NIFA-DAG2PI-32942: Agricultural Genome to Phenome Initiative - Workshop Grants (FY 2026)
Key details
| Field | Details |
|---|---|
| Source | USDA National Institute of Food and Agriculture (NIFA) |
| Funding opportunity | USDA-NIFA-DAG2PI-32942 |
| Opportunity name | Agricultural Genome to Phenome Initiative (AG2PI) - Workshop Grants |
| Cycle | FY 2026 (research year context from NOFO) |
| Funding | USDA confirms total AG2PI FY 2026 funding pool around $1,827,495, with approximately $50,000 dedicated to workshop grants |
| Budget size | Minimum award $20,000, maximum $50,000 |
| Duration | 12 months |
| Deadline | 2026-06-29 |
| Project type | Workshop grants (not general conference sponsorship) |
| Match | 100% required; waiver may be granted for specific statutory exceptions |
| Application method | Electronic only through Grants.gov / eRA Grants Management |
| Status | Open for FY 2026 submission window as of the cited NOFO date |
What this opportunity funds
This is not a broad, unrestricted conference funding line. It is a narrow USDA competition inside the wider AG2PI program, built specifically to support workshop-style events that move genome-to-phenome science forward in practical ways for U.S. agriculture. The language in the announcement is explicit that workshop proposals should be used to organize interdisciplinary events that engage scientists and other relevant stakeholders around high-priority, stakeholder-driven questions. It is not meant to replace or subsidize standard conference sponsorship, and proposals that look like pre-existing events or purely networking activities are not aligned with the stated intent.
The competition is part of the broader AG2PI programmatic goals, including improved prediction and selection in crop and livestock systems, better use of genomic and phenomic data, and stronger cross-disciplinary collaboration. In practice, this means applications should not only describe a workshop topic, but clearly connect that topic to AG2PI priorities and explain why a workshop mechanism is the best way to address those priorities. This is important because review emphasis is on program alignment and practical outcome quality, not just event logistics.
Because AG2PI itself spans both crop and animal systems and targets real-world agricultural production environments, workshop proposals that are narrowly technical and isolated from these broader goals usually underperform. The strongest proposals typically show a concrete workflow: a focused scientific need, evidence that a workshop format is needed, planned cross-talk between disciplines, and a clear path for outputs that can be shared or reused.
The announcement states this is a workshop grant opportunity with a 12-month project period and explicit funding boundaries ($20k to $50k per award). The FY 2026 pool size indicates this is intentionally small and competitive. The small cap means teams should prepare a tightly scoped budget and avoid a “big science program” structure.
Who this is for and who it may not be for
The opportunity is aimed at researchers and institutions that can convene and deliver outcomes from scientific workshop activity. It accepts individuals and organizations, including universities, agricultural experiment stations, research foundations, federal entities, national laboratories, private groups, and consortia. Consortia are explicitly encouraged, which is significant: if your effort requires multiple stakeholders (for example, a breeder network, a university phenotyping group, and a data science partner), an organized consortium can be a strategic fit.
The opportunity is particularly suitable if all of these conditions are true:
- You need a temporary, structured event format (one workshop or series) to solve a clearly bounded scientific bottleneck.
- Your proposal can produce measurable workshop outputs (method notes, tool adoption plans, dataset guidance, model workflows, standards alignment, training pathways, etc.).
- The topic is interdisciplinary and difficult to run in a single-discipline project, for example linking genomics, phenomics, and deployment or modeling.
- You already have potential participants from multiple sectors and can justify participant composition with a clear rationale.
The NOFO also says all applications must come from entities with a valid registration posture (SAM, UEI, eRA Commons through the managing system) and that electronic systems must be used. If your organization is not fully registered or not yet comfortable with Grants.gov/eRA, this opportunity should probably not be your first submission unless you can secure compliance quickly.
Potential fit is lower for teams asking for pure travel support, broad annual conference support, or workshop plans that duplicate existing institutional meetings. The wording around “not intended to support existing conferences” is strict enough that review committees are likely to penalize recycled event formats.
Eligibility, compliance obligations, and match
The NOFO is clear that a broad set of applicant entities are eligible, from universities to private organizations and individuals, and it also allows groups composed of two or more eligible entities. This does not mean eligibility alone is enough; your application still needs to meet all administrative and compliance criteria by deadline.
A central compliance point is match. For FY 2026, the announcement says matching funds are required at 100% of Federal funds unless waived. The waiver conditions are narrowly framed around transferability and agricultural significance: waivers may be considered when work is both highly transferable across commodities or when specific scientifically important cases involve minor commodities with demonstrably constrained match capacity. In practical terms, teams should assume they need matching support and only plan a waiver as a contingency or exception, not as default strategy.
A few important compliance points from the NOFO and associated guidance:
- Match documentation: If match is required, budget justification must name the matching sources and total pledged amount.
- No dangerous gain-of-function applications are accepted.
- Research integrity requirements apply, including governance and training expectations at the institution level.
- Data release requirements are active. Data-related outputs should be planned in a data management context consistent with open access and FAIR principles.
- Administrative restrictions include IDC caps (up to 30% of recipient total federal funds), which affects indirect rate structure and budget narrative.
For teams with limited development support capacity, the hardest part is often not the science idea, but meeting federal registration and budget integrity requirements in time. The 100% match rule plus indirect cap can reshape the whole budget.
Application package, form structure, and the review lens
Applications must be submitted electronically and are managed through the usual federal stack (Grants.gov + NIFA’s grants administration flow under the GMI architecture). If you are applying, assume this process requires the same front-end documentation discipline you would use for any NIH/NIFA R&R submission. The core technical application content includes a project narrative in a constrained format with required structure:
- Introduction
- Rationale and significance
- Objectives
- Approach
- Project timeline
- Resubmission response (if applicable)
The project narrative has a strict 18-page limit (12-point font, single-spaced style context, minimum 1-inch margins, no narrow fonts). The NOFO explicitly says page limits are used to keep review parity, so compressing content is not just a formatting task; it is part of competitiveness.
For this workshop opportunity, practical competitiveness depends on a clear “why now” argument and implementation detail. The review criteria place substantial weight on significance and relevance to AG2PI priorities, then on uniqueness/timeliness, then on organizational quality. Together they imply that a good proposal should show:
- Why this workshop solves a pressing AG2PI problem.
- What is new about the workshop versus a standard field or lab meeting.
- How participant mix and output design will produce transferable outcomes.
- How the budget is lean but realistic.
- How the organizing committee is strong enough to execute.
A second major required element is a Data Management Plan. The NOFO requires a budgeted data dissemination strategy and compatibility with open sharing expectations. Even for workshop grants with non-traditional deliverables, reviewers and compliance teams will likely treat weak DMPs as avoidable risk.
The evaluation structure is also highly specific:
- Significance (35 points): AG2PI relevance, U.S. agriculture relevance, and workshop value for scientific exchange.
- Uniqueness and timeliness (35 points): workshop design quality, measurable outputs, and schedule coherence.
- Organization and implementation (30 points): committee credentials, stakeholder involvement, speaker quality, and venue fit.
Because these criteria are explicitly listed, your response should map to them with section headings and evidence. The strongest scoring applications make this mapping very obvious.
Timeline and practical preparation strategy
The target submission date in the official source listing is 2026-06-29 for this NOFO. Treat that as non-negotiable even if there are internal institutional deadlines. You want internal approvals complete ahead of the external due date because institutional routing often consumes multiple days, especially for institutions using strict compliance workflows.
A practical sequence that aligns with how federal reviewers read applications:
10-8 weeks before deadline: positioning and governance
- Identify one narrow workshop intervention that directly maps to a current AG2PI need.
- Validate that this is not just a conference upgrade, but a focused mechanism to generate outputs.
- Confirm registrational readiness: SAM/UEI/eRA/Grants.gov are in good status.
- Draft the preliminary budget with full match and indirect assumptions.
8-6 weeks before deadline: structure and content
- Draft core narrative around the five required PN components.
- Write the Data Management Plan in parallel rather than at the end.
- Identify measurable outputs (e.g., protocol draft, shared dataset catalog, code or tools, training module) and include them explicitly.
- Build panel-ready evidence for why the workshop is interdisciplinary and timely.
6-3 weeks before deadline: review hardening
- Run an internal dry review against the three evaluation dimensions.
- Confirm no line crosses the page limits.
- Verify matching commitments are realistic and budgeted with names and amounts.
- Confirm all required registration and organization roles are assigned.
- Prepare resubmission strategy if needed: if this is a resubmission, ensure response to previous review comments is included and fits the instructions.
3 weeks to submission week: final validation
- Perform final format and compliance check in Grants.gov/eRA flow.
- Validate all attachments are complete and labeled.
- Re-check eRA Commons account activity for applicant organization.
- Submit early enough to absorb workflow failures.
Even if you cannot finalize all speaker invitations by the date of submission, it is usually acceptable to present confirmed themes plus a fallback plan, as long as commitments, outputs, and governance remain credible.
Common mistakes and practical fixes
Below are failure modes I see repeatedly in federal workshop calls like this one:
Subsidizing existing events
- Mistake: Positioning the application as funding to run an already planned conference.
- Fix: Reframe as a workshop with clear intervention points, outputs, and AG2PI alignment.
Underexplained outputs
- Mistake: Listing a broad workshop agenda without explicit deliverables.
- Fix: Define exact outputs and where they will be published (data resource, methods guide, workshop outputs repository, training material).
Weak justification for match
- Mistake: Vague statements like “match will be sought.”
- Fix: Name sources, totals, in-kind vs cash assumptions, and timing.
Ignoring the DMP requirement
- Mistake: Submitting a perfunctory data statement.
- Fix: Include data generation, storage, sharing, and release route explicitly. Mention how output formats align with reuse.
Narrative not mapped to criteria
- Mistake: Strong science but little direct mapping to 35/35/30 point structure.
- Fix: Add section headers for “Significance,” “Uniqueness/Timeliness,” and “Organizing Capacity.”
Ineligible registration posture at deadline
- Mistake: Assuming institutional systems are “almost done.”
- Fix: Keep registrations active weeks before submission and collect screenshots or confirmations if needed internally.
Ambiguous scope creep
- Mistake: Trying to fund unrelated activities under one workshop budget.
- Fix: Keep scope tied to one or two outcomes and show why each component is needed for workshop execution.
Reviewers evaluate feasibility and fit as much as novelty. In a capped-pool opportunity, a clear, well-scoped, well-governed workshop can outperform a large but diffuse concept.
Frequently asked questions
Is this opportunity still useful for 2026/2027 planning?
Yes, because it is directly tied to FY 2026 AG2PI and still has a defined submission deadline of 2026-06-29. That date is still relevant for planners in late May 2026 preparing near-term submissions.
Can individuals apply directly?
Yes. The NOFO permits individuals among eligible applicants. But individuals still need institutional and system-facing structures to submit through the federal systems used by this NOFO.
Is workshop funding separate from AG2PI research grants?
Yes. AG2PI-32942 is the workshop companion to another NOFO, AG2PI Research Grants (DAG2PI-32940). They are adjacent but distinct. If your core need is scientific pilot funding rather than workshop facilitation, you should evaluate the research NOFO instead.
Can I ask for a much larger budget than $50,000?
No. The NOFO provides a maximum award level of $50,000 for this NOFO.
Do I need a consortium?
No, but consortia are encouraged and often stronger for cross-sector topics.
Are travel costs and large venue costs likely to be funded?
They can be funded where justified by workshop design and reviewed under output-value logic. However, because the mechanism is specifically for workshop outputs and collaboration around AG2PI needs, administrative and programmatic discipline matters more than event hospitality.
What is the key differentiator for a competitive proposal?
A strong application is one that demonstrates:
- AG2PI strategic fit.
- Distinct workshop value.
- Realistic execution capacity.
- Clear outputs and responsible budget structure.
That combination is usually enough to stand out even with similar technical topics.
Official links and next steps
For application preparation, use these primary resources:
- AG2PI program page with NOFO listing and contact details: https://www.nifa.usda.gov/grants/programs/agricultural-genome-phenome-initiative-ag2pi
- Full official NOFO (AG2PI Workshop Grants, USDA-NIFA-DAG2PI-32942): https://files.simpler.grants.gov/opportunities/def4bf12-ab84-4bd6-8b10-0e0338685a34/attachments/309c3300-6bca-42fe-923a-31a3e98f96fe/USDA-NIFA-DAG2PI-32942-Full-Announcement.html
- Companion research grants NOFO (same program area): https://files.simpler.grants.gov/opportunities/def4bf12-ab84-4bd6-8b10-0e0338685a34/attachments/64684849-bb6e-443c-9d8d-68718a31de72/USDA-NIFA-DAG2PI-32940-Revised-Full-Announcement.html
- Grants.gov landing page for submission workflows and support: https://www.grants.gov
Current official contacts listed in the NOFO include [email protected], [email protected], and [email protected], with administrative support contacts for Grants.gov and award questions.
Final practical guidance
If your submission goal is to win under a small but competitive budget, this is a “clarity and evidence” competition more than a “volume and ambition” competition. The NOFO is explicit enough that reviewers can score weak and unclear applications quickly. That means your best tactical advantage is not complexity but relevance and execution certainty.
Start by choosing one urgent technical or biological bottleneck and design one workshop ecosystem around it. Keep the narrative tightly mapped to significance, uniqueness, and execution quality. If match is a constraint, be explicit and conservative. If you are a first-time applicant, use this as a systems discipline test as much as a science exercise: perfect registrations, clean budget, and a realistic plan for openable outputs usually outweigh purely novel topic statements.
Teams that follow this playbook tend to produce stronger, cleaner applications and survive the first administrative filter, which is where many promising ideas are lost.
