Cell Tower Locations and Rooftop Antenna Sites in 2026

Start a Fairfax County telecom inventory with the FCC’s Antenna Structure Registration system and you get the registered-structure layer. The county’s telecom application requirements ask for something a tower count cannot describe: roof plans showing antennas beside penthouses and mechanical equipment. A maintenance territory needs those rooftop sites alongside the towers.

Asset Search by PorchRocket investigates visible telecom installations through aerial and satellite views cross-referenced with public records. Your team defines what counts. People review every candidate before delivery, including sites where the available evidence leaves one question for your team to settle through a records request or an authorized field check.

Ground Control by PorchRocket offers the standard property-list route through its visible antennas or dishes feature. Choose the workflow around the decision: a roofing prospect list, a telecom maintenance territory, a landlord’s equipment reconciliation or a site acquisition search. Each needs a different acceptance rule.

What does the FCC registry include and leave out?

ASR contains registered antenna structures, with registration generally tied to FAA obstruction-notification requirements; its coverage therefore differs from a census of cellular installations.

Under 47 CFR 17.4, an antenna structure requiring FAA notice because of physical obstruction must be registered, subject to the rule’s provisions. Voluntary registration is also possible. The trigger concerns the structure and its location.

The FAA notification criteria in 47 CFR 17.7 include construction exceeding 200 feet above ground and airport-related criteria that can apply below that height, plus exceptions. In 2026, “under 200 feet” is still an inadequate rule for deciding whether registration applies.

Missing ASR registration cannot settle whether a roof has antennas. Conversely, finding a registered structure does not establish that it fits your cellular maintenance offer. Section 17.4 requires registration before construction for proposed structures subject to the rule, so a registration alone also cannot establish that a tower has been built. Check construction status and site classification before routing the location to sales.

Keep the registration identifier beside the physical site identifier so an address change does not break the link to the federal record you checked. Record a missing registration as a missing field, then continue the investigation through local records and imagery.

I would keep separate totals for registered structures and reviewed telecom sites, then group the buying accounts beneath them before anyone uses the file to set a sales target. That prevents a manager from dividing sales results by a tower count that excluded the roofs the crew services. It also stops several antenna groups on one property from inflating the account forecast.

The counting method belongs in the file specification. Decide whether one building with equipment on opposite roof edges is one site with two equipment groups, and apply that decision throughout the territory. The aerial asset inventory hub explains how to count visible equipment separately from sites and buying accounts.

Rooftop antennas and water-tower mounts

Include building-mounted antennas and water-tower hosts when those structures fit the buyer’s service or acquisition brief, and give each host type its own acceptance rules.

Fairfax County’s application checklist calls for rooftop equipment plans and antenna mounting details and distinguishes existing-site photographs from simulations of proposed equipment, so a reviewer can compare what the applicant photographed with what it intended to install. They are different evidence.

Use the plans to guide the search, then compare them with dated observations. Mark the visible equipment groups on the building record and preserve the related application number. A proposed array and a visible array should have separate evidence dates, even when both documents use the same street address.

For a roofer, I would request a building-level list with the antenna location described relative to the roof work area. Ask the property manager for the current roof plan and the person responsible for telecom coordination before preparing the work scope. Keep that request attached to the property so the estimator receives it with the roof dimensions.

Oregon OSHA’s radiofrequency fact sheet describes concealed rooftop antennas and directs workers to obtain information from the building owner or property manager when antenna presence is unclear. Treat the inventory as an input to that coordination. A photograph cannot establish the site’s RF exposure conditions.

For a water-tower campaign, specify whether the assignment concerns the host structure, the antenna installation or both. Send the water-tower location search the host requirements and keep a linked telecom record for the antenna investigation. That lets a coating contractor and a telecom subcontractor use the same location without assigning identical scopes.

Require an unresolved answer when the available view does not settle equipment identity. A reviewer should be able to ask for a mounting plan or a permitted field photograph instead of forcing an uncertain shape into the accepted count.

Where can you find small cell locations?

City attachment maps and right-of-way records can identify small-cell candidates, but the map’s coverage and status definitions determine which locations count as installed sites.

The City of Bellevue’s small wireless facility page links a streetlight map of potential hosts with lease or reservation information. A potential host belongs in a site acquisition worksheet. Require additional installation evidence before assigning it to a maintenance campaign.

The City of Fremont’s public viewer guide makes the distinction explicit. Pending means the application is under review; reserved means the location has been approved for installation but further permits are needed; active means installed and operational in the city’s terminology.

Preserve the city’s original status and add your campaign disposition in another column. A reserved pole can fit a construction prospecting brief while failing an installed-equipment search. Reviewers need both fields to explain that result.

Record or observation	Candidate for installation work	Candidate for installed-site maintenance	Next evidence to request
Potential host shown on a city map	Keep for initial screening	Hold outside the installed count	Attachment application or installation record
Reserved location	Check project timing	Hold for installation confirmation	Issued permits and dated site evidence
City record marked active	Check for a separate expansion scope	Review against service requirements	Current equipment and purchasing contact
Visible equipment with unclear identity	Investigate the site type	Leave unresolved	Equipment plan or authorized field photograph

For a corridor search, identify poles by their local pole numbers where available and retain the coordinates. A postal address alone may leave the crew choosing between two attachments near the same intersection. Test that the receiving team can distinguish the two locations in its working map.

Set the geography tightly for the pilot. One connected corridor makes it easier to review ambiguous cases with the buyer than a scattered collection of points across several jurisdictions.

Who needs a reviewed telecom site list?

Maintenance contractors and property teams need different views of a telecom territory, with site acquisition firms using a separate definition for potential hosts.

A tower service contractor should define the work it wants before counting locations. “Find tower maintenance contracts” leaves the scope open. An instruction to find sites for grounds maintenance, fence repair or a specified equipment-service offer gives the reviewer a decision to support. Put excluded work in writing too.

For a site acquisition firm, keep engineering acceptance and commercial negotiations as later milestones, with parcel details and supporting evidence organized around the owner outreach needed to decide which potential hosts deserve the next review. Separate existing installations from possible hosts. A visible roof enters screening; the acquisition team decides whether it can support the project.

A landlord can use the inventory to reconcile observed equipment against its property file. Request the current equipment schedule and lease exhibits from the parties involved. Record discrepancies as questions with a responsible contact. The resulting worklist might concern an undocumented equipment group or a missing plan, rather than a new lease opportunity.

For commercial roofers, prioritize buildings that fit the roofing offer and carry visible antenna equipment. That gives the estimator a reason to ask about access and sequencing during qualification. Use a dedicated telecom search when the antenna requirements determine which buildings qualify.

I would give each buyer a separate view of a shared site table. The roofing team needs roof and property fields. The telecom service team needs the equipment classification and service buyer. The acquisition team needs host screening and owner outreach status. Preserve one site identifier across those views.

The installed-base mapping guide develops this approach for service networks working across equipment categories. It keeps an observed installation connected to the account and the offer that makes it worth pursuing.

For public building roof work or municipal maintenance solicitations, Bid Control by PorchRocket finds trade and area matches, with bid papers and addenda attached to each opportunity’s due date. Keep those advertised opportunities beside the private prospecting campaign, with their procurement deadlines assigned to a separate work queue.

How do you find cell towers near you on a map?

Start with the FCC registration lookup, add the local records relevant to your territory, then review physical evidence before treating a location as a qualified site.

Use the official ASR registration search as the federal record source. For a service business, define “near me” as the area your branch will accept for a site visit. Give the search team a boundary and any excluded accounts before expanding the investigation.

Add local telecom applications to the buyer’s existing site file, then check any published small-cell attachment records for additional candidates. Preserve where each candidate came from. That allows a manager to distinguish a location discovered through imagery from a familiar account appearing under a different address.

Next, place the candidate coordinates on the team’s working map and review them against the property. Join duplicate descriptions to one site record while retaining their source identifiers. Make a reviewer resolve address conflicts before a salesperson receives two versions of the same location.

Compare the latest available dated view with the records. Write down the observed support type and where the equipment sits. Keep installation status and equipment identity unresolved wherever the evidence does not settle them. The field request should explain what would settle the case.

For reception questions, use the FCC’s National Broadband Map instructions. Its mobile layers describe provider-reported outdoor or in-vehicle coverage. That information answers a service-availability question; a tower inventory answers a physical-location question.

I would run the first map review with the person assigning visits and ask them to open both a tower record and a rooftop record, then identify the next action using only the evidence supplied. Watch where they stop. If they have to repeat the location research, revise the delivery fields during the pilot.

Save the boundary with the edition date. When the branch later asks how many sites it added, the team can compare the same geography instead of mixing a larger territory with improved detection.

Evidence that makes a site ready for review

Each telecom record needs dated observations attached to a stable identifier, plus a reviewed answer and a clearly assigned next check.

The USGS explanation of aerial resolution says enlarging an image makes the object bigger without adding detail. I would therefore require evidence adequate for the classification, rather than accepting a closer crop as proof of equipment identity.

The investigation cross-references aerial and satellite views with public datasets, joining the evidence to property records and owner information. Search rules are set with the buyer’s experts, including edge cases. Every candidate receives human review before delivery, with the observations supporting its answer.

Agree on the counting unit before the pilot. Keep separate building records beneath a campus buying account, with equipment groups attached to the building that hosts them. Review those relationships in the pilot before applying the convention across the territory.

Field	What to record	How the receiving team uses it
Site identifier	Stable reference plus linked source identifiers	Joins later research and refresh editions
Location and parcel	Coordinates, site address where applicable and parcel reference	Assigns the property investigation
Observed host and equipment	Visible arrangement, with evidence references	Screens against the agreed service scope
Evidence dates	Observation date and record date in separate fields	Shows which fact was checked when
Owner context	Property owner plus separately researched roles	Routes the records request or qualification call
Disposition	Fits, rejects with reason, or unresolved	Assigns the campaign queue
Next check	One question and the evidence needed to answer it	Gives a field or records team a defined task

Ask for every disposition. Rejected candidates explain what was searched and why it failed the rules. Unresolved candidates preserve work that needs another view or a field check. Neither should disappear merely because the first delivery is being presented as a map of accepted sites.

For an unresolved roof, “obtain the current antenna mounting plan” is an assignable next step. “Needs more research” sends the problem back without a scope. Review several such rows with the buyer before accepting the pilot’s format.

Separate land ownership from purchasing authority

Keep the person approving work in a separate field from property and equipment ownership, then confirm the purchasing route before preparing a proposal.

Fremont’s viewer guide distinguishes the equipment owner from the service provider using that equipment. Apply the same discipline to your own site records: retain each researched role with its supporting record rather than copying one organization into every ownership field.

For a rooftop service offer, begin with the property contact and ask who handles the specified scope. Record whether the next request goes through property management or a separate telecom contact. Route the opportunity based on the answer, with the site identifier included in the handoff.

A landlord reviewing equipment should gather the installation plans and relevant property records before describing a discrepancy. Put the observation beside the document question. “The dated view shows a second equipment group; please identify its approved plan” gives the recipient something to investigate without asserting an ownership conclusion.

When a tower service contact buys for a portfolio, group the eligible locations beneath that account and request the onboarding requirements once, while retaining the individual scopes your crews would price for each site. Confirm the buyer’s territory. Flag locations handled by another purchasing team before booking the proposal meeting.

I would use this short call opening for a maintenance campaign:

We service telecom sites in this territory and are qualifying locations for our maintenance scope. Who handles contractor approval for this site? If your team manages several locations, which ones should be reviewed together?

Follow the opening with the narrow scope your crew performs and a request for the next document. Avoid asking the contact to interpret your entire spreadsheet over the phone.

Add the response date and next action to the account record. A named person without an assigned scope leaves the salesperson to restart qualification. The aerial prospecting workflow explains how to carry visible property evidence into the first conversation.

When is Ground Control the right starting point?

The fastest self-serve route to commercial buildings with visible antennas or dishes is Ground Control by PorchRocket, using the antennas or dishes filter alongside area, business type and building size. Commercial lists cost $10 to $20 per building, with the exact price shown before payment and orders starting at 10 buildings. Files arrive within 48 hours after payment, often sooner. Each property says why it matched. Wrong matches are credited back within 30 days. Owner information and decision-maker research are separately priced add-ons. These are target properties for your outreach; the owners have not requested quotes.

A roofer can combine the antennas or dishes feature with the roof age band and material needed for the re-roofing offer. The commercial roof lists page covers those building filters. Start with the roofs that fit the crew’s work, then use the visible equipment flag to prepare the qualification questions.

Write a short account brief for sales that names the roof offer and its matching features, then tells the salesperson which contact role to request. The building list supplies the starting properties. Your team confirms the work timing during outreach.

For a telecom site inventory, define requirements beyond the standard feature flag before commissioning the investigation. You might need rooftop and pole sites in separate layers, an existing-account exclusion file, or a particular unresolved-case procedure. Those belong in an Asset Search scope.

Use a small territory to test the choice. If the salesperson can qualify the intended offer from the standard property record, expand that order. If the job depends on a more detailed telecom classification, take the pilot through the custom search process.

What is one qualified telecom site worth?

Value each accepted site from the probability of winning its work and the account’s expected gross profit, then compare that value with total acquisition expense.

Say a two-crew telecom service contractor near Richmond works 240 accepted sites, each representing a different prospective buying account, and signs two new accounts. Each signed account brings $18,450 in annual service revenue against $12,070 in direct costs that include travel and crew time. Assume a full first service year, unchanged annual revenue and direct costs, and an 85% renewal probability at each anniversary. The horizon is three years, with no discounting of future cash flows. Fixed overhead and acquisition expense sit outside account gross profit.

Annual gross profit is $18,450 minus $12,070, or $6,380 per account. Expected three-year gross profit weights later years by the probability the account remains: $6,380 multiplied by (1 + 0.85 + 0.85 squared) equals $16,412.55.

Two accounts produce $32,825.10 in expected gross profit. Across the 240 accepted sites, that is $32,825.10 divided by 240, or $136.77 per accepted site before acquisition expense, rounded to cents. The accepted-site-to-account conversion is 2 divided by 240, about 0.83%.

The base-case funnel assumes 48 buying-contact conversations from 240 sites, a 20% conversation rate. One-third of those conversations produce 16 scoped opportunities; half reach proposal, giving eight proposals. Signing two means a 25% proposal-to-account rate. Track each stage separately. A weak conversation rate points to contact research or outreach; a weak opportunity rate points to the service offer or the site-selection rules.

Count each buying account once. If several accepted sites belong to one portfolio buyer, group them before applying the funnel and estimate the revenue of that portfolio’s scope. Multiplying a portfolio contract value by every site would overstate the opportunity.

Scenario	New accounts from 240 accepted sites	Total expected three-year gross profit	Gross profit per accepted site
Low	1	$16,412.55	$68.39
Base	2	$32,825.10	$136.77
High	3	$49,237.65	$205.16

Request a scoped quote from Asset Search and add the remaining acquisition expenses, including contact research and the salesperson’s qualification visits. Count the pilot credit once when calculating the total search expense. Keep that campaign budget separate from the direct costs of servicing signed accounts.

Customer lifetime value is the gross profit expected from an account over the chosen period. Customer acquisition cost is all acquisition spending divided by accounts won. For this base case, divide total campaign spending by two to get acquisition cost per account. Lead-list ROI is ($32,825.10 minus total campaign spending) divided by total campaign spending. Use the lead-list ROI calculator with your quote and outreach budget. The low case’s $16,412.55 is the ceiling for acquisition spending before the modeled gross profit is exhausted; set a lower budget to leave room for overhead and profit.

My decision rule is to approve the pilot only when the low case leaves enough gross profit for the acquisition budget and the branch can serve the accounts. Change the model for a one-time roofing project: use project gross profit and its probability of signing. Add future service only when the offer and delivery capacity support it.

More selling time from the same 40 hours

In the Richmond model, reducing desk qualification from 24 hours to eight doubles the records a salesperson can work within the same 40-hour work block.

Budget the hours first. Assume four distinct records worked per outreach hour and hold that pace constant across the two workflows, including time spent on attempts and notes. This table covers one salesperson’s 40-hour work block, not the full 240-site campaign. Purchased research belongs in the acquisition budget; the hours below measure the salesperson’s remaining desk work and outreach.

Use of the salesperson’s campaign time	Manual candidate research	Reviewed site file
Available hours	40	40
Desk qualification and record repair	24	8
Outreach hours remaining	16	32
Records worked at four per hour	64	128

The extra 64 records receive attention without adding sales hours. “Record worked” counts outreach activity; it does not count a conversation or a signed account. At four records per outreach hour, working all 240 sites requires 60 outreach hours, plus desk qualification. Budget that campaign time before assigning an account target to a single week.

For operations, attach a travel allowance to the territory before sales offers service. The account calculation already includes direct delivery costs. If an outlying site requires more travel than the allowance covers, revise that site’s margin before quoting it.

I would review those exceptions with the service manager once a week. A salesperson can group several eligible locations for a portfolio call, while operations checks which ones fit a service day. Give both teams the same site identifiers so the account promise matches the route being priced.

The economic gain starts with hours assigned to qualified properties. Measure desk time saved during the pilot, then replace the eight-hour assumption with the branch’s own result before ordering a larger territory.

How to build a telecom site list, step by step

Use an eight-step monthly playbook that takes a territory definition through a paid pilot, followed by assigned outreach or acquisition work.

1. Choose one decision in week one. Write the offer and buyer at the top of the request. For a maintenance campaign, name the service scope and the person likely to approve it. Keep potential hosts in a separate site acquisition brief.
2. Set the counting rule and boundary. Define a site, equipment group and account. Supply the branch territory and an exclusion file for current accounts. Ask operations to approve the proposed travel area before the pilot begins.
3. Commission an Asset Search telecom pilot. Use the telecom search request to specify towers, rooftop antennas, small cells or the combination required. Agree on dated evidence, owner fields and acceptance rules. Start with a small paid pilot credited toward the full order, delivered in your working format.
4. Reconcile public records with observations. Retain ASR and local application identifiers where found. Compare proposed plans with dated equipment evidence. Keep a city’s source status alongside the search disposition so reserved locations do not enter an installed-only campaign.
5. Review fits, rejects and unresolved cases in week two. Have your technical lead check the evidence and edge cases. Require a reason for every rejection and one settling check for each unresolved site. Approve the specification after reviewing those rows together.
6. Confirm the purchasing route in week three. Separate the property owner from the equipment and service roles. Assign a contact request and next action to every accepted priority site. Group portfolio locations while preserving the individual scopes.
7. Work the first campaign and record the funnel. Measure records worked, conversations, scoped opportunities, proposals and signed accounts. Compare desk qualification hours with the manual workflow. Use the account margin calculation before accepting distant or unusually demanding work.
8. Expand or refresh in week four. Resolve the pilot’s open questions and revise the rules where needed. Test the accepted file in the CRM or GIS system, then expand the territory using the approved specification. Set a refresh cadence around the next buying decision.

Test the import with a rooftop site and an unresolved case before moving the whole file. Check that the evidence date and disposition survive the import. A map pin without its review notes sends the next person back to desk research.

Assign one owner to the acceptance rules. When sales and operations disagree about a site, record the decision in that rule set and recheck comparable candidates. The next edition should carry the revised rule rather than relying on someone remembering the discussion.

Refresh schedules for telecom territories

Choose quarterly review for a territory prospecting book, then use more frequent monitoring when new installations or changes drive the next decision.

For ongoing work, Asset Search can deliver scheduled editions at intervals ranging from annual to weekly, alongside one-time searches. Near-real-time alerts fit watches where daily satellite coverage exists. Set the cadence around available evidence and the buyer’s response time during scoping.

For a maintenance contractor, I would start with quarterly territory review. Have sales update purchasing contacts as responses arrive, so a corrected contact reaches the account record without waiting for the next image review. A new equipment observation needs its own reviewed site record.

For a site acquisition team watching a corridor, use a more frequent change review when construction activity affects screening. Ask for before-and-after observation dates. Those dates establish the interval between views, while installation or operational dates remain separate record fields.

A revised service requirement can also trigger a new answer from Asset Search, often using evidence already on hand. When your service scope expands to another host type, ask for the revised rule to be applied to earlier candidates, including rejected sites. Preserve the previous answer with the edition history.

The asset monitoring guide covers ongoing territory watches. For telecom work, agree on the event that earns an alert, such as newly visible equipment or a removed installation, and who reviews it before sales assigns an opportunity.

Keep a change log tied to stable site identifiers. A location absent from one delivery needs an explained disposition or a boundary change. Ask the team receiving the file to reconcile those differences before replacing its prior edition.

Building your telecom territory with Asset Search

Asset Search investigates visible telecom sites against your team’s rules and delivers reviewed answers with the evidence needed to assign each location’s next action.

For a tower service contractor, I would scope per-accepted-result terms around the maintenance definition, with the evidence and handling of disputed matches agreed during a small paid pilot before expanding across the branch territory. A site acquisition firm paying for investigated candidates can choose per-completed-investigation terms. An ongoing territory watch fits a monitoring subscription.

The telecom request should specify what the receiving team gets:

• A search boundary covering the chosen corridor, counties or contiguous U.S. territory.
• Agreed definitions for towers, rooftop installations and small sites, including the difficult cases.
• Locations and parcels joined to owner information, with decision-maker contacts where they apply.
• Dated views and observed facts supporting each site’s reviewed disposition.
• Fits, rejects with reasons, and unresolved candidates with the field check that settles the question.
• CSV, Excel, GIS-ready files or an import for the team’s CRM, with refresh requirements agreed in scope.

The search goes beyond existing directories, investigating sites across brands and looking for installations missing from the buyer’s current records. Your experts define the question; people review the candidates before the file ships.

Use the two-minute telecom Asset Search request to describe what to find and where. PorchRocket returns a scope and quote, then the paid pilot ships in the agreed format. Start with one service corridor and expand from the accepted pilot.