Preparing a Documentum entitlement reconstruction

The single most valuable thing a buyer can do before a Documentum audit measures anything is to reconstruct the entitlement position independently. A reconstruction is the buyer's own account of what was licensed, what is deployed, and who genuinely uses it, built from records rather than from the vendor's extract, and it is the foundation every later argument rests on.

An audit produces a finding by running its measurement against your environment and comparing the result to its record of your entitlements. If the only version of the entitlement position is the vendor's, the buyer is arguing against the vendor's math with the vendor's numbers. A Documentum entitlement reconstruction changes that by establishing an independent baseline: a complete picture of the licenses held, the systems deployed, and the active users, assembled and documented by the buyer before any vendor script runs. Because the OpenText EULA makes compliance the sole responsibility of the licensee, the buyer is expected to be able to account for the position anyway, so building the reconstruction is both a defense and a duty. Preparing it well is what makes the difference between reacting to a finding and contesting it from a position of knowledge.

What a reconstruction establishes

A reconstruction answers three questions with evidence. First, what is entitled: every license, its metric, its quantity, and the terms that govern it, drawn from contracts, order forms, and amendments. Second, what is deployed: every Documentum repository, server, and module actually in service, with the non production and decommissioned systems clearly separated. Third, who uses it: the genuine active user or consumer count, with dormant, departed, service, read only, and duplicate accounts identified. Together these produce the effective license position, the count the entitlements actually support, against which any vendor finding can be measured. The reconstruction is not an estimate; it is a documented record, and its value is precisely that it can be defended line by line.

The principle is that the buyer who knows the position can contest the finding, and the buyer who does not is left negotiating against a number they cannot independently check. The reconstruction is the knowledge that makes the rebuttal possible.

What records to gather

Entitlement records

Contracts, order forms, amendments, and support renewals establish what is licensed and on what metric. Assembling and interpreting these is the core of how to reconcile Documentum entitlements before an audit.

Deployment inventory

A record of every repository, server, and module in service, with non production and retired systems flagged, supports the arguments in Documentum non production environments and license claims and decommissioned Documentum repositories still on the audit.

User and usage data

Repository extracts paired with activity logs and directory data establish the genuine active count, the evidence discipline set out in reducing a Documentum finding with usage evidence and documented as in how to document Documentum named users for a rebuttal.

How the reconstruction fits the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. In that window we take over the channel and preserve every record the reconstruction needs, entitlements, deployment inventory, extracts, usage logs, and directory data, because the reconstruction can only be as complete as the data captured at the start.

Reconstruct. This is the reconstruction itself. We build the effective license position independently, against entitlements and the Additional License Authorizations where relevant, before any vendor measurement script runs, so the buyer enters the process with a documented baseline rather than a blank page.

Rebut. We use the reconstruction to challenge the finding line by line, setting the documented position against the vendor's count so every difference can be examined and defended. The finding falls to the figure the reconstruction supports.

Resolve. We settle on the reconstructed position and, where it serves you, convert forward into an OpenPass agreement that records the agreed baseline, so the next audit starts from the reconstruction rather than a fresh extract.

An anonymised outcome

The reason the reconstruction is worth the effort 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 an independent baseline that removes unsupported counts removes that fourfold charge with them. In our anonymised insurance engagement, case file E-01, a Documentum centred ECM finding fell from $7.2M to $1.6M, a 78 percent reduction, built on exactly this kind of reconstruction: a documented position of entitlement, deployment, and active use set against the vendor's opening count.

Build the baseline before the audit does

The lasting lesson is that the reconstruction is the foundation, and everything else, the usage arguments, the consumer definitions, the non production and decommissioning challenges, builds on it. A buyer who arrives at an audit with a documented, independent entitlement position has already changed the contest from accepting a number to testing it. To start, read how to reconcile Documentum entitlements before an audit, and to see how the reconstruction becomes a rebuttal, read defending a Documentum seat overclaim line by line. For the full method see our ECM and Documentum audit defense track and our complete OpenText audit defense playbook for 2026. To build your reconstruction with us, open a case.

When to start the reconstruction

The best time to build a reconstruction is before any notice arrives, because the records it depends on, contracts, deployment inventories, usage logs, and directory data, are easiest to assemble when no clock is running. An organization that maintains a current effective license position is never caught flat, and it enters any review able to test the finding immediately rather than scrambling to understand its own estate.

Where a notice has already landed, the reconstruction still comes first, built inside the seven day response window using the records preserved at the start. Either way, the reconstruction is the asset that every later argument draws on, and keeping it current is the difference between defending an audit and being surprised by one. It is the foundation beneath the work described in defending a Documentum seat overclaim line by line.