Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
We Have Workday but Still Use Spreadsheets: What HRTech Are We Missing?
- Workday is an HR system of record, not a planning or analytics platform. Spreadsheets fill the gap between what Workday stores and what your business actually needs to decide.
- The spreadsheet habit usually signals one of six specific problems: reporting gaps, missing workforce planning tools, weak integrations, data quality issues, adoption failures, or the absence of specialist HR tech layers.
- Workday’s built-in reporting, Prism Analytics, and People Analytics modules are real products with real capability limits. Knowing what they cover determines what you need to add.
- Most teams do not need to replace Workday. They need to diagnose which layer is broken and add the right specialist tool on top.
- The fix is rarely more training. It is usually a missing integration, a missing planning tool, or a decision about whether your Workday configuration was ever set up to do the job you are now asking it to do.
If your HR team uses Workday as the system of record and spreadsheets as the system of truth, you are not alone , and this pattern is common enough that it has a name. Organizations that run Workday but still use spreadsheets for planning, reporting, and talent tracking have identified a real architectural gap in their HR tech stack. Workday is designed to store and transact on workforce data. It was not designed to replace a dedicated workforce planning tool, a real-time analytics layer, or a talent intelligence platform. Spreadsheets fill whatever gap exists between those categories.
Why Do HR Teams Still Use Spreadsheets When They Have Workday?
The assumption that Workday should eliminate spreadsheets is the wrong starting point. Workday replaced paper forms, email approvals, and disconnected HR databases. It did not promise to replace every downstream analytical or planning workflow that HR teams run. The persistence of spreadsheets is not a sign of user error. It is a symptom that points to something specific.
Research consistently shows that FP&A and HR teams at enterprise companies lean on spreadsheets for daily and weekly planning and reporting work , even when enterprise software is in place. According to a Workday blog post citing AFP research, the majority of FP&A professionals continue to use spreadsheets for both planning and financial reporting on a regular basis. That is not a Workday-specific problem. It reflects a broader reality: enterprise software handles transactions and records, and people reach for spreadsheets when they need to model, compare, or narrate data for a decision.
The question worth asking is not “why are we using spreadsheets?” It is “what specific thing are the spreadsheets doing that our stack cannot?” The answer usually falls into one of six categories. Each one points to a different fix.
Is This a Reporting Problem or a Planning Problem? The Distinction Matters
Most HR teams conflate reporting and planning, then buy the wrong tool for both. Reporting means describing what happened: headcount by department, turnover rate, time-to-fill. Planning means modeling what should happen: headcount targets for next quarter, scenario analysis on a proposed reorg, skills gap projections for a new business unit.
Workday handles reporting reasonably well through its native report writer and Workday Prism Analytics. Where it falls short is forward-looking planning. Workday Adaptive Planning exists as a separate product and covers FP&A and workforce planning, but it is not automatically included with an HCM license and requires its own implementation. Many teams that have Workday HCM have never purchased Adaptive Planning and do not realize the gap exists until they are building next year’s headcount plan in a shared Google Sheet.
If your spreadsheets are mostly backward-looking reports that someone has to pull and reformat manually, that is a reporting configuration or integration problem. If your spreadsheets are forward-looking models with scenario tabs and assumptions cells, that is a planning tool gap. The fixes are different.
What Are the Six Most Common Stack Gaps Behind the Spreadsheet Habit?
Gap 1: Workforce Planning Has No Dedicated Tool
Workday stores headcount data. It does not natively support headcount scenario modeling, skills-based capacity planning, or organizational design simulation without Adaptive Planning, which requires a separate license and implementation. Teams without it default to spreadsheets because there is literally no other place in the stack to do this work.
Dedicated workforce planning software from vendors like Anaplan, Planful, Pigment, or Workday Adaptive Planning itself fills this gap. These tools connect to Workday as the data source, run modeling on top of that data, and push approved headcount plans back into Workday. The spreadsheet becomes unnecessary because the planning environment has scenario controls, approval workflows, and version history built in.
Gap 2: People Analytics Is Not Configured or Is Underpowered
Workday People Analytics exists as an AI-powered product that surfaces workforce insights. It is not turned on by default for all HCM customers and requires its own enablement work. Many organizations that have Workday also have People Analytics sitting unused or partially configured, while their HR analytics team runs reports in Excel because that is faster than learning the report writer.
The bigger issue is that Workday People Analytics is strong on Workday data but has limited ability to blend external data sources, compensation benchmarks, or engagement survey results from third-party tools. If your analysis requires connecting Workday data to Glint, Culture Amp, LinkedIn Salary Insights, or your ATS pipeline data, you need a layer that Workday does not natively provide. The best AI people analytics platforms like Visier, One Model, or Orgnostic are built specifically to aggregate, blend, and visualize workforce data from multiple source systems. They sit on top of Workday rather than replacing it.
Gap 3: Integrations Are Missing or Broken
Workday connects to most major HR systems through its Workday Marketplace and API layer. In practice, many implementations go live with only partial integrations built, because building every integration at launch delays go-live. Teams then compensate by manually exporting data from Workday, transforming it in Excel, and uploading it to another system. This is one of the most common sources of permanent spreadsheet dependency.
Broken or missing integrations between Workday and your ATS, your payroll processor, your benefits administration platform, or your LMS are fixable. The fix requires either a Workday integration consultant, a middleware tool like Boomi, MuleSoft, or Workato, or a reimplementation of the integration with proper error handling and field mapping. If your spreadsheets are primarily about moving data between systems, the problem is integration architecture, not HR strategy.
Gap 4: Data Quality Inside Workday Is Unreliable
If your HR team does not trust Workday’s data, they will not use Workday’s reports. They will pull raw data into Excel, clean it, and build their own version of the truth. This happens when job profiles are inconsistently applied, manager hierarchies are out of date, cost center assignments are wrong, or employee records have missing fields.
Poor data quality is often a configuration and governance problem from the original implementation. Fields that were optional during go-live accumulate missing values over years. Job architecture that was never completed creates reporting anomalies. The fix is a data governance project, not a new tool purchase. An audit of your Workday configuration, combined with clear data stewardship ownership, is the prerequisite to any analytics or reporting investment. If the data going into Workday is dirty, every tool you put on top of it will produce dirty output.
Gap 5: Specialist Talent Processes Have No Dedicated Tool
Workday’s ATS, known as Workday Recruiting, is a competent enterprise recruiting system for structured hiring processes. It is not a strong AI sourcing tool, is not a talent intelligence platform, and does not natively support internal talent marketplace functionality in the way that purpose-built vendors do.
Teams running complex talent acquisition programs often build sourcing trackers in Airtable or Excel because Workday Recruiting’s pipeline visibility is not granular enough for their needs. Teams trying to map skills across the organization build their own skills databases in spreadsheets because Workday Skills Cloud requires significant configuration and governance to be useful. These are gaps where specialist tools outperform Workday significantly. If you are evaluating options here, the comparison of Eightfold, Gloat, Beamery, and Findem is a useful starting point for understanding what talent intelligence platforms actually do versus what Workday provides out of the box.
Gap 6: HR Service Delivery Has No Workflow Layer
Workday handles transactional workflows: a leave request, a job change, a termination. It does not handle complex multi-step HR service cases, employee inquiries, or knowledge management well. Teams without a dedicated HR service delivery tool often manage employee questions, policy requests, and escalation tracking in email threads and shared spreadsheets because Workday has no native ticketing or case management system designed for HR helpdesk work.
Tools like ServiceNow HRSD, Zendesk, or dedicated HR case management platforms fill this gap. They sit on top of Workday, pull employee data for context, and provide a structured way to track, resolve, and report on HR service volume. Without this layer, spreadsheets become the informal case tracker for every HR team that handles significant employee query volume.
How Do You Know Which Gap You Actually Have?
Run this diagnostic before spending anything. For each spreadsheet your team maintains, ask three questions: What data goes into it? Where does that data come from? What decision does it inform? The answers will cluster into patterns.
| Spreadsheet Type | What It Usually Signals | Likely Fix |
|---|---|---|
| Headcount tracker by department / role | No workforce planning tool or Adaptive Planning not licensed | Evaluate dedicated workforce planning platforms |
| Monthly HR dashboard sent to CHRO | Reporting configuration gap or data trust issue | Workday report configuration or people analytics platform |
| Employee data export cleaned and reformatted | Data quality problem or missing integration | Data governance audit + integration rebuild |
| Recruiting pipeline tracker | ATS reporting gap or missing talent acquisition analytics | ATS analytics upgrade or AI sourcing / talent intelligence tool |
| Skills inventory or internal talent map | No talent intelligence or internal mobility platform | Evaluate Eightfold, Beamery, or Gloat |
| HR inquiry log or case tracker | No HR service delivery or case management tool | ServiceNow HRSD, HR ticketing tool, or AI HR chatbot |
| Compensation benchmarking model | No comp intelligence integration | Radford, Mercer, or comp analytics platform integration |
| Org chart or span of control analysis | No organizational design tool | OrgVue, Workday Org Management, or planning layer |
One spreadsheet rarely means one problem. Most HR teams have three to five persistent spreadsheets, each pointing to a different gap. Treat the list as a diagnostic inventory rather than a single issue to fix.
What Does Workday Actually Do Well, and Where Does It Stop?
Workday’s core strength is being the authoritative system of record for workforce data. Employee records, organizational hierarchy, compensation history, time and absence, benefits enrollment, and core compliance documentation are areas where Workday performs at enterprise scale. Its audit trail, role-based security, and SOC 2 compliance make it the right place to store that data.
Where Workday trails specialist tools: real-time labor market intelligence, AI-driven talent matching, deep engagement survey analytics, team-level manager insights, and complex financial scenario modeling. Workday has added AI capability through Workday AI features including Workday Assist and embedded AI in recruiting and skills, but these are early-stage compared to purpose-built platforms that have spent years building in these categories. Knowing where Workday’s AI genuinely competes versus where it is catching up is useful when you are deciding whether to extend your Workday investment or add a point solution.
The practical implication is that expecting Workday to eliminate every spreadsheet is like expecting your ERP to replace your BI platform. They serve different functions. The better question is which spreadsheets represent genuine product gaps and which represent configuration work you have not done yet.
Is the Spreadsheet Problem Actually a Workday Adoption Problem?
Sometimes, yes. If your HR business partners were not adequately trained on report building, if your managers do not know how to access their team dashboards in Workday, or if your implementation partner cut corners on custom report development during go-live, the spreadsheet habit may have formed because Workday was never properly handed over to the users who need it.
Signs that adoption is the primary issue: Workday data is accurate and complete, the reports exist in the system but nobody uses them, and spreadsheets replicate information that is already in Workday. In this case, buying more tools makes the problem worse, not better. The investment is in Workday optimization through a specialist partner, not in additional software. If you are in this situation, a Workday consulting firm focused on optimization and support is the right starting point. They can audit your report library, improve your dashboard configuration, and train the teams who never got proper enablement.
Adoption problems and gap problems look similar from the outside. The way to tell them apart is to check whether the data and reports your team needs actually exist in Workday, even if unused. If they do, it is an adoption problem. If they do not, it is a gap problem.
What HRTech Categories Are Worth Evaluating Alongside Workday?
People Analytics and Workforce Reporting
Visier, One Model, Orgnostic, and ChartHop sit on top of Workday and provide blended analytics that Workday cannot produce natively. These platforms pull data from Workday, your ATS, your engagement survey tool, and other sources, then provide a unified analytics layer. If your monthly HR reporting involves pulling three exports and combining them in Excel, this is the category to evaluate. Our guide on choosing a people analytics platform without buying another dashboard nobody uses covers how to evaluate these tools against your actual use cases.
Workforce Planning and Headcount Modeling
Workday Adaptive Planning is the natural extension if you are already in the Workday environment. Anaplan, Planful, and Pigment are credible alternatives with stronger financial modeling roots. The choice depends on whether you need tight integration with your FP&A process and whether your finance team is already on a planning platform. HR and finance often end up on different planning tools and then reconcile in spreadsheets, which creates a secondary problem. Aligning on a shared planning platform with HR and finance access eliminates an entire category of manual reconciliation work.
Talent Intelligence and Internal Mobility
Workday Skills Cloud is the right place to manage skills data if you have invested in configuring it properly. For talent intelligence, market intelligence, and internal mobility at scale, Eightfold AI, Gloat, and Beamery offer capabilities that Workday does not match: AI-driven skills inference, labor market benchmarking, and proactive internal opportunity matching. If your talent team is building skills matrices in spreadsheets because Workday Skills Cloud was never fully implemented, evaluate whether the investment in configuring Skills Cloud or purchasing a specialist platform makes more sense for your scale. The decision framework for AI internal mobility platforms can help you structure that comparison.
HR Service Delivery
If your team tracks employee inquiries in a shared inbox or a spreadsheet, a proper HR case management tool or AI-powered HR chatbot will eliminate that immediately. ServiceNow HRSD is the enterprise standard. Leapsome, Moveworks, and Espressive are worth evaluating for teams that want an AI layer in front of their HR service desk. These tools connect to Workday for employee context and reduce the volume of manual case handling significantly.
Compensation Analytics
Workday compensation handles the transaction: recording pay changes, running compensation review cycles. It does not provide real-time benchmarking against external salary data. Tools like Radford (now Aon), Mercer, Payscale, or Compa provide compensation intelligence that connects to Workday, surfaces where you are out of market, and supports real-time offer decisions. Compensation spreadsheets are almost always a signal that this layer is missing.
How Should You Prioritize Which Gap to Fix First?
Start with the spreadsheet that is costing the most time per week and creating the most decision risk. A headcount planning spreadsheet that three people maintain across weekly versions and that informs board-level decisions is a higher-priority fix than a recruiting tracker that one person updates for their own visibility.
Second, distinguish between fixes that require buying a new product and fixes that require investment in your existing Workday configuration. Before adding any new tool, validate that the capability does not already exist in your Workday license. Many teams discover they have licensed modules that were never turned on. The cost of activating an existing module is almost always lower than a new vendor contract.
Third, consider integration complexity. Every new tool you add creates an integration to Workday. The more tools you add without a clear integration strategy, the more data reconciliation work you create. If your HRIS implementation was already challenging, adding five point solutions without a middleware strategy will recreate the problem at a higher cost. Our HR software implementation checklist covers the integration planning questions worth working through before signing any new contract.
For teams evaluating a broader stack overhaul rather than point solutions, a structured vendor evaluation process matters more at that level. The HR software buying checklist provides a framework for that conversation across HRIS, payroll, ATS, and HCM categories.
Frequently Asked Questions
Is it normal for companies with Workday to still use spreadsheets?
Yes, and it is widespread. Workday is a system of record and transaction management platform, not a comprehensive planning or analytics environment. Teams regularly supplement it with spreadsheets for workforce planning, headcount modeling, compensation benchmarking, and analytics workflows that require blending data from multiple sources. The spreadsheet habit reflects real gaps in the platform’s native scope, not misuse.
Does Workday replace the need for a people analytics platform?
Partially. Workday People Analytics provides AI-powered insights on Workday data, but it does not natively blend data from your ATS, engagement survey tools, or external labor market sources. Organizations with complex analytics needs or data from multiple HR systems generally need a dedicated people analytics platform like Visier or One Model that aggregates across sources and provides a unified reporting layer.
What is the difference between Workday HCM and Workday Adaptive Planning?
Workday HCM is the core HR platform covering employee records, payroll, recruiting, benefits, and workforce management. Workday Adaptive Planning is a separate product focused on financial and workforce planning, headcount scenario modeling, and budgeting. The two integrate but are licensed and implemented separately. Many organizations have HCM without Adaptive Planning and consequently have no structured environment for headcount forecasting outside of spreadsheets.
Why does Workday data end up in spreadsheets instead of dashboards?
Usually for one of three reasons: the reports and dashboards were never properly configured during implementation, the data inside Workday is not trusted because of quality issues, or the required analysis blends Workday data with external sources that Workday cannot natively combine. Each cause requires a different fix: configuration work, a data governance project, or an analytics platform investment respectively.
Can Workday connect directly to Excel?
Yes. Workday supports data export to Excel and XML. Third-party connector tools like CData Connect Spreadsheets are marketed as providing live Workday data access within Excel , worth evaluating if manual export steps are creating bottlenecks, though you should verify the specific connection method against your Workday version and IT security requirements. Either way, connecting Workday to Excel addresses the data transfer problem, not the underlying gap in planning, analytics, or workflow capabilities that drives spreadsheet dependency in the first place.
When should an HR team consider replacing Workday rather than adding tools on top of it?
Replacing Workday is rarely the right answer for the spreadsheet problem specifically. The cases where replacement makes sense are: total cost of ownership has grown unsustainable relative to the features actually being used, a significant portion of the workforce is now international and Workday’s global payroll coverage is insufficient, or the organization has moved downmarket and a mid-market platform like a Workday alternative covers all required features at significantly lower cost. Spreadsheet dependency alone does not justify a platform change.
What HR tech tools complement Workday most commonly in enterprise stacks?
The most common Workday complement stack includes: a people analytics platform (Visier, One Model, or Orgnostic), a workforce planning tool (Adaptive Planning, Anaplan, or Pigment), a talent intelligence or skills platform (Eightfold, Beamery, or Gloat), an HR service delivery tool (ServiceNow HRSD or a dedicated HR chatbot), and a compensation intelligence tool (Radford, Payscale, or Compa). The specific combination depends on which gap categories are most acute for a given organization.
How do I know if my Workday problem is configuration or a genuine product gap?
Ask whether the capability exists in your Workday license, whether it was configured during implementation, and whether it has been activated and adopted. If the feature exists and was configured but is not used, it is an adoption problem. If the feature does not exist in your license tier or was never built out, it is a product gap. A Workday audit by a specialist partner is the fastest way to get a definitive answer, particularly for organizations more than two years post go-live whose needs have grown beyond the original implementation scope.
The Mental Model That Resolves This
Workday is infrastructure, not a complete HR operating system. Think of it the way you think of Salesforce in a sales organization: it stores the data, manages the transactions, and provides a system of record, but sales teams still need BI tools, outreach platforms, and territory planning software on top of it. No sophisticated organization expects Salesforce to eliminate all spreadsheets. The same logic applies to Workday.
The spreadsheets your team maintains are a reliable signal of where your stack has genuine gaps. Treating them as evidence of user error delays the real diagnosis. Treating them as a symptom that points to a specific missing layer lets you fix the actual problem at its source rather than paper over it with training and hope.
The practical move is to inventory your persistent spreadsheets, categorize them against the six gap types, check your existing Workday license for unused modules, and then prioritize the one or two gaps that create the most decision risk or operational drag. Most HR teams need fewer new tools than they expect, but they need the right ones configured properly and integrated cleanly. That is a more tractable problem than it looks.
