When a Java review lands, it can feel arbitrary, as if your name was drawn from a hat. It was not. Oracle License Management Services, the function that runs compliance reviews, selects targets through a deliberate process that weighs what Oracle already knows about you against the size of the claim a review might produce. The selection is closer to a sales pipeline than a lottery. If you understand how that pipeline is built, you can see your own organization the way LMS sees it and reduce the signals that move you up the list before a letter ever arrives.
For the licensing mechanics that make a Java review worth Oracle's effort in the first place, keep the Oracle Java licensing guide for 2026 open alongside this article.
Start with the incentive behind the list
Every selection decision flows from one number: the size of the potential claim. Since January 2023 Oracle has priced Java SE on the Universal Subscription, a per employee charge running from 5.25 to 15.00 dollars per employee per month that counts every full time and part time employee, every contractor, and every temporary worker regardless of who actually touches Java. For a large employer that metric reaches into the millions. LMS does not chase small numbers when large ones are available, so the first thing that puts you on the list is simply being an organization where the employee count makes the math worthwhile.
The thing to remember. LMS is not auditing because you broke a rule. It is auditing because your employee count makes the claim large and a signal suggested you might owe.
The signals LMS combines
On top of the raw size of the prize, LMS layers signals that suggest a review will actually land. A durable download record tied to a corporate domain tells Oracle that Java is present. An approaching renewal of any Oracle agreement creates a scheduled moment of contact. Visible growth, a funding round, or an acquisition implies a larger counted population. An existing Oracle relationship, even one that has nothing to do with Java, gives the account team a foothold and a reason to raise the topic. None of these signals is decisive on its own. LMS weighs them together to estimate the likelihood that a review converts into revenue.
How the list gets ranked
Think of selection as a simple ranking. The organizations that rise to the top combine a large likely employee count with one or more active signals. A company with a visible download trail, a renewal in the next two quarters, and recent public growth is far more attractive than one with none of those. LMS prioritizes the accounts where the expected claim, multiplied by the probability of collection, is highest. That is why two companies of similar size can have very different audit risk: the one with cleaner signals is simply a worse bet for Oracle.
What the selection weighs, at a glance
| Factor LMS weighs | What it signals | Buyer response |
|---|---|---|
| Employee count | Size of the potential claim | Validate the counted population early |
| Download record | Java is present | Sweep, default to a free distribution |
| Renewal date | A scheduled contact point | Model exposure before the renewal |
| Public growth | A larger likely population | Keep the estate clean as you scale |
| Existing Oracle deal | An account foothold | Keep Java separate from other talks |
The role telemetry and records play
LMS does not work from guesses alone. Download accounts, support history, and update activity give it evidence that Java is in use and how long it has been. We go deeper on this in the role of Java telemetry in audits, but the headline for selection is that the more visible your Java activity, the more confident LMS can be that a review will produce a number. Reducing avoidable visibility lowers that confidence.
Why the soft inquiry comes first
Selection rarely opens with a formal letter. LMS or the account team often begins with a friendly inquiry, an offer to help you review your Java estate, or a suggestion that a subscription would give you peace of mind. This soft approach is part of the funnel: it tests whether you will volunteer data and whether you look like a likely buyer. Many organizations give away ground here without realizing the inquiry was a qualification step. Treat the first soft question with the same care you would give a formal notice.
How to lower your position on the list
Several of the signals LMS weighs are within your control. You can sweep the estate so you know exactly where Oracle Java runs, default every new deployment to a supported free OpenJDK distribution, control who is allowed to download Oracle Java, and keep records that show your real footprint over time. None of this hides anything from Oracle. It simply means that when LMS runs its calculation, your account looks like a poor bet: a clean estate, a small defensible footprint, and a buyer who clearly knows their own numbers. The accounts that get hurt are the ones surprised by their own estate. To see the full set of triggers that feed the selection, read what triggers an Oracle Java audit.
How a buyer side advisor helps
Reading these signals correctly and acting on them before a review begins is exactly where an independent buyer side advisor earns its place. We know how Oracle builds a Java claim, which signals tend to precede a formal review, and how to turn a clean estate into a smaller defended residual. We sit between you and Oracle and we never take vendor money, so the advice points one way only. We work two ways, both built so the risk sits with us. A Fixed Fee starts from $18,000, agreed up front. Or choose Gainshare, a share of verified savings or avoided exposure, with zero retainer and no risk to you. We have defended more than $120M in Java exposure and over 300 Java audits, with more than 20 years of combined experience and an average reduction of 68 percent versus Oracle's opening number.
Where to go next
LMS selects targets with a calculation, and much of that calculation is made of signals you can manage. Sweep your estate, control your downloads, and model your exposure before you rise up the list. Download the guide for the full buyer side playbook, then bring your questions to a Strategy Call.
Download the guide.
Get the Oracle Java Audit Survival Guide for the complete buyer side playbook, then bring your questions to a Strategy Call.
Download guide