A Workday license audit is the prerequisite to any meaningful renewal negotiation, optimization initiative, or cost-reduction project. Without an honest audit, the buyer enters the renewal cycle blind to shelfware, unaware of right-sizing opportunities, and unable to challenge the account team's representation of usage. The audit is not complex but it is structured. This checklist walks through 18 questions across six categories that every Workday license audit should answer before the renewal cycle begins.
License audits are conducted by buyers for buyers. They are not Workday-conducted true-up audits. The internal audit produces the data foundation for renewal negotiation, module rationalization, environment consolidation, and shelfware recovery. Done well, the audit takes 4-8 weeks for a midsize Workday footprint and produces a documented baseline that anchors the next 12-18 months of optimization work.
The checklist below organizes the audit into six categories: licensed quantity reconciliation, module utilization, environment configuration, integration usage, security profile rationalization, and historical change tracking. Each category produces specific findings that translate to specific negotiation levers.
The first category establishes the contractual baseline.
Pull the current contract and every amendment. Document licensed quantities by module, tier, geography, and any other contractual qualifier. The contractual quantity is the baseline against which actual usage is measured.
Request Workday's internal record of licensed quantity. Discrepancies between the buyer's contract reading and Workday's internal record are surprisingly common — especially after multiple amendments, mergers, or account team transitions.
Document the precise definition of countable quantity for each module. Worker records, active employees, contingent workers, retirees, named users, and concurrent users all carry different counting rules. The definition determines the true-up mechanic.
The second category measures actual usage against licensed entitlements.
For each licensed module, document whether the module is configured, deployed to users, and actively used. Modules that are licensed but not deployed are shelfware candidates.
Pull active-user counts for each module over the trailing 90 days. Compare active users to licensed users. Modules with substantially fewer active users than licensed users are right-sizing candidates.
For deployed modules, document feature utilization. Premium tiers that are licensed but not utilizing premium features can often be downgraded.
Many right-sizing opportunities live at the feature level rather than the module level. A licensed Premium Recruiting tier with no premium features in use can be downgraded to Standard. A licensed Advanced Compensation module with no advanced configurations in use can be replaced with the standard Compensation module. Feature-level analysis often surfaces 15-30% of license cost.
The third category audits non-production environments.
Document every licensed environment — Production, Implementation, Sandbox, Sandbox Preview, Gold, Training, and any custom-named tenants. Each environment carries license cost.
Document the active use of each environment. Environments that are no longer used for testing, training, or development are consolidation candidates.
Environments with stale refresh dates (more than 6-9 months old) often indicate environments that have fallen out of active use.
Document environment-merge opportunities — combining Training and Sandbox, decommissioning Gold, consolidating multi-region tenants.
The fourth category audits the integration footprint.
Document every active integration — PECI, Core Connect, EIB, Studio, Cloud Connect, and partner integrations. Document inbound and outbound separately.
Audit integration runtime — integrations that have not run in 60+ days are deactivation candidates. Document integrations with high error rates — integrations that fail silently may be operating below business expectations.
Workday integration licensing varies by integration type and volume. Document which integrations are licensed under which contract terms and identify integrations approaching license caps.
The fifth category audits security profile and named-user counts.
Document the security group count. Bloated security group counts (>200 for a midsize organization) typically indicate accumulated configuration debt and license inefficiency.
Workday tiers and meters several admin license types. Document admin license counts against actual administrator usage. Inactive admin accounts contribute to license cost without business value.
Users with redundant security group assignments often indicate access creep that should be cleaned up. The cleanup typically reduces administrative burden but rarely affects core license cost.
The sixth category documents how the license footprint has changed over time.
Document the licensed-quantity history across the past 3 renewal cycles. The trajectory informs the renewal forecast and surfaces growth patterns that affect the next renewal.
Document module additions and any deactivations across the past 3 renewal cycles. Module add/drop history informs the rationalization conversation at the next renewal.
Audit findings translate to specific negotiation levers. Five translation patterns recur.
Shelfware identification translates to module-drop or right-size asks. Modules with low utilization become candidates for deactivation or tier downgrade at renewal.
Environment consolidation translates to tenant-count reduction. Environments no longer in active use can be deactivated at renewal.
Feature-level downgrade translates to tier reduction. Premium tiers without premium feature use can be downgraded to standard.
Integration cleanup translates to integration license reduction. Inactive integrations can be deactivated without business impact.
Forecast accuracy translates to better renewal sizing. Accurate forecasts limit true-up exposure and enable confident renewal commitments.
The audit timing affects its leverage. Three timing principles produce better outcomes.
First, complete the initial audit 9-12 months before renewal. The audit must precede the renewal preparation phase to be useful.
Second, refresh utilization data 60 days before renewal. Utilization patterns shift — the audit baseline should be current at the negotiation.
Third, conduct annual mini-audits even outside the renewal cycle. Annual mini-audits surface drift before it becomes shelfware.
Should we engage Workday in the audit? Workday's account team can provide data but typically presents it through the lens of expansion opportunity. Buyer-conducted audits surface optimization opportunities that account-team-led audits typically do not surface.
Can we audit usage without admin access? Limited. Workday's reporting infrastructure is necessary for the audit. The audit team needs at least one administrator and access to standard reports.
How long does a midsize audit take? 4-8 weeks for a midsize Workday footprint with reasonable record-keeping. Larger footprints with multiple acquisitions or sparse documentation can take 10-14 weeks.
What is the typical optimization yield? Initial audits typically surface 12-28% optimization potential in licensed cost. Subsequent annual audits typically surface 4-10% incremental opportunity.
Should we use an external auditor? External auditors specialized in Workday licensing typically surface 30-60% more opportunity than internal-only audits, primarily because they bring benchmarks, pattern recognition from comparable deployments, and structured questioning that internal teams often lack.
Independent Workday-only advisory. 500+ engagements, $28M+ saved, 34% average reduction across 14 modules. Two engagement models — choose whichever fits your risk posture.
Scoped advisory with a known price. Benchmarks, contract redlines, and on-call negotiation support through signature.
Zero upfront cost. Our fee is a percentage of verified savings against your baseline. If we don't save you money, you don't pay.
Predictable scope or pay-only-on-savings. Whichever model fits your risk posture.
Compare →Benchmarks, tactics, and contract language for Workday buyers.
Fixed fee or gain share — strategy memo within 48 hours.
Contact Us →One email per week. Benchmarks, contract language, and tactics.