How OpenText measures Exstream usage in an audit

An Exstream finding does not appear from nowhere. It is the output of a measurement process, and the buyer who understands that process can see where the resulting number was shaped. The vendor sends a notice, requests data and records, and applies a method to derive a volume figure from what it receives. Each step in that sequence is a place where the measurement can be steered toward the largest defensible reading, and each is a place the buyer can intervene. Knowing how OpenText measures Exstream usage in an audit is what lets a buyer respond to the measurement rather than simply receive its result.

This article walks through the measurement process, identifies where it overreaches, and explains how a buyer controls and corrects it. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

The measurement process step by step

The process generally follows a familiar arc. OpenText issues an audit notice, which under the EULA carries seven days notice and a right to copy relevant records. A global software compliance team, run with executive sponsorship, then requests usage data, output records, and configuration information, and a Compliance Manager prepares an entitlement and support review. From the records received, the team derives a measured volume and compares it to the entitlement to produce a finding. The records the vendor asks for, and which it is entitled to, are examined in what records does OpenText copy in an Exstream audit.

Where the measurement overreaches

The measurement overreaches at the same points the volume metric inflates, because the measurement is how those choices enter the finding:

• Unit selection. Counting at the page or component layer rather than the contractual layer, the subject of Exstream page and document counting explained.
• Channel multiplication. Counting each delivery separately, examined in Exstream output channel counting traps.
• Counting window. Reading a peak or seasonal surge rather than a representative period.
• Non production inclusion. Folding test, development, and disaster recovery runs into the production total, scoped in Exstream non production and test volume scope.
• Capacity for consumption. Treating provisioned capacity as produced output, examined in Exstream transactional versus capacity metrics.

How a buyer controls the measurement

The buyer's strongest move is to control what data reaches the vendor and in what form, so the measurement is built on the buyer's own reconstructed records rather than on raw exports the vendor interprets. Through a single controlled channel, the buyer provides records that are scoped, labelled, and tied to the contractual unit, and reconstructs the genuine production volume independently before any vendor measurement script runs. When the vendor's measured figure arrives, the buyer can then place its own reconstruction beside it and account for every difference. This is the discipline described in reconciling Exstream entitlements before an audit, and the rebuttal it supports is set out in defending an Exstream volume overclaim line by line.

How the four Rs apply to the measurement

The method is built around controlling the measurement. In the respond stage the firm takes over the single controlled channel inside the seven day notice window, so first contact, scope, and the NDA are managed and no raw output data reaches the vendor unmanaged. In the reconstruct stage it rebuilds the genuine production volume against the contractual unit and counting window, independently and before any vendor measurement script runs. In the rebut stage the vendor's measured figure is placed beside the reconstruction and every difference is challenged at its source: unit, channel, window, and production scope. In the resolve stage the settlement reflects the corrected measurement, and the forward agreement defines the metric so the next measurement is unambiguous. The earlier the buyer controls the data, the less the measurement can overreach.

A representative outcome

In a recent engagement, an Exstream finding had been measured from raw output exports the vendor interpreted on its own terms, folding non production runs and a peak counting window into a single large volume. The buyer reconstructed the genuine production volume from its own labelled records, scoped out the non production runs, and read a representative period, then placed its reconstruction beside the vendor's measurement and accounted for every difference. Once each overreach was traced to its source and corrected, the measured volume fell substantially. The matter settled well below its opening number, consistent with the reductions the firm sees across customer communications matters, with no figure introduced beyond what the production records contained.

The measurement in one line

OpenText measures Exstream usage by deriving a volume from records and assumptions the buyer can see, scope, and contest, and the finding is only as large as the most aggressive of those assumptions. Control the data, reconstruct independently, and the measurement returns to a defensible figure. To understand what that figure should cost, read how much does an Exstream volume finding usually cost, and to control your own measurement you can open a case with our team.

For the first week after a notice arrives, read the OpenText seven day notice response white paper.