Pass an IBM audit with the 90 day readiness checklist

What does an IBM audit readiness check cover?

A readiness check tests whether you could prove compliance today, before IBM asks. It walks your ILMT coverage, your entitlement records, and your sub capacity proof against what an auditor would request.

Buyers who skip the check find the gaps during the audit instead. A readiness review surfaces them while they are still cheap to fix.

What does the ILMT coverage check confirm?

It confirms ILMT is deployed and reporting on every eligible core, not just installed. A tool that runs but misses clusters leaves those cores counted at full capacity.

What goes on the core checklist?

• Coverage: ILMT reporting on all eligible cores.
• Records: entitlements matched to deployed versions.
• Ownership: a named person who can produce the proof.

What gaps does a readiness check usually find?

Partial ILMT coverage, mismatched entitlement records, and missing ownership are the usual gaps. None of them require new licenses to fix.

How often should you run the check?

Run it quarterly, aligned to the ILMT reporting cycle. A check that matches the reporting cadence keeps the proof continuous instead of stale.

Which primary sources set the rules?

Confirm the sub capacity reporting requirement in the IBM License Metric Tool documentation and verify the eligibility terms on the IBM sub capacity licensing page before you rely on the proof.

Where is the common advice on audit readiness wrong?

The standard line is that installing ILMT is enough to secure sub capacity pricing, so a deployed tool means you are covered. We disagree.

In the reviews Morten ran, ILMT was often installed but silently missing eligible cores, so those cores would count at full capacity in an audit. The buyer side move is to verify ILMT reporting on every eligible core, reconcile entitlements to deployed versions, and assign one owner who can produce the proof on demand.

The buyer side move is to verify coverage, not assume that installed equals compliant.

An installed ILMT proves nothing in an audit; only continuous reporting on every eligible core does.

What should you do to get audit ready?

Verify, then fix. Proven coverage and reconciled records, not an installed tool, set your readiness.

1. Confirm ILMT reports on every eligible core.
2. List clusters where reporting is missing or stale.
3. Reconcile entitlements to deployed product versions.
4. Document sub capacity eligibility for each product.
5. Assign one owner for the compliance proof.
6. Set a quarterly readiness review cadence.
7. Close the highest exposure gaps first.

When should you bring in a buyer side advisor?

Bring help in before an audit letter arrives, while the gaps are still cheap to close. A readiness review done early is far cheaper than a settlement done late.