Reducing a Documentum finding with usage evidence

A Documentum finding is built from a list of accounts, but a list says nothing about whether those accounts are used. Usage evidence is what converts a raw roster into a defensible count, because an account that shows no activity over the contract period is hard for any audit to charge as an active consumer.

Most Documentum findings begin with an extract: every account that exists in the repository, counted as a chargeable user or consumer. That extract overstates almost by design, because repositories accumulate accounts that were created and forgotten, staff who left, processes that run under their own identities, and people who hold access they never exercise. Usage evidence is the record that exposes the gap between accounts that exist and accounts that are used, and reducing a Documentum finding with usage evidence is, in practice, the work of attaching activity data to every account the audit wants to charge. Because the OpenText EULA makes compliance the sole responsibility of the licensee, the buyer carries the burden of producing that evidence, but the evidence lives in the buyer's own systems, which makes the burden an advantage.

Why usage evidence carries weight

The licensed unit in Documentum is the named user or consumer as the entitlement defines it, and that definition is about who actively uses the system, not who has a row in a table. An audit can assert that an account is a consumer because it appears in the extract, but it has little ground to maintain that assertion against a log showing the account performed no meaningful action across the measured period. Usage evidence shifts the argument from existence to activity, and activity is the thing the license is actually meant to meter. A dormant account, a departed employee's account, a service identity that performs no human action, all of these can be documented out of the count with the right activity records attached.

The principle is that an account that does nothing is not a consumer of anything. The extract proves existence; usage evidence proves consumption, and only consumption is chargeable.

What usage evidence looks like

Activity and login logs

The backbone of a usage argument is the activity record: login history, document actions, session data showing whether an account did anything over the contract period. Accounts with no activity are candidates for removal, and the same logs support the wider headcount challenge in how to challenge a Documentum repository headcount.

Directory and leaver data

Cross referencing the extract against directory and human resources data identifies accounts belonging to people who have left or moved on. Those accounts persist in the repository long after the person is gone, and pairing the absence of activity with a leaver record is decisive.

Service and read only classification

Usage patterns also identify service accounts, which act continuously but never as a person would, and read only access, which performs no chargeable action. These classifications connect to service and dormant accounts counted as Documentum consumers and Documentum read only users and the consumer definition.

How we apply usage evidence under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take over the channel and, critically, preserve the usage logs alongside the repository extract, because activity data that is not captured at the start can be impossible to reconstruct later.

Reconstruct. We build the effective license position by attaching usage evidence to every account, classifying each as active, dormant, departed, service, or read only, and assembling the activity backed count that the entitlement actually supports.

Rebut. We present the finding account by account, each removal supported by its activity record, so the audit reviews usage data rather than assertion. The finding falls by the documented value of every account the usage evidence disqualifies.

Resolve. We settle on the activity backed count and, where it serves you, convert forward into an OpenPass agreement that records how usage defines a consumer, so the next audit starts from an agreed activity standard rather than a raw extract.

An anonymised outcome

Usage evidence is decisive because of 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 every dormant account removed takes that fourfold charge with it. 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, and the reduction was carried by usage and directory records that proved, account by account, which identities were never active consumers.

Let the activity decide the count

The lasting lesson is that the strongest Documentum argument is not rhetorical but evidentiary, and usage data is the evidence. A buyer who can show, with activity logs, that a large share of the extracted accounts performed no meaningful work over the contract period has already won most of the reduction before any definitional argument begins. To turn that evidence into a finished position, read how to document Documentum named users for a rebuttal, and to set the groundwork, read how to reconcile Documentum entitlements before an audit. For the full method see our ECM and Documentum audit defense track and our complete OpenText audit defense playbook for 2026. If your finding rests on a raw account list, open a case.

What good usage evidence looks like in practice

Not all usage data carries equal weight. The strongest evidence covers the full contract period rather than a recent snapshot, because an account dormant for two years can still look active if the window is only the last month. It ties activity to identity, so that an absence of action can be matched to a specific account and, where relevant, to a departed person in the directory. And it distinguishes meaningful work from background noise, since an automated touch or a single incidental login is not the activity that defines a consumer.

We assemble this evidence into a structured table that pairs each account with its activity record and a conclusion, which is the form that lets an audit review the position line by line. Building that table is the bridge between raw logs and a finished rebuttal, and it connects directly to how to document Documentum named users for a rebuttal.