HomeJournal › Negotiating OpenPass measurement and reporting clauses
OpenPass & Negotiation · Field Note

Negotiating OpenPass measurement and reporting clauses

Published 2026-05-29 · By OpenText Audit Defense · Buyer side only

The measurement and reporting clauses in an OpenPass agreement decide how the buyer's usage will be counted for the life of the term, and they are written, in an opening draft, entirely in the vendor's interest. They name the tools, the methods, the reporting cadence, and the uses to which a usage report can be put, and every one of those choices can quietly become the basis of the next finding. Negotiating OpenPass measurement and reporting clauses means taking control of what is measured, who measures it, how the result is calculated, and crucially what a report can and cannot be used for, so that an ordinary act of reporting does not turn into an admission.

These clauses are easy to overlook because they read as procedure rather than money. In practice they are where the metric definitions are either protected or undone, and where the buyer either keeps the right to contest a count or signs it away in advance.

Who runs the measurement, and on what tools

An opening draft typically gives the vendor the right to run its own measurement scripts on the buyer's systems and to treat the output as authoritative. A vendor measurement tool is built to produce the largest defensible number, and accepting its output as conclusive removes the buyer's ability to challenge it. The clause should require that any measurement method be disclosed and agreed in advance, that the buyer may run or verify the measurement itself, and that no script output is treated as conclusive without the buyer's review. The discipline of reconstructing the position independently, rather than accepting a vendor count, is described in building an OpenPass target baseline before negotiation.

A vendor measurement tool is built to produce the largest defensible number. A clause that treats its output as conclusive signs away the right to contest the count before the count is even taken.

Locking the calculation to the agreed metrics

Measurement clauses only protect the buyer if they are tied to the metric definitions negotiated elsewhere in the agreement. A precisely defined metric is worthless if a separate measurement clause permits the vendor to calculate it by a different method. The reporting and measurement language must reference the agreed definitions explicitly and state that the measurement will be performed according to them and no other interpretation. The work of fixing those definitions is covered in defined metrics in an OpenPass enterprise agreement and the way to contest a loose one in how to challenge OpenPass metric definitions. Measurement and definition have to be negotiated as a single, consistent package.

Reporting cadence and the self report trap

Many drafts impose a periodic self reporting obligation, requiring the buyer to submit usage figures on a schedule. This sounds administrative but creates recurring opportunities for the vendor to open a dispute without invoking the formal audit right, and a careless report can be treated as an admission of overuse. Where a reporting obligation cannot be removed, define exactly what is reported, on which agreed metric, at what interval, and in what format, and limit it to the minimum the agreement genuinely requires. A vague reporting clause is a standing invitation to a finding between audits.

What a report can and cannot be used for

The most important and most neglected piece of a reporting clause is the limitation on use. A usage report submitted in good faith should not be convertible into a compliance finding without the buyer's right to review, correct, and contest the figures first. The clause should state that a report is provided for administration, that it is not an admission of noncompliance, and that any discrepancy is subject to the dispute process rather than to immediate remedy. Without this, the buyer's own reporting becomes the evidence used against it. The protections that keep routine reporting from becoming a dispute are set out in audit protections to negotiate into an OpenPass agreement.

Frequency, notice, and the limits of the measurement right

A measurement right should not be exercisable at will. The grounding standard is that OpenText gives seven days notice before an audit, and the agreement should not permit measurement on terms more permissive than that. Limit the measurement right to a defined frequency, require reasonable written notice, confine it to records relevant to the licensed products, and prevent any clause that lets the vendor change its measurement methodology mid term. The broader question of what audit and measurement language to strike or rebalance is covered in what audit clauses to remove from an OpenPass draft. A measurement right with no frequency limit and no notice requirement is an open ended audit right by another name.

How this works in practice

In a recent engagement, a buyer had signed an earlier agreement whose measurement clause let the vendor run its own tooling and treat the output as conclusive, with a quarterly self reporting obligation and no limitation on how a report could be used. A routine report was being turned into a finding. When the estate was converted forward into a new OpenPass agreement, the defense rewrote the measurement and reporting language: measurement methods had to be agreed and verifiable, the calculation was tied to the negotiated metrics, the reporting obligation was narrowed and defined, and an explicit clause established that a good faith report was not an admission and that any discrepancy ran through the dispute process. The buyer kept the right to contest every future count. The discipline behind that rewrite runs through the complete OpenText audit defense playbook, and comparable outcomes appear across our engagements.

Controlling the count before it is taken

Negotiating OpenPass measurement and reporting clauses is about deciding, in advance, how usage will be counted and what the count can be used for. Require agreed and verifiable measurement methods, tie the calculation to the negotiated metrics, narrow any reporting obligation, and make explicit that a report is not an admission. Handled this way, the measurement clauses protect the buyer rather than arming the vendor. This work sits inside our OpenPass enterprise agreement negotiation track. If an OpenPass draft in front of you lets the vendor measure on its own terms, open a case before you sign the clauses that decide the next count.

If an OpenText or Micro Focus audit notice has arrived, the first seven days matter more than any week that follows them. OpenText Audit Defense is an independent, buyer side practice founded in 2020 by former vendor compliance leadership. Across more than 200 defended audits we have reduced the average finding 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.

Decide how usage is counted in advance.

We rewrite measurement and reporting clauses so methods are agreed and verifiable, calculation tracks the negotiated metrics, and a report is never an admission. Buyer side only. Not affiliated with OpenText Corporation.