ALA territory and use restrictions

A license is not only a quantity; it is a quantity bounded by where and how it may be used. ALA territory and use restrictions are the scope conditions in an Additional License Authorization that say in what geography, by which entities, and for what purposes the licensed software may run. A finding that counts deployments outside those boundaries, or that ignores conditions limiting how a quantity may be used, overstates the obligation by treating scope as if it did not exist.

This field note explains what territory and use restrictions cover, how findings overreach on scope, and how to defend the boundary the authorization actually drew. It pairs with our ALA and entitlement review track.

Scope is part of the entitlement

An order form names a quantity, but the authorization names the conditions under which that quantity may be used. Territory restrictions limit the geography in which the software may run. Use restrictions limit the purpose, the permitted entities, or the manner of deployment. These conditions are not fine print around the entitlement; they are part of it. A quantity read without its scope conditions is only half the grant, and a finding built on quantity alone misunderstands what was actually licensed.

How territory restrictions are misread

Territory restrictions can cut both ways in a finding. Where a license is granted for a defined territory, an auditor may count deployments and users in that territory correctly but fail to account for how the territory boundary affects the count, or may sweep in entities the territory grant was always understood to cover. The defensible reading establishes exactly what the territory clause permits and tests the count against it. Where the finding has counted as if no territory boundary existed, or has misapplied one, correcting the reading aligns the count with the grant.

How use restrictions inflate a finding

Use restrictions are where scope most often inflates a count. A grant limited to a particular purpose, a permitted set of affiliates, or a defined manner of deployment does not authorise unlimited use, but it equally does not justify counting permitted use as if it were excess. The error runs in the inflating direction when an auditor counts deployments the use grant actually permits, or counts affiliated entities the authorization covered, as though each were a separate unlicensed use. Reading the use restriction precisely separates the use the grant permits from the use it does not, and only the latter belongs in a finding.

Affiliates and permitted entities

A common scope question is which corporate entities the license covers. Authorizations frequently permit use by affiliates or defined group entities, and a finding that counts an affiliate's permitted use as a separate, unlicensed deployment overstates the obligation. Establishing which entities the grant covers, and showing that the counted use falls within them, removes a category of finding that arises purely from a narrow reading of who is permitted to use the software. This is part of reading the grant as a whole rather than line by line in isolation, a discipline we set out in defending an ALA based finding line by line.

Scope must be read with the metric

Territory and use restrictions cannot be read apart from the metric. The metric counts something; the scope conditions say where and how that something may exist. A count that applies the metric correctly but ignores scope, or that reads scope without reference to what the metric measures, produces a figure neither clause supports on its own. Reading the two together, as the authorization intends, is what fixes the count, and it connects directly to the relationship between the grant and the order examined in ALA metric definitions versus the order form.

How we defend the scope boundary

The defense reconstructs the scope conditions from the authorization that governed each purchase and tests the finding against them. We establish the territory permitted, the use permitted, and the entities covered, then show where the finding counted deployment outside the metric but inside the scope, or treated permitted use as excess. Where the finding ignored a scope condition that limits what counts, the count is corrected to the boundary the grant actually drew. This is the Reconstruct and Rebut work in our method, and disqualifying counts that scope does not support is consistent with the kind of correction reflected in our E-01 case file, where a seat count finding moved from $7.2M to $1.6M, a 78 percent reduction.

Scope evidence is documentary

Scope disputes are won on documents, because territory and use are matters of contract language, not of measurement. The authorization states the boundary; the buyer's records show that the deployment falls within it. A buyer who holds the governing authorization and a clear record of where and by whom the software is used can answer a scope based finding with the grant itself. The cleaner the record of deployment geography and permitted entities, the faster a scope overreach is corrected, because there is little to argue once the boundary and the deployment are both on the table.

Closing the scope question forward

Once a finding has been corrected to respect the territory and use boundary, the forward agreement should state the scope plainly: the territory, the permitted purposes, and the covered entities, written so the next review cannot treat permitted use as excess. Recording the scope clearly in the forward terms removes the ambiguity that let the audit overreach, so a future review starts from an agreed boundary rather than a contested one. Resolving the present finding and fixing the scope forward are two halves of the same work, and completing both keeps territory and use from becoming a recurring source of inflation.

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. If a finding counts deployment your scope conditions actually permit, open a case.