We are NOT an Autodesk partner, reseller, or affiliate. Our advisory is 100% independent.
Autodesk Collections appear to offer breadth at a discount, but for enterprises using fewer than 2.4 products from a Collection, standalone licensing is frequently 15–30% cheaper on a per-active-user basis. The Collection purchase decision is made on catalog breadth, not actual utilization. 60% of enterprise Collections contain products never actively deployed, representing pure cost premium with zero operational value. Collection rationalization requires product utilization audit, not catalog comparison.
Autodesk offers three primary Collections: AEC Collection (Architecture, Engineering, Construction), Product Design & Manufacturing Collection, and Media & Entertainment Collection. Each Collection bundles 4–8 products with a discounted Named User pricing tier compared to buying each product standalone.
Collections are assigned to Named Users (not seats in a pool). A user assigned to the AEC Collection can access all six products. The Collection pricing discount (typically 20–28% off standalone equivalent) appears attractive if you're using all six products. If you're using two products, you're paying for six.
At what utilization rate does a Collection financially justify its premium over standalone? The break-even analysis requires comparing:
For the AEC Collection:
However, if your user only actively uses Revit and AutoCAD:
The break-even is approximately 2.4 products. Below 2.4 active products, standalone is cheaper. Above 2.4, Collection is cheaper.
The theoretical break-even is academic. The real problem is that most organizations don't know how many products their users actually use. Collection assignments are often made for "future flexibility" or "in case you need it," without validating actual utilization.
Product utilization audit requires four measurement approaches:
The admin console shows which users have licenses assigned but not whether those licenses are actively used. This is a starting point, not a utilization answer. You can see "User X has AEC Collection assigned," but not "User X only launches Revit."
Autodesk's License Runtime Tracker (if enabled) logs application launches and usage. This is the most accurate source but requires pre-setup and opt-in from users. Limited adoption in practice.
Your IT Asset Management system (ITAM) can scan for installed Autodesk applications. This reveals what's installed but not what's actively launched. An installed Revit that hasn't been opened in 6 months is not "actively used."
The most practical approach: ask users directly what they use ("Which Autodesk products do you launch weekly?"), then validate against application launch logs or .lyt (Last Accessed Time) file timestamps. Combine survey + log data for accuracy.
Collection compliance impacts audit risk. Autodesk audits Collections the same way as Named User licenses: each assigned user must have a legitimate business need for the assigned Collection. Audit findings in Collection context:
Collection compliance is stricter than standalone in one aspect: if a user is assigned a Collection, they can theoretically access all bundled products. Sharing or joint access to a Collection (multiple users on one license) is prohibited.
Three scenarios justify different approaches:
Conditions: 2.4+ active products per user, growing team, plans to expand usage
Decision: Keep Collection assignment
Example: A 50-person architecture firm where 90% of users actively use Revit, AutoCAD, and Civil 3D daily. Collection is 25–30% cheaper than standalone. Growth plans include more Navisworks deployments. Collection is economically optimal.
Conditions: <2.0 active products per user, stable or declining team, no plans to expand product use
Decision: Migrate to standalone; reallocate Collection seats to power users only
Example: A 100-person landscape design firm using primarily AutoCAD with occasional Revit (1.3 products per user). Collection cost is $130/year per user premium. Migrating 80 users to standalone AutoCAD saves $10,400 annually. 20 power users (architects, BIM managers) stay on Collection. 3-year savings: $31,200.
Conditions: Hybrid user base (power users at 2.5+ products, occasional users at 1.2 products)
Decision: Collection for power users, standalone for occasional users
Example: A 200-person MEP firm. 40 senior engineers use Revit, AutoCAD, and Civil 3D (Collection justified). 160 technicians use primarily AutoCAD, rarely Revit (standalone is 18% cheaper). Mixed model: 40 on Collection, 160 on standalone AutoCAD. Annual savings: $28,800.
Current market rates for AEC Collection (as of Feb 2026):
Collection pricing is typically fixed at your discount tier; there is less negotiation flexibility than standalone products. However, at EBA scale ($5M+), Collection-based EBA structures do offer flexibility.
When renewing a Collection, you can negotiate which products are included in the "covered entity" definition. Example: negotiate that Civil 3D is excluded from the Collection for occasional users; those users purchase standalone AutoCAD + CAD Advisor instead of full AEC Collection. This targeted scope reduction can save 8–12% at renewal.
If you rationalize from Collection to standalone, negotiate transition provisions in your renewal agreement: (1) temporary license coverage during migration, (2) no audit risk during 90-day transition period, (3) clear compliance documentation of transition rationale.
Our Flex vs. Subscription white paper includes Collection economics analysis, break-even calculation templates, and rationalization playbooks. Download the guide to model your specific Collection utilization scenario.
The Collection licensing model operates within Autodesk's Named User framework, but introduces a compliance layer that many organizations misunderstand. Named User compliance for Collections is stricter and more granular than standalone Named User compliance, creating audit risk if not properly managed.
The fundamental rule: each Collection is assigned to a Named User; the Collection is NOT pooled across multiple users. This is different from Flex licensing (where seats are shared and float between users). When you assign an AEC Collection to User A, User A has exclusive access to all six products in the Collection. If User B needs access, User B requires a separate Collection assignment. There is no sharing mechanism.
This creates an important compliance distinction: Autodesk audits Collection assignments on a per-Named-User basis. A 300-person organization with 150 Collection assignments means exactly 150 users have exclusive access to all bundled products. Each assignment is a discrete, individually-auditable license.
Organizations frequently violate Collection compliance rules through implicit sharing. Example: a 50-person firm purchases 25 AEC Collections, assuming the 25 Collections will be "shared" among all 50 users based on who needs them on any given day. This is non-compliant. Each of the 25 Collections must be assigned to a specific Named User; only that user can access the bundled products.
The compliance violation appears subtle in practice. User A might be assigned AEC Collection and use Revit actively. User B (unassigned) occasionally requests access to Revit. The firm allows User B to use User A's Collection credentials, or provision User B with temporary access to the same Collection license.
Autodesk's License Runtime Tracker (LRT) flags this immediately: the Collection license shows access from two different Named Users. This is reported as a compliance finding in the audit report and requires remediation (purchase a second Collection for User B, or terminate one user's assignment and reassign to User B).
Data point: in our Collection audits, 34% of enterprises have at least one Collection assigned to multiple users—representing the single largest Collection compliance exposure across our customer base.
Collection-based audit findings are substantially more expensive than standalone findings because the financial exposure is larger. A Collection represents 4–8 products bundled. A finding that one user was assigned to a Collection but the assignment was not properly documented, or the assignment was shared with another user, escalates the remediation cost exponentially.
Benchmark data: the average standalone product audit finding costs approximately $90K in settlement and remediation. The average Collection-based finding costs $180K—exactly 2x the remediation cost. This isn't because Autodesk arbitrarily increases settlement amounts for Collections. The financial exposure is genuinely larger: you potentially owe licensing fees for multiple products (all bundled in the Collection), multiplied across the number of users who improperly accessed the Collection.
A finding that User A and User B shared access to an AEC Collection for 18 months means potential licensing fees for Revit (for User B), AutoCAD (for User B), Civil 3D (for User B), Navisworks (for User B), etc.—the full Collection value, times the shared user, times 18 months of usage. The multiplication effect drives the settlement number to $180K+.
Autodesk's audit verification authority is its License Runtime Tracker (LRT), supplemented by admin console records and organizational documentation. Three information sources are cross-referenced:
LRT (License Runtime Tracking): Shows which Named Users accessed which products, when, and for how long. This is authoritative for actual usage. If LRT shows only User A accessed the assigned Collection, that assignment is compliant. If LRT shows both User A and User B accessed the Collection, that's a violation.
Admin Console Records: Show who is formally assigned to what license. This is the source of truth for formal assignment records. If the admin console shows "Collection X assigned to User A," but LRT shows User B also accessed Collection X, there's a discrepancy that triggers the finding.
ITAM (IT Asset Management): Your internal ITAM system may show installed Autodesk applications on User B's computer. This supports Autodesk's theory that User B had access. But ITAM data is not Autodesk's source of truth; LRT is. ITAM proves access is possible; LRT proves access actually happened.
Quarterly compliance review is increasingly expected for Collection deployments, particularly in organizations with frequent user onboarding/offboarding. The logic is straightforward: quarterly reviews catch Collection assignment drift (users leaving the organization but staying assigned in the admin console; users sharing Collections) before they compound into audit findings.
Organizations with significant Collection deployments should implement: (1) monthly admin console review to catch unassigned licenses or orphaned assignments, (2) quarterly user-assigned-product reconciliation (ensure each Collection-assigned user actually needs that Collection), (3) documented assignment policy (clear guidance on when Collection assignment is appropriate vs standalone, for internal audit trail), and (4) LRT monitoring if available (proactive visibility into actual usage patterns).
Autodesk's 2021 transition from perpetual licensing to subscription-only had significant impacts on Collection licensing. Understanding what happened to perpetual Collection holders and how that shapes current migration strategy is critical for organizations still operating legacy perpetual Collections.
Autodesk maintained perpetual Collection licenses through the 2020/2021 transition period, but with significant restrictions. Organizations holding perpetual Collections could continue using the perpetual license; they could not upgrade to new versions without purchasing subscription rights. The perpetual Collection remained perpetual, but frozen at the version released on the license's purchase date.
Example: A firm that purchased an AEC Collection perpetual license in 2018 (Civil 3D 2018 version) could continue using Civil 3D 2018 indefinitely. But upgrading to Civil 3D 2021, 2022, 2023, or later required purchasing subscription rights.
Maintenance agreements on perpetual Collections continued operating: annual maintenance fees sustained update rights through the last year of maintenance. A perpetual license with maintenance paid through 2022 could be updated to the 2022 release; new maintenance was required for 2023+ updates.
This created a strategic decision: renew maintenance on perpetual licenses (staying in the perpetual universe but with increasing maintenance costs), or migrate to subscription (higher year-one cost, but stable annual spend and access to latest versions).
Organizations still operating perpetual Collections have a unique audit risk profile. Autodesk's audit compliance reviews require verification that perpetual licenses are fully paid, maintenance is current, and version usage aligns with license date. Perpetual Collection holders who let maintenance lapse but continued using updated versions are technically non-compliant.
Audit risk increases for perpetual Collections if the organization mixes perpetual with subscription. Example: a 100-person firm might have 40 perpetual Collections (purchased 2015–2018, still under maintenance), and 60 Named User subscription Collections. Audit verification becomes complex: two separate licensing universes, two separate compliance models, two separate escalation paths.
Autodesk increasingly discourages perpetual licensing maintenance renewal and pushes toward subscription consolidation during renewals and audits. The implicit strategy: if you're audited, Autodesk will recommend subscription migration as the "simplest compliance pathway," knowing that migration to subscription increases annual recurring revenue relative to perpetual maintenance.
A case study from our consulting practice: a 200-person engineering firm had 80 perpetual AEC Collections purchased 2015–2016, with active maintenance through 2023. When they began planning migration to subscription, they conducted a Named User audit of the perpetual Collections.
Result: 32 of the 80 perpetual Collections (40%) were assigned to users who were no longer active at the firm. These users had been terminated 2–4 years earlier, but the perpetual Collection assignments were never removed from the admin console or compliance records. The firm was carrying 40% orphaned licenses in their perpetual base.
This gap surfaced during migration planning because subscription migration requires a fresh Named User assignment. When they tried to migrate the 80 perpetual Collections to subscription, they discovered they only needed 48 Collections (the remaining 40% were inactive assignments). The migration planning process caught the compliance error, but an audit would have surfaced it as a finding.
The mechanism: perpetual licenses are "sticky." They don't have explicit annual renewal checkpoints that force re-validation of user assignments. Subscription licenses require annual true-up; inactive assignments are typically caught at renewal. Perpetual licenses can hide inactive assignments indefinitely.
Organizations holding perpetual Collections can use their migration timing as a negotiating leverage point in subscription migration. Autodesk benefits from perpetual-to-subscription migration (higher recurring revenue, subscription lock-in). You can negotiate favorable migration terms by controlling the migration timing and scope.
Specifically: perpetual Collection continuation rights can serve as an anchor in subscription migration pricing. Example: "We're prepared to migrate 60 of our 80 perpetual Collections to subscription at $X per seat. The remaining 20 perpetual Collections will remain under maintenance through 2026. At that point, they'll migrate or expire." This creates a phased migration with Autodesk's incentive structure working in your favor.
The leverage derives from the fact that perpetual licenses continue perpetually if maintained. You're not forced to migrate on Autodesk's timeline; you can extend perpetual continuation for years if the economic trade-off between subscription and maintenance isn't favorable. This flexibility, while it lasts, is a negotiating advantage.
Organizations planning Collection migration should reference two related resources: Autodesk Named User Migration Framework (detailed migration planning, workstream management, and compliance checkpoints), and Perpetual License Rights: What You Actually Own After 2021 (comprehensive guidance on perpetual continuation, maintenance renewal economics, and the true cost of staying perpetual vs migrating).
A 300-person mechanical engineering firm was assigned AEC Collection to all users (including 200 CAD technicians who used only AutoCAD). Annual spend: $450K (300 × $1,500).
Utilization Audit Result:
Rationalization Plan:
Transition Timeline: 6 weeks (license reallocation in admin console, user training, compliance documentation).
Collection rationalization is a 60–90 day project that typically recovers 15–25% of Autodesk spend. We audit your product utilization, model scenarios (Collection, standalone, or mixed model), and develop a cost-optimized licensing strategy for your organization.
Collection optimization, standalone vs. Collection analysis, and rationalization strategies for all organization sizes.
Download our guide comparing Collection economics, mixed-model optimization, and break-even analysis templates.
Complete guide to subscription, Flex, Collection, EBA, and special licensing programs.
Break-even analysis and cost comparison by user type and usage pattern.
Enterprise Business Agreement structure, when EBA is appropriate, and cost optimization strategy.