Why this matters.
An IBM audit is a defined commercial process with predictable phases and predictable deadlines. The buyer that maps the timeline at week one of the engagement has a structural advantage over the buyer that responds incident by incident. This article is the buyer side reference for the typical IBM audit calendar.
Phase 1. The audit letter (week 0 to week 2).
The audit begins with a letter. The letter names the audit period, the products in scope, the firm conducting the audit, and the requested kickoff date. The buyer has rights at this step that are best exercised before any data is sent. The standard buyer side action is to confirm the audit scope in writing, defer the kickoff by 30 to 45 days, engage independent advisory, and run a parallel internal self assessment. See audit notification response.
Do not send any data at this stage. The data scope is a separate negotiation that takes place in phase 2. The audit defence work is a structured engagement starting from this letter. The audit defense service is the engagement frame.
Phase 2. Scope negotiation and data request (week 2 to week 8).
The auditor sends a Data Request List. The list typically runs to 30 to 60 pages and asks for ILMT reports, hardware inventory, virtualisation configuration, contract evidence, and operational logs. The buyer side action is to negotiate the data scope down to the contractually required minimum. The data list is the most consequential single negotiation inside the audit. See audit legal rights.
The internal self assessment runs in parallel. The independent advisory work runs in parallel. The ILMT cleanup, where required, runs in parallel. The buyer arrives at the data submission deadline with a defensible position and the auditor receives a clean, complete, narrow data set.
Phase 3. Data review and clarification (week 8 to week 16).
The auditor reviews the data and returns a list of clarification questions. The clarification questions are the audit firm asking the buyer to fill the evidentiary gaps the audit team has identified. Each clarification question is an opportunity and a risk. A poorly answered question typically widens the finding. A well answered question typically narrows it.
The buyer side action is the structured response. Each question is answered with the evidence that supports the buyer position, the contractual reference that bounds the question, and the operational record that demonstrates compliance. The discipline is the same discipline the litigation team applies to discovery production.
Phase 4. Preliminary findings (week 14 to week 18).
The auditor produces a preliminary findings document. The preliminary findings are the auditor opening position. The opening number is typically 200 to 400 percent of the eventual settlement number. The buyer side action is the formal response to the preliminary findings with documented counter positions on each material item.
This is the step where the audit converts from a data exercise to a commercial negotiation. The strength of the buyer side position at this step is set by the work done in phases 1 to 3. A buyer that arrives at preliminary findings without prepared counter positions has no commercial leverage. See audit settlement.
Phase 5. Settlement (week 16 to week 24).
The settlement phase is the commercial negotiation against the preliminary findings. The buyer position is documented. The IBM commercial team enters the conversation. The discount levers, the multi year commitment, the renewal sequencing, and the bundling decisions all enter the conversation at this step.
The disciplined settlement methodology, applied across 200 plus engagements, has reduced the initial findings by 40 to 60 percent. The audit settlement negotiation white paper documents the framework.
Phase 6. Statement of Compliance and close (week 22 to week 26).
The audit closes with a signed Statement of Compliance. The Statement records the settled position and the remediation commitments. The buyer side action is to ensure the Statement language is bounded, the remediation timeline is realistic, and the renewal terms are not entangled with the Statement.
The post audit work is the discipline that prevents the next audit. The ILMT environment is tightened. The exception log is documented. The harvested entitlement is captured. The renewal calendar is set 12 to 18 months ahead. See self assessment and the audit pillar.
Related reading.
- The IBM Audit Complete Guide (pillar)
- What triggers an IBM audit
- Your IBM audit legal rights
- IBM audit settlement negotiation
- How to respond to the IBM audit letter
- Drafting the audit response letter
- IBM audit defense service
- Audit Defense Playbook (white paper)
- Renewal negotiation (cross cluster)
- IBM Licensing Complete Guide (cross cluster)
Ready to put this work into practice?
An independent senior advisor on your IBM estate. No resell margin, no IBM relationship to protect, no time pressure to push a product. Just the buyer side view.