Build Rural Broadband with USDA ReConnect Grants and Loans: How to Prepare for Funding Up to $50M

Rural broadband funding is the closest thing infrastructure folks have to a summer blockbuster: big budgets, big stakes, big deadlines, and a whole cast of characters who suddenly appear the minute a Notice of Funding Opportunity (NOFO) drops.

USDA ReConnect is one of the headliners. When it’s open, it can support serious, steel-in-the-ground broadband builds—the kind that take a community from buffering wheels and parking-lot Wi‑Fi to real, modern connectivity that doesn’t collapse when it rains or when three kids try to do homework at once.

Here’s the twist, though (and it matters): as of mid-February 2026, USDA is not showing an open ReConnect application window. The latest widely referenced cycle—Round 5 / FY 2024—closed on May 21, 2024 (11:59 AM ET) after an extension. So if you came here hoping to hit “Apply” tonight… not quite.

But if you’re smart—and ReConnect rewards the prepared—you’ll treat this “closed window” period as your competitive advantage. Because the teams that win ReConnect aren’t the ones who write pretty narratives at the last minute. They’re the ones who show up with clean maps, defensible numbers, ready partners, and a build plan that reads like it’s already happening.

This guide walks you through what ReConnect typically funds, who tends to be eligible, how competitive applications are built, and exactly what you can do now so you’re ready when the next NOFO opens.

USDA ReConnect Program status and what it means for applicants (February 2026)

Let’s get the awkward part out of the way: USDA ReConnect currently does not list an open application window on the program page. The public-facing materials still point back to the most recent round, and Federal Register documentation shows the FY 2024 submission window closed May 21, 2024.

Two important implications:

First, do not assume the next round will look like the last round. USDA can (and does) change eligibility rules, scoring, required broadband speeds, funding “products” (loan vs grant), match expectations, and what counts as an eligible rural service area.

Second, the best time to build your ReConnect application is when you’re not allowed to submit it. That sounds backwards, but it’s the truth. When the window opens, you’ll be competing with teams who already have engineering, financials, and governance locked. If you’re still arguing about service area boundaries at that moment, you’re toast.

At a Glance: USDA ReConnect rural broadband funding

What this rural broadband opportunity actually offers (and what it does not)

ReConnect exists for one job: get broadband built in places the market keeps skipping. That means funding that can support the expensive, unglamorous reality of rural deployment—make-ready, pole attachments, trenching, fiber, huts, electronics, backhaul/interconnection, and all the other line items that turn “we should get broadband” into “we have broadband.”

Historically, ReConnect has offered different “products.” Some rounds included 100% loan options, some had loan/grant combinations, and some had 100% grant categories tied to specific community characteristics. In at least one recent cycle, program materials also pointed toward 100 Mbps symmetrical expectations in funded service areas—again, specifics are round-dependent, but the direction is clear: USDA wants real capacity, not “technically broadband if you squint.”

What ReConnect generally does not want is a polite planning exercise. This program is typically designed for infrastructure-scale deployment, not early-stage feasibility studies. Think of it like the difference between funding an architect to sketch a house versus funding the concrete, framing, wiring, and roof. ReConnect is the roof money.

And there’s a quieter benefit that experienced applicants understand: winning ReConnect can de-risk everything else. If you’re a co-op, municipality, tribe, or rural ISP, a major federal award can help you secure better terms with vendors, strengthen middle-mile negotiations, and give lenders and boards more confidence. It’s not just capital; it’s credibility.

What ReConnect funds: eligible broadband project types in rural areas

At its core, ReConnect supports projects that construct, improve, or acquire the facilities and equipment needed to deliver broadband to eligible rural service areas.

In practical terms, this usually means:

• Last-mile network builds (often fiber, sometimes hybrid approaches depending on terrain and rules)
• Network electronics and infrastructure required to deliver service
• Acquisitions that directly support delivering broadband (when allowed under the NOFO)
• The “real build” costs that show up in engineering designs and construction schedules

The exact list of eligible and ineligible costs will be spelled out in the NOFO when a round opens. Until then, your best move is to prepare your project like a construction lender would evaluate it: clear scope, verified demand, detailed cost model, and a plan to operate it without magical thinking.

Who should apply for USDA ReConnect (eligibility, in plain English)

ReConnect eligibility is NOFO-driven, meaning it’s set by the specific notice for the active round. Historically, USDA has allowed a range of applicant types—often including states, local governments, tribes, nonprofits, cooperatives, and for-profit entities—but the fine print matters. Some rounds create categories that favor certain geographies or community types; others set financial or operational thresholds that quietly narrow who can compete.

Beyond the entity type, the real “gate” is usually the service area. Your project must serve qualifying rural areas under the program’s current definitions. That sounds simple until you try to prove it.

Here’s what “prove it” looks like in the real world:

A county government might have a strong case politically, but if the proposed funded service area includes pockets that are already served (or appear served on maps), you can lose points—or lose eligibility outright—unless you’ve built a defensible, well-documented service evidence package.

A telephone cooperative may have operational credibility and existing plant, but still needs to show that the proposed expansion area meets the program’s rural criteria and service thresholds, and that the co-op has the financial and technical capacity to complete the build.

A tribe may have a compelling need and strong community support, but still must wrangle rights-of-way, interconnection, and partner commitments into writing—and make sure the network design matches what the budget claims it will build.

In short: ReConnect is open to many, but it’s not friendly to the unprepared. If your organization can manage engineering, procurement, compliance, and long-term operations—and you can back up every claim with documentation—you’re the type of applicant this program is built for.

Why ReConnect is tough (and why it is still worth it)

This is a tough program to win, and pretending otherwise doesn’t help anyone. ReConnect applications can fail for reasons that feel maddeningly small—like shapefile inconsistencies, mismatched location counts between narrative and budget, or an adoption forecast that makes reviewers raise an eyebrow.

But if you’re trying to finance rural broadband at scale, ReConnect is still one of the rare opportunities where the federal government can meaningfully move the needle. Private capital often avoids these areas for a reason: long distances, low density, expensive construction, and slower payback. ReConnect is designed to tackle exactly that math problem.

Insider tips for a winning USDA ReConnect application (the stuff that actually moves your score)

1) Treat your service area map like it is evidence in court

ReConnect mapping isn’t arts-and-crafts; it’s sworn testimony. Build a single source of truth for your service area boundaries and location counts, then ensure your narrative, budget, and technical exhibits all match it perfectly.

If one document says 1,243 locations and another says 1,318, reviewers don’t think “minor typo.” They think “these people don’t control their own numbers.”

2) Build one integrated model: engineering + finance + operations

A common failure mode is having three separate “truths”: the engineer’s design, the finance team’s spreadsheet, and the operations plan someone wrote because the application asked for it.

You want one integrated model where:

• Your design assumptions drive quantities (miles, passings, drops, electronics)
• Those quantities drive costs and construction schedule
• Those costs and schedule drive cash flow needs
• Cash flow needs align with the funding request and any match/debt structure
• Operations assumptions (staffing, maintenance, pricing, churn) connect to long-term sustainability

If any of those pieces live in isolation, the application reads like a Frankenstein monster.

3) Make partnership commitments real—written, priced, and reflected in the design

If your plan depends on pole access, middle-mile interconnection, contractors, or anchor institutions, don’t submit “we expect to.” Get commitments in writing, and make sure they show up in your numbers.

Unsigned assumptions are risk. Named partners with documented terms are confidence.

4) Build a compliance story, not just a network story

Federal infrastructure money comes with rules—procurement standards, reporting, environmental and historic preservation considerations, and other requirements that vary by program and project.

Successful teams don’t pretend compliance is “paperwork later.” They show readiness now: governance, procurement policies, internal controls, and a realistic plan for documentation and audits.

5) Stress-test your adoption and revenue assumptions like a skeptic would

Overly rosy adoption forecasts sink applications because they signal you haven’t done the hard thinking. Reviewers know rural take rates vary. They know competition appears. They know affordability programs change.

Build forecasts with conservative cases, explain your pricing strategy, show how you’ll market and install, and demonstrate you can operate even if adoption ramps slower than you’d like.

6) Assign one accountable lead who can end turf wars

ReConnect applications often die from “death by committee.” Engineering says one thing, finance says another, legal redlines the third, and nobody owns reconciliation.

Pick one application owner with authority to resolve conflicts and force a single coherent package. Think of them as the air-traffic controller: without them, you don’t take off.

7) Start now by assembling a version-controlled data package

Before the next NOFO, build a “master package” and keep it under version control (yes, even if it’s just a disciplined SharePoint/Drive setup with naming rules). Include shapefiles, location lists, unit costs, permitting constraints, make-ready assumptions, and the sources behind every number.

When the NOFO drops and changes scoring language, you won’t scramble. You’ll adapt.

Application timeline: a realistic plan even without an open deadline

Because ReConnect isn’t open right now, your timeline is less “countdown to submission” and more “build readiness in phases.” Here’s a workable approach that prepares you for a sudden NOFO release.

Phase 1 (Weeks 1–4): Service area definition and evidence. Lock your proposed funded service area boundaries. Compile baseline service evidence and document why locations qualify. Create your master location counts and make them traceable.

Phase 2 (Weeks 5–10): Engineering design and cost model. Develop preliminary engineering, BOM-level quantities where possible, and a cost-per-location calculation that you can defend. Start early conversations on pole attachments, interconnection, and permitting constraints.

Phase 3 (Weeks 11–16): Financial model and operations plan. Build cash flow aligned to construction schedule. Develop an operations plan that matches staffing reality. Stress-test adoption/revenue.

Phase 4 (Ongoing until NOFO): Governance, procurement, and partner documentation. Gather letters/commitments, finalize internal controls, document procurement approach, and prepare for reporting.

When the NOFO opens, your goal is to spend your time tailoring—not inventing.

Required materials to prepare (typical ReConnect-style package components)

The exact checklist will come from the next NOFO, but most ReConnect-caliber applications end up needing a similar set of components. Prepare these now so you’re not building them during the sprint.

• Service area mapping files and location evidence. This usually includes shapefiles and supporting data that demonstrate eligibility and current service conditions. Keep every boundary and count consistent across all documents.
• Engineering design narrative and exhibits. Even if final construction drawings come later, you’ll need a credible network plan, technology approach, and build methodology.
• Detailed budget and budget narrative. This is where you show your math. Tie costs to quantities and design assumptions, not vibes.
• Financial projections and sustainability narrative. Plan for construction cash flow, operating expenses, revenues, and contingencies. Explain how the network stays healthy after the ribbon-cutting photos.
• Organizational documents and proof of capacity. Show you can manage federal funds, execute procurement properly, and oversee contractors.
• Partner letters and interconnection documentation. Where your plan depends on others, document it.

Even if you can’t finalize everything without an active NOFO, you can build 80% of the package now—and that 80% is usually what separates winners from late-night scramblers.

What makes a ReConnect application stand out to reviewers

Reviewers are typically looking for a mix of need, readiness, and credibility.

Need is the why: unserved/underserved realities, rural geography, lack of viable alternatives.

Readiness is the how: engineering that makes sense, partners already lined up, permitting and make-ready realities acknowledged, and a build schedule that doesn’t pretend winter doesn’t exist.

Credibility is the proof: numbers that match across documents, conservative financial assumptions, and an applicant that clearly has (or has secured) the capacity to execute and operate.

The strongest applications feel boring in the best way. They read like a project that’s already managed well.

Common mistakes to avoid (and how to fix them)

Mistake 1: Waiting for the NOFO to start foundational work.
Fix: Do your mapping, service evidence, and preliminary engineering now. When the NOFO arrives, you’ll adjust to rules—not start from scratch.

Mistake 2: Inconsistencies across narrative, maps, and budget.
Fix: Create a reconciliation sheet: location counts, miles, unit costs, totals. If anything changes, update everywhere.

Mistake 3: Overconfident adoption and revenue forecasts.
Fix: Build a conservative base case and explain your marketing/installation plan. Show how you handle slower ramps.

Mistake 4: Treating last round’s criteria as permanent.
Fix: Assume scoring and thresholds will change. Build modular narratives and models you can reconfigure quickly.

Mistake 5: Weak governance and unclear accountability.
Fix: Name one project/application lead and define who signs off on engineering, finance, procurement, and compliance.

Frequently asked questions about USDA ReConnect (as of 2026)

Is USDA ReConnect open right now?

Not as of 2026-02-16 based on the public program page. The last referenced cycle (FY 2024 / Round 5) closed May 21, 2024. Check official sources regularly for updates.

How much money can you get from ReConnect?

It depends on the funding category in the active NOFO. Historically, structures have included loans up to $50M and grants up to $25M in some categories, but you should treat that as context—not a promise.

Is ReConnect a grant or a loan?

It can be either, or a combination, depending on the NOFO. Some rounds have offered multiple “products” with different terms and scoring priorities.

What kinds of entities can apply?

Often a mix: governments, tribes, nonprofits, co-ops, and sometimes for-profit entities. But eligibility can change round-to-round, so you must follow the next NOFO language when it’s released.

What does qualifying rural mean?

It’s defined by USDA for the program and can change based on the round. Your job as an applicant is to select a service area that meets the definition and back it up with clear evidence.

Does ReConnect fund planning or feasibility studies?

ReConnect is generally oriented toward deployment—construction, improvement, or acquisition tied to delivering broadband—not light planning work. Always confirm with the active NOFO.

What should we do if we missed the last round?

Use the downtime to build your service area evidence, preliminary engineering, partner commitments, and integrated financial/operational model. That preparation is reusable even if the next NOFO tweaks scoring.

Where should we monitor for the next NOFO?

Three places: the USDA ReConnect page, Federal Register notices, and Grants.gov (when postings appear). Teams that see the NOFO early gain time for QA and packaging.

How to apply (and what to do next while the window is closed)

Since there’s no open application window right now, your immediate “apply” step is really a “get ready” step.

Start by setting up a simple monitoring workflow: assign a person (not a committee) to check official sources weekly, and to alert your internal team the moment a new NOFO is announced. Then build your readiness package in parallel: service area boundaries, eligibility evidence, preliminary engineering, a reconciled cost model, partner commitments in writing, and governance/compliance documentation that won’t collapse under federal scrutiny.

If your organization has never managed a federal infrastructure award, consider doing a readiness review now—procurement standards, internal controls, document retention, and reporting cadence. ReConnect is not the place to learn those lessons in real time.

When the next NOFO opens, you want to be in “tailor and submit” mode, not “panic and invent.”

Apply Now / Full Details (Official Links)

Ready to track the program and prepare for the next round? Use the official sources below:

• Official USDA Rural Development ReConnect page: https://www.rd.usda.gov/programs-services/all-programs/telecommunications-programs/reconnect-loan-and-grant-program
• USDA ReConnect program home: https://www.usda.gov/reconnect
• Federal Register FY 2024 NOFO (historical reference): https://www.federalregister.gov/documents/2024/02/21/2024-03484/notice-of-funding-opportunity-for-the-rural-econnectivity-program-for-fiscal-year-2024
• USDA Rural Development Telecommunications Programs hub: https://www.rd.usda.gov/programs-services/telecommunications-programs