Sensitivity Versus Selectivity in Radar Detectors

Two words that decide daily behavior

Specification conversations reach for sensitivity and stop there. Selectivity, the receiver's ability to separate the wanted signal from other signals nearby in frequency, matters just as much to how a unit feels in use, and it is the word most listings never use. A seller who can explain both, simply, answers the category's hardest customer question: why two units with the same band list behave differently.

Sensitivity: how quiet a signal it hears

Sensitivity is how weak a signal the receiver can process. A more sensitive receiver hears sources earlier, all else equal, and any sensitivity figure is only meaningful with its test method: the bench setup, the signal level, the band. Ask for the method on the specification sheet. Sensitivity is the ceiling on performance; above it, nothing in the listing raises the number.

Selectivity: what it ignores on purpose

The road is full of signals near the ones the receiver wants. Selectivity is the receiver's ability to keep them apart, and filtering is the logic that decides which received signals become alerts. A unit with strong sensitivity and weak selectivity alerts early and often, at everything; the driver trains to ignore it. A unit with balanced selectivity alerts less often and more meaningfully, and the driver trusts it. Daily satisfaction tracks selectivity more closely than sensitivity, which is why the city customer cares about it most.

The trade, and the controls

Sensitivity and selectivity pull against each other: the widest listening hears the most and discriminates the least. The unit's modes and adjustments exist to let the driver move along that trade, band by band: full reach on an empty highway, tightened filtering in dense traffic. The controls to confirm per SKU are the band-by-band sensitivity adjustment, the filtering features the firmware includes, and what each named mode actually changes. A control the sheet does not describe is a control the support desk will have to reverse engineer later.

How to explain it at the counter

The working analogy is hearing: sensitivity is how quietly someone can speak and still be heard across the room; selectivity is following one voice in a loud room. Both matter, and different rooms reward different balances. Ten seconds of analogy converts a specification argument into a driving-habits conversation, which is the conversation that ends in the right unit.

The listing discipline

• State sensitivity figures only with their method, or not at all.
• Describe the filtering controls by what they do, in plain words.
• Never promise an absence of false alerts; describe the controls that manage them.
• Keep the scope statements standing: receive-only, private passenger vehicles, rules differ by location.

The two words also organize support: a "it alerts too much" complaint is a selectivity conversation, and a "it hears too late" complaint is a sensitivity or installation conversation. Diagnosing which one you are holding is half the support answer, and it starts with the seller knowing the difference.

How the two words organize the range

Across a range, the two words describe the ladder better than any feature list: entry units are tuned for composure, because their buyers drive dense routes and forgave reach; upper units add reach and the control depth to manage it. Write the ladder's step descriptions with the two words, and the assortment reads as a deliberate progression rather than a price list. The vocabulary also trains buyers upward honestly: the shopper who now says "I want more selectivity" has understood the category better than most listings ever taught them, and that shopper buys the step that matches their route the first time.

Reading a filtering feature list critically

Suppliers describe filtering with varying precision, and the buyer's job is to convert adjectives into fields. For each named feature, ask: what does it act on, which bands, what does the driver give up when it is on, and can it be disabled. A feature without an off switch is a behavior, not a control, and behaviors belong in the listing as facts. Record the answers on the specification sheet next to the feature names, and let the sheet's plain sentences become the listing's tuning section unchanged. The exercise takes one message round and buys years of accurate support answers, because the support desk inherits the sheet, not the adjectives.

Where the two words meet the warranty conversation

Sensitivity and selectivity also shape warranty disputes, because "too quiet" and "too chatty" are the category's most common complaints, and neither is a defect. The supplier terms will define defects as failures against the specification, which is why the specification must carry the controls and behaviors in writing: a unit performing to its documented filtering is not warrantiable, and a customer who was sold its documented behavior has no dispute. Sellers who keep the sheet's filtering section precise resolve these conversations in one reply, and the reply is a link, not an argument.

A counter demonstration for the two words

The senses analogy opens the door; the counter closes it. Power two units, one known for reach and one for composure, and cycle the same menu on both. Let the customer feel the difference in the mode structure: one offers reach steps, the other offers filtering depth. Then ask the drive question and hand them the unit their answer points to. Ninety seconds, no jargon beyond the two words, and the customer leaves owning the comparison instead of fearing it. The demo also quietly disqualifies any unit in the range whose filtering cannot be explained, which is information the assortment meeting wants before the next order.

The two words in the specification file

Add both words to the specification sheet as named fields, even where the supplier's answers are partial: sensitivity with its test method and level, selectivity as the named filtering features and their behaviors. A field with a partial answer still outperforms a field that was never asked, because partial answers invite the follow-up that eventually completes them. Across a range, the two fields become the fastest technical comparison between candidate models, and across suppliers, they become a fluency test: the factory that answers both precisely is fluent in its own product, which is the factory whose other answers you will not have to double-check.