Why We Compute Awards When Your Logging Program Already Does

Sooner or later somebody asks it directly, usually a logger author and usually not warmly: you track DXCC, Worked All States, grids and POTA — so does my program. What exactly are you doing? It is a fair question and it deserves a straight answer rather than a feature list.

Here is the answer, and it starts by conceding the part that is obviously true.

The overlap is real

Your logging program computes these awards, and it very likely computes them well. DXKeeper, Log4OM, Ham Radio Deluxe, N3FJP, MacLoggerDX — award tracking has been core to serious logging software for years. LoTW® computes awards too, and publishes its own award definitions.

We are not going to pretend otherwise, and we are certainly not going to claim we do it better. Anyone can check in about ninety seconds.

The line, in one sentence

That is the whole distinction, and it is a distinction of territory rather than of quality. A desktop logger cannot reach an operator who is away from the desk. That is not a gap in the product — it is what a desktop program is.

So why compute the awards at all?

Two reasons, and neither is "to have the feature."

One: the award state is the input to an alert, not a scoreboard. When a confirmation lands, the useful message is not a QSO confirmed. It is that was a new entity, or that completes 5-Band WAS, or that one is now ready to submit. You cannot say any of that without knowing where the operator stands. The award computation exists so the notification can be worth reading.

Two: the more we understand about how you actually operate, the more appropriate the alerting gets. Which bands, which modes, which awards are live for you, what you chase — that is what separates a useful alert from a nuisance. An operator chasing 6 m grids and an operator chasing POTA parks should not be told the same things.

Both of those depend on something a single logging program is not positioned to do: aggregating several third-party sources — LoTW, QRZ, cluster spots, POTA — into one picture.

And the half that isn't about individuals at all

The community platform is not a social add-on bolted to a logbook. It is the point.

Clubs, on-air activity, DXing, contests and events within clubs, with shared standings and alerting for the group as well as the person. An award is worth more when somebody notices, and no logging program is trying to be the place where that happens. That is not a competitive claim — it is simply a different thing to build.

What this means in practice

• We are not trying to replace your logger, and we will keep saying so. Keep using what you like. DxQSO reads your confirmations; it does not want your logging workflow.
• We would rather integrate than compete. The DxQSO API is open, and the invitation to logger authors is a standing one.
• Where we overlap, we will say so plainly rather than implying we are the only ones who do something.

If your program tells you everything you need at the desk, that is genuinely fine. We are interested in the other twenty-three hours.

73, Steve, N1EZ

LoTW® is a registered trademark of the American Radio Relay League. DxQSO is not affiliated with or endorsed by the ARRL.