What to do in the first 72 hours
Acknowledge receipt politely and commit to nothing else. Do not confirm the scope Oracle proposes, do not agree a kickoff date, and do not run any collection scripts. The audit clause in your Oracle Master Agreement gives you a response window, usually 30 to 45 days, and both the timeline and the scope are negotiable before you agree to anything. Read the audit clause in your Oracle contract before you reply, because the contract, not the letter, defines what Oracle may audit and how.
Control the clock, not the other way around
Audits are also a sales channel, and the pressure to settle fast is deliberate. Use the window to agree scope in writing and prepare a defensible measurement, rather than rushing to run whatever Oracle sends. The kickoff call is where scope is won or lost, and agreeing to nothing on the first call is a valid first move.
Scripts are a decision, not an obligation
Oracle's collection scripts can overcount across virtualization layers, and a single Enterprise Manager click can register a pack as in use. Review what the scripts collect, and where appropriate provide equivalent data instead. See alternatives to running Oracle's scripts before anything is sent.
Who to involve, and when
Someone must read the audit clause immediately; full legal escalation is usually a later move. When to bring legal into the audit covers the trigger points. An independent buyer side team like our Oracle audit defense practice manages the whole sequence, from the first reply to the signed settlement, on your side of the table only.
| When | Do | Do not |
|---|---|---|
| Day 1 | Acknowledge receipt, start the contract reading | Confirm scope or timeline |
| Days 2–3 | Map the estate the letter touches, brief the team | Run any scripts |
| Week 1 | Negotiate scope and timeline in writing | Volunteer data Oracle did not request |
| Weeks 2–6 | Build the defensible count, review before submission | Accept the preliminary finding as a bill |