Blueprint Playbook for TEP Group

Who the Hell is Jordan Crawford?

Founder of Blueprint. I help companies stop sending emails nobody wants to read.

The problem with outbound isn't the message. It's the list. When you know WHO to target and WHY they need you right now, the message writes itself.

I built this system using government databases, public records, and 25 million job posts to find pain signals most companies miss. Predictable Revenue is dead. Data-driven intelligence is what works now.

The Old Way (What Everyone Does)

Your GTM team is buying lists from ZoomInfo, adding "personalization" like mentioning a LinkedIn post, then blasting generic messages about features. Here's what it actually looks like:

The Typical TEP Group SDR Email:

Subject: Accelerating Your Infrastructure Deployment Hi [FirstName], I noticed on LinkedIn that your team is expanding into new markets. Congratulations on the growth! At TEP Group, we've helped companies like AT&T and Verizon accelerate their infrastructure deployment timelines by up to 30%. With over 1,000 professionals and 120,000 projects per year, we're the industry leader in telecommunications infrastructure. Our full-service capabilities include site acquisition, engineering, construction, permitting, and maintenance. We can help you: • Reduce time-to-deployment • Ensure regulatory compliance • Manage complex multi-site projects Would you be open to a 15-minute call next week to discuss how we can support your infrastructure goals? Best, [SDR Name]

Why this fails: The prospect is an expert. They've seen this template 1,000 times. There's zero indication you understand their specific situation. Delete.

The New Way: Intelligence-Driven GTM

Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.

1. Hard Data Over Soft Signals

Stop: "I see you're hiring compliance people" (job postings - everyone sees this)

Start: "Your Charlotte tower has a license expiring March 15, 2025 and sits in a SHPO high-sensitivity zone" (FCC database with exact dates and regulatory context)

2. Mirror Situations, Don't Pitch Solutions

PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use government data with dates, record numbers, facility addresses.

PVP (Permissionless Value Proposition): Deliver immediate value they can use today - analysis already done, deadlines already pulled, patterns already identified - whether they buy or not.

TEP Group Intelligence Plays

These messages demonstrate precise understanding of the prospect's current situation and deliver actionable intelligence. Every claim traces to specific government databases with verifiable record numbers.

PVP Public + Internal Strong (9.3/10)

Airport Proximity FAA Coordination Alert

What's the play?

Identify tower owners with expiring licenses where the tower sits within FAA airport proximity zones requiring Notice Criteria analysis. Cross-reference FCC license data with FAA airport location data to find specific towers requiring coordination.

Why this works

The exact address and airport proximity calculation proves you've done detailed research. Providing the specific FAA coordinator contact makes this immediately actionable and saves the recipient hours of work finding the right person.

Data Sources
  1. FCC Antenna Structure Registration (ASR) - antenna_structure_owner_name, location_coordinates, structure_height
  2. FCC Universal Licensing System (ULS) - license_expiration_date, licensee_name
  3. FAA Airport Location Database - airport proximity zones, coordinator contacts

The message:

Subject: Your tower at 1247 Highway 29 needs FAA coordination Your tower at 1247 Highway 29 in Charlottesville has a license expiring April 18, 2025 and sits within 3 miles of Charlottesville-Albemarle Airport. FAA Notice Criteria analysis takes 4-6 weeks and you have 16 weeks left. Want me to send the FAA coordinator contact at CHO?
DATA REQUIREMENT

This play requires internal client portfolio data (tower locations and license expiration tracking) combined with public FCC ASR/ULS databases and FAA airport proximity rules.

The value is in the synthesis: matching client assets with regulatory requirements and providing actionable contacts.
PVP Public + Internal Strong (9.4/10)

Tribal Consultation Section 106 Alert

What's the play?

Map BroadbandUSA grant fiber routes against tribal land databases to identify projects requiring NHPA Section 106 tribal consultation. Alert recipients to consultation requirements they may not be aware of, which add 60-90 days if not started early.

Why this works

Most grant recipients don't realize their route crosses areas requiring tribal consultation until they're already in permitting. Surfacing this requirement early with specific tribe names and THPO contacts prevents massive timeline delays and demonstrates expert-level regulatory knowledge.

Data Sources
  1. BroadbandUSA Award Recipients Database - awardee_organization_name, project_location, service_area_map
  2. Tribal Land Database - tribal consultation trigger zones
  3. THPO (Tribal Historic Preservation Officer) Contact Database

The message:

Subject: 3 tribal consultation requirements on your route Your fiber route passes through areas requiring consultation with the Cherokee Nation, Eastern Band Cherokee, and Catawba Nation under NHPA Section 106. Tribal consultation adds 60-90 days to your timeline if not started early. Want the tribal historic preservation officer contacts?
DATA REQUIREMENT

This play requires route mapping capabilities to overlay BroadbandUSA grant project routes with tribal land consultation trigger zones, combined with THPO contact database.

The value is in proactive identification of compliance requirements the recipient may not be aware of, preventing critical delays.
PVP Public + Internal Strong (9.2/10)

Wetland Zone Permit Mapping

What's the play?

Overlay BroadbandUSA grant fiber routes with National Wetlands Inventory database to identify Corps of Engineers permit requirements. Provide recipients with exact wetland crossing locations and Corps district contacts before they discover these requirements during construction.

Why this works

Wetland permits are a massive blind spot for fiber projects. Most operators don't know they're crossing wetlands until they're already in construction, causing 90-120 day delays. Delivering a map with coordinates and Corps contacts prevents this disaster and positions you as the expert who sees around corners.

Data Sources
  1. BroadbandUSA Award Recipients Database - awardee_organization_name, project_location, service_area_map
  2. National Wetlands Inventory (NWI) Database - wetland locations and classifications
  3. US Army Corps of Engineers District Contact Database

The message:

Subject: I found 11 wetland zones in your fiber route Your 47-mile fiber route crosses 11 identified wetland zones in the National Wetlands Inventory database. 8 of those require Corps of Engineers permits that take 90-120 days in your region. Want the map with coordinates and Corps district contacts?
DATA REQUIREMENT

This play requires GIS mapping capabilities to overlay grant award fiber routes with NWI wetland data, plus Corps of Engineers district contact database.

The synthesis of route data + wetland locations + permit requirements is unique and highly valuable for preventing project delays.
PVP Public + Internal Strong (9.1/10)

Portfolio License Renewal Timeline Analysis

What's the play?

Identify tower owners with multiple expiring licenses in 2025 and map each tower against historical permit approval timelines and environmental review triggers. Deliver a comprehensive spreadsheet showing at-risk towers and recommended submission start dates.

Why this works

Multi-tower operators face complex coordination challenges when licenses expire across different jurisdictions. Delivering a ready-made timeline analysis saves them days of planning work and identifies specific risk areas requiring immediate attention. This is consulting-level value delivered upfront.

Data Sources
  1. FCC Universal Licensing System (ULS) - license_expiration_date, licensee_name, geographic_area
  2. FCC Antenna Structure Registration (ASR) - antenna_structure_owner_name, location_coordinates, registration_number

The message:

Subject: I mapped your 23 towers expiring in 2025 You have 23 tower licenses expiring between January and June 2025 across 8 states. 14 of them are in jurisdictions where your past permits took 120+ days and 6 have environmental review triggers. Want the spreadsheet with timelines and next steps?
DATA REQUIREMENT

This play requires internal tracking of client portfolio data (tower locations, historical permit timelines by jurisdiction) combined with FCC ULS/ASR databases.

The value is in the portfolio-level synthesis and timeline planning, which prevents license expiration penalties.
PVP Public + Internal Strong (9.1/10)

Environmental Consultant Performance Benchmarking

What's the play?

Track environmental consulting firm performance by jurisdiction - which firms get NEPA approvals fastest in specific counties. Deliver jurisdiction-specific consultant comparisons with average approval times and contact information to BroadbandUSA grant recipients.

Why this works

Consultant performance data is nearly impossible for operators to access. Choosing the wrong environmental firm can add months to project timelines. Providing verified performance benchmarks in the recipient's specific counties enables better vendor selection and directly improves project execution speed.

Data Sources
  1. BroadbandUSA Award Recipients Database - awardee_organization_name, project_location
  2. County Environmental Review Records - consultant names, approval timelines

The message:

Subject: Your environmental consultant comparison I pulled the environmental firms that worked your 6 counties in 2024 and tracked their average NEPA approval times. Eco-Tech averaged 52 days while Regional Environmental took 118 days in the same jurisdictions. Want the consultant comparison with contact info?
DATA REQUIREMENT

This play requires internal database tracking environmental consultant performance by jurisdiction with approval timelines, combined with BroadbandUSA grant location data.

This proprietary performance benchmarking data is unique and highly actionable for recipients.
PVP Public + Internal Strong (9.0/10)

License Renewal Gantt Chart with Risk Assessment

What's the play?

Build a comprehensive Gantt chart for tower owners with multiple 2025 license expirations, mapping each license against permit history, environmental triggers, and jurisdiction processing times. Identify specific at-risk towers and recommended submission start dates.

Why this works

This is project management consulting delivered for free. The Gantt chart format is immediately usable for planning and resource allocation. Identifying at-risk towers creates urgency while the deliverable format (ready-to-use planning document) demonstrates immediate value whether they respond or not.

Data Sources
  1. FCC Universal Licensing System (ULS) - license_expiration_date, licensee_name
  2. FCC Antenna Structure Registration (ASR) - antenna_structure_owner_name, location_coordinates

The message:

Subject: I built your license renewal timeline for 2025 You have 23 licenses expiring in 2025 and I mapped each one against permit history, environmental triggers, and jurisdiction timelines. 6 of them are at risk of missing deadlines based on current processing times. Want the Gantt chart showing when to start each submission?
DATA REQUIREMENT

This play requires internal client portfolio data and historical jurisdiction processing time tracking, combined with FCC ULS/ASR databases.

The Gantt chart synthesis with risk identification is ready-to-use project planning value.
PVP Public + Internal Strong (8.9/10)

County-Specific Permit Roadmap with Application Checklists

What's the play?

Create county-by-county permitting guides for BroadbandUSA grant recipients showing jurisdiction-specific requirements, average approval times, and common rejection reasons. Include application checklists to reduce permit deficiency risk.

Why this works

Multi-county fiber deployments face wildly different permitting requirements across jurisdictions. Operators waste weeks researching county rules and often submit incomplete applications. Delivering ready-made checklists that prevent rejections and identify bottleneck counties enables proactive resource allocation and timeline planning.

Data Sources
  1. BroadbandUSA Award Recipients Database - awardee_organization_name, project_location
  2. County Permit Records - approval timelines, rejection reasons, application requirements

The message:

Subject: Your county-by-county permitting roadmap I broke down your 6-county fiber deployment by permit requirements, average approval times, and common rejection reasons. Jefferson and Boone Counties will be your bottlenecks with 120+ day timelines. Want the county playbook with application checklists?
DATA REQUIREMENT

This play requires internal database of jurisdiction-specific permit requirements, approval timelines, and common deficiency patterns by county.

This jurisdiction-specific playbook enables proactive planning and reduces permit rejection risk.
PQS Public + Internal Strong (8.7/10)

BroadbandUSA Grant Recipients Entering Active Construction in High-Risk Permitting Jurisdictions

What's the play?

Target BroadbandUSA and USDA ReConnect grant recipients with construction start dates in the next 90 days, specifically in counties where TEP's historical data shows high environmental permit failure rates (40%+ denial/delay rate due to NEPA non-compliance).

Why this works

Grant recipients are under extreme timeline pressure to meet federal funding milestones. Surfacing specific county-level compliance risks with verifiable permit denial rates creates immediate urgency. The recipient realizes you've done research they haven't, identifying a risk that could jeopardize their entire federal funding draw-down schedule.

Data Sources
  1. BroadbandUSA Award Recipients Database - awardee_organization_name, award_amount, project_location, project_start_date, project_end_date
  2. USDA ReConnect Program - project_awardee, rural_county, project_timeline

The message:

Subject: Your $4.2M BroadbandUSA grant enters construction February 2025 Your BroadbandUSA award for rural fiber in Appalachian Virginia begins active construction February 2025 across 6 counties. 4 of those counties denied or delayed 40% of telecom permits in 2024 due to environmental non-compliance. Who's handling your NEPA coordination?
DATA REQUIREMENT

This play requires internal tracking of permit approval/denial rates by county with root cause analysis (e.g., "40% denied for incomplete wetland surveys").

Combined with public BroadbandUSA grant data to identify at-risk projects with specific timeline pressure.
PQS Public + Internal Strong (8.6/10)

Tower Owners Approaching FCC License Renewal with Permitting Bottleneck History

What's the play?

Target wireless carriers and tower owners with FCC licenses expiring in 6-12 months in specific counties where TEP's project data shows high Section 106 cultural resource review trigger rates and long SHPO approval timelines.

Why this works

The specificity of naming exact tower locations (Charlotte, Raleigh, Durham) and SHPO high-sensitivity zones proves you've done detailed research on their portfolio. The 60-90 day timeline for cultural assessments combined with Q2 2025 license expirations creates legitimate mathematical urgency - they need to start NOW.

Data Sources
  1. FCC Universal Licensing System (ULS) - license_expiration_date, licensee_name, geographic_area
  2. FCC Antenna Structure Registration (ASR) - antenna_structure_owner_name, location_coordinates, registration_number

The message:

Subject: 3 of your towers need cultural assessments by January Your Charlotte, Raleigh, and Durham towers all have licenses expiring Q2 2025 and sit in SHPO high-sensitivity zones. Cultural resource assessments take 60-90 days in North Carolina right now. Is someone coordinating the SHPO submissions?
DATA REQUIREMENT

This play requires internal tracking of client tower portfolios cross-referenced with SHPO jurisdiction maps and historical Section 106 approval timelines by state.

The synthesis of portfolio data + regulatory geography + historical timelines creates the urgency calculation.
PVP Public + Internal Strong (8.6/10)

Certified Climber Capacity Analysis for License Renewals

What's the play?

Calculate total certified climber hours required for tower owners with multiple expiring licenses, then alert them to regional crew booking constraints. Offer to check internal crew availability to help them avoid labor bottlenecks during high-demand renewal periods.

Why this works

The specific hour calculation (340-400 hours) proves you've done detailed capacity planning they haven't thought about yet. Certified climber shortages are a real fear for tower operators, and the 60-90 day booking timeline creates urgency to secure resources now before crews sell out.

Data Sources
  1. FCC Universal Licensing System (ULS) - license_expiration_date, licensee_name
  2. FCC Antenna Structure Registration (ASR) - antenna_structure_owner_name, structure_height

The message:

Subject: I found your certified climber gap for renewals Your 23 tower renewals will need structural assessments and antenna work requiring 340-400 hours of certified climber time between January and April. Certified climbers in your regions are booking 60-90 days out right now. Want me to check if our field teams have capacity in your timeline?
DATA REQUIREMENT

This play requires labor capacity modeling (hours per tower by height/complexity) and internal crew booking visibility by region, combined with FCC license expiration data.

The value is in capacity forecasting that prevents labor bottlenecks during critical renewal windows.
PQS Public + Internal Strong (8.4/10)

Tower Owners with Expiring Licenses Facing Historical Permit Delays

What's the play?

Identify tower owners with FCC licenses expiring in 6 months or less where their historical permit applications in that jurisdiction averaged 120+ days to approval. Alert them that their past timeline performance puts them at risk of missing renewal deadlines.

Why this works

The 147-day average is specific to THEIR past applications, not industry benchmarks. The math is simple and urgent: with 120 days left and a 147-day average approval time, they're mathematically at risk of missing their deadline. The routing question makes response easy.

Data Sources
  1. FCC Universal Licensing System (ULS) - license_expiration_date, licensee_name
  2. FCC Antenna Structure Registration (ASR) - antenna_structure_owner_name, registration_number

The message:

Subject: Your WPXJ-TV license expires March 2025 Your WPXJ-TV license expires March 15, 2025 and your last 3 permit applications averaged 147 days to approval. With 120 days left, that timeline puts you past your renewal deadline. Who's managing the environmental review submission?
DATA REQUIREMENT

This play requires internal tracking of past permit approval timelines by client and jurisdiction, showing average days-to-approval for the recipient's historical applications.

The historical performance data creates urgency based on THEIR past experience, not generic industry timelines.
PQS Public + Internal Strong (8.4/10)

BroadbandUSA Grant Recipients in USFWS Endangered Species Habitat Zones

What's the play?

Cross-reference BroadbandUSA grant project locations with USFWS endangered species habitat maps to identify fiber deployments requiring biological assessments. Alert recipients to USFWS consultation requirements that add 45-90 days if not submitted early.

Why this works

Naming specific endangered species (Indiana bat, running buffalo clover) proves this isn't generic environmental advice - you've mapped THEIR project area. USFWS biological assessments are a real compliance requirement that most grant recipients don't discover until they're already delayed. The yes/no question makes response easy.

Data Sources
  1. BroadbandUSA Award Recipients Database - awardee_organization_name, project_location, service_area_map
  2. USFWS Endangered Species Critical Habitat Maps

The message:

Subject: Your grant area has 6 endangered species listings Your fiber deployment zone in southwestern Virginia overlaps with 6 federally listed endangered species habitats including Indiana bat and running buffalo clover. USFWS biological assessments take 45-90 days and are required before construction permits. Is your USFWS consultation already submitted?
DATA REQUIREMENT

This play requires GIS mapping to overlay BroadbandUSA grant routes with USFWS endangered species habitat maps, plus knowledge of consultation timelines by species/region.

The habitat overlay with specific species identification prevents compliance surprises during construction.
PQS Public + Internal Strong (8.5/10)

Grant Recipients Deploying in High-Rejection Counties with Specific Deficiency Patterns

What's the play?

Target BroadbandUSA grant recipients with construction starting in 90 days in counties where TEP's data shows specific permit rejection patterns (e.g., "12 of 29 permits rejected for incomplete wetland surveys"). Alert them to start environmental assessments NOW to avoid the same rejection.

Why this works

The specific rejection rate (12 of 29 permits) and exact reason (incomplete wetland surveys) is verifiable and scary. Knowing the root cause of rejections in their specific county lets them file correctly the first time. The timeline math (90 days to construction start, 45-60 days for wetland assessment) creates clear urgency.

Data Sources
  1. BroadbandUSA Award Recipients Database - awardee_organization_name, project_location, project_start_date
  2. County Permit Records - permit outcomes by type, rejection reasons

The message:

Subject: Jefferson County rejected 12 fiber permits in 2024 Your grant covers 47 miles of fiber through Jefferson County where 12 of 29 telecom permits were rejected last year for incomplete wetland surveys. Your construction start is 90 days out and wetland assessments take 45-60 days in West Virginia. Is your environmental review already underway?
DATA REQUIREMENT

This play requires internal database of permit outcomes by jurisdiction with specific denial reasons and typical environmental assessment timelines.

The rejection pattern analysis helps recipients file correctly the first time, avoiding costly delays.
PQS Public + Internal Strong (8.3/10)

Tower Portfolio Coordination Strategy for Clustered License Expirations

What's the play?

Identify tower owners with multiple licenses expiring within a 3-month window in the same state, creating coordination complexity. Ask strategic question about whether they're coordinating renewals together (more efficient) or separately (risks inconsistent outcomes).

Why this works

Naming specific tower lessor (American Tower) and exact expiration window (January 15 - March 30) shows detailed portfolio knowledge. The coordination question reveals strategic understanding of portfolio management challenges and makes the recipient think about their approach, positioning you as an expert advisor.

Data Sources
  1. FCC Universal Licensing System (ULS) - license_expiration_date, licensee_name, geographic_area
  2. FCC Antenna Structure Registration (ASR) - antenna_structure_owner_name, location_coordinates

The message:

Subject: Your American Tower portfolio in Georgia expires Q1 Your 8 towers leased from American Tower in Georgia all have licenses expiring between January 15 and March 30, 2025. Georgia EPD environmental reviews took 89 days average in 2024 for telecom projects. Are you coordinating these renewals together or separately?
DATA REQUIREMENT

This play requires internal tracking of client tower portfolios by lessor/state and state-specific environmental review timeline data.

The portfolio view with coordination strategy question demonstrates understanding of operational complexity.
PQS Public + Internal Strong (8.3/10)

Recent Regulatory Changes in Grant Recipient Project Counties

What's the play?

Monitor county-level telecom permit rule changes and alert BroadbandUSA grant recipients when their project counties add new requirements (like traffic impact studies for state highway crossings) that their engineering team may not know about yet.

Why this works

Recent rule changes (December 3, 2024) are easy to miss but can cause permit rejections. Naming the specific highways in their grant route (Highway 19 and Highway 61) proves you've mapped their project against the new requirements. This prevents a costly permit rejection and positions you as monitoring regulatory changes on their behalf.

Data Sources
  1. BroadbandUSA Award Recipients Database - awardee_organization_name, project_location, service_area_map
  2. County Municipal Code Updates - recent permit rule changes

The message:

Subject: Tazewell County changed fiber permit rules December 2024 Tazewell County updated telecom permit requirements on December 3, 2024 adding mandatory traffic impact studies for routes crossing state highways. Your grant route crosses Highway 19 and Highway 61 in Tazewell. Does your engineering team know about the new TIS requirement?
DATA REQUIREMENT

This play requires monitoring of jurisdiction regulatory changes and route mapping to cross-reference new requirements with client project routes.

Proactive regulatory monitoring prevents permit rejections from rule changes the recipient hasn't discovered yet.
PQS Public + Internal Strong (8.2/10)

Towers in Historic Districts with Outdated Cultural Resource Surveys

What's the play?

Identify tower owners with assets in National Register historic districts where past cultural resource surveys are over 5 years old. Alert them that state SHPO offices require updated surveys during license renewals, creating a timeline requirement they may not be tracking.

Why this works

The specific tower (WJHL in Johnson City), exact survey date (2018), and state-specific SHPO rule (Tennessee requires updates over 5 years) demonstrates detailed asset tracking and regulatory knowledge. The routing question makes response easy while positioning you as tracking compliance details they may have forgotten.

Data Sources
  1. FCC Universal Licensing System (ULS) - license_expiration_date, licensee_name
  2. FCC Antenna Structure Registration (ASR) - antenna_structure_owner_name, location_coordinates
  3. National Register of Historic Places - historic district boundaries

The message:

Subject: Your WJHL tower needs historical survey update Your WJHL tower in Johnson City sits in a National Register historic district and your last cultural resource survey was completed in 2018. Tennessee SHPO requires updated surveys for sites over 5 years old during license renewals. Who should I connect with about scheduling the updated survey?
DATA REQUIREMENT

This play requires tracking of client assets with past survey dates, cross-referenced with National Register historic district maps and state-specific SHPO requirements.

The survey aging calculation prevents compliance surprises during renewal processes.

What Changes

Old way: Spray generic messages at job titles. Hope someone replies.

New way: Use public data to find companies in specific painful situations. Then mirror that situation back to them with evidence.

Why this works: When you lead with "Your Charlotte tower has a license expiring March 15, 2025 and sits in a SHPO high-sensitivity zone" instead of "I see you're hiring for infrastructure roles," you're not another sales email. You're the person who did the homework.

The messages above aren't templates. They're examples of what happens when you combine real data sources with specific situations. Your team can replicate this using the data recipes in each play.

Data Sources Reference

Every play traces back to verifiable public data. Here are the sources used in this playbook:

Source Key Fields Used For
FCC Antenna Structure Registration (ASR) Database registration_number, antenna_structure_owner_name, licensee_name, structure_height, location_coordinates Identifying tower owners and locations for license renewal tracking
FCC Universal Licensing System (ULS) licensee_name, license_type, license_status, grant_date, expiration_date, geographic_area Tracking wireless carrier licenses and expiration dates
FCC Broadcast Station Query (AM/FM/TV) station_call_letters, licensee_name, city_and_state, frequency, license_status, license_expiration_date Identifying broadcast station operators with expiring licenses
BroadbandUSA Award Recipients Database awardee_organization_name, project_location, award_amount, project_type, project_start_date, project_end_date Identifying fiber infrastructure projects entering construction phase
NEVI Awards Dashboard state, project_developer, charging_corridor, number_of_sites, award_amount, project_status Tracking EV charging infrastructure grant recipients and deployment timelines
Alternative Fuels Data Center (AFDC) station_name, operator_name, network_name, state, charger_count, open_date, funding_source Census of public EV charging stations with operator information
USDA ReConnect Program project_awardee, rural_county, project_type, funding_amount, project_timeline, service_addresses Rural broadband projects with federal funding and timelines
National Wetlands Inventory (NWI) wetland_type, location_coordinates, classification Identifying wetland zones requiring Corps of Engineers permits
USFWS Endangered Species Habitat Maps species_name, critical_habitat_boundaries, consultation_requirements Identifying projects requiring USFWS biological assessments
National Register of Historic Places historic_district_name, boundary_coordinates, SHPO_jurisdiction Identifying towers requiring cultural resource assessments