UFT seat counting and concurrent license models
UFT seat counting depends entirely on which license model governs the deployment, named or concurrent, and a finding inflates when an audit applies the stricter named reading to seats the organization actually holds on a concurrent basis. Understanding the difference between the two models, and proving which one applies, is where a UFT finding either holds or comes apart.
UFT, the functional and regression testing tool in the ALM family, is commonly available under two distinct seat models. A named seat ties a license to a specific individual, who consumes it regardless of how often they use the tool. A concurrent seat is shared from a pool, consuming a license only while in active use, so a pool of concurrent seats can serve a far larger population of occasional users. The two models produce very different counts from the same installed base, and an audit that counts every install or every authorized user as if it were a named seat, when the entitlement is in fact concurrent, overstates the requirement dramatically. Because the EULA makes compliance the sole responsibility of the licensee, the buyer must establish which model applies and what the genuine usage is, and the entitlement and activity records that prove it belong to the buyer.
How UFT seat models differ
The named model counts people: every individual authorized to use UFT consumes a dedicated seat. The concurrent model counts simultaneous use: a pool of concurrent licenses is checked out when a session starts and returned when it ends, so the requirement is the peak number of simultaneous sessions, not the total number of people who might run the tool. For a team where many testers use UFT only occasionally, the concurrent model can require a fraction of the seats a named reading would imply. The inflation in a UFT finding very often comes from applying the named logic, count the installs, count the authorized users, to an estate that is genuinely entitled and used on a concurrent basis.
This is the same named versus concurrent tension that runs through the whole testing family, set out in named versus concurrent user counting in ALM audits. With UFT the distinction is especially valuable because functional testing is often intermittent, exactly the usage pattern a concurrent pool is designed to serve efficiently.
An audit counts every UFT install or authorized user as a named seat, even where the entitlement is concurrent. A concurrent pool consumes a license only during active use and serves a much larger population than its seat count. Applying named logic to a concurrent entitlement inflates the requirement far beyond genuine simultaneous use.
Where UFT seat counting overstates
Named logic on a concurrent entitlement
The largest overstatement is counting people when the license counts simultaneous sessions. Establishing which model the entitlement actually grants, and holding the count to it, is the heart of a UFT defense, and challenging an inflated headcount follows the approach in how to challenge an ALM concurrent user headcount.
UFT One and UFT Developer confusion
UFT exists in more than one edition, and counting one edition under the terms of another inflates the finding. The distinction between editions is set out in UFT One versus UFT Developer licensing, which matters because an audit can apply the wrong edition's entitlement to a deployment.
Idle and decommissioned installs
Installs left on retired machines or unused for long periods are not genuine seats, and counting them inflates the base. The same discipline applied to retired systems is described in decommissioned ALM projects still on the audit.
How we defend a UFT seat finding under the four Rs
Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take the single controlled channel and preserve the entitlement documents, the license server and check out records, and the install inventory, because the model argument depends on showing what the entitlement grants and how seats were actually consumed.
Reconstruct. We build the effective license position by establishing which model governs, named or concurrent, and reconstructing genuine usage, peak simultaneous sessions for a concurrent pool, real authorized individuals for a named entitlement, before any vendor measurement script runs.
Rebut. We challenge every line that applies named logic to a concurrent entitlement, counts the wrong edition, or includes idle and decommissioned installs. The finding falls by the difference between the named reading and the genuine concurrent requirement the records support.
Resolve. We settle on the reconstructed seat count and, where it serves the buyer, convert forward into an OpenPass agreement that records which model applies and how seats are measured, so the next review cannot reapply the stricter reading.
An anonymised outcome
The reason the model question is worth pressing is the remedy behind the finding. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so each seat removed by the correct model carries a fourfold saving. In a recent engagement the opening UFT count applied named logic to a concurrent pool that served an intermittent testing team; once the entitlement and check out records established the concurrent model and the genuine peak of simultaneous sessions, the count fell to a fraction of the opening figure. The pattern echoes our anonymised insurance ECM case, where a seat count finding dropped 78 percent from $7.2M to $1.6M once the count reflected genuine use rather than the widest reading.
Count seats the model actually grants
The lasting lesson is that UFT seat counting is meaningless without the model, and a buyer who establishes whether the entitlement is named or concurrent, then holds the count to genuine usage under that model, removes the inflation that a stricter reading creates. To prepare the entitlement picture, read reconciling ALM entitlements before an audit, and to address the named definition that governs related products, read Quality Center named user definitions and traps. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If a UFT finding has applied named logic to a concurrent entitlement, 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, 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.