Preparing an ALA entitlement reconstruction
An audit measures deployment and presents the result as the buyer's obligation, but a measurement of what is running is not a statement of what is owed. The obligation is decided by what the buyer is entitled to use, and establishing that entitlement independently, before the vendor's number is allowed to stand, is the work that turns a finding from a demand into a dispute. Preparing an ALA entitlement reconstruction is the building of that independent position: a complete reconstruction of what every Additional License Authorization in the estate grants, set against deployment so that each line of a finding can be tested rather than accepted.
This field note explains what a reconstruction is, how it is built, and why it is the spine of the defense. It pairs with our ALA and entitlement review track, and it is the reconstruct step of our four Rs applied to the Micro Focus estate.
What a reconstruction is and why it comes first
A reconstruction is the buyer's own determination of its effective license position, built from the contracts and reconciled against actual deployment, assembled before any vendor measurement script runs. It is deliberately built first, because a buyer that lets the vendor measure before establishing its own position is negotiating against a number it cannot test, while a buyer that arrives with a reconstruction already in hand controls the terms of the comparison. This sequencing, reconstruct before the vendor measures, is the discipline that separates a controlled defense from a reactive one, and it is why the work begins the moment the seven day notice clock starts.
A measurement of what is running is not a statement of what is owed. The obligation is the gap between deployment and entitlement, and only an independent reconstruction of entitlement lets the buyer see that gap before the vendor defines it for them.
From inventory to baseline to reconstruction
A reconstruction builds on a baseline, which is the evidenced statement of what the contracts grant, and extends it by reconciling that entitlement against deployment to produce the effective position. The baseline answers what the buyer is entitled to; the reconstruction answers how that entitlement maps onto what is actually running, and where the two diverge. Building the baseline that the reconstruction rests on is the work set out in how to build an ALA entitlement baseline, and identifying which products fall under the ALA framework at all is the inventory step in how to inventory products governed by ALAs.
Reconciling entitlement against deployment
The core of a reconstruction is the reconciliation: setting the evidenced entitlement for each product against what is deployed, and classifying every divergence. Some divergences are genuine gaps the buyer must address; many are artefacts of how the vendor would measure, such as non production environments counted as production, decommissioned systems still on the books, or capacity counted at a peak that was never sustained. Separating the real gaps from the measurement artefacts is what the reconstruction exists to do, and the discipline of reconciling the two sides is examined in reconciling ALA entitlements before an audit.
Evidencing every line
A reconstruction is only as strong as the records behind each line, because an entitlement asserted without proof will not survive a vendor challenge, and a deployment fact stated without evidence carries no weight in a rebuttal. For each product, the reconstruction cites the authorizations that establish entitlement and the deployment records that establish use, so that every line can be defended on its own. What records carry this weight is the subject of what records support an ALA entitlement position, and the way that evidence is organised for a rebuttal is examined in documenting ALA entitlements for a rebuttal.
How a reconstruction reduces the number
In a recent engagement, a buyer faced a finding built entirely on the vendor's measurement of deployment, with no independent position to test it against. Preparing the reconstruction reconciled entitlement against deployment product by product and showed that much of the asserted gap was measurement artefact rather than real shortfall: environments the finding counted as production fell under non production rights, decommissioned systems were still in the count, and separately purchased entitlement the finding had ignored covered a further slice. Each reconciled line subtracted from the claim. This is the ordinary mechanism: the reconstruction converts a vendor measurement into a tested, line by line comparison, and every line where the buyer's evidenced position differs from the finding's assumption reduces the number. It is the foundation of the 68 percent average reduction we have achieved across more than 200 defended audits.
Carrying the reconstruction into resolution
A completed reconstruction does more than rebut the present finding; it frames the settlement and defines what a clean forward agreement should protect. The position the reconstruction establishes becomes the anchor for resolving the finding on the buyer's terms and converting forward into a clean OpenPass arrangement with audit protections and defined metrics, so the same gaps cannot be reopened later. A buyer that prepares a reconstruction is not reacting to the vendor's number but proposing its own. If a finding has measured your deployment and presented it as your obligation, open a case and we will reconstruct the entitlement position that the finding has to answer.
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.
A measurement is not an obligation
We reconstruct your entitlement independently and reconcile it against deployment, separating the real gaps from the measurement artefacts, before the vendor number is allowed to stand. Open a case.
Open A Case →