USDA Community Connect Grant Program FY 2026: Rural Broadband Grants for Unserved Communities

USDA Community Connect Grant Program FY 2026: Rural Broadband Grants for Unserved Communities

If your organization is working to solve the broadband gap in a rural area where internet service is missing or still underperforming, the Community Connect Grant Program (CCG), FY 2026 is one of the clearest federal funding windows for practical, infrastructure-grade outcomes. The Rural Utilities Service (RUS) page for this NOFO publishes a concrete target: fund projects that provide service on a community basis and that deliver meaningful speeds where service is currently absent or inadequate.

What makes this opportunity useful for planning is its clarity on who can apply, what they can fund, where projects may be considered ineligible, and when applications must be submitted. The NOFO language is operationally practical rather than conceptual, which means teams can map tasks to requirements with less ambiguity.

Key details

What this opportunity is and what it is not

The call is simple in its purpose and strict in execution:

• It is for grant-funded, project-based broadband buildout in rural areas.
• It is centered on a community-oriented connectivity model rather than one-off service to individual addresses.
• It is not intended as operating support in general; the funding should support infrastructure and service access targets, with explicit restrictions around ineligible uses.

The summary states the NOFO’s core objective clearly: support broadband networks that provide access to all premises in areas where broadband service does not exist or is commercially insufficient by the agency’s standards. This means your proposal should read like a deployment plan and a service-design plan, not just a statement of concern.

Your project should be measurable against that mission:

1. Is the proposed service area currently underserved according to the NOFO definition?
2. Will service be provided at at least 100/20 Mbps?
3. Is the project serving the whole area in a way that reaches all premises and not just one route or one institution?
4. Are your costs and timeline realistic for a 3-year performance structure?

If all four are clearly answered, it is likely a true fit.

Eligibility and accepted applicants in plain terms

The NOFO list of eligible entities is broader than many grant programs, but also includes hard compliance checks. It is not just “nonprofit only.” In practical terms, eligible applicants in FY 2026 include incorporated entities, Indian tribes and recognized tribal entities, state or local government entities, and for-profit/non-profit legal entities.

The important practical interpretation is this:

• You may be a utility-like private entity, a provider, or a public-sector applicant — if you are legally eligible and can carry Federal grant obligations.
• Your corporate or organizational background matters only if you can prove good standing and pass federal eligibility screens.
• You should assume that legal and compliance issues can disqualify you if neglected.

From the NOFO:

• Applicants with recent federal felonies (past 24 months), unresolved federal tax liabilities, debarment/suspension status, or federal debt issues can be excluded.
• Federal disqualification checks include Do Not Pay screening.

For the service footprint and eligibility criteria, the NOFO is explicit and detailed:

• The proposed service area must be contiguous and rural.
• Broadband should be absent or below 10/1 Mbps baseline.
• The requested service must be on fixed broadband at 100 Mbps down / 20 Mbps up for residential and business premises.
• The area cannot overlap with existing current borrower/grantee service areas.
• Areas already receiving certain federal support for qualifying infrastructure can be excluded.
• Tribal lands need the right communications/authorization and coordination if included.

This means your first due-diligence milestone is not the engineering model — it is geographic and service eligibility. Build a compliance matrix before your technical team drafts architecture.

Eligibility fit by applicant profile

The NOFO language tends to reward teams that are project-ready, not just concept-ready. Use this checklist to decide whether to proceed:

Best fit

• A local government, county, tribe, cooperative, or nonprofit that already has an implementation footprint in one or more rural zones.
• A rural electric, telecom, or infrastructure partner that can demonstrate execution ability and legal authority.
• A consortium where one entity leads grant administration and another handles buildout and service deployment.

Borderline cases to handle cautiously

• Applicants without SAM registration or UEI planning to “figure out registration after grant selection.”
• Applicants with unclear or contested service area definition.
• Applicants proposing areas already covered by recent federal funding commitments.
• Applicants seeking to use one application for multiple overlapping geographies without clear separation and compliance.

What to document before writing

Applicants should prepare:

1. Legal formation records and authority to enter federal agreements.
2. Clear entity registration and compliance profile in SAM.
3. Preliminary maps of proposed service area, including baseline and desired speeds.
4. Early community need evidence and current broadband mapping.
5. Procurement or implementation structure for 3-year service obligations.

Application process and deadlines

This is an electronic-only process and that is non-negotiable. The NOFO says applications are submitted through the USDA Community Connect application system, with a hard cutoff:

• May 13, 2026: window opens
• June 29, 2026, 11:59 AM ET: final submission deadline
• Late or incomplete applications are not accepted

For teams tracking readiness, this is a tight calendar.

Required pre-submission setup

1. SAM activation and UEI
   • Active SAM registration is mandatory at submission.
   • Incomplete SAM and UEI information is a common reason for disqualification risk.
2. Application system access
   • USDA requires Level II eAuth and authorized representative workflow.
   • Expect a few business days for access setup.
3. Community Connect application checklist and forms
   • The NOFO points to the Application Guide and related checklists.
4. Single proposal rule
   • One proposal per applicant in FY 2026 CCG window is eligible for approval.
   • Multiple applications from same applicant may be reduced to highest-scoring one.

Submission mechanics that matter

The NOFO is strict on submission order and file completeness. It explicitly warns that items should be assembled and tabbed as instructed to avoid timely eligibility issues. Do not overinvest in narrative before final compliance folder assembly. The quality signal in this process is not only strong writing; it is whether your package is complete, ordered, and technically complete by the deadline.

Practical timeline plan (2022026)

You should run backward from June 29 and block:

• May 15–19: finalize governance, UEI/SAM status, entity documents.
• May 20–25: finalize proposed funded service area and mapping evidence.
• May 26–31: complete project budget assumptions, match plan, and procurement assumptions.
• June 1–10: draft narrative and technical sections, with review by compliance lead.
• June 11–19: integrate forms/checklists in required order.
• June 20–27: technical QA pass and response simulation.
• June 28–29: final submit and receipt confirmation.

What funds can be used for

The NOFO clarifies that this is a grant, competitive in nature, with a 3-year performance horizon.

Core funded obligations include:

• Broadband buildout to underserved rural premises.
• Community-level delivery commitments.
• Support for free community-oriented service components required by the program (including required free community center access).

The program does include a minimum and maximum grant scale, so your proposal should justify scale against measurable coverage and area requirements.

Cost-sharing and match

The NOFO states that matching contributions are required and points to 7 CFR 1739.14 plus program guide instructions for exact terms. Because match language affects your entire financial structure, prepare this before budget write-up. A common failure mode is submitting an appealing technical plan without a credible local/non-federal match plan, which makes scores drop after technical review even when architecture is strong.

Ineligible purpose checks

Ineligible uses (as stated) include prohibited duplication and non-permitted operating spending categories. That means proposals should avoid framing funds primarily for recurrent costs that are not clearly tied to eligible deployment, build, or program requirements. If you intend to include support operations, tie every line item to program outcomes and avoid vague “ongoing general costs” framing.

Review logic and evaluation strategy

RUS uses the standard CCG criteria path with scoring under 7 CFR 1739.17 and selection framework from 7 CFR 1739.16. Practically:

• The review process is not just technical merit; it is also fit with eligibility,
• Geographic uniqueness and duplication controls matter deeply,
• Public notice and eligibility validation are part of selection, and
• A higher scored application is not guaranteed the highest award if funds are constrained.

The NOFO explicitly confirms ranked selection with practical funding constraints and possible partial awards. A lower-scoring proposal may still be awarded if selection mechanics make it the best use of available funds in a specific area.

How to make the scoring package stronger

Build your narrative around five proof points:

1. Service need evidence: clearly map where service is absent/insufficient.
2. Technical realism: show design and rollout plan at the required speed.
3. Coverage model: demonstrate all-premises service design, not isolated nodes.
4. Community outcomes: education, health, and business relevance in measurable terms.
5. Execution readiness: show governance, permit chain, staffing, and sequencing for 36 months.

The strongest applications do not overpromise future expansions. They show first-year execution and a credible second- and third-year maintenance/upgrade sequence.

Common mistakes to avoid

1) Missing hard eligibility gates

Commonly, teams submit a technically strong proposal and lose points because the proposed service area does not satisfy official definitions. Keep a pre-check: Is service truly under 10/1 in defined locations? Is there prior federal support? Is tribal coordination complete?

2) Late or weak SAM/UEI setup

For this NOFO, SAM and UEI are not optional admin tasks. They are gating items. If your registration is incomplete, your application is likely invalid even if everything else is high quality.

3) Overlapping or duplicative geography

RUS checks against existing service, both federal and previously approved projects in the same place. If your area overlaps with existing commitments, document why this is not duplication and avoid contested segments.

4) Assuming speed in brochure is sufficient

Saying “100 Mbps capability” is not enough. Reviewers want implementation architecture and sequencing so the service speed is credible in rural topology, terrain, and demand profile.

5) Ignoring required local obligations

If the proposal includes community facilities or essential facility service commitments, include them in cost and operations sections. Hidden omissions create risk of adverse compliance reviews later.

6) Submitting without pre-public notice prep

The public notice/filer process is embedded in the selection process. Teams should expect community response and ensure their submitted assumptions are reproducible and defensible.

Practical preparation guidance by team function

For lead applicants (government/nonprofit/private entity)

• Assign one program lead responsible for compliance closure by section (authority, entities, PFSA, match).
• Run the NOFO against your draft and track each numbered requirement as pass/fail before submission.

For technical teams

• Prioritize reliable deployment method and geography mapping over exotic architecture.
• Produce implementation milestones that match the 3-year performance period.

For finance teams

• Build a budget with match assumptions separated clearly.
• Tie every cost to eligible purpose and expected eligible duration.

For policy/community teams

• Add local stakeholder language but avoid token community narrative.
• Include letters, tribal approvals, and partnership commitments if needed.

FAQ

Is this still active for 2027?

The reviewed window is FY 2026 with a June 29, 2026 deadline. If you are planning for 2027, the current materials are still useful as a structural reference, but you should wait for the new publication and confirm a new NOFO before submission.

Do only government entities qualify?

No. Eligible entities include a broad legal set under 7 CFR 1739.10, including for-profit and not-for-profit legal structures, as long as they meet federal eligibility and registration requirements.

Can small rural cooperatives apply?

Yes, if they meet legal and technical eligibility and can support the federal grant obligations, including registration and reporting.

Is private investment required?

A matching contribution is required in FY 2026 CCG. The exact match details are in regulation and the application guide; you should budget it explicitly before final drafting.

Can organizations submit multiple applications?

The FY 2026 guidance says one proposal per applicant is eligible for approval. Additional submissions from the same applicant are collapsed and only the highest-scoring one may be considered, subject to exception language.

Can this be used for urban neighborhoods?

This opportunity targets rural areas and areas deemed eligible under 7 CFR 1739.3 definitions, and includes additional rural-area-specific checks.

Official links and what to verify right now

Use only official sources during final prep:

• Official NOFO PDF: https://files.simpler.grants.gov/opportunities/068ef5f3-2cd1-415b-8f32-f96fa63d91ba/attachments/78e6e0cd-0344-4479-8d86-036901e55ffe/CCG_NOFO_FY_26_corrected.pdf
• Program application hub: https://www.rd.usda.gov/community-connect
• Grants listing record (official): https://simpler.grants.gov/opportunity/068ef5f3-2cd1-415b-8f32-f96fa63d91ba

Before your final submission, verify:

1. Opportunity status and any amendments after 2026-05-31.
2. Whether community mapping layers have changed.
3. Whether match rates in 7 CFR 1739.14 have been updated.
4. Any technical assistance notices from the USDA Community Connect team.

This is one of the programs where technical writing is important but compliance quality is everything. If your application is complete, aligned, and non-overlapping, it is a strong candidate in a competitive but rule-driven competition.