Why BEAD make-ready is a data problem
The Broadband Equity, Access, and Deployment (BEAD) program, run by NTIA with $42.45 billion from the Infrastructure Investment and Jobs Act, funds broadband in unserved and underserved areas. Much of that fiber goes onto existing utility poles. Before a new line can attach, each pole is surveyed, the attachment is engineered, and any make-ready work to create space is estimated and done.
Every one of those steps runs on pole data: photographs, heights, attachments, clearances, and increasingly drone imagery and point clouds for each structure. On a large route that is thousands of poles and a great deal of data, collected in rural areas with weak connections and needed by engineers somewhere else.
The FCC clocks, as the rule now reads
The timelines are in the FCC's pole attachment rule, 47 CFR § 1.1411, most recently amended with effect from 7 May 2026. They apply to utilities the FCC regulates; some states set their own pole attachment rules instead.
| Stage | Standard order | Mid-sized order | Large order |
|---|---|---|---|
| Survey, after a complete application | 45 days | 60 days | 90 days |
| Estimate, after the survey | 14 days | 14 days | 29 days |
| Make-ready in the communications space, after notice | 30 days | up to 75 days | up to 120 days |
| Make-ready above the communications space, after notice | 90 days | 135 days | 180 days |
- A mid-sized order is more than the lesser of 300 poles or 0.5% of the utility's poles in a state, up to the lesser of 3,000 poles or 5%. A large order runs from there up to the lesser of 6,000 poles or 10%.
- A utility must tell the new attacher within 15 days of a complete application if it knows it cannot meet the survey deadline.
- A utility may withdraw an outstanding make-ready estimate beginning 14 days after presenting it.
- If a utility misses the survey, estimate or make-ready deadlines, the rule allows the new attacher to use self-help, including hiring a contractor to do the survey.
Where pole survey data travels
| Handoff | What moves | What delays it |
|---|---|---|
| Field crew to processing | Pole photographs, measurements, drone imagery and point clouds by route segment | Data waiting on laptops until crews return, uploads restarting on rural links |
| Processing to engineer of record | Extracted pole attributes, loading inputs, imagery for review | Large folders sent as many separate links, missing poles found late |
| Engineer to utility and attachers | Application packages, loading analysis, make-ready designs | Each utility's own portal and format, unclear records of what was sent when |
| Back to the field | Poles flagged for recapture or clarification | Requests that arrive after the crew has moved on |
Where the days get lost
- Data that sits on a laptop or in a truck for days before anyone in the office sees it.
- Uploads from rural sites that restart after every dropped connection.
- Deliverables split across dozens of links that an engineer has to collect and check.
- Missing or unusable poles discovered only when engineering starts, after the crew has left the area.
- No clear record of when data reached the engineer or the utility, so disputes about dates come down to memory and email searches.
A delivery routine that keeps up
- 1Name every file and folder by route segment and pole ID, the same way the engineer and utility will refer to them.
- 2Upload each day's capture from the field the same day, with a method that resumes after a dropped connection.
- 3Include a manifest of the poles captured and any the crew could not capture, so gaps are visible at once.
- 4Run a quick completeness check in processing the next morning and send recapture requests while the crew is still nearby.
- 5Deliver to the engineer of record as one package per segment, not a link per pole.
- 6Keep the delivery record: what was sent, to whom, and when it was downloaded.
A dated record of each handoff helps both sides. If a deadline is questioned, it shows when the data was delivered rather than relying on recollection.
Where Ripton Cloud fits
Ripton Desktop sends each segment's capture as one encrypted package from the field to a Ripton node on your own servers or cloud account, over a protocol built for high-latency, lossy links, resuming after interruptions. Packages go on to engineers of record, utilities and other attachers through scoped links they open in a browser without an account. Each package keeps a record of delivery, views and downloads.
Ripton Cloud moves and records the data. Pole attribute extraction, loading analysis and utility applications stay in the tools and portals you already use.
Sources
- 47 CFR § 1.1411, Timeline for access to utility poles
The current text of the FCC rule, retrieved 30 October 2026.
- NTIA: Broadband Equity, Access, and Deployment program
Program overview from the agency that runs BEAD.