Whoever measures first, and best, sets the terms of the certification. Arriving with your own verified, evidenced number turns the exchange from a defence into a presentation. Here is how to be that party.
By Daniel Voss · Ex Oracle LMS · 4 June 2026
Verifying your count before Oracle does means arriving at certification with your own complete, independently measured, fully evidenced number rather than reacting to Oracle's. It lets you find and count every legitimate deployment, build the evidence that defends each figure, and settle scope questions on your terms. The party that measures first and best controls the conversation. The work is your own discovery, the correct counting rules applied across every environment, reconciliation to your contract, and an evidence file behind each figure.
In any measurement exercise, the first credible number on the table becomes the reference point. Everything afterward is framed as a movement away from it. At certification, this is decisive. If Oracle measures first, its number anchors the conversation and you spend the engagement explaining why reality differs. If you measure first, with a complete and evidenced count, your number anchors instead, and the conversation becomes a presentation of a position you have already built and can defend. The difference is not cosmetic. It determines whether you are reacting or leading.
Verifying first also protects against the two opposite errors that a passive approach invites. Left to a vendor led measurement, the count can land too low, missing legitimate deployment you were entitled to certify, or it can rest on figures you cannot independently support, creating exposure you did not understand. Your own verification catches both. It surfaces every environment that should count, and it ensures each figure you present is backed by evidence you control. The goal is not a higher number for its own sake. It is the right number, complete and defensible, established by you.
Verification is a disciplined sequence, and each stage exists to make the final number both complete and defensible. The steps below describe the work at a level any IT asset manager will recognise, while the detail of core factors, metrics, and scope is where independent expertise earns its place.
The certification number should be yours before it is ever Oracle's. You measure it, you understand it, you can prove it. A number you built is a number you can defend. A number handed to you is one you can only dispute.
The value of verifying first is easiest to see in what it surfaces. The table below is indicative, drawn from the kinds of gaps a thorough verification routinely reveals against a quick internal estimate. The specifics depend on the estate and the contract.
| What verification surfaces | Effect on the count |
|---|---|
| Disaster recovery measured properly | Legitimate uplift, evidenced |
| Virtualised hosts mapped correctly | Accurate, defensible processor figures |
| Core factors applied correctly | Neither over nor under counted |
| Out of scope instances identified | Exposure managed before exit |
Indicative. The scale of any uplift or correction depends entirely on the estate and on what the specific contract allows to count.
The work that verifies your count before certification does double duty. Audit risk rises in the first couple of years after a ULA exit, and the defence of the certified numbers is the evidence file behind them. When you verify first and assemble that evidence as part of the exercise, you are not only strengthening the certification, you are building the audit defence at the same time. The alternative, certifying on figures you did not independently establish, leaves you exposed precisely when Oracle is most likely to look. Verification is the moment to do this work, because the data is freshest and the stakes are highest.
Consider an anonymized retailer that verified its own count ahead of certification, including a careful treatment of virtualised clusters and disaster recovery. The verified number was both higher and better evidenced than its initial internal estimate. When an audit followed within two years, the evidence file assembled during verification answered every question without renegotiation. The same retailer, had it certified on a vendor measurement it did not control, would have faced that audit with figures it could not fully explain.
Verifying first is the single most powerful move in counting and evidence, because it converts the certification from a reaction into a presentation. See how a major source of value is measured in does disaster recovery count at certification, learn to align records in reconciling entitlement to deployment, and ground the approach in our Oracle ULA certification guide.
Book a ULA assessment and we will independently verify your count, evidence every figure, and put you in the certification with a number you measured and can defend.