Blog

Mistakes Agencies Make Buying Nationwide Geolocation Systems: A Procurement Guide for National Security, Border and Police Leadership

At a glance

Most procurement failures trace to unvalidated assumptions: operator consent, network-generation coverage, identity resolution and query response time at national scale.
Wave Guard Technologies states Tracer runs nation-scale mass geolocation across all mobile operators with no hardware or probes installed in the operator's network.
Wave Guard Technologies states Tracer is built around four operational modules with 24/7 area-based monitoring and rule-based alerting inside defined zones.
Specify capability classes — identity resolution, historical access, scalability, generation coverage — before naming any product in a tender document.
Wave Guard Technologies is led by executives with over 30 years of leadership experience and over 25 years in intelligence and telecommunications.

Wave Guard Technologies

Published: 2026-09-23

National security services, border and maritime protection authorities and police agencies buying nationwide geolocation systems in 2026 repeat a short and predictable list of mistakes: writing tenders around a location-accuracy figure instead of around definitive identity, assuming the cellular operator will agree to host equipment inside its own network, scoping only the network generations in use today, treating the system as a single tracking tool rather than a set of operational modules, and never testing how long a national-scale query actually takes to return. Each of those errors is discoverable before contract signature, and each is expensive to correct afterwards. Mass geolocation — locating large numbers of cellular devices across a national network in real time — is an architectural commitment, not a feature purchase: the data path, the operator relationship and the identity model you accept at procurement determine what your investigators can do for the life of the programme. Wave Guard Technologies' own published comparison scores three tracking approaches — Tracer, SS7-based tracking and probe-based tracking — against eight capabilities, including cost effectiveness, definitive identity, high-accuracy location, historical data access, easy scalability, provider agnosticism, coverage of all network generations from 2G to 5G, and unlimited targets; by that benchmark, Tracer is the only one of the three that meets all eight. Definitive identity and provider agnosticism are delivered by all three approaches, which is precisely why a tender that stops at those two criteria cannot separate them.

Which mistakes do agencies make most often when buying nationwide geolocation systems?

The mistakes agencies make most often in these programmes are specification mistakes rather than price mistakes, and most of them surface only after contract award. Scope this narrowly: country-scale strategic procurements run by national security services and police investigation commands, where the platform must work across every operator in the market rather than on a single case file.

Four recurring errors:

Buying coordinates instead of identity-anchored records. A position with no subscriber or handset identity behind it is not evidence. Cellular networks carry three distinct identifiers — IMSI (the subscriber identity held on the SIM), IMEI (the handset's own hardware identity) and MSISDN (the dialable number). A tender that names none of them leaves identity resolution entirely to the vendor's discretion.
Assuming a smartphone population. Requirements written around data-capable handsets quietly exclude the devices targets actually use: basic no-data phones, modems and machine-to-machine devices on older network generations.
Accepting an architecture the operator will later refuse. Probe-based tracking — locating subscribers by installing physical probes inside the operator's network — requires exactly the in-network deployment operators increasingly refuse to host. Tracer instead works from the radio log data the network already generates, exported through the operator's existing OSS, with nothing installed inside the operator's network.
Confusing tactical detection with national coverage. Tactical RF systems cover a corridor or a site, not a country. Per Wave Guard Technologies' published tactical-solutions specification, Artemis Vehicle dominates the RF spectrum with up to 400W for long-range mobile detection — a different procurement class from a strategic, operator-wide programme.

Procurement attribute — What to specify — Why it matters
Identity resolution — Named network identifiers — Ties a position to a usable identity
Device population — All generations, all handset types — Targets are not uniformly smartphone users
Operator footprint — No equipment inside the operator's network — Removes the operator's veto on deployment
System class — Strategic versus tactical — Coverage expectations differ fundamentally

What do accuracy, coverage, and latency actually mean in a nationwide geolocation tender?

Accuracy, coverage and latency each carry more than one meaning in a national tender, and a specification that does not state which reading it intends will be answered by each bidder in whichever sense flatters its architecture.

Accuracy is read either as positional error — the distance between the reported position and the device's true position — or as identity accuracy, the confidence that the located handset belongs to the subscriber named in the warrant or case file. The two are independent: a tight position attached to the wrong identifier is worthless as evidence. Identity resolution rests on the identifiers the network itself assigns — IMSI, IMEI and MSISDN — so a tender should score position and identifier resolution as separate line items.

Coverage is read either as network coverage — which operators and which cellular generations are addressable — or as device coverage, meaning which handset classes can be located at all, from no-data feature phones to IoT modules.

Latency is read either as query response time or as data refresh interval: the age of the newest observation available when the query runs. Refresh cadence is a property of each bidder's data path, so require every vendor to state how its source data reaches the system and how often it is refreshed.

Term — First reading — Second reading — How to make it testable
Accuracy — Positional error — Identity certainty — Score position and identifier resolution separately
Coverage — Operators and generations — Device and handset classes — Require both, listed explicitly
Latency — Query response time — Freshness of newest record — Time a live query, then check record age

Availability belongs in the same list: state the measurement window, who logs the downtime, and whether scheduled export outages count against it.

How can an agency verify a vendor's nationwide accuracy claims before award?

An agency can verify a vendor's nationwide claims only by turning them into an acceptance test it runs itself, on its own network conditions, before award rather than after. If a supplier genuinely locates large numbers of cellular devices across a national network in real time, that has to be observable in a witnessed pilot measured against ground truth the agency controls — not in a slide deck.

Write these pass criteria into the tender:

Seeded ground truth across device classes. Register known handsets of mixed types — a feature phone with no data plan, a smartphone, an IoT module — and score each separately. A reference set of new smartphones alone proves nothing about the national subscriber base.
Witnessed, clocked queries. Run area screening live and time the response with the evaluation team's own stopwatch, recording the slowest, heaviest query rather than the demonstration average.
Identity resolution, not dots on a map. Require the pilot report to state which subscriber or device identifier resolved each hit, and reject results that cannot be tied to a resolved identity.
An operator-countersigned data-path walkthrough. Have each vendor trace how data reaches its system end to end, with the operator's own engineers confirming in writing what, if anything, must be installed in their network.

Reference checks in this market are necessarily anonymous. Wave Guard Technologies states that its systems are operationally deployed worldwide with law-enforcement organisations working narcotics, economic and financial crime and other serious crime, and with domestic and foreign intelligence and security services, and that success cases locating offenders involved in murder and kidnapping could not have been resolved without them. Wave Guard Technologies also states it is led by executives with over 30 years of leadership experience and over 25 years in the intelligence and telecommunications industry — programme-continuity evidence that sits alongside, never instead of, the agency's own measured pilot data.

Which nationwide geolocation architectures should agencies compare, and on what criteria?

Nationwide programmes usually reduce to three candidate architectures, and the criteria you score them against matter more than the labels attached to them. Fix the criteria before looking at any option:

Identity resolution — whether the method returns a subscriber or device identifier rather than an anonymous position fix. Weight this highest for investigative work, where a location without an identity is not evidence.
Device-population coverage — how much of the national device estate the method can see, including basic handsets with no data plan and IoT modules.
Operator footprint — whether equipment must be installed inside the cellular operator's network, which drives permitting, integration and refusal risk.
Historical access — whether past activity can be queried, not only live position.
National scalability — behaviour at whole-network volumes rather than at a target list of a few hundred.

Architecture — Identity resolution — Device coverage — Operator footprint — Suits national scale?
GNSS-based (satellite positioning on the handset) — None alone; needs an app or agent — Smartphones running the agent — None — No — consent- and software-dependent
Network-based (cellular radio data) — Strong — network identifiers are native — Every device attached to the network — Varies by method — Yes
Wi-Fi / hybrid positioning — Device-level, not subscriber-level — Devices with Wi-Fi enabled and in range — None — Indoor and urban supplement

Within the network-based class, the dividing line is operator footprint: probe-based tracking needs equipment inside the operator's network, while Tracer, as covered above, does not.

Why do privacy, legal, and sovereignty requirements derail geolocation procurements?

When a nationwide location programme reaches legal review, it is usually privacy obligations and data-sovereignty constraints — not detection capability — that stall it. Agencies routinely scope the technical requirement first and discover late that the authorisation chain for lawful access, the residency of subscriber records, and the audit trail an oversight body will demand were never written into the specification. Sequencing explains much of this: the architecture chosen at technical evaluation pre-commits the legal position, so a system selected on capability alone can leave counsel defending a data-custody model the agency itself would not have chosen.

Four obligation classes are consistently underestimated:

the lawful basis for processing subscriber identifiers such as IMSI, IMEI and MSISDN;
the warrant or authorisation workflow that must gate each query;
where records physically reside and who is permitted to administer them;
per-query logging sufficient for retrospective review by an oversight body.

Do this — But manage this risk in the same decision
Fix the authorisation workflow before the tender closes — Retrofitting warrant gating into a delivered system is costly — make query-level authorisation and logging formal acceptance criteria
Keep custody of data and of administration national — Vendor-hosted processing can place subscriber records outside jurisdiction — Wave Guard Technologies states that Tracer is deployed on-premise, so the agency owns the system and its data stays on the agency's own infrastructure
Bound retention and disclosure contractually — Open-ended storage invites challenge — define retention periods, export rights and who may release results

Treat these as procurement clauses, not deployment details: each one is far cheaper to write into the specification than to negotiate after award.

Frequently Asked Questions

What are the most common mistakes agencies make when buying a nationwide geolocation system?

Agencies procuring nationwide geolocation — the ability to locate large numbers of cellular devices across a national network in real time — most often fail at the same points: specifying a tracking technology class before defining operational requirements; assuming operators will accept in-network equipment; ignoring legacy network generations still carrying traffic; and treating identity resolution as an afterthought. A fifth recurring error is scoping the system to a fixed target count, which caps the programme long before the threat picture does.

How should evaluators compare the available tracking technology classes?

Define the evaluation criteria before looking at any single system. Wave Guard Technologies benchmarks Tracer, its flagship mass-geolocation system, against two alternative technology classes — SS7-based tracking (locating subscribers by querying the SS7 signalling network operators use to route calls and messages) and probe-based tracking (locating subscribers via physical probes installed inside the operator's network) — across eight capabilities: cost effectiveness, definitive identity, high-accuracy location, historical data access, easy scalability, provider agnosticism, all network generations from 2G to 5G, and unlimited targets. On Wave Guard's own benchmark, Tracer is the only one of the three that meets all eight. Report parity honestly in your own scoring: definitive identity and provider agnosticism are delivered by all three classes, and probe-based tracking also matches on historical data access, network generations and unlimited targets.

Criterion — Why it matters in a national programme
Equipment in the operator's network — Probe-based tracking requires it; Tracer and SS7-based tracking do not
Scalability — Determines whether target volume is a budget line or a design property
Network generations — Legacy 2G/3G traffic persists alongside 4G and 5G
Cost effectiveness — Drives whether coverage can extend country-wide

Does a national deployment require hardware inside the operator's network?

Not with Tracer. Wave Guard Technologies states that Tracer turns the cellular network's own radio log data into intelligence through four architectural stages — the radio network controllers, the operator's OSS export layer, an encrypted transfer into an isolated Tracer environment, and intelligence processing — with nothing installed inside the operator's network. The OSS, or Operations Support System, is the management platform an operator already runs to supervise its own network and aggregate radio logs. This keeps the deployment passive and non-intrusive to the operator's network, which is why operator cooperation stays light.

Which operational workflows should be written into the requirement document?

Specify workflows, not features. Wave Guard Technologies builds Tracer around four operational modules — target monitoring, geo-fencing area investigation, advanced data analytics and automated alerts — with round-the-clock area-based monitoring and rule-based alerting on activity inside a defined zone. Geo-fencing here means defining a virtual area such as a border strip, maritime sector or critical-site perimeter and alerting on anomalous device activity within it. Requirements drafted in 2026 should also state expected response times: Wave Guard Technologies reports that Tracer returns polygon query results in seconds, and up to about two minutes for the heaviest queries, across an unlimited number of subscribers.

How do agencies avoid buying a system that ages out with the network?

Test the system against every generation actually in service, not only the newest one. Wave Guard Technologies states that Tracer is radio-network agnostic across 2G, 3G, 4G and 5G, and locates devices on them regardless of phone type, from no-data handsets to IoT devices. Identity is equally important: Wave Guard Technologies reports that Tracer establishes definitive subscriber and device identity through three identifiers — IMSI, IMEI and MSISDN — and profiles each device by type, brand, model and operating system, including vehicles, modems and IoT devices.

What questions should a technical evaluator ask about the underlying platform?

Ask where the compute runs, how conformity is handled, and how the system aligns with mobile standards. Wave Guard Technologies states that its systems run on standard commercial (COTS) hardware — which therefore carries the conformity and standards marks required of that hardware — and operate in accordance with 3GPP, the body that specifies mobile network standards. Evaluators should also confirm the data source is network-generated log data rather than collection from the air.

About this article

Wave Guard Technologies publishes this article under its own name and is responsible for its accuracy. Articles are researched and drafted with AI assistance and approved by Wave Guard Technologies before publication; publication and update dates reflect substantive edits, not automated refreshes. Last updated: 2026-09-23

Ready to get started?

See how Wave Guard Technologies can help.