An Autodesk software audit typically spans 6–12 months from initial notification through final settlement — longer when findings are contested or commercial escalation is required. Enterprises that understand the timeline in advance are able to make better decisions at each stage: what to provide, what to refuse, when to challenge, and how to integrate commercial leverage.
This guide maps the complete audit process across eight stages, identifies the key decisions at each point, and explains what Autodesk's team is doing in parallel — information that most enterprises do not have until the process is well advanced.
Before the Audit: What Autodesk Sees
Understanding the audit timeline requires starting before notification. Autodesk does not select audit targets randomly. The License Reporting Tool (LRT) generates continuous telemetry from every installed Autodesk product — installation records, Named User authentication events, session data, version history, and geographic deployment patterns. This data is analyzed by Autodesk's License Compliance Organization (LCO) to identify accounts where deployment patterns suggest potential non-compliance.
The most common pre-notification triggers are LRT anomalies (deployment count materially exceeding subscription count), M&A activity (change of control, acquisition, divestiture), renewal resistance (declining renewal engagement or competitive alternative emergence), and perpetual-to-subscription migration gaps. By the time a notification letter arrives, Autodesk has typically been monitoring the account for 3–6 months and has a preliminary compliance theory in place.
This means the enterprise is not starting from zero at notification — it is entering a process that Autodesk has been preparing for considerably longer. For the complete trigger analysis, see our guide on what triggers an Autodesk software audit.
Stage 1: Audit Notification (Day 0)
What Happens: The Notification Letter
Autodesk's notification arrives as a formal letter or email from the License Compliance Organization (LCO) or a third-party audit firm (typically BSA, FTI Consulting, or KPMG). The letter identifies the audit scope, requests document production, and establishes initial deadlines. There are four letter types: Type 1 (Formal Audit Notification), Type 2 (Compliance Inquiry), Type 3 (True-Up Demand), and Type 4 (Post-Transaction). Each requires a different response strategy.
The first 72 hours after notification are the most consequential. Organizations that engage independent advisory within this window achieve 31% lower final settlements on average. After initial communications are made — even informal ones — positions harden and the scope of what has been acknowledged becomes difficult to retract.
The key actions in Stage 1: Do not respond to the notification letter without advisory review. Forward to legal and IT leadership immediately. Do not conduct internal compliance self-assessment and share results with Autodesk's team — this is the most common mistake, and it locks in a count before your independent baseline is established. Do not make written or verbal commitments about cooperation scope. See our complete audit letter response guide for the day-by-day action framework.
Stage 2: Initial Response Period (Days 1–30)
What Happens: Scope Definition and Response Framing
Autodesk's team will follow up the notification letter with requests for specific data. These typically exceed the contractual audit scope — 78% of initial audit requests include data categories the agreement does not require the enterprise to produce. Your written response must formally establish the scope boundary, acknowledge the contractual audit obligation, and decline out-of-scope requests with specific contractual citations.
What Autodesk is doing in parallel: the account team and LCO are sharing the account profile, renewal timing, and preliminary LRT analysis. The audit is not managed in isolation from commercial relationships — the two tracks are coordinated, and renewal timing significantly affects the audit's commercial resolution trajectory.
For scope limitation strategy and the complete list of what you are not required to provide, see our audit scope limitation guide and the Understanding Your Autodesk Audit Rights white paper.
The Autodesk Audit Playbook
Complete methodology for navigating the full audit process — from notification through settlement. Covers every stage in this guide with detailed decision frameworks and evidence requirements.
Access the White PaperStage 3: Data Collection and Entitlement Assessment (Days 15–60)
What Happens: LRT Data Submission and Independent Baseline
Autodesk will request LRT export data. This is the core of their assessment methodology — and providing LRT data without an independent baseline means Autodesk's measurement becomes the only measurement. Your independent baseline should be in development simultaneously, comparing ITAM scan data, admin console records, HR employment records, and agreement entitlements against the LRT figures.
The most critical work in this stage is the inactive Named User identification process. An enterprise with 500 Named Users and a 20% inactive rate has 100 users appearing in LRT data who are not actively using Autodesk products. Identifying and documenting these users before the compliance assessment is submitted reduces the finding basis before it is ever formally established.
| Data Request Type | Contractually Required | Recommended Approach | If Provided Without Review |
|---|---|---|---|
| LRT installation export | Generally yes (within scope) | Provide with written cover letter limiting scope; obtain independently first | Locks in LRT count as baseline — difficult to challenge later |
| Named User license assignments | Generally yes | Provide admin console export; accompany with reclamation log | Inactive users included without correction |
| HR employment records | No — out of scope | Decline with contractual citation | Expands finding basis to include contractor population |
| Network architecture diagrams | No — out of scope | Decline with contractual citation | Expands geographic and virtual deployment finding basis |
| Software purchase invoices | Generally yes (entitlement verification) | Provide; use to establish entitlement baseline simultaneously | Generally low risk; establishes entitlement record |
Stage 4: Preliminary Findings (Days 45–90)
What Happens: Autodesk Issues Preliminary Compliance Position
Autodesk's team will issue a preliminary compliance position — a statement of their initial finding based on LRT data and submitted documentation. This is almost never the final number, but it establishes an anchor. Organizations without independent baselines are at severe disadvantage here: the preliminary finding becomes the reference point for all subsequent negotiation unless actively challenged.
The preliminary findings document should be reviewed with independent advisory before any response. The response window is typically 30–45 days. Key review points: which specific LRT records form the basis of each finding, whether the finding reflects active Named Users or includes inactive/departed users, whether version misclassification is present, and whether the audit scope includes products outside the contractual scope definition.
Stage 5: Challenge and Counter-Position (Days 60–150)
What Happens: Formal Finding Challenges and Evidence Submission
The challenge phase is where the largest finding reductions occur. Organizations with documented independent baselines, reclamation logs, and Named User governance evidence achieve 67% finding reduction at this stage versus 31% for those without. The challenge is submitted as a formal written document — not informal email — citing each finding category, the specific evidence rebutting it, and the contractual basis for exclusion.
Challenge priority order: (1) inactive Named Users — highest volume finding, best evidence, strongest challenge success rate; (2) perpetual license overlaps — version continuity rights under maintenance plan terms; (3) contractor and third-party user misclassification; (4) background process attribution errors; (5) version misclassification against agreement version entitlement. For the complete challenge methodology, see our audit findings challenge guide.
Stage 6: Commercial Escalation (Days 90–180)
What Happens: Moving from Compliance to Commercial Resolution
The compliance team (LCO) has limited authority to reduce findings beyond a certain threshold. When compliance challenges are exhausted, the resolution path shifts to commercial escalation — engaging the account team and potentially regional commercial management. This transition is not automatic; it must be deliberately engineered by separating the compliance track from the commercial relationship and introducing commercial leverage (renewal timing, competitive alternatives, EBA commitment).
The most powerful commercial leverage is renewal timing. An enterprise with a renewal approaching within 12 months has substantially more commercial leverage than one at the midpoint of a multi-year agreement. Autodesk's account team is measured on renewal revenue, not compliance revenue — the incentive alignment favors settlement when renewal is at stake. For the complete escalation framework, see our audit settlement negotiation guide.
Stage 7: Settlement Negotiation (Days 120–270)
What Happens: Settlement Structure and Contractual Protections
Settlement negotiation focuses on two elements: the financial amount and the contractual terms. Four financial structures are available: lump sum payment, subscription reconciliation (convert finding to subscription commitment), purchase credit (apply finding value as future purchase credit), and combined structures. The financial amount should be negotiated against benchmark data from comparable engagements — Autodesk's initial settlement demand is typically 40–60% above market-rate settlement outcomes for the same finding category.
The contractual protections negotiated in settlement are often more valuable than the financial reduction. A 12-month audit moratorium, count adjustment rights in the settlement agreement, and a post-audit governance cooperation commitment all reduce future exposure beyond the immediate settlement amount. Organizations that negotiate only on the financial number without addressing contractual protections leave significant value unrealized.
Stage 8: Post-Settlement Governance (Days 240+)
What Happens: Converting Audit Data Into Governance Foundation
The post-settlement window — typically 90 days — is when the data generated by the audit process is most valuable for building sustainable compliance infrastructure. The finding categories identified by Autodesk's team, even if successfully challenged, reveal where the compliance gaps actually exist. The ITAM foundation, Named User governance protocols, and quarterly review cycle should be implemented using this data as the starting point.
Organizations that invest in ITAM governance within 90 days of settlement achieve 78% reduction in repeat audit findings at the next audit cycle. Those that do not — that treat the audit as a closed chapter — face the same vulnerabilities at the next notification, with less negotiating credibility and potentially a shorter challenge window. For the governance framework, see our post-audit governance guide and the 90-Day Post-Audit Plan white paper.
Active Audit? Know What Stage You Are In
AutodeskAudits provides independent advisory at any stage of an active Autodesk audit — from initial notification response through settlement negotiation. Our advisors have no commercial relationship with Autodesk and no incentive other than protecting your position.
Schedule a Consultation