USDA ReConnect Construction Progress Reporting: What R&C Asks Awardees For

A ReConnect awardee exports last week's service-area polygons and drops them in a folder named USDA annual. The folder is treated as filed. R&C is still empty. January 31 is still the due date printed in the User Guide.

This article is for ReConnect awardees preparing project-level construction-progress information for Rural Development's Reporting and Compliance system. It does not walk quarterly financials or BEAD Eligible Entity SARs. Final as-built acceptance stays off this page.

USDA ReConnect construction progress reporting is a project-level R&C filing

USDA ReConnect construction progress reporting is the project-level Construction Progress Report filed in R&C. Version 6 of the Rural Development Reporting and Compliance User Guide, dated December 2025, creates it on the first day of the calendar year after funds are released and due January 31. 7 CFR 1740.80 is the duty. Award documents can change that clock.

The regulation and the portal are not the same instrument. 7 CFR 1740.80, Accounting, monitoring, and reporting requirements, is displayed on the eCFR as of September 14, 2026, with Title 7 last amended September 9, 2026. Its source is 86 FR 11609, February 26, 2021, as amended at 88 FR 5727, January 30, 2023. That section is the duty. The clicks live in the User Guide.

USDA's ReConnect Reporting and Compliance FAQ, current as of this draft, states that the release of funds date determines when the first reports are generated. Other reports are generated based on the date of first advance or when construction has been completed. Project-level reports are required for each award the entity received. They rest on the specific award requirements. USDA reserves the right to adjust frequencies and deadlines at any time.

That last sentence is why we open the executed award before we open the portal. The User Guide is the current system walk-through. It is not a substitute for the legal agreement that created the award. If a GFR instruction disagrees with the User Guide, we record the conflict against the award. We follow the award plus the written Agency direction.

A commercial workfront register is a different job. Our construction progress reporting telecom fiber guide is the owner control record that freezes a named span. This page is the ReConnect R&C filing that sits on top of that record, if the awardee actually keeps one.

Split 7 CFR 1740.80 from the R&C clicks

Awardees mix three clocks and then wonder why a certified Construction Progress Report did not move money. 1740.80 carries account-level financial duties and an annual mapping duty. It also carries a 3-year post-construction report and a records-retention duty. R&C then splits those duties into named screens. The award can still rewrite frequency and content. Keep the three sources labeled.

We use the table below as a source map, not as a substitute for the award. If a cell is blank on a live project, someone will invent a file type under pressure.

The rows that follow expand that map 1:1. Do not paste a CAD export into the map cell and call 1740.80 closed. Do not paste a subscriber point file into the map cell either.

Account-level reports stay off this page

1740.80(a) requires a system of accounts acceptable to the Agency, as described in 7 CFR part 1770, subpart B. 1740.80(b) and (c) split the annual audit path: awardees subject to 2 CFR part 200 follow 2 CFR part 200, subpart F; awardees not subject to that part follow 7 CFR part 1773 on the RUS online reporting system. 1740.80(d) then requires balance sheets, income statements, statements of cash flow, rate package summaries, and the number of customers taking broadband service on a per community basis, 30 calendar days after the end of each calendar year quarter, throughout the loan amortization period or for the economic life of grant-funded facilities.

Those are account-level clocks. They are real. They are not the Construction Progress Report. We leave them named so a finance desk does not treat January 31 as the only USDA date on the award.

Construction Progress Map covers completed service-ready areas

Version 6 of the User Guide, section 3.3, states that the Construction Progress Report is used to report construction progress in the Approved Project Service Area for each reporting period until construction of the project is complete. For that report, Construction Complete areas are the areas on the Construction Progress Map that are fully constructed and ready to deliver broadband service to subscribers as defined in the latest federal register notice for the program under which the project was approved.

USDA's ReConnect reporting FAQ is stricter on the map's coverage. The Construction Progress Map is due annually. It must be completed for any area where construction was completed (ready to receive service) within the Approved Project Service Area during the current reporting period. In-progress plant that is not ready to receive service does not belong on that map as complete.

1740.80(e) is the regulatory cousin, not a duplicate sentence. Awardees must submit annually updated service area maps through the RUS mapping tool showing the areas where construction has been completed and premises are receiving service, until the entire Proposed Funded Service Area can receive the broadband service. At the end of the project, awardees must submit a service area map indicating that all construction has been completed as proposed in the application. If parts of the PFSA have not been constructed, RUS may require a portion of the award to be rescinded or paid back.

Ready to receive service is not the same claim as premises are receiving service. The User Guide map is the first claim. 1740.80(e) is the second. Mixing them is how a certified map later collides with a service-area update that still shows dark addresses.

Construction Status has to match saved map data

The User Guide's Construction Progress Map is a mapping tool used to upload a shapefile of, or plot, construction progress on an annual basis as part of the Construction Progress Report. Shapefile or plot. That is the current system step. It is not a USDA rule that every awardee must upload CAD files. Route centerlines and a named GIS schema are not Version 6 requirements either. Direct GIS or CAD upload is not a universal R&C requirement in Version 6.

The same guide warns on a status mismatch. If Construction Status signifies work has been performed for the current reporting period, and no map data was saved, the report cannot be certified until the status selection is changed or the required map data is provided. The reverse warning fires when status says no work was performed and the map still needs an update. Status and geometry have to agree.

The limitation of our preferred GIS-export approach is that the file can be internally tidy and still describe in-progress plant the User Guide will not accept as complete. We now refuse to call a polygon "R&C complete" until it matches the User Guide definition for that reporting period.

Geocoded new subscribers are a separate upload

Version 6 of the User Guide puts New Broadband Subscribers to Report for this Period under the Construction Progress Report's second schedule, as its own subsection, with a geospatial upload of subscriber locations. That upload is not the Construction Progress Map. Keep the two files, and the two screens, distinct.

USDA's ReConnect reporting FAQ answers the subscriber question directly. With the exception of the final Construction Progress Report, the entity is required to complete the New Broadband Subscribers to Report for this Period section of the Construction Progress Report or the Annual Performance Report. Subscriber data has to be uploaded and geocoded on those reports. The final Construction Progress Report is the named exception.

1740.80(h) is easy to misread onto this screen. After construction completion, awardees must submit annual reports for 3 years. Those reports must include existing network service improvements and facility upgrades, the estimated number of end users currently using or forecasted to use the new or upgraded infrastructure, progress toward the objectives for which assistance was granted, the number and geospatial location of residences and businesses that will receive new broadband service, the speed and price of the awardee's broadband service offerings, and the average price of broadband service in the project's service area.

That 3-year window is the Annual Performance Report path in R&C, not the Construction Progress Report filed while construction is still open. USDA's FAQ sets Annual Performance reporting annually for a period of 3 years following the year that construction was completed and certified in R&C. Creation is the day following a submitted Construction Complete Construction Progress Report. The due date is January 31. Do not dump 1740.80(h) fields into a mid-build CPR and call the 3-year clock started.

A geocoded subscriber point is still not an as-built. It is not a splice record. It is not owner acceptance of the drop. If the award later asks for an installed-plant GIS package, that package is a different deliverable, and our fiber network construction record accuracy guide is the QA screen for that record, not for this R&C upload.

Optional controls when the award file is thin

USDA does not universally require a Draftech source register, a GIS reconciliation pass, QA gates, or a construction-handoff package as the Construction Progress Report. Those are optional project controls we use when the award file is thin and the portal still has to be filled from something defensible. They are not 1740.80. They are not Version 6 of the User Guide.

We still recommend them on awards where the PFSA is large enough that a January export will otherwise be a reconstruction. The register names the source file and the cutoff date. It also names the person who can freeze a polygon. GIS reconciliation then compares that source to the Approved Project Service Area the map already displays. QA gates stop a status click that the saved geometry cannot support. The handoff package is how a later closeout desk finds the same identities.

• Source register: Name the current issued design and the PFSA identity on the row that will feed R&C, with the cutoff datetime attached.
• GIS reconciliation: Compare completed, service-ready geometry to the Approved Project Service Area before anyone plots or uploads a shapefile.
• QA gates: Refuse a Construction Complete status when the native evidence for that area is still a production total.
• Handoff package: Keep redlines and tests on their own identities so closeout does not raid the CPR folder. Remaining holds stay named.

The OSP documentation construction handoff page is that last control, written as a construction-release standard rather than as an R&C form. Use it if the award actually needs a crew package. Do not file it in R&C and call the Construction Progress Report certified.

Closeout is later, and it is a different instrument. The fiber construction closeout process is the owner package that keeps redlines and native tests on a retrievable index with remaining holds still named. USDA's Close Out Report in R&C is created after the first closeout event Version 6 names. USDA's FAQ due date is 120 days after that creation date. Section 3.3.6 walks that screen. Neither clock is the January 31 Construction Progress Report.

Grant as-builts, when the award actually asks for them, are still not this report. Our fiber as-built services for grant compliance page stays on the installed record. This page stays on the R&C construction-progress screens.

Choose who owns USDA ReConnect construction progress reporting

Pick the reporting seat that can open the award and the User Guide on the same day, with the native geometry sitting next to both. Do not award the seat to a dashboard demo.

Single-award rural cooperative: keep the R&C filing in-house if one named person can own Construction Status and the map through January 31. That person also owns the subscriber upload. Buy coordinated preparation only if that person cannot also freeze the cutoff date. Keep the Rep Sign Cert on the awardee's staff. Do not outsource the certification click.

ISP with more than one ReConnect award: file project-level reports per award. USDA's FAQ is explicit that project-level reports are required for each award the entity received. A rolled-up company map is not a Construction Progress Report. Keep PFSA identity on every row. If one award is Construction Complete and another is still in progress, those statuses do not travel.

Engineering firm supporting an awardee: prepare the source register and the map geometry. Do not take the awardee's certification. Do not treat a Draftech QA gate as USDA acceptance. Engineering stays 100% in-house at Draftech. When construction is in scope, full turnkey work is delivered by Draftech-managed subcontract crews under our QA/QC and safety program. We still do not take an owner or Agency signature the award assigned elsewhere.

I still catch myself asking whether January 31 is the USDA date before I open the award. The User Guide date is the system default. The award can rewrite it. Write the conflict down. Then file what the award plus the written Agency direction actually require.

Active in 24 states. Available across all 50 U.S. states. Draftech's as-built documentation services can convert accepted field evidence into a controlled record the January filing can quote, without pretending that record is the Construction Progress Report. We do not certify grant compliance. We do not substitute a GIS schema for 1740.80.

If you need a source register and a map-versus-subscriber split before the next January 31 cycle, reach out at info@draftech.com with the award's reporting schedule and the current Construction Status.

If USDA ReConnect construction progress reporting is part of a qualifying route, Draftech engineers the first 20,000 linear feet at no cost, from feasibility and field survey through permit approval. Request the free design package. The owner reviews each request before Draftech commits the package.