HomeField Notes › Exstream · Reconstruction
Exstream · Entitlement Reconstruction

Preparing an Exstream entitlement reconstruction

An Exstream audit is decided less by the vendor's measurement script than by whether the buyer can show, independently, what it is actually entitled to and what it actually produced. The measurement script counts usage. It does not interpret the contract, it does not separate test volume from production, and it does not credit the buyer with the capacity the authorization already grants. That interpretation is the buyer's work, and it has to be done before the script runs, not after. Preparing an Exstream entitlement reconstruction means assembling the contracts, the authorizations, and the operational records into a single, defensible statement of the effective license position, so that when the finding arrives it lands against a position the buyer has already built rather than a blank page.

This article explains what an entitlement reconstruction contains, the order in which to build it, and how it changes the shape of the negotiation. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

Why reconstruction comes before measurement

Under the four Rs, reconstruction is the second step, and it sits deliberately ahead of any vendor measurement. The reason is structural. Once a measurement script has run and produced a number, the conversation anchors on that number, and every reduction has to be argued backward against it. A buyer that has already built its own effective license position arrives with a competing figure and a documented basis for it, so the negotiation becomes a reconciliation of two positions rather than a defence against one. The reconstruction is what makes the buyer's number credible: it is not an assertion, it is a calculation tied to the contract and the records. The discipline of doing this ahead of the vendor is the same one described in reconciling Exstream entitlements before an audit.

The principle

The party that builds the license position first sets the terms of the argument. Reconstruction before measurement turns a defence into a reconciliation.

What the reconstruction has to contain

An Exstream entitlement reconstruction pulls together four bodies of material, each of which the buyer controls and the vendor does not:

The reconstruction is the reconciliation of these four against each other: entitlements on one side, measured production on the other, with the metric definition as the bridge. Where the authorization grants capacity the buyer has not exceeded, that is credit. Where production records show test, reruns, or undelivered output, that is volume removed from the chargeable base.

Reading the authorizations correctly

The authorizations are the part of the reconstruction that most often moves the number, because the metric and the capacity they define are frequently more generous, or simply different, from what a measurement script assumes. A volume authorization may permit a capacity that the buyer is comfortably within once test and rerun volume is removed. A document metric may be defined in a way that does not support charging each output channel separately, the question examined in can OpenText count all output channels separately. Reading the authorization against the measurement, line by line, is where credits that a script would never apply on its own come into view. Because these authorizations govern most of the Exstream estate, this reading is also the connective tissue between the Exstream defence and the broader Micro Focus ALA and entitlement review work that applies across every acquired product line.

Building the production side from records

The measured side of the reconstruction is built from the same operational evidence used to challenge any volume finding. Scheduler and composition logs separate composed production from reruns and test executions. Delivery and output management records show which communications were actually delivered and through which channels. Non production environments are identified and their volume set aside, the scope described in Exstream non production and test volume scope. The aim is a production figure that reflects delivered communications and nothing else, assembled from records the buyer can stand behind. That same evidence then carries directly into the rebuttal, as set out in documenting Exstream output volume for a rebuttal and in reducing an Exstream finding with volume evidence.

A representative outcome

In a recent engagement, a buyer facing an Exstream review built its reconstruction before the vendor measurement was scheduled. The authorizations turned out to grant a volume capacity the buyer was within once test and rerun volume was separated, and the production records showed a delivered figure well below the usage the monitoring counters implied. When the finding arrived, the buyer did not argue against it from scratch; it reconciled it against a documented position it had already prepared, and the gap closed quickly. The matter settled far below the opening claim, consistent with the firm reductions, where the average finding has come down 68 percent across more than 200 defended audits since 2020.

How the reconstruction shapes the resolution

A reconstruction done well does more than reduce the current finding; it sets up the forward agreement. The metric definitions, capacity credits, and production baselines established during reconstruction become the terms the buyer carries into the resolution, so the next review starts from an agreed position rather than from another raw measurement. This is the point at which a clean reconstruction converts into durable protection, the conversion described across the OpenPass work. For the line by line method that turns a reconstruction into a settled finding, see defending an Exstream volume overclaim line by line, and to begin the work, open a case using the contact form on this site.

Why early reconstruction beats reactive defence

The strongest reason to prepare an Exstream entitlement reconstruction before a notice arrives is that the materials it depends on are easiest to assemble when no one is under pressure to produce them. Contracts and order documents are scattered across procurement, legal, and the application owners, and gathering them coherently takes time that a seven day notice does not allow. Authorizations have to be matched to the orders they govern, which is a careful exercise rather than a quick one. Operational logs that distinguish production from test and reruns age and roll over, so the records for the earlier part of an audit window can be lost if they were never captured for this purpose. A buyer that builds the reconstruction as a standing exercise, and refreshes it as the estate changes, holds a complete and current license position at all times, and can drop it into a defence the moment a review begins. The buyer that waits builds the same position under a clock, with gaps where the records have expired, and from a weaker starting point. The reconstruction is therefore not only a defensive document but a management one: it tells the buyer where its real exposure sits long before any vendor measurement, and it lets the buyer correct an overdeployment or under licensing on its own terms rather than discovering it inside a finding. That is the difference between meeting an audit with a prepared position and meeting it with a scramble, and across more than 200 defended audits it is consistently the prepared buyers who keep the most of the reduction.

Build your Exstream position before the vendor measures

We assemble your contracts, authorizations, and production records into a defensible effective license position, so the finding lands against a number you have already built. Open a case and we will start your Exstream entitlement reconstruction.

Open a case →

If an OpenText or Micro Focus audit notice has arrived, the first seven days shape the outcome more than any week that follows. OpenText Audit Defense is an independent, buyer side practice founded in 2020 by former vendor compliance leadership. We have defended more than 200 audits, brought the average finding down by 68 percent, and mitigated more than $90M in claims against vendor positions. We do not resell OpenText software and we are not affiliated with OpenText Corporation. To open a case, use the contact form on this site.