Spectrum License Management Software: When One Person Remembers Every Renewal and Buildout Date

Why a spectrum portfolio outgrows the spreadsheet, then quietly stays there

The asset on the balance sheet is often the most valuable thing the company owns, and the operational record of it is a workbook with a tab per service and a column called notes. That is not negligence, it is history. The portfolio started small, one person built the sheet, the same person filed every renewal on time for a decade, and nothing bad happened. Then the company acquired a regional operator with a hundred more call signs, deployed private network spectrum at industrial sites, and picked up microwave paths for backhaul that each carry their own coordination history. The sheet still exists. It is now the single point of failure for an asset class where the failure mode is forfeiture.

The specific danger in spectrum is that nothing warns you. A missed maintenance window on a tower produces a visible defect. A missed buildout milestone produces silence, followed much later by a licence that automatically terminates or a market that has to be handed back. The regulator does not chase you. The clock runs whether or not anyone is watching it, and the obligation was written in an order issued years before the person currently responsible joined.

Three things collapse at once as a portfolio grows. Deadlines multiply across licence terms, interim and final buildout milestones, coordination response windows, and annual or periodic filings, and they are all in one person's head. The evidence needed to prove an obligation was met lives in an engineering tool nobody in the regulatory team can operate. And the correspondence trail with neighbouring licensees, which is the entire basis for interference protection, lives in an email inbox that leaves with the employee.

Problem 1: the obligation is a coverage proof, not a date on a calendar

Putting a renewal date in a shared calendar is the version of this problem everyone solves first, and it is the easy half. The hard half is that many licences carry a performance condition: coverage of a share of the population in the licensed area by a milestone, or a substantial service showing, or a deployment count for a private network. Proving it means running coverage from your own planning tool, intersecting the result with census or market geography, and producing a defensible number with the propagation assumptions documented.

That is an engineering exercise, so it happens once, close to the deadline, under pressure, by someone who then exports a map to PDF and emails it to the regulatory lead. The number that went into the filing and the assumptions behind it are now unreproducible. When a challenge or an audit arrives two years later, you are trying to rebuild a calculation from a picture.

What a custom build does: hold the obligation as a structured rule attached to the licence, with its measurement geography, its threshold and its deadline, and then hold the evidence as data rather than as an attachment. Coverage comes from your existing planning environment, whether that is LS telcom, ATDI or an internal tool, imported as a polygon or raster with the propagation model, terrain data and clutter settings recorded alongside it. The system computes the covered population against the licensed area and stores the result with a timestamp and the parameter set. Then the position is visible continuously rather than annually, which means a market that is drifting short of its milestone becomes a capital planning decision two years out instead of a crisis two months out. That single change is usually the reason this project gets funded.

Problem 2: coordination lives in an inbox and interference protection lives with it

Microwave paths, and increasingly shared spectrum deployments, depend on a correspondence record: notices sent, objections received, resolutions agreed, conditions accepted. Industry practice for terrestrial microwave coordination follows the recognised TIA bulletin process, and the value of that process is entirely in the record it produces. If a neighbouring licensee later claims your path is causing harmful interference, your defence is the notice you sent and their lack of objection within the window.

Comsearch and the other coordinators do the coordination work well and you should keep using them. What they do not do is hold your side of the file for the life of the licence, joined to the path, the site, the equipment and the licence record. So the notices sit in an inbox, and when the engineer who ran that project leaves, the file leaves too.

What a custom build does: attach correspondence to the asset rather than to a person. Every coordination notice, response and resolution is filed against the path or site with its dates, so the response window is tracked as an obligation with a clock rather than as an email waiting for someone to remember. Conditions accepted during coordination, such as an azimuth restriction or a power limit, get recorded as constraints on that asset, which is what stops a future engineer from making a change that quietly breaks an agreement made years earlier. That is not a document management problem, it is a constraint that has to be enforceable at the point of change.

Problem 3: your holdings record and the regulator's record drift apart

The regulator holds the authoritative version. In the United States that is the FCC's licensing database, publicly searchable and updated as filings are processed. Your spreadsheet holds your version. The two disagree more often than anyone expects, because assignments and transfers from an acquisition process at their own pace, consummation notices get filed late, call signs change, and administrative updates happen without anyone internally being told.

The consequence is not theoretical. Companies discover during a financing or a sale that a licence they believed they held is recorded against the acquired entity's name, or that a call sign they have been operating under expired because the renewal was filed against a different entity. The diligence process finds it, which is the worst possible moment.

What a custom build does: reconcile continuously against the regulator's public data. The build pulls your holdings from the licensing database on a schedule, compares against your internal register, and raises differences as exceptions: licences you think you hold that are recorded elsewhere, expiry dates that moved, conditions added to an authorisation, applications pending that nobody internally is tracking. This is the least glamorous part of the system and frequently the first thing that pays for itself, because it converts diligence archaeology into a report that is always current.

Problem 4: leases, secondary markets and the discontinuance trap

Spectrum gets leased. Utilities lease from holders such as Anterix, operators lease to and from each other, and private network deployments increasingly sit on shared frameworks where a spectrum access system controls assignments dynamically. Each of those creates obligations that are not on the licence itself but sit in an agreement, and the licence holder usually remains responsible to the regulator regardless of who is operating.

There is also a trap that catches companies with legacy holdings: permanent discontinuance of operation can terminate an authorisation. A site that was decommissioned during a network consolidation, and quietly never rebuilt, can put a licence at risk without anyone filing anything or noticing anything. The spreadsheet has no view of operational status because it was never joined to the network inventory.

What a custom build does: link the licence record to the sites and equipment actually operating under it, sourced from your network inventory rather than typed. Then a decommissioned site raises a flag against every authorisation that depends on it, and lease agreements are held as structured terms with their own obligations and expiry so that a sublease renewal does not depend on someone's memory. Where a spectrum access system governs assignments, the build should consume its records so your view of what you are actually authorised to transmit matches what the system is granting, rather than what you assume.

What a spectrum licence management build costs and how long it takes

From Digital Heroes delivery experience, a first release covering a structured holdings register with market and site geography, obligations and deadlines with owners and escalation, document and correspondence attachment, and automated reconciliation against the regulator's database runs $45,000 to $95,000 and ships in 8 to 12 weeks. A full platform adding coverage evidence generation from your planning tools, coordination workflow, lease and secondary market handling, network inventory linkage and filing preparation runs $120,000 to $280,000 phased over 5 to 9 months.

What drives cost up in this specific portfolio type: the number of distinct services you hold, since a broadcast authorisation, a mobile market licence, a Part 90 site licence and a microwave path are four different obligation shapes. Multiple regulators, if you operate across borders, because each publishes data differently and some publish very little. Coverage evidence, which is the heaviest single component when propagation results have to be imported and processed rather than screenshotted. And the state of your historical file, which is the honest one: if the coordination and filing history for acquired markets exists only in boxes and inboxes, someone has to read it, and that is a real line in the budget.

What keeps cost down: starting with the services that carry buildout risk and leaving the stable site licences on the existing process for a phase.

When LS telcom, ATDI, Comsearch or Federated Wireless is the right answer

Buy where the product is the specialism. LS telcom and ATDI are serious spectrum engineering and planning environments, and you should not attempt to rebuild propagation modelling, which is decades of physics and validation work. Comsearch does coordination properly and there is no reason to take that in house. Federated Wireless operates as a spectrum access system administrator for shared spectrum, and that is a regulated role you cannot replicate.

Our position on when to build: when two or more of these are true. You carry performance or buildout obligations that require evidence rather than a filing. Your holdings span more than one service type or more than one acquired entity. Coordination correspondence is your interference defence and it lives in individual inboxes. You lease spectrum in or out. Or a single person is the only reliable index of what you hold and when it is due.

The tipping point is that planning tools model propagation and coordinators manage notices, while the thing at risk is the obligation register that sits above both. Nobody sells that register because it is made of your holdings, your acquisitions, your agreements and the specific orders that granted your licences. It is also small, cheap and fast to build relative to what it protects, which is unusual in this industry and worth saying plainly.

How to choose a developer for spectrum compliance software

Ask them to model an obligation on a whiteboard. The right answer has a licence, an authorisation area as real geography, an obligation with a rule and a threshold and a deadline, an evidence record with parameters, and an owner. Someone who draws a task list with due dates has built a project tracker and will not survive the first coverage showing.

Ask how they would import coverage results from your planning environment. If the answer involves a screenshot or a PDF, the evidence will not be reproducible and the system fails at the only moment it matters. The workable answer handles a geospatial export with the model parameters recorded as data.

Ask whether they have worked with public regulatory data feeds. Reconciling against a licensing database sounds trivial and is not, because entity naming, call sign history and pending applications all have edge cases that only appear at volume. A developer who has done it will ask about your acquired entity names before quoting.

Ask who owns the code, the repository and the hosting accounts, in writing, before kickoff. At Digital Heroes it is yours from the first commit. A practical starting move: export your current holdings sheet and pull the regulator's record for your entity names on the same day, then compare them. The size of that gap is your business case, and it takes an afternoon to measure.