Broadband Coverage & Unserved Area Mapping Services
Define your service area with reconciled coverage boundaries, location records and eligibility data. Draftech's in-house GIS team keeps the dataset current as program data and your network footprint change.
Unserved area mapping services for a defensible project boundary
Draftech delivers coverage-area boundaries, unserved- and underserved-location analysis, address-level coverage layers and recurring dataset updates. Our unserved area mapping services support fiber ISPs, BEAD subgrantees, electric and telecom cooperatives, state broadband offices and regional planning bodies that need a consistent basis for defining investment areas.
GIS production and engineering are 100% in-house. One accountable team reconciles the program's current location and eligibility data with your service-area records, checks the result against available engineering and field information, and prepares the agreed delivery files. Questions about a boundary or a location count come back to the team that built the dataset.
This engagement is the coverage and unserved-location side of Draftech's GIS mapping services.
Stop conflicting records from defining your funded area
A coverage picture assembled from separate shapefiles, address lists and spreadsheets can carry contradictions into a grant review. An eligible location disappears because the address list predates the program data. A serviceable location lands in the wrong footprint. Overlapping boundaries count the same location twice. The location count in the application no longer matches the count derived from the boundary.
When a program office, competing provider or local government questions those inconsistencies, the project team must revisit its boundary and location counts. Work already used to define the project may need to be redrawn and resubmitted.
Draftech builds the coverage dataset around an agreed data model and program data. We match each address in the client's list to a program location by location identifier or geocoded address, then assign each matched location to a single proposed project area. Duplicate assignments, unmatched addresses and locations outside every boundary go on an exceptions list for the client to resolve before relying on the boundary for an application or award decision.
What your mapping engagement delivers
Our broadband coverage mapping services produce files your GIS staff and program team can use together. The scope defines the geographic area, source records, receiving platform and update needs before production begins.
- Coverage-area and service-area boundary mapping: Spatial boundaries reconciled with the location records they include, so mapped areas and associated counts describe the same scope.
- Unserved- and underserved-location analysis: Analysis built on program data, showing the locations relevant to your proposed investment area.
- Serviceable-location datasets and address-level coverage layers: Structured records formatted for your GIS platform or the program's required template, with one record per location and each location assigned to a single project area.
- Location-status documentation: The record or field basis behind a location's classification, prepared for a state grant program review or challenge.
- Recurring dataset updates: Refreshed coverage boundaries and location records as program data or your network footprint changes, keeping the existing dataset useful through successive data cycles.
A boundary-only assignment and a recurring address-level mapping engagement require different inputs and effort. We establish which outputs you need and where a missing source record could limit the result.
How we build and reconcile your coverage dataset
Establish the working inputs
We begin with the program's location data, your existing coverage and service-area files, and the requirements of the receiving platform. You identify the project area under consideration and supply the engineering, field and as-built records available for comparison.
The agreed model defines how a location relates to the coverage area and proposed service boundary. It also establishes which information the delivery must contain. This gives the production team a common basis for handling an address list and a spatial boundary that do not initially agree.
Compare the map with the supporting records
Draftech builds or updates the dataset, then checks its location assignments against those records. We examine mismatches that affect the coverage picture: locations omitted from the proposed area, overlapping assignments, and records whose stated coverage does not agree with the supporting information.
For example, an address may appear in a provider spreadsheet while falling outside the supplied service-area boundary. We compare the available records to identify the inconsistency and the information needed to resolve it.
Deliver files for the receiving team
The output follows the client's GIS requirements or the grant program's template. We agree those requirements at scoping so the receiving team gets the required location information with the mapped boundary.
Teams coordinating a broader grant package can use our guide to BEAD GIS deliverables and QA for the surrounding documentation discipline. This mapping engagement supplies the coverage and location dataset that those broader records draw on.
Documentation for a state program review or challenge
A reviewer questioning a location's classification needs the supporting record behind it. Draftech prepares location-status documentation that identifies the record or field basis used in the mapping work.
We scope the documentation around the locations in question and the records available to support them. If the supplied information does not establish the classification, the gap stays flagged in the documentation for you to resolve.
Draftech prepares the documentation; your team handles submission and any required certification, and the program office determines the outcome. For the separate record-management issues involved in a challenge, see our BEAD challenge record guide.
Keep coverage current as the project changes
A dataset can become outdated while an application or award review is still underway. Updated program data may change the locations under consideration, and new network information may change the coverage picture. Rebuilding the map at every deadline repeats the same reconciliation work and creates opportunities for records to diverge.
Draftech provides recurring updates to the agreed dataset as those inputs change. Each cycle compares the new information with the existing coverage and location records, updates affected assignments and boundaries, and refreshes the delivery files. You can assess the changed area using the same model you already understand.
The update arrangement identifies who supplies program data, who provides network changes and when refreshed files are needed. For broader management of network records, our guide to maintaining network GIS records addresses the surrounding discipline.
Mapping scope for providers, cooperatives and public agencies
For ISPs and subgrantees, the starting question is whether the proposed service boundary and location list agree well enough to support review before and during award. The resulting dataset feeds the engineering exhibits behind ReConnect, RDOF and federal broadband grant engineering. For cooperatives, the question is where unserved territory falls inside the distribution footprint, and the dataset supports electric cooperative broadband engineering ahead of a fiber buildout. State broadband offices and regional planning bodies need an independent coverage and unserved-location layer to compare areas for investment.
Our broadband eligibility mapping services start with those decisions and the applicable program data. The receiving team's needs determine the mapped area and delivery format, while the available supporting records determine which coverage questions can be resolved.
An ongoing distribution asset dataset belongs under electric utility GIS mapping. A backlog of legacy drawings and records belongs under as-built and CAD-to-GIS conversion.
Broadband Coverage & Unserved Area Mapping Services FAQ
What should we provide to scope the work?
Bring your current service-area boundaries, address lists, the program's current location and eligibility data, and any required delivery template. Note which design and field records you can share for comparison. Include the review deadline and expected update needs.
Can a public agency commission an independent layer without a provider network footprint?
Yes. A public agency can commission an independent coverage and unserved-location layer for investment planning using program data and available supporting records. We scope the layer around those inputs and the agreed delivery requirements, with gaps in the evidence flagged in the location-status documentation.
How is the engagement sized when only part of a proposed project area needs review?
We define the boundary segment and associated location records that need reconciliation. The scope accounts for overlapping assignments and records outside that boundary where they affect the location count, with effort based on the available inputs and required outputs.
Can one dataset feed both our GIS and the program's template?
Yes. When your GIS schema and the program's required template differ, we agree at scoping which structure governs the location records and produce the other delivery from the same dataset. Both deliveries then carry the same boundaries and location counts.
Scope your coverage and unserved-area dataset
Bring the boundary your team needs to defend, the location records behind it and the format your reviewers expect. Draftech will scope the mapping and the update cycle needed to keep those records usable.
Contact Draftech about your coverage mapping scope