White Paper · LMS Audit Edition
Oracle Audit Day-by-Day Field Manual: The First 90 Days of an LMS Audit, Hour-by-Hour
Last updated: June 2026
An Oracle LMS audit is won or lost in the first 21 days. The engagement letter sets the audit scope. The first conference call sets the evidence framework. The first USMM run, the first GLAS portal upload, the first written response to the LMS auditor's clarification question — each of those moments anchors the audit toward a defensible resolution or toward a multi-million-dollar back-licence claim. There is no second draft of those first responses. This 56-page field manual is the day-by-day playbook — what to do on day 1, day 7, day 21, day 45 and day 90 of an Oracle LMS audit, with the engagement-scope language, the USMM and Reviewlite script analysis, the GLAS portal evidence pattern, the back-licence claim counter, and the settlement negotiation calendar that takes the audit from notice to closed resolution inside the defensible window.
Why Oracle's LMS team relies on speed asymmetry: Oracle's LMS audit engagement is calibrated around the customer being slower to respond than the auditor is to ask. Every clarification question, every script-output request and every evidence ask is timed to land while internal stakeholders are still confused about the scope. The buyer-side counter is a day-by-day calendar that pre-stages the response framework, the evidence package and the audit-defence team before the auditor asks. The Field Manual is that calendar — pre-staged for the day the engagement letter lands, not constructed in reaction to it.
What the Day-by-Day Field Manual Covers
- Day 1 — engagement letter response: the written acknowledgement language, the audit scope clarification ask, the data-protection and confidentiality framework, the named-point-of-contact appointment, and the audit-defence team formation that happens inside 72 hours of receipt
- Day 2–7 — scope negotiation: the LMS-typical scope expansion pattern, the buyer-side counter that contains scope to the specific contract and CSI, the Audit Right clause analysis, and the documented precedent for scope reduction
- Day 8–21 — evidence framework: the USMM script analysis, the Reviewlite output interpretation, the Tideway scan position, the GLAS portal upload sequence, and the evidence-by-exception pattern that does not over-disclose
- Day 22–45 — first findings response: Oracle's preliminary findings letter, the back-licence claim pattern, the line-by-line response framework, the Database Option mis-attribution counter, and the Named User Plus reconciliation that closes the most common Oracle finding category
- Day 46–60 — secondary evidence: the targeted evidence pull, the contract-as-written defence, the Core Factor Table application against the deployed processor population, and the partitioning policy challenge
- Day 61–75 — settlement framing: the back-licence claim negotiation, the support-back-fee challenge, the future-licensing-commitment leverage, the cloud-conversion offer, and the documented settlement ratios across comparable LMS audits
- Day 76–90 — settlement closure: the final settlement letter language, the audit-closure certificate, the precedent-protection clause, the future-audit-window agreement, and the post-audit support contract clean-up
- The 11 LMS evidence categories — USMM Database output, GLAS portal Java extract, Reviewlite Middleware output, Tideway scan, Options usage report, NUP reconciliation, virtualisation evidence, partitioning policy evidence, cloud deployment evidence, support contract reconciliation, prior-audit settlement evidence
- Communications calendar — every internal stakeholder briefing, every executive update, every legal counsel checkpoint, every external counsel touchpoint, every Oracle-facing written response, and the cadence that holds the audit-defence team aligned
- The audit-defence retainer — the team composition (former LMS executive, former Oracle Sales executive, contract counsel, technical evidence lead), the engagement model, and the documented audit outcomes that the retainer structure produces
Field Manual Sections
Day 1
Engagement Letter Response & Team Formation
Day 2–7
Scope Negotiation & Audit Right Clause
Day 8–21
Evidence Framework — USMM, GLAS, Reviewlite
Day 22–45
First Findings & Line-by-Line Response
Day 46–60
Secondary Evidence & Core Factor Defence
Day 61–75
Settlement Framing & Back-Licence Counter
Day 76–90
Settlement Closure & Audit Certificate
Reference
11 LMS Evidence Categories — Per-Script Analysis
Cadence
Communications Calendar & Stakeholder Map
Team
Audit-Defence Retainer Composition
Framework Insight 01
"The engagement letter is the audit. Oracle's LMS engagement letter sets the scope, the evidence framework, the timeline and the negotiating posture for the entire audit. Customers who treat the engagement letter as an administrative formality lose the audit before evidence is exchanged. Customers who treat it as the first negotiating instrument — and respond inside 72 hours with the scope clarification, the named contact, the data-protection framework and the audit-defence team appointment — set the floor on the entire audit outcome."
Framework Insight 02
"Oracle's preliminary findings letter is the moment the audit can be reframed. Across documented LMS audits, the preliminary findings overstate the actual compliance gap by 60–85%. The reason is structural — the USMM and GLAS scripts capture deployed state, not contracted entitlement, and the Database Option attribution model is calibrated to maximise the back-licence claim. The line-by-line response to the preliminary findings is where 60–85% of the claim is contained — but only if the response is filed inside the documented window with the contract-as-written defence and the NUP reconciliation."