Cooperative Agreements in the Grant Feed: What They Signal

At $14.30 million in total listed funding per open state-source record, the current GrantLens feed carries a much larger average amount per state listing than its federal counterpart, at $1.29 million per record. That roughly eleven-to-one difference is not a promise about any one award, and it is not a reason to chase every large public opportunity. It is a practical reminder that high-dollar listings can bring a high-touch operating model—especially when the opportunity is a cooperative agreement.

For nonprofits in Miami-Dade, Broward, Palm Beach, Alameda, Contra Costa, Marin, and San Francisco counties, the label deserves a pause before the usual question of “Are we eligible?” A cooperative agreement may fund work that closely matches an organization’s mission, but it can also require more reporting, more communication, more approvals, and more adaptation during the project period than a conventional grant. The right question is whether the organization can deliver the work with the funder’s ongoing involvement while still serving participants well.

A cooperative agreement changes the operating model

A cooperative agreement is generally a funding arrangement in which the funder expects substantial involvement in carrying out the supported work. That involvement can take several forms: scheduled implementation meetings, review of work plans, approval of changes, shared development of materials, access to program data, or direction tied to performance milestones. The exact terms belong in the opportunity materials, not in assumptions based on the title alone.

For an executive director, this is a governance and capacity issue. For a grant writer, it is a proposal-design issue. For development staff, it is a pipeline-quality issue. An organization can be fully eligible, have a compelling program, and still be a poor fit if no one has the authority or staff time to maintain the relationship the award requires.

Treat the phrase “cooperative agreement” as a signal to investigate these practical questions:

• Who on staff owns the relationship? Identify a program lead with enough decision-making authority to respond to feedback and attend required meetings.
• What can the funder influence? Look for language about approvals, required plans, performance targets, curriculum, procurement, communications, or changes in scope.
• What data must move both ways? Determine whether reporting is limited to periodic submissions or whether the funder will review data during implementation.
• What happens when conditions change? Ask whether participant needs, partnerships, staffing, or timelines can change without formal approval.
• Can indirect work be supported? Build realistic administrative time into the budget rather than treating coordination and compliance as free.

None of these conditions automatically makes an opportunity undesirable. A funder that is actively engaged can bring technical support, access to partners, or clearer implementation standards. The problem begins when a nonprofit writes the application as if it were receiving unrestricted discretion, then discovers that the award requires a closely managed partnership.

The current feed calls for screening before proposal writing

The current feed contains 1,223 federal and 221 state open records. State-source records therefore represent about 15% of these records, yet their combined listed total is much larger on a per-record basis. That mismatch is a useful warning against using listing volume as a proxy for either likely award size or organizational fit.

The category data reinforces the point. Across categories that overlap with work many community-serving nonprofits pursue, average listed amounts sit far above median amounts. Averages can be pulled upward by unusually large opportunities; the median often gives a more grounded indication of the middle of the listed range.

For example, the average listed amount in community development is nearly twenty-seven times its median, while education’s average is about sixty-nine times its median. Those are feed-level patterns, not award forecasts. Still, they make a strong case for reading the full terms before letting a large number set the agenda for a board discussion or program plan.

The currently open Local Food for Schools Cooperative Agreement Program is the clearest example in the supplied opportunities of why the title and the operating details both matter. It is categorized around education and food security and identifies food banks, nonprofits, and community partners as eligible applicants. Its stated purpose is facilitating fresh Florida produce delivery to rural schools. A South Florida organization should not assume that a Florida-wide label makes it eligible or programmatically appropriate; the rural-school focus, delivery capacity, partnerships, and the cooperative-agreement terms all require careful confirmation.

Likewise, a listing tagged as community development or social services may be relevant without being a cooperative agreement, and an opportunity that sounds mission-aligned may still have a narrow applicant type. The Strong Communities Grant Organization listing, for instance, is focused on organizations operating or planning Family Resource Centers, rather than every nonprofit that provides family services. Use a search filtered by geography, category, and applicant fit to narrow the initial pool, then read the source materials for the actual decision.

A sensible screening sequence is:

• Confirm the applicant type and service model match the published eligibility language.
• Check whether the work is feasible in the counties and communities the organization actually serves.
• Identify every point where the funder retains a role in implementation.
• Estimate the staff time required for coordination, documentation, and change approvals.
• Decide whether the likely benefit justifies that operational commitment.

This sequence prevents a common compliance failure: building a polished narrative around a program concept before discovering that the organization cannot meet the management conditions attached to the money.

Put funder involvement into the work plan and budget

The most reliable way to assess a cooperative agreement is to turn its language into operating tasks. “Collaboration,” “technical assistance,” “approval,” and “monitoring” can sound routine in a notice. Each word should become an assigned responsibility, a cadence, and a budget assumption.

Start with a one-page implementation map. Place the project outcomes on one side and the activities required to reach them on the other. Then add a third column: what the funder must review, approve, receive, or join. That third column exposes whether the organization has designed enough management capacity into the proposal.

For a food distribution project, funder involvement might affect delivery schedules, partner coordination, participant reporting, or how outcomes are documented. For a family-support project, it could affect service standards, data collection, or expansion plans for a Family Resource Center. The details will vary, but the discipline is the same: do not bury administrative obligations in the program director’s already-full workload.

Before committing, test the proposal against the following controls:

• Authority: The person attending funder meetings can make or quickly obtain operational decisions.
• Documentation: The organization has a clear place to retain approvals, meeting notes, submitted reports, amendments, and correspondence.
• Data stewardship: Staff know what information will be collected, who will validate it, and how corrections will be made.
• Budget control: The finance lead can separate allowable project costs and track spending against the approved plan.
• Change management: The team understands who must approve a shift in timeline, staffing, vendors, partners, or activities.
• Board awareness: Leadership knows when the award would create a material obligation beyond the grant period.

Eligibility also needs to be verified as an operational fact, not merely declared in a cover letter. Current status, governance records, program descriptions, financial documentation, and service geography should be ready before a notice asks for them. Teams can identify eligibility gaps and verify readiness before they spend weeks drafting a response that will fail on a threshold requirement.

When the notice is lengthy, convert each obligation into a checklist before assigning writing tasks. A NOFO checklist parser can help turn scattered instructions into a working list of attachments, certifications, scoring criteria, reporting expectations, and deadlines. The purpose is not to automate judgment; it is to make sure the organization sees the compliance workload early enough to make a deliberate bid-or-no-bid decision.

Feed volume makes deadline discipline part of compliance

A cooperative agreement often demands more than a strong narrative, and the current pace of new records makes reactive prospecting risky. Newly ingested opportunities rose from 14 in September 2025 to a high of 1,000 in May 2026 before falling to 189 in September 2026. The May high was about 239% above the March 2026 level of 295. Ingestion volume is not the same as the number of suitable opportunities, but it does show why teams need a repeatable process for sorting, assigning, and monitoring opportunities.

A rolling or unlisted deadline should not be treated as an invitation to wait. The Local Food for Schools listing is marked rolling/none, but a nonprofit should still confirm the current submission process, internal review steps, and any cycle-specific requirements on the source page. For every opportunity, record the source link, the person responsible for eligibility verification, the internal go/no-go date, and the person who will own post-award compliance if the application succeeds.

That practice is particularly useful for lean development teams serving multiple programs across South Florida or the Bay Area. Use deadline alerts for newly matched opportunities to surface possibilities as they appear, but pair alerts with a calendar-based internal decision date. An alert is valuable only if someone has time to decide whether the organization can genuinely carry the award’s obligations.

Past awards can also sharpen judgment, where data is available. Award history in the dataset shows 2,260 records in 2024 and 1,587 in 2025, a decline of about 30% in recorded awards. The recorded totals moved from about $3.79 billion to about $2.86 billion, a decline of about 24%. Those movements should not be read as a broad funding forecast, but they do underline the value of examining individual funder and award patterns rather than relying on a single year’s apparent abundance. Teams can review funder histories and recipient patterns when deciding whether a demanding opportunity fits their track record and capacity.

What this data cannot tell you

The figures above describe the GrantLens database at generation time, not the full universe of available grants or cooperative agreements. An opportunity absent from the feed may still exist, and a record in the feed may change after it is ingested. The open-grant figures should therefore support prioritization, not replace source-document review.

The data also contains no county-level open-grant figures. It cannot tell a nonprofit whether Miami-Dade has more relevant open opportunities than Broward or Palm Beach, nor whether Alameda, Contra Costa, Marin, or San Francisco has a larger current pool. County service-area eligibility must be checked opportunity by opportunity.

Award-history coverage varies by source and year. The year-over-year award changes are directional only, not a complete measure of the funding market. They cannot establish that a particular funder is increasing, reducing, or changing its use of cooperative agreements. Nor can average and median listed amounts reveal what an individual applicant will receive, whether indirect costs are allowed, or how much funder involvement will occur after award.

Most importantly, the dataset does not classify every open record by the intensity of funder participation. The words “cooperative agreement” should trigger a close reading, but the binding requirements are the terms, conditions, and communications attached to the particular opportunity.

Make capacity the deciding factor before you apply

The best cooperative-agreement prospect is not necessarily the largest item in the feed. It is the one where mission, eligibility, delivery capacity, leadership authority, financial controls, and funder involvement all align. A smaller, clearly manageable opportunity can be more valuable than a larger award that overwhelms program staff or forces the organization into commitments it cannot sustain.

Set a simple organizational rule: no cooperative-agreement application moves into full drafting until a program lead, finance lead, and executive decision-maker have reviewed the expected funder role. That conversation should produce a named owner, a documented compliance plan, and a realistic budget for coordination. If the team cannot identify those elements, declining early protects both the organization and the communities it serves.

Before pursuing the next listing, run the opportunity through a readiness and eligibility review. It is a practical way to turn a promising title in the grant feed into a disciplined decision about whether your nonprofit is prepared to deliver.