How to build an ALA entitlement baseline

When an audit notice arrives, the vendor already has a number in mind, and the buyer who cannot state its own entitlement with precision is negotiating against a figure it has no way to test. The single most powerful asset a buyer can bring to a Micro Focus audit is an independent count of what it is actually entitled to use, assembled from its own contracts before any vendor measurement script runs. Building an ALA entitlement baseline is the work of constructing that count: a complete, evidenced statement of what every Additional License Authorization in the estate grants, against which any finding can be measured line by line.

This field note explains what a baseline is, how to assemble one, and why it decides the strength of every later challenge. It pairs with our ALA and entitlement review track and the reconstruction work in our method.

What an entitlement baseline is

An entitlement baseline is the buyer's own determination of what it is licensed to use, built from the contracts rather than from the vendor's reading of them. It records, for each product, the metric that governs it, the quantity granted, the conditions and restrictions that apply, and the documents that prove each of those points. This is the document the vendor's finding must beat: where the finding asserts more than the baseline shows the buyer needs, the gap is the negotiation, and where the baseline shows entitlement the finding ignored, that entitlement subtracts from the claim. Building this position before the vendor measures is the reconstruct step of our four Rs, and it is the foundation of a credible rebuttal.

Step one: inventory the products under ALA

The baseline begins with knowing which products in the estate are governed by Additional License Authorizations at all, because the ALA framework and the OpenText EULA cover different parts of the estate and carry different terms. Most Micro Focus products fall under ALAs, while the OpenText ECM line is governed by the EULA, and a finding that applies the wrong framework to a product is reaching past the contract that actually governs it. Establishing the product list and the governing framework for each is the first inventory step, set out in how to inventory products governed by ALAs.

Step two: read every grant for its real terms

For each product under an ALA, the baseline records the actual grant: the metric, the quantity, and the conditions. This is close reading, because the metric and quantity that matter are the ones in the authorization, not the ones a finding assumes, and the distinction between named user and capacity counting, between perpetual and term, and between production and non production rights all live in the grant language. The way that language fixes the unit of counting is examined in ALA grant language and the deployment count, and the metric distinctions in ALA named user versus capacity metrics. Each grant read accurately is one line of the baseline.

Step three: resolve stacked and superseded authorizations

Estates accumulate authorizations over years of purchases, renewals, and acquisitions, and the same product often carries several documents whose relationship is not obvious. A baseline must determine which authorizations are still in force, which have been superseded, and how separately purchased quantities combine, because a finding that reads only the documents that favor the vendor can understate the buyer's true entitlement. Resolving these overlaps is the work examined in stacked and superseded ALAs in a license estate, and it frequently uncovers entitlement a buyer did not know it held.

Step four: assemble the supporting evidence

A baseline is only as strong as the records behind it, because an entitlement the buyer asserts but cannot prove will not survive a vendor challenge. For each line, the baseline cites the order forms, authorizations, renewal records, and amendments that establish the metric and quantity claimed. What records carry this weight is the subject of what records support an ALA entitlement position, and assembling them at baseline time, rather than scrambling for them under audit pressure, is what makes the count defensible when it is challenged.

How a baseline reduces the number

In a recent engagement, a buyer faced a finding built entirely on the vendor's reading of a partial set of documents, with no independent count to test it. Assembling the full baseline surfaced separately purchased quantities the finding had ignored, established the metric that actually governed two disputed products, and showed that several deployments the finding counted fell under non production rights the buyer already held. Each of those baseline lines subtracted directly from the claim. This is the ordinary mechanism: the baseline converts a vendor assertion into a line by line comparison, and every line where the buyer's evidenced entitlement exceeds the finding's assumption reduces the number. Applied across an estate, this discipline is part of how we deliver the 68 percent average reduction we have achieved across more than 200 defended audits.

Keeping the baseline current

A baseline is not a one time exercise, because purchases, renewals, and deployment changes shift the position continuously, and a baseline that is current when the notice arrives is worth far more than one assembled in haste afterward. Maintaining it means recording new authorizations as they are acquired and reconciling deployment against entitlement periodically, the discipline examined in reconciling ALA entitlements before an audit. A current baseline turns the seven day notice from a scramble into a controlled response.

Bringing the baseline to the table

Once the baseline is built, it becomes the spine of the defense: the document that frames the rebuttal, anchors the settlement, and defines what a clean forward agreement should protect. A finding cannot stand against an evidenced, line by line entitlement count, and the buyer who brings one to the table is no longer reacting to the vendor's number but proposing its own. If you are facing an audit without an independent count of your entitlement, open a case and we will build the baseline the finding has to beat.

For the full method, read the complete OpenText audit defense playbook, and for entitlement defense across the Micro Focus estate see our ALA and entitlement review track.