Decommissioned ALM projects still on the audit

Decommissioned ALM projects are one of the quietest sources of audit inflation, because a project that was shut down months or years ago still leaves behind user records, server entries, and stored data that a measurement can sweep up as though the project were live. The way to defend a finding built on dead projects is to prove the date each one was retired and to remove the users and footprint tied to it from the count.

An Application Lifecycle Management estate accumulates projects the way any long running system accumulates history. Teams stand up a project for a release, work it hard for a year, then move on, and the project sits dormant or is formally retired without anyone removing the accounts that were once attached to it. When an audit measures the environment, it sees those residual records and, unless the buyer shows otherwise, treats every one as a current consumer of the license. The EULA places the burden of demonstrating the real position on the licensee, so the evidence that a project is dead has to come from the buyer, and producing it cleanly is where a decommissioned project finding comes apart.

Why decommissioned ALM projects inflate the count

A measurement script counts what exists at the moment it runs. It does not know that a project was retired last year, that its users were reassigned, or that the data was kept only for retention rather than active work. It sees user records, project entries, and server footprint, and it attributes all of them to the live entitlement. The result is a finding that charges for activity that stopped long ago, and the gap between the measured total and the genuinely active estate is exactly the amount that should never have been on the count.

The problem compounds with named user licensing, where each residual account on a dead project reads as a billable consumer. A user who left the company two years ago, or who was reassigned off a retired project, still appears in the records, and unless the buyer disqualifies that account it counts against the entitlement. This is the same disqualification logic applied to live populations in defending an ALM named user overclaim line by line, extended to accounts that should have been removed when the project closed.

What counts as a decommissioned project

A project is decommissioned when active work on it has stopped and it has been formally retired, even if its data remains in the system for retention or reference. The distinction that matters to the audit is between data that is merely retained and an application that is in active use, the same line drawn in records management generally. A retired project that holds historical data for compliance is not a live consumer of the license, and the users once attached to it are not active named users unless they are working on it today.

Establishing that line requires dating the decommission and showing that no current work depends on the project. Change records, project closure approvals, and access logs that go quiet after a known date are the evidence that fixes the retirement in time. Once a project is dated as dead, every account and every footprint element tied only to it drops out of the live count, which is why reconciling the estate before a measurement runs, as set out in reconciling ALM entitlements before an audit, matters so much.

How we defend a decommissioned project finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take over the single controlled channel and ensure that change records, project closure approvals, and access logs are preserved, because these are the documents that prove which projects were already dead when the measurement ran.

Reconstruct. We build the effective license position against entitlements before any vendor script runs, dating each retired project and separating the live estate from the residual one. The reconstruction establishes what was genuinely in use, so the dead footprint never enters the baseline.

Rebut. We challenge every line that counts a decommissioned project or its orphaned accounts as a live consumer, presenting the retirement date and the quiet access logs for each one. The finding falls by the full weight of the residual estate the measurement swept up.

Resolve. We settle on the count that reflects the active estate and, where it serves you, convert forward into an OpenPass agreement that records how retired projects are excluded, so the next review starts from a clean baseline rather than the accumulated history.

An anonymised outcome

The reason a decommissioned project finding is worth dismantling is the remedy that sits behind it. 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 every dead project left on the count multiplies into several charges at once. Our anonymised case files show what disqualifying records that do not belong can do: an insurance ECM seat count finding was reduced from $7.2M to $1.6M, a 78 percent reduction built entirely on removing accounts that should never have been counted. A decommissioned ALM project responds to the same discipline, because once the retirement date is on the table the residual estate has no claim on the live entitlement.

Clean the estate before the audit measures it

The durable lesson is that decommissioned projects are a documentation problem before they are a licensing problem. A buyer who retires projects cleanly, records the date, and removes the orphaned accounts gives an audit nothing to sweep up, and a buyer who has not done so can still defend the finding by proving each retirement after the fact. Either way the principle is the same: only the active estate counts. To prepare the position, read reconciling ALM entitlements before an audit and the rebuttal discipline in documenting concurrent ALM users for a rebuttal. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If an audit has counted retired projects against your live license, open a case.