A crew can stand under a pole that exists and still not know which Location ID that span is supposed to serve. The sheet looks issued. The award file lives in a different folder. That is how a BEAD build produces plant the reporting system cannot later join.
This guide is the LLD release crosswalk from award and owner inputs to route-level and structure-level construction issue evidence that a crew may occupy under a named revision. It is not another HLD definition. It is not a generic BEAD support catalog. Change-control evidence sits on the same sheet as the issue set. Held remainder stays visible.
OSP LLD for BEAD Subgrantees: What the Release Crosswalk Proves
OSP LLD for BEAD subgrantees is the construction-issue crosswalk from the executed subgrant and owner plant file to each issued route segment and structure. The BEAD Program General Terms and Conditions, Updated November 2025, sit in a six-authority stack. They do not publish a national sheet list.
When those texts cannot be harmonized, the November 2025 GTCs state their own order. Highest is 47 U.S.C. § 1702. Next is the award's Specific Award Conditions. Then come the BEAD Program General Terms and Conditions themselves. The BEAD Restructuring Policy Notice of June 2025 follows that. The BEAD NOFO sits below the notice. The Department of Commerce General Terms and Conditions dated September 22, 2025 sit last in that list. That order is the document's hierarchy. It is not a Draftech house ranking.
The BEAD Restructuring Policy Notice, issued June 6, 2025, modifies and replaces certain NOFO requirements that a copied 2023 folder still treats as live. It also prohibits Eligible Entities from imposing the removed obligations as BEAD requirements after that notice has already taken them off the federal stack. A 2023 closeout folder copied forward can therefore still carry duties that notice already stripped. We compare the project's register to the June 6, 2025 notice before we treat a copied row as binding on an issued construction sheet.
Current BEAD FAQs, version 22, state they exist to help recipients understand the statute and the NOFO as modified by that notice, including later Eligible Entity questions. They also help readers understand the program. They are assistance. They are not a substitute for the executed subgrant. FAQ 8.2 in that set says Eligible Entities must sign binding subgrant agreements no later than 6 months from Final Proposal approval by the NIST Grants Office. That is an Eligible Entity clock. It is not an LLD duration we publish.
Draftech's in-house OSP engineering writes this crosswalk. Engineering stays in-house. When construction is later in scope, Draftech-managed subcontract crews deliver full turnkey under our QA/QC and safety program, with a single point of accountability on that work. We do not claim a self-perform construction crew today.
What this crosswalk is not
The difference between HLD and LLD in fiber design is a different article. Architecture versus construction drawings lives there. Fiber network HLD for BEAD subgrantees is the architecture package this sheet must not silently reopen. Generic program-support pages and grant-reporting catalogs are also out of scope here. The ReConnect Construction Progress Report in R&C is covered in our USDA ReConnect construction progress reporting guide. We are only tracing inputs to issued objects.
One thing I still catch in our own reviews: we have issued a construction sheet while the location-file version on the register was still blank. The drawing looked finished. The award join was not. We now refuse that release.
Scope rule: cite the executed agreement or current Eligible Entity instruction for every claimed BEAD requirement. Label the rest as owner standards or permit criteria. A house preference is not a federal mandate.
Lock Award and Owner Inputs Before Sheets Move
The register starts with required outputs and works backward. If a later report will need a Location ID, the issued segment must carry that ID now so the award file can join the plant later. If the pole owner needs a structure ID, the sheet must not invent a prettier internal number and drop the owner ID the owner file already uses.
We will not release a construction sheet until every row below is closed against that project and the named source version on the register. A convenient street name is not a Location ID. A copied 2023 checklist is not the November 2025 GTCs.
| Input family | LLD object it must identify | Construction-issue evidence | Hold the release if |
|---|---|---|---|
| Award stack | Funded project identity | Register citing the executed subgrant clause | The sheet treats a 2023 checklist as if it still binds |
| Location file | Location ID to serving path | Issued segment that carries the Location ID | The crew sheet names a street but not the Location ID |
| Owner plant file | Structure ID and cable identity | Structure callout on the issued sheet | Owner ID and internal ID disagree and the sheet picked a winner |
| Locked HLD log | Route corridor and node class | Issue set that does not reopen a locked HLD decision | A pole move silently changes a serving-area claim |
| Permit or ROW grant | Occupied segment to authority | Permit reference on the issued segment | A crossing is issued with a blank permit row |
| Change-control path | Issued revision versus field observation | Disposition that names each required owner | A redline is treated as funded-scope approval |
Those six rows are the whole release. We do not add a seventh judgment column that lets a pretty alignment skip a blank. If a value is not on the executed agreement, the owner file, the locked HLD log, or the named permit, it is not a value.
Build the authority register first
The register names each claimed requirement and the clause that created it, and a public intake page such as our BEAD checklist is not that clause and cannot close a register row. It records the source version. When an Eligible Entity updates a template, the project can then decide whether that update applies to the existing agreement rather than silently replacing the baseline. We preserve the superseded copy. Deleting it is how a later reviewer loses the join.
2 CFR Part 200, Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards, as updated October 1, 2024, is the Uniform Guidance the November 2025 GTCs point at for subrecipient terminology. It does not become a fiber layer list. We cite it where the award points at it. We do not invent a CAD schema from it.
Move Location IDs onto route objects
NTIA's current BEAD Final Proposal Guidance for Eligible Entities, version 2.1, uses structured CSV files for subgrantees and deployment projects. Location rows sit in the same guidance set. It references the 10-digit FCC Registration Number and Location IDs. Those templates address Eligible Entity submissions, not a final fiber asset schema. They still show why project identity must remain stable across reporting systems.
Our issued segment carries the Location ID the location file already assigned. We do not mint a second ID because the CAD layer was easier to type. A street name can help a crew find the work. It cannot replace the identifier the award file will later ask for.
Keep owner structure IDs on the issued sheet
A pole owner ID and an internal design ID can both exist. They cannot be collapsed by picking the prettier one. The issued sheet shows both, or it shows the owner ID and a documented alias. Guessing is how the wrong structure enters the construction set.
Cable identity follows the same rule. The issued callout names the cable the owner file will later accept. A catalog description without that identity is a note. It is not an issued object.
Issue Route and Structure Objects, Not a Folder
A folder of PDFs is not an issue set. The issue set is the list of route segments and structures a crew may occupy under a named revision, with held remainder listed on the same transmittal. Everything else is held remainder. Both lists must be visible on the same transmittal.
For owners who want that issue set written end-to-end in-house, that is what our low-level design construction packages produce before any crew occupies a route segment. The service is the release gate, not a cleanup after a complete-looking folder has already been treated as plant.
Name the issued segment
An issued segment has a stable ID, a from-to, a construction method the owner actually authorized, and a revision. It points at the Location IDs it serves. It points at the permit or ROW grant that occupies it, or it carries a named hold. A highlighted alignment on a planning map is not that object.
We issue by segment so a held crossing does not freeze an unrelated span. That is a records choice. It is not a promise about duration.
Name the issued structure
An issued structure has the owner ID and the attachment the sheet actually authorizes. The cable or closure relationship that belongs on that structure sits on the same callout. Mid-span hardware still needs a structure or span ID the field can find. A pin with no owner ID is a hypothesis.
Make-ready status is a separate row when the pole owner requires it. We do not treat a loading sketch as an issued attachment. The pole owner's written grant is the occupancy evidence for that structure.
Keep held remainder on the transmittal
Held remainder is not a secret. The transmittal lists the object and the missing input. It names the owner of the hold. Accepted sheets around a closed workfront can keep moving. The held segment stays closed. Hide the hold and a crew will occupy it anyway.
The later OSP documentation construction handoff is a different object. This sheet only names what may be occupied now. Handoff records after the work stay off this page.
Change-Control Evidence When Field Conditions Move
A redline is an observation. It is not a scope change. The crew records the departure against a known segment or structure plus the issued revision the transmittal already named. A photo without that identity can document activity. It cannot prove which issued object moved.
That limitation becomes a construction hold, and this is the section where we refuse to treat the redline as funded-scope approval.
Keep three dispositions separate
In-house engineering writes the technical disposition: can the installed condition satisfy the accepted technical basis. The authorized program owner decides whether the funded scope moves. The permit authority decides its own occupancy. Those three owners stay linked. They are not one signature.
We retain the issued basis and the observed change. Each required disposition stays on the record before the installed model is allowed to look like the issued model the crew was told to occupy. Collapsing those states creates false certainty at the next report.
A field redline does not approve a funded-scope change. Record the observation. Send the technical question to engineering. Send the award question to the program owner named in the subgrant. Send the occupancy question to the permit authority. Do not let one markup close all three.
Preserve the issued revision
Superseded sheets remain controlled. The transmittal states which revision the crew may occupy. A later as-built process can inherit that lineage. It cannot invent it after invoices have already accumulated.
Candidly, our stable-ID model demands setup discipline. It does not rescue evidence that was never captured. When the award file is silent, we label the blank. We do not fill it with confidence.
We also do not publish a universal PE or milestone claim. A schedule figure is not a national rule here, and neither is a cost figure. Savings language stays off this page. Approval language stays off unless the executed subgrant already names it. The executed subgrant and the Eligible Entity's current instruction still control those duties where they exist. Our job is the join from those inputs to the objects a crew may occupy.
OSP LLD for BEAD Subgrantees: Release by Reader Type
New subgrantee with an executed agreement and no issue set yet: build the authority register and the identity model before anyone treats a planning alignment as plant. Freeze the location-file version. Freeze the HLD decision log. Do not accept a vendor's generic BEAD folder as proof those sources were covered. Require a clause-level crosswalk to the executed subgrant.
Established ISP extending an operating plant model: keep Location IDs and owner structure IDs inside the existing control structure. Let operations own the accepted network record. Let the grant team own the reporting view and the source crosswalk. Do not stand up a second GIS that mints new IDs the award file will not recognize.
Prime contractor issuing workfronts: put capture fields and naming rules in every relevant subcontract. Change thresholds belong in that same subcontract. Reject an issue transmittal that cannot name the held remainder. A complete-looking drawing set with a silent hold is how a crew occupies a crossing the permit row never closed, even when the rest of the workfront is ready.
When construction asks which spans it may occupy, we release only the segments and structures whose six rows already match the current revision, and we keep every other object on the hold list. Verbal interest in a future alignment stays off that list. The next revision can add a held object once the named source agrees, without reopening units that already match the current issued set.
Draftech writes that construction-issue list in-house. Active in 24 states. Available across all 50 U.S. states. If a live award file needs the LLD release crosswalk before crews occupy a route, reach out at info@draftech.com.
If osp lld for bead subgrantees 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.
Talk to our LLD team about construction-issue release. Request a review of award inputs before the first route segment is issued.
