“Who Changed the Offer BP?” – A Common Workday Problem
Almost every Workday team has experienced this moment: recruiting suddenly stops working as expected, offers get stuck, approvers change, and someone finally asks, “Who changed the Offer business process last week?” The room goes quiet, people check emails and messages, and no one has a clear answer.
This is not just a technical problem. It is a governance and accountability problem. When business process (BP) changes are not properly tracked, communicated, and owned, HR, Talent Acquisition, and Hiring Managers lose confidence in Workday. The system appears unpredictable and “risky,” even when the root cause is simply a missing process for change control.
Why Workday Business Process Changes Are So Sensitive
Business processes in Workday control the steps, routing, notifications, and validations that drive core workflows: hiring, offers, onboarding, job changes, promotions, terminations, and more. A small change in a condition, approver, or step can materially impact:
Who needs to approve an action.
How long a transaction takes.
Which data is required or optional.
Which stakeholders are notified—or not notified.
When these changes are made quickly, without documentation or testing, they often look harmless in the moment. But a week later, when a recruiter asks why offers are stuck or a manager wonders why a new approver is suddenly in the chain, the lack of visibility becomes a major issue.
Typical Symptoms of Poor BP Change Governance
If your Workday tenant has weak governance around business process changes, you might notice some of these symptoms:
Recruiting or HR users report “something changed” in approval flow, but no one knows exactly what.
Approvers change without clear business agreement, creating political or compliance issues.
Testing happens directly in production because “it’s just a small tweak.”
Documentation about the current BP design is outdated, or doesn’t exist at all.
The same issues reappear across releases because no one tracks previous decisions.
Over time, this erodes trust. Business users start to see Workday as a black box that “randomly changes,” even if those changes were made with good intentions.
The Foundation: Clear Ownership and Roles
Before getting into tools and reports, it is crucial to define who actually owns each key business process. For example:
HR Operations might own the Hire and Termination processes.
Talent Acquisition might own the Offer and Recruiting processes.
HR and Finance together might own Job Change and Compensation changes.
Clear ownership means:
No changes to a process are made without the knowledge and approval of its owner.
Owners participate in design, testing, and sign-off for any configuration updates.
There is a known “RACI” (who is Responsible, Accountable, Consulted, and Informed) for each core BP.
When ownership is vague, changes happen informally, through ad-hoc requests and one-off messages. When ownership is explicit, it becomes easier to implement a simple but effective change control process.
Practical Ways to Track Who Changed What and When
Workday provides multiple tools and logs that help teams understand configuration changes, but they only work if you build them into your operating rhythm. Depending on your tenant setup and access, you may have options such as:
Configuration reports that show recent changes in business processes and related objects.
Delivered or custom audit reports that track who made specific configuration updates and when.
Change tickets or requests in your ITSM tool (e.g., Jira, ServiceNow) that record the “why” behind changes.
The key is to combine system-level visibility (who changed what, technically) with process-level governance (who approved the change, and what problem it solved). Technical logs alone are not enough; they need to be tied to a clear request and approval trail.
A Simple Change Control Flow for Workday Business Processes
You do not need a huge bureaucracy to manage business process changes. A lightweight change control flow is enough to avoid most issues. For example:
Request A user identifies a problem (e.g., an approver is missing, a step is unnecessary) and submits a change request with context.
Review and Design The Workday admin and BP owner review the request, explore options, and agree on the design.
Configure in Non-Production The change is made in a test or sandbox tenant, not directly in production.
Test with Real Scenarios HR, Talent, or Finance users test the change using realistic scenarios and confirm the expected behavior.
Approve and Document The owner approves the change, and a short design note is recorded (what changed, why, and any impacts).
Move to Production and Communicate The change is migrated, and impacted users receive a short update—especially if their approvals or steps change.
With this simple pattern, the question “Who changed the Offer BP last week?” has a clear answer: there is a ticket, an owner, and documentation.
Communicating Business Process Changes to Stakeholders
Even when changes are well-controlled, they can still cause confusion if users are not informed. For Workday business process changes, communication should match the impact:
Small, low-impact tweaks can be summarized in a monthly “Workday changes” digest.
Medium-impact changes, like new approvers or extra validation steps, should be highlighted in targeted emails or intranet posts.
High-impact changes that affect many users or critical workflows may deserve training sessions, FAQs, or quick reference guides.
The goal is not to flood users with technical details, but to answer their key questions: What changed? Why did it change? What do I need to do differently?
Building Trust by Making Workday Changes Visible
Ultimately, tracking and governing business process changes is about building trust. HR, Talent, and Finance teams are more willing to rely on Workday when:
They know there is a stable process for changing core workflows.
They can see, in plain language, what has changed and why.
They feel involved in design decisions rather than surprised by new behavior.
The next time someone asks, “Who changed the Offer BP last week?”, your goal is not just to have a name. Your goal is to be able to say: “Here’s the change request, here’s who approved it, here’s the test we ran, and here’s how we communicated it.”
That is how Workday becomes simpler, more predictable, and more trusted for HR and Finance teams.
This is the kind of Workday mistake you only need to make once.
Late on a Friday, a new approval step was added to the Hire business process. The intent was simple: add an extra approval when hiring senior employees in a specific part of the organisation.
The condition looked neat in the step:
Company = Subsidiary A
Worker Type = Employee
Management Level ≥ 3
Evaluation: All of these conditions
Save. Exit. Weekend.
On Monday, onboarding stalled.
Approvals weren’t appearing in anyone’s inbox.
New hires sat stuck in “in progress” with no obvious next action.
Slack/Teams channels lit up with “Why is Hire not moving?” messages.
The root cause? That beautiful condition almost never evaluated to TRUE at that point in the process.
Real hires were more complicated:
Some were being hired into a different Company and moving into Subsidiary A later.
Some didn’t have Management Level populated yet at the time the step ran.
Some didn’t match all three attributes simultaneously in that specific Hire context.
On paper, the step looked perfect. In production, it was effectively invisible for most real-world transactions.
No approver. No routing. No progress.
Several hours were then spent:
Digging through Business Process History.
Manually advancing urgent hires via BP Actions.
Re-routing and cleaning up partial transactions.
All because one Boolean was wrong.
That incident led to a personal rule: Treat Workday changes like production deployments, not quick edits.
Here’s the playbook that came out of it.
1. Write the Routing Rule in Plain English First
Before touching the condition builder, force the logic into a simple sentence:
“If the Worker is Management Level ≥ 3 OR in salary band X, route Hire to HR Director.”
If you can’t express it clearly in one sentence, or it sounds like a legal contract, you’re probably trying to cram too many scenarios into a single condition.
Only after the plain-English version is clear should you translate it into Workday terms:
Which field(s) exactly? (e.g., Management Level, Grade, Compensation Grade Profile)
Which object? (Worker vs Position vs Job)
At which step in the Hire BP will those fields reliably be populated?
If you skip this step, you risk building a condition that looks right but never matches reality.
2. Prefer Small, Testable Steps Over Mega-Conditions
Complex routing buried in one step is hard to reason about.
Instead of one approval step with five ANDs and three ORs, consider:
Two separate approval steps with simpler conditions.
Clear, specific criteria for each step (for example, one for senior management, one for specific companies or countries).
Two clean steps that you can easily test and explain are safer than one monster step that only you understand.
Simple rules are easier to:
Review with HR/Finance.
Debug later.
Hand over to another Workday admin.
3. Test in a Non-Production Tenant With Real Personas
“Happy path” testing is how mistakes sneak through.
When testing a new Hire step in Sandbox/Preview, don’t just run one generic Employee hire. Use edge personas:
Different Companies and legal entities.
Different Worker Types (Employee vs Contingent Worker, where appropriate).
Different Management Levels, Grades, or Job Profiles.
Different Locations and supervisory orgs.
Try to recreate the weird hire that always shows up in week 3 of every go-live:
Senior hire into a new entity.
Rehire with unusual history.
Cross-company or cross-country moves that go through Hire.
If your condition only works in a perfect, single-country scenario, it isn’t ready.
4. Validate the Routing, Not Just “Does the Step Save?”
It’s easy to stop testing when the step configuration saves without errors. But what matters is how the business process behaves.
For each persona test:
Run the Hire end to end until your new step is supposed to fire.
Check if the step actually renders in the BP history.
Confirm the approver receives a Workday inbox item and can act on it.
See whether the step is skipped, triggered, or silently bypassed.
BP History is your best friend here:
If you don’t see your step at all, your condition never evaluated to TRUE.
If it appears and auto-skips, your logic or prerequisites may be off.
If it appears but nobody gets an inbox item, security or assignee setup might be wrong.
“Step saved” isn’t enough. “Step appears, routes, and can be actioned” is the real bar.
5. Document Like an Auditor Will Read It
If you ever need to explain a routing decision under time pressure, documentation saves you.
Capture:
A screenshot of the full condition in the step.
A short “Why” paragraph: what this step is for and what it protects (for example, “Extra review for senior hires or high-salary positions”).
Positive examples (transactions that should match) and negative examples (transactions that should not match).
The effective date and which tenant(s) it applies to.
Store this where your Workday team can find it (shared documentation, change log, or configuration library). Future you—and future admins—will thank you.
6. Guard Security-Related Changes With Extra Care
If your change touches domain security or BP security:
Make sure you Activate Pending Security Policy Changes. Without activation, nothing actually takes effect, and your tests may be misleading.
Re-test the end-to-end Hire with the proper security context, not just as an all-powerful admin.
It’s surprisingly easy to think “the logic works” when you’re testing as a user who has more security than any real stakeholder. Always try at least one run as a realistic role (HR Partner, HRBP, Manager, etc.).
7. Make Peer Review Non-Negotiable
A five-minute review from another Workday practitioner can save a five-hour fire drill.
Before migrating a change to Preview/Production:
Have a peer walk through your condition line by line.
Ask them to repeat the logic back in plain language.
Ask, “Where could this fail in a real Hire scenario?”
Many subtle mistakes—wrong field, wrong object, wrong timing are obvious to fresh eyes and invisible to the person who built the step.
A Reusable Playbook for Hire Approvals
That one onboarding incident turned into a reusable checklist for Hire BP changes, especially approvals:
Start with one condition. Prove it works with multiple personas.
Add one more condition. Prove it again.
If you use Any of (OR logic), justify it clearly in the step comments.
Run edge-case personas from different companies, worker types, and management levels.
Capture screenshots plus a short explanation thread.
Get a peer review before promoting.
Promote to Production only after it passes fully in Preview/Sandbox.
One Boolean can stall an organisation.
Treating Workday like a production system where every change is a mini-deployment with design, testing, documentation, and review is how you ensure it doesn’t happen again.
Where Your Workday Project Really Fails Or Succeeds
On one of the first Workday projects worked on, everything looked perfect in the Workday HCM tenant. The Business Processes were flowing, the Supervisory Organizations were clean, and the Compensation configuration finally matched what the customer wanted.
Then the first payroll run failed. Not inside Workday. At the external payroll provider. Their team called and said, “We did not get half of your employees, the file format looks wrong and we cannot load this.” In that moment, nobody said “our payroll vendor has an issue.” Everyone said “Workday is broken.”
That experience changed the way integration is viewed forever. For business users, Workday does not live only in the browser. It lives in the way Workday Integrations keep payroll, benefits, identity, finance, and reporting systems in sync day after day. If integrations are fragile, Workday will take the blame, no matter how elegant the configuration is.
The good news is that Workday Integration Cloud gives you three powerful tools to control this: Enterprise Interface Builder (EIB), Core Connectors with Cloud Connect, and Workday Studio. Early in a career, these three tools can feel like three different ways of doing the same thing. With experience, you learn that each one solves a very specific class of problem and that choosing correctly is one of the fastest ways to earn trust as a Workday Integration Consultant.
This guide walks through EIB, Core Connectors, and Workday Studio the way they are used on real projects: how they behave in a live tenant, where they shine, where they hurt you, and how to explain your choices clearly to a customer who just wants an integration that works.
How Integrations Actually Work Inside A Workday Tenant
When new people join a project and hear the word Workday Integration, they usually think about a single file or an API call leaving Workday. In reality, every integration touches multiple layers of the platform such as Web Services, Custom Reports, Business Process events, Security, and the Integration Cloud runtime.
The Building Blocks You Design With
On real projects, you work with the same core building blocks again and again.
Workday Web Services (SOAP and REST) Almost every important object in Workday, such as Worker, Position, Compensation, Supplier, Journal, and financial accounts, has operations exposed as Web Services. These are the operations that EIB, Core Connectors, and Workday Studio call behind the scenes.
Custom Reports For most outbound integrations, the real design work happens in Custom Reports. The report determines which effective‑dated fields you use, how you filter populations, and how stable your file layout is across releases. A good Advanced Report or Report‑as‑a‑Service (RaaS) can turn a complex requirement into a simple EIB, while a weak report often forces you into Workday Studio even when it is not truly required.
Business Process Events Events such as Hire, Change Job, Terminate Employee, Change Benefits, and Complete Payroll can trigger Workday Integrations. Core Connectors take special advantage of these events to build change‑driven feeds for workers and benefits.
Integration System and Integration System User Every integration runs as an Integration System User with specific Security Groups and Domain permissions. If security is too restrictive, your integration will silently miss workers or transactions; if security is too broad, you create audit and compliance risk.
Workday Integration Cloud Runtime When you deploy EIB and Workday Studio integrations, they run inside the Workday Integration Cloud. The runtime handles scheduling, logging, alerts, and error handling. Knowing how to read Integration Events, Integration Attachments, and Integration System logs is a core day‑to‑day skill on any Workday team.
Once you see integrations this way, you stop thinking “Which tool do I like?” and start thinking “Which combination of Web Service, Report, Event, and Runtime gives my customer the simplest integration that will still survive production?”
Inbound, Outbound And When It Becomes Bidirectional
Every Workday Integration you design fits into one of three flow types.
Outbound Integration Workday is the system of record and sends data to another system, such as sending workers to an external payroll engine, sending benefit elections to a third‑party administrator, or sending organization data to a planning tool.
Inbound Integration An external system sends data into Workday, and Workday becomes the system of record for that data. Examples include new hires from an ATS, cost centers from an upstream ERP, or exchange rates from a treasury system.
Bidirectional Integration Data flows in both directions and you need rules about which system wins when there is a conflict. A simple example is basic worker profile data mastered in Workday, with optional attributes updated in a separate talent or engagement platform.
Choosing between EIB, Core Connectors, and Workday Studio becomes much easier when you are clear about which of these flows you are designing and where the System Of Record sits for each field. A senior consultant will say this explicitly in design workshops; that habit alone prevents many integration issues during testing.
Workday EIB: The First Integration Tool Most Consultants Master
The first time a simple outbound file was built using Enterprise Interface Builder (EIB), it felt like a cheat code. No external tool, no local IDE, everything inside the Workday tenant. A few hours later, the customer had a recurring file to a small benefits vendor that they had been manually creating in spreadsheets for months.
Since then, EIB has become the default starting point for many integration problems. It does not solve everything, but it is the most accessible entry point into Workday Integration for functional consultants and HRIS teams.
What EIB Really Is Inside Workday
Enterprise Interface Builder (EIB) is an integration framework inside Workday that lets you build inbound and outbound file integrations using configuration instead of code. It is designed to work hand in hand with Custom Reports and Workday Web Services.
In practice, EIB is built around a very simple pattern that you will see referenced often in integration training: Get Data, Transform, Deliver.
Get Data For outbound integrations, EIB uses a Custom Report or RaaS as the data source. You decide which Business Object you report on, which fields to pull, and how to filter the population.
Transform In many cases, you can send the report output as it is. When you cannot, EIB supports basic transformation logic and optional XSLT for more complex XML reshaping.
Deliver EIB can send the file to a secure SFTP server, Workday Drive, or as an attachment in notification emails, depending on the requirement and security policies.
Because everything lives in Workday, there is no external deployment pipeline to manage. That makes EIB extremely attractive for customers who want their internal Workday team to own as much of the integration lifecycle as possible.
Where EIB Shows Up On Real Projects
If you sit with a project team and list all the interfaces they need, a surprising number can be solved with EIB plus strong Report Writer skills. Patterns you see repeatedly include:
Recurring outbound Worker demographic files for small payroll or benefits providers that only support CSV via SFTP.
Outbound Cost Center, Company, and Supervisory Organization structures to a downstream ERP or planning application.
One‑time or limited‑duration inbound loads during deployment, such as historical time off balances, legacy positions, or existing assets for Workday Financials.
Internal “admin utilities”, such as quarterly security role extracts, audit files for SOX controls, or snapshots of key metrics for HR analytics.
Whenever a requirement looks like a straightforward file with relatively stable columns and no complicated orchestration, EIB deserves to be your first candidate.
How An Outbound EIB Feels When You Build It
From a distance, the steps to create an outbound EIB look procedural. In reality, the process feels like a conversation between what the downstream system needs and what Workday can provide through reporting.
You start by designing the Custom Report, map each field in the vendor specification to a Workday field, and decide how to handle effective dating and terminated workers. Once the report returns exactly what you need, you create the outbound EIB, select the report as the source, and decide if users can override prompts.
If the target system needs a different layout, you configure transformation, sometimes just renaming headers and changing date formats, sometimes using XSLT for XML. You then configure Delivery, test SFTP connectivity, agree on file naming conventions, and set Integration Scheduling and notifications.
By the time you promote an outbound EIB to production, you know the file, the report, and the downstream system well enough to explain every column and filter to both HR and IT stakeholders. That confidence is one reason EIB is such a good training ground for new Workday Integration practitioners.
How Inbound EIBs Expose Data Quality Quickly
Inbound EIB work can be more stressful than outbound because bad data will break your Business Processes and sometimes your customer’s trust. At the same time, it is one of the fastest ways to understand how Workday models core data.
You generate a template for the relevant Workday Web Service, such as Import Worker or Import Positions, map legacy data into that structure, and then discover incomplete codes, missing Supervisory Organizations, or invalid locations. You create the inbound EIB, configure security for the Integration System User, and run multiple cycles in a non‑production tenant, fixing every “Invalid reference” or “Business process validation failed” error along the way.
By the time you run the final loads in production, you have a much deeper respect for data governance and reference data ownership. After a few inbound EIB conversions, you start viewing data quality as a core part of Workday Integration Design, not just a client problem.
When EIB Is Exactly Right And When It Is Not
Over time, a simple rule emerges.
If the requirement is a stable, mostly flat file and Workday can supply all data through a single Custom Report, EIB is usually the best first choice. If you need event‑driven worker changes, complex benefit logic, or payroll specific flows that Workday already understands, then Core Connectors deserve a serious look. If you find yourself chaining multiple EIBs, adding complex transformations, or trying to coordinate multiple external systems manually, it is time to consider Workday Studio.
The goal is not to be an “EIB person” or a “Studio person”. The goal is to be the consultant who consistently chooses the simplest Workday Integration pattern that will still survive real‑world change, volume, and audits.
Workday Core Connectors: When “Standard” Is Actually An Advantage
The first time a project used Core Connector: Worker instead of a custom file, it transformed the integration landscape. The customer had multiple downstream systems that all needed worker changes from Workday HCM. Every Hire, Change Job, or Terminate Employee event had to reach at least one vendor.
Originally the plan was to design separate EIB outputs for each vendor, meaning multiple reports, schedules, and duplicate change logic. When Core Connector: Worker entered the design, everything simplified. Instead of building separate integration brains, there was now one Core Connector extracting worker changes, and the team focused only on how each target system wanted the data formatted.
That project made one thing clear. Core Connectors are not just another integration option. They are Workday delivered integration frameworks that understand worker and benefits data more deeply than any custom file you will design.
What Core Connectors Really Are Inside Workday
In simple terms, Core Connectors are prebuilt integration templates delivered as part of Workday Integration Cloud. They are designed specifically for domains such as worker data, payroll, and benefits and come with out‑of‑the‑box logic for detecting changes, filtering populations, and producing structured output.
Where EIB expects you to design almost everything in a Custom Report, a Core Connector starts from the idea that Workday already knows how workers and benefits behave over time. It uses that knowledge to calculate what changed between runs rather than making you reinvent change detection.
Two ideas matter most.
They are template integrations that you configure and extend rather than writing from zero, and they are change aware. A Core Connector: Worker does not simply dump all workers every time. It compares the current state with previous runs and picks out only the relevant changes, according to the rules you configure.
How Cloud Connect Builds On Core Connectors
You will often hear about Cloud Connect for Benefits or Cloud Connect for Third Party Payroll. Under the hood, these are Core Connectors that Workday has extended with vendor‑specific content, sample mappings, transforms, and documentation.
For example, Cloud Connect for Benefits provides a full framework for sending enrollment data, eligibility, and coverage details from Workday HCM to benefits administrators, using Core Connector logic plus content for plan types such as medical, dental, and pension. Cloud Connect for Third Party Payroll gives you a structure for sending worker, pay input, and other payroll‑related data from Workday HCM to external payroll engines.
In both cases, you are not starting with a blank page. You are taking something already close to what you need and aligning it with your vendors and configuration, spending more time on mapping and testing and less time inventing change logic.
How Core Connector: Worker Actually Detects Changes
To understand why Core Connector: Worker is powerful, imagine it has access to a transaction log that records staffing events in your Workday tenant. At each run, it looks at worker‑related events since the last successful run, such as Hire Employee, Change Job, Change Personal Data, or Terminate Employee. It compares key fields at the previous and current run, determines what changed, sets event flags like “New hire” or “Termination”, and then produces structured output in XML or CSV for downstream systems.
From the outside, this feels like magic. From the inside, it is disciplined event‑driven integration that uses Workday knowledge of worker life cycle events. Building this logic from scratch in Workday Studio is possible but more complex to maintain.
When Core Connectors Are A Better Fit Than EIB
On real projects, the decision to use Core Connectors instead of EIB appears in conversations such as a payroll team asking for “everything that changed since last payroll”. You could design a report and EIB, but then you must write change logic and avoid duplicates. Or you can say, “There is a Core Connector: Worker and Cloud Connect for Third Party Payroll that already know how to detect worker changes.”
Core Connectors shine when you need change‑driven data for workers and benefits, want to align with Workday delivered patterns, or have multiple downstream systems that all need worker changes and you want a central integration spine to feed them.
They are less suitable when the scenario sits outside their domains, when logic is highly custom and better handled in Workday Studio, or when the requirement is simply to send a flat report‑like file once a week, which EIB handles more simply.
Workday Integrations At A Glance
Workday Studio: When Your Integration Stops Being “Simple”
There is usually a moment in a project when nobody wants to say it, but everyone feels it: “This integration is not simple anymore.” That is usually when Workday Studio enters the conversation.
Workday Studio is an external, Eclipse based IDE that lets you design advanced Workday Integrations that go beyond what EIB and Core Connectors can comfortably handle. It allows complex flows, multiple steps, parallel branches, calls to external APIs, large file handling, compression, encryption, and sophisticated error routing.
You reach for Workday Studio when one of three things is true: the business process spans multiple systems and must be orchestrated, the transformation logic is too complex for simple mappings, or the volume and performance requirements push beyond what EIB and Core Connectors handle well.
On many projects, Workday Studio is used to combine outputs from Core Connectors, enrich them with additional data, call external services for validation, and then produce a final file per country or vendor. It becomes the orchestration layer for your integration landscape rather than a replacement for EIB or Core Connectors.
Workday Integrations At A Glance
Dimension
EIB (Enterprise Interface Builder)
Core Connectors
Workday Studio
Primary purpose
File based inbound and outbound Workday Integrations using Custom Reports and simple transformations.
Productized Workday Integrations for worker, payroll, and benefits data using delivered logic and Business Process events.
Complex, orchestrated Workday Integrations built in an external IDE for multi step, high volume, or API heavy scenarios.
Typical users
Workday Functional Consultant, HRIS Analyst, Reporting specialist with some integration knowledge.
Workday Integration Consultant focusing on HR, payroll, or benefits, comfortable with events and change logic.
Integration developer or Workday Studio specialist with strong technical and architectural skills.
Best suited for
Simple recurring files, one time data loads, admin utilities and “report as file” patterns.
Change driven worker and benefits feeds, external payroll, time, and vendor interfaces where Cloud Connect content exists.
Multi system flows, complex routing, advanced transformations, batch splitting and API orchestration across platforms.
Trigger model
Manual runs and Integration Scheduling based on time.
Event driven from Business Processes with options for deltas and effective date logic, plus scheduling.
Flexible: can be event based, scheduled, or invoked as a Web Service for near real time patterns.
Data source pattern
Outbound relies heavily on Custom Reports or RaaS delivering flat files. Inbound uses Workday Web Services with templates.
Many designs use delivered worker and benefits structures, with configuration to extend or map to vendor formats.
Can combine Workday Web Services, external APIs, multiple files, and conditional steps inside one Integration System.
Transformation capability
Basic mapping and formatting, with optional XSLT for XML if required.
More sophisticated, domain specific transforms, often packaged in Cloud Connect content.
Full control over transformation logic, branching, looping, error routing and custom components.
Volume and performance
Suitable for low to moderate volumes and batch frequency when file sizes remain reasonable.
Designed for ongoing, production grade deltas in worker and benefits data across the life of the tenant.
Best for high volume, complex or global integrations where throughput, error handling and resilience matter most.
Maintenance ownership
Typically owned by the internal Workday team through the tenant UI, with no external code repository.
Shared ownership between customer and Workday where delivered logic is reused and only configuration changes.
Requires version control, deployment practices and a clear owner for the Workday Studio codebase.
When it is the wrong choice
When you need event driven logic, multi system orchestration, or very high frequency updates.
When your scenario does not match a supported domain, or needs custom logic far beyond the connector’s intent.
When a single Custom Report plus EIB, or a standard Core Connector, would solve the problem more simply.
How A Senior Consultant Actually Chooses
With experience, the decision path becomes repeatable.
If the requirement is a straightforward file that Workday can provide via Custom Report, start with EIB. If it is worker or benefits related, needs deltas based on events, and aligns with domains Workday has already modeled, evaluate Core Connectors and Cloud Connect. If it spans multiple systems, requires complex orchestration, or must support high volume or near real time behavior, consider Workday Studio.
The consultant who can explain this logic clearly to both HR and IT, and then deliver integrations that behave exactly as promised in production, quickly becomes the person everyone wants on their next Workday project.
Here’s the first question every Workday implementation team asks during kickoff:
“Should we use Position Management or Job Management?”
And here’s what usually happens next:
Someone from Finance says: “We need Position Management for headcount budgeting and control.”
Someone from HR says: “Position Management sounds complicated. Can we just use Job Management?”
Someone from IT says: “What’s the difference?”
The conversation stalls. The team defaults to Job Management because it seems simpler. Implementation moves forward.
Six months after go-live, Finance complains: “We can’t track approved headcount. We can’t freeze positions. We can’t budget by position.”
HR says: “We told you Job Management was easier.”
Finance says: “Easier doesn’t mean right.”
Now you’re stuck. Switching from Job Management to Position Management post-go-live requires a complete data migration, org redesign, and business process reconfiguration. It’s a multi-month project that could have been avoided with the right decision during implementation.
This guide explains the difference between Position Management and Job Management, when to use each, and how to make the right choice for your organization before you go live.
Let’s start with the fundamentals.
What Is Job Management?
Job Management is Workday’s default staffing model. It’s simpler, more flexible, and easier to implement. In Job Management, you hire workers directly into Job Profiles without creating predefined positions.
How Job Management Works
When you hire a worker using Job Management:
You select a Job Profile (e.g., “Software Engineer,” “HR Business Partner,” “Sales Manager”)
You assign the worker to a Supervisory Organization
You assign a Location, Cost Center, and other job details
The worker is hired, and their job data is tracked in Workday
There is no position object. The worker’s job is defined by their Job Profile, organization assignments, and manager relationship.
Example: Hiring with Job Management
Scenario: You need to hire a new Software Engineer for the Engineering – Product team.
Steps:
Navigate to Hire Employee
Enter worker details (name, email, hire date)
In Job Details:
Job Profile: Software Engineer
Supervisory Organization: Engineering – Product
Manager: Alex Garcia (Director, Engineering Product)
Location: San Francisco Office
Cost Center: Engineering Product Cost Center
Submit and approve
The worker is now employed. Workday tracks their job data, but there is no “Position 12345” assigned to them. They simply hold the job “Software Engineer” in the “Engineering – Product” organization.
Key Characteristics of Job Management
Flexibility:
You can hire as many people as you want into the same Job Profile
No need to create positions in advance
Easy to restructure organizations without worrying about position assignments
Simplicity:
Fewer Workday objects to manage (no positions)
Easier to implement and configure
Less training required for HR and hiring managers
Limitations:
No headcount control: You can’t limit the number of people in a Job Profile
No position-level budgeting: You can’t budget for “Position 12345” with a specific salary
No position freeze: You can’t freeze hiring for a specific position
No position requisition tracking: You can’t track which positions are open vs. filled
Who Uses Job Management:
Small to mid-sized companies (under 5,000 employees)
Companies with flexible, rapidly changing org structures
Startups and high-growth companies
Organizations without strict headcount control requirements
Companies that don’t need position-level budgeting
What Is Position Management?
Position Management is Workday’s advanced staffing model. It’s more structured, more controlled, and more complex. In Position Management, you create predefined Positions in advance, and workers are hired into those positions.
How Position Management Works
In Position Management, you follow this workflow:
Create a Position in Workday (e.g., “Software Engineer – Position 12345”)
Assign the position a Job Profile, Supervisory Organization, Location, and budgeted salary
The position exists in Workday with status = Unfilled (no worker assigned yet)
When you’re ready to hire, you create a Requisition linked to that position
When you hire a worker, you assign them to the position
The position status changes to Filled
The position object exists independently of the worker. If the worker terminates, the position remains and can be refilled.
Example: Hiring with Position Management
Scenario: You need to hire a new Software Engineer for the Engineering – Product team.
Step 1: Create the Position
Navigate to Create Position
Fill in position details:
Position ID: POS-12345 (auto-generated or manually entered)
Job Profile: Software Engineer
Supervisory Organization: Engineering – Product
Manager: Alex Garcia (Director, Engineering Product)
Location: San Francisco Office
Cost Center: Engineering Product Cost Center
Budgeted Salary: $120,000 annually
Effective Date: January 1, 2025
Submit and approve
Position is created with status = Unfilled
Step 2: Create a Requisition
Navigate to Create Requisition
Link the requisition to Position POS-12345
Submit for approval
Requisition is posted, recruiting begins
Step 3: Hire a Worker into the Position
Navigate to Hire Employee
Enter worker details (name, email, hire date)
In Job Details:
Position: POS-12345 (select the position)
Workday auto-fills Job Profile, Supervisory Org, Location, Cost Center, and Budgeted Salary from the position
Submit and approve
The worker is now employed in Position POS-12345. The position status changes from Unfilled to Filled.
Key Characteristics of Position Management
Control:
Predefined positions with approved headcount
Each position has a budgeted salary
You can freeze positions to prevent hiring
You can track open vs. filled positions in real time
Budgeting:
Finance can budget by position (not just by Job Profile or org)
Each position has a salary budget that can be tracked against actuals
Position-level cost forecasting and workforce planning
Tracking:
Requisitions are linked to positions
You can see which positions are open, filled, or frozen
Historical tracking: who held each position over time
Complexity:
More Workday objects to manage (positions, requisitions, position hierarchies)
Requires upfront planning (you must create positions before hiring)
More training required for HR, hiring managers, and Finance
Less flexibility (harder to restructure orgs when positions are involved)
Who Uses Position Management:
Large enterprises (5,000+ employees)
Government agencies and public sector organizations
Organizations with strict headcount control and budget governance
Companies that need position-level budgeting and forecasting
Key Differences: Job Management vs. Position Management
Dimension
Job Management
Position Management
Staffing Model
Workers hired into Job Profiles
Workers hired into predefined Positions
Headcount Control
No control (hire as many as you want)
Strict control (only hire into approved positions)
Budgeting
Budget by Job Profile or Org
Budget by individual Position
Position Freeze
Not available
Can freeze positions to prevent hiring
Requisition Tracking
Requisitions not linked to positions
Requisitions linked to positions
Flexibility
High (easy to restructure orgs)
Lower (positions tied to orgs)
Complexity
Simple (fewer objects to manage)
Complex (positions, requisitions, hierarchies)
Implementation Time
Faster (less configuration)
Slower (requires position setup)
Best For
Small/mid-sized, flexible orgs
Large enterprises, regulated industries
Workday Default
Yes (default staffing model)
Optional (must be enabled and configured)
When to Use Job Management
Choose Job Management if:
1. You’re a Small to Mid-Sized Organization (Under 5,000 Employees)
Small companies value flexibility over control. You need to hire quickly, restructure frequently, and avoid bureaucratic headcount approval processes.
Why Job Management Works:
No need to create positions in advance (hire as needed)
Easy to scale up or down rapidly
Minimal overhead for HR and Finance teams
Example: A 500-person startup needs to hire 50 engineers over the next quarter. Instead of creating 50 positions, approving budgets for each, and tracking requisitions, they simply hire engineers into the “Software Engineer” Job Profile as candidates are found.
2. Your Organization Restructures Frequently
If you reorganize teams quarterly, change reporting lines often, or operate in a fast-paced, agile environment, Position Management becomes a maintenance burden.
Why Job Management Works:
Workers are tied to Job Profiles and Supervisory Orgs, not positions
When you restructure, you just reassign workers to new orgs (no position reassignments)
No risk of orphaned positions or position hierarchy mismatches
Example: A tech company reorganizes product teams every quarter based on roadmap priorities. Workers move between teams frequently. Job Management keeps HR administration simple without worrying about position updates.
3. You Don’t Need Strict Headcount Control
If Finance doesn’t require position-level budgeting, and your leadership trusts managers to hire within budget guidelines, you don’t need the overhead of Position Management.
Why Job Management Works:
Budget at the Supervisory Org or Cost Center level (not position level)
Managers approve hires based on team need, not predefined positions
Simpler approval workflows (no position requisition step)
Example: A consulting firm hires based on client demand. Headcount fluctuates based on project pipeline. Finance budgets by Cost Center and trusts practice leaders to hire appropriately without position-level control.
4. You Want a Faster, Simpler Implementation
Position Management requires significant upfront configuration, position data setup, and business process customization. If you’re on a tight implementation timeline, Job Management is faster.
Why Job Management Works:
Fewer Workday objects to configure
No need to load historical position data
Simpler business process workflows (Hire, Terminate, Change Job)
Less training required for end users
Example: A company switching from a legacy HRIS to Workday has 4 months to go live. They choose Job Management to avoid the complexity of creating and loading 3,000 positions during migration.
When to Use Position Management
Choose Position Management if:
1. You Need Strict Headcount Control and Budget Governance
Large organizations, government agencies, and highly regulated industries require tight control over headcount. Every hire must be approved, budgeted, and tracked at the position level.
Why Position Management Works:
Finance approves each position with a budgeted salary before recruiting begins
You can’t hire unless a position exists and is unfilled
Position freeze prevents hiring into specific roles without additional approval
Example: A state government agency has a fixed annual headcount budget approved by the legislature. Every position must be authorized, budgeted, and tracked. Position Management ensures compliance with public sector headcount rules.
2. You Budget and Forecast at the Position Level
If Finance builds budgets by position (not just by department or Job Profile), you need Position Management to align Workday with your budgeting process.
Why Position Management Works:
Each position has a budgeted salary that flows into financial planning tools
Finance can compare budgeted salary (position) vs. actual salary (worker)
Workforce planning tools show open positions, filled positions, and budget variance
Example: A Fortune 500 company builds annual budgets by position. Finance allocates $150,000 for “Senior Product Manager – Position 45678.” Workday tracks actual salary against this budgeted amount and reports variance monthly.
3. You Need to Track Open vs. Filled Positions in Real Time
If leadership wants real-time visibility into open headcount, requisition status, and time-to-fill metrics, Position Management provides this out of the box.
Why Position Management Works:
Positions have status: Unfilled, Filled, Frozen
Requisitions are linked to positions (easy to track open reqs)
Reports show open position counts by department, location, Job Profile
Example: A healthcare system with 10,000 employees needs to track critical open positions (nurses, physicians, therapists). Position Management gives HR and leadership a live dashboard of open positions, requisition status, and hiring pipeline.
4. You Operate in a Highly Regulated Industry
Government agencies, healthcare organizations, and financial services firms often have regulatory requirements for headcount tracking, position documentation, and audit trails.
Why Position Management Works:
Full audit trail: who created the position, who approved it, who filled it, when
Position history shows all workers who held a position over time
Supports compliance reporting and external audits
Example: A federal agency must document every position, justify every hire, and provide audit trails for inspector general reviews. Position Management provides the required documentation and compliance tracking.
5. You Want to Freeze Hiring for Specific Positions
If your organization needs the ability to temporarily freeze hiring for specific roles (due to budget cuts, hiring freezes, or organizational changes), Position Management supports this.
Why Position Management Works:
You can freeze individual positions or groups of positions
Frozen positions can’t be filled until unfrozen
Provides granular control over hiring without blanket freezes
Example: A company facing budget constraints freezes 50 mid-level manager positions while keeping engineering and sales positions open. Position Management allows this selective freeze without stopping all hiring.
Hybrid Model: Can You Use Both?
Yes. Workday allows you to use Position Management for some Job Profiles and Job Management for others.
How the Hybrid Model Works
You configure specific Job Profiles to require positions. Workers hired into those Job Profiles must be assigned to a position. Other Job Profiles remain position-optional.
You need headcount control for leadership and management roles but want flexibility for individual contributors
Finance wants to budget senior positions individually but budget IC roles at the org level
You want to phase Position Management in gradually (start with exec roles, expand over time)
Hybrid Model Challenges
Complexity:
Two staffing models to manage and maintain
Users need to understand which roles require positions and which don’t
Reporting becomes more complex (some workers have positions, some don’t)
Recommendation: Only use hybrid if you have a clear business reason. Most organizations should choose one model and stick with it for simplicity.
Implementation Considerations
Switching from Job Management to Position Management
The Bad News: Switching from Job Management to Position Management post-go-live is painful. You need to:
Create positions for every current worker
Assign workers to positions (mass update via Change Job)
Reconfigure business processes to require positions
Retrain HR, hiring managers, and recruiters
Migrate requisition workflows
This is a multi-month project with significant change management effort.
The Good News: If you choose the right model during implementation, you won’t need to switch.
Switching from Position Management to Job Management
Even Harder. Workday strongly discourages switching from Position Management to Job Management because:
You lose all position-level budget data
Historical position tracking is lost
Requisitions become unlinked from positions
Finance loses position-based forecasting
Recommendation: If you think you might need Position Management in the future, implement it from day one. It’s easier to start with Position Management and simplify later than to retrofit it after go-live.
Decision Framework: Job Management vs. Position Management
Use this decision tree to choose the right model:
Question 1: Do you need strict headcount control?
Yes: Position Management
No: Continue to Question 2
Question 2: Does Finance budget at the position level?
Yes: Position Management
No: Continue to Question 3
Question 3: Do you need to track open vs. filled positions in real time?
Yes: Position Management
No: Continue to Question 4
Question 4: Are you in a highly regulated industry (government, healthcare, financial services)?
Yes: Position Management
No: Continue to Question 5
Question 5: Do you have more than 5,000 employees?
Yes: Consider Position Management (depends on control requirements)
No: Job Management is likely sufficient
Question 6: Do you restructure frequently or operate in a fast-paced environment?
Yes: Job Management
No: Position Management may work
Common Mistakes
Mistake 1: Choosing Job Management Because “It’s Easier”
The Problem: Teams default to Job Management during implementation because it’s simpler and faster. They ignore long-term requirements for headcount control and budgeting.
What Happens: Finance complains post-go-live. You’re forced to retrofit Position Management 12 months later at massive cost and effort.
The Fix: Involve Finance early. Understand budgeting and headcount control requirements before choosing a staffing model.
Mistake 2: Choosing Position Management When You Don’t Need It
The Problem: Teams assume “bigger companies use Position Management, so we should too.” They implement Position Management without clear business requirements.
What Happens: HR drowns in position administration. Creating and maintaining positions becomes a bottleneck. Hiring slows down. Users complain about complexity.
The Fix: Only implement Position Management if you have a clear business need for position-level control and budgeting.
Mistake 3: Not Planning for Future Growth
The Problem: A 1,000-person company chooses Job Management because “we don’t need position control today.” They plan to grow to 10,000 employees over 5 years.
What Happens: At 5,000 employees, Finance demands position-level budgeting. Now you need to retrofit Position Management across a live tenant.
The Fix: Design your staffing model for future state, not current state. If you plan to grow significantly, choose Position Management from the start.
Workday Tasks for Position Management
Create and Manage Positions:
Create Position (define new positions)
Edit Position (update position details)
Fill Position (assign worker to position)
End Position (inactivate position)
Freeze Position (prevent hiring into position)
Position Requisitions:
Create Requisition (linked to position)
Edit Requisition (update req details)
Close Requisition (when position is filled)
Position Reporting:
View Position (see position details and history)
Position Summary (track open vs. filled positions)
Position Budget vs. Actuals (Finance reporting)
Position Hierarchies:
Create Position Hierarchy (group positions for reporting)
View Position Hierarchy (see position org structure)
Final Thoughts
Choosing between Job Management and Position Management is one of the most important decisions you’ll make during Workday implementation.
Choose Job Management if:
You’re small to mid-sized (under 5,000 employees)
You value flexibility and speed over control
You don’t need position-level budgeting
You restructure frequently
You want a simpler, faster implementation
Choose Position Management if:
You need strict headcount control and governance
Finance budgets at the position level
You need to track open vs. filled positions in real time
You’re in a highly regulated industry
You’re a large enterprise with complex workforce planning needs
The Right Time to Decide: During implementation, not after go-live.
Involve Finance, HR, and leadership. Understand your current requirements AND your future state. Choose the model that supports your business for the long term.
Because switching later is expensive, disruptive, and avoidable.
“We’re implementing Workday Position Management next quarter. Any advice?”
I get this question at least once a month from HR leaders embarking on Workday implementations.
My honest answer? Position Management works beautifully when configured correctly. When configured poorly, it becomes the most complained-about feature in your entire Workday tenant.
Last year, I joined a client project three months after their Workday go-live. The HR Operations team was drowning in position management tickets:
“Why can’t I fill this position?”
“The system says this position is filled, but the worker terminated two weeks ago.”
“I need to create 50 new positions for our expansion, but it takes 45 minutes per position.”
“Position data doesn’t match our headcount reports.”
“Why do I need a position AND a job? They’re the same thing!”
Their Position Management implementation had all the classic problems. Five thousand positions. Three thousand active workers. Dozens of unfillable positions. No clear ownership. Inconsistent data quality. And an HR team that had completely lost trust in the system.
We spent six weeks systematically fixing the root causes. By the end, position management went from their most hated feature to a strategic workforce planning tool that executives actually used.
This guide will show you the seven fixes that transformed their implementation and have since worked across dozens of other Workday tenants. These are not theoretical best practices from Workday Community. These are battle-tested solutions to the specific problems that make people hate Position Management.
Why Position Management Gets So Much Hate
Before we dive into fixes, you need to understand why Position Management creates so much frustration.
The Fundamental Misunderstanding
Most organizations implement Position Management because they think they need it for budgeting or headcount planning.
They are partially right. Position Management can support those use cases. But that is not what Position Management actually does.
Position Management is a workforce structure management tool that maintains a parallel organizational structure based on positions rather than workers.
When you enable Position Management in Workday, you are making a fundamental architectural decision: Your organizational structure will be built on positions first, workers second.
Without Position Management, your organizational structure looks like this:
Worker → Job → Supervisory Organization → Cost Center
With Position Management, your organizational structure looks like this:
Position → Worker → Job → Supervisory Organization → Cost Center
That extra layer creates the complexity that frustrates everyone.
The Three Core Complaints
Every Position Management complaint falls into one of three categories:
Complaint 1: “It’s too much work”
Creating positions is more work than just hiring workers directly into jobs. Managing position changes is more work than managing worker job changes. Every organizational change now requires updating positions first, then workers.
Complaint 2: “The data doesn’t match reality”
Positions show as filled when workers have terminated. Positions show as vacant when workers are actively working. Position budgets don’t match actual headcount. Position titles don’t match what people actually do.
Complaint 3: “Nobody understands it”
Hiring managers do not understand the difference between a position and a job. Finance does not understand why budget is allocated to positions that have no workers. HR does not understand when to create new positions versus reusing existing vacant positions.
All three complaints stem from the same root cause: Position Management was implemented without clear business rules and governance.
The fixes I am about to show you establish those rules and governance.
This is the most important fix. Get this wrong and everything else fails.
The Problem
Most organizations have no clear rules for when to create a new position versus reusing an existing vacant position.
The result? Managers create new positions for every hire because it is easier than searching for vacant positions to reuse. Three years later, you have 8,000 positions for 3,000 workers.
Your position-to-worker ratio should rarely exceed 1.5:1 (1.5 positions for every 1 worker). When you hit 2:1 or 3:1, your position data has become meaningless.
The Fix: Establish Position Creation Governance
Implement one of these three position creation strategies based on your organizational needs:
Strategy 1: Strict Position Control (Best for stable, hierarchical organizations)
New positions can only be created through:
Annual budgeting process (Finance approves all position budget)
Formal headcount planning (HR Ops creates positions in batches)
Executive approval for unbudgeted positions
When to use this: Large enterprises with formal budgeting processes, government organizations, healthcare systems with strict FTE budgeting.
Position-to-worker ratio target: 1.1:1 to 1.3:1
Strategy 2: Manager-Initiated with Approval (Best for growing organizations)
Managers can create positions through a business process that requires:
Business justification
Budget code assignment
HR Operations approval
Finance approval for new budget allocation
When to use this: Mid-sized companies with active hiring, organizations in growth mode, companies with distributed HR.
Position-to-worker ratio target: 1.3:1 to 1.5:1
Strategy 3: Just-in-Time Position Creation (Best for dynamic organizations)
Positions are created automatically during the hiring process:
Requisition approval creates the position
Position is filled immediately upon hire
Position closes automatically when worker terminates
When to use this: High-growth startups, project-based organizations, consulting firms with rapid hiring cycles.
Position-to-worker ratio target: 1.0:1 to 1.2:1
Implementation Guidance
Step 1: Audit your current state
Calculate your current position-to-worker ratio:
Total positions ÷ Total active workers = Ratio
If your ratio exceeds 2:1, you have a data quality crisis that needs immediate cleanup before implementing governance.
Step 2: Choose your strategy
Select the strategy that matches your culture. Do not choose Strategy 1 (Strict Position Control) if your organization values manager autonomy. Do not choose Strategy 3 (Just-in-Time) if you need position budget before hiring approval.
Step 3: Document the rules
Create a position management policy document that answers:
Who can create positions?
What approval is required?
When should positions be created (before requisition? during hiring? after offer acceptance)?
How are vacant positions reused?
When are positions closed or inactivated?
Step 4: Train your stakeholders
Position creation rules mean nothing if managers, recruiters, and HR do not understand them. Include position management in:
New manager onboarding
Recruiter training
HR operations procedures
Finance budgeting processes
Step 5: Enforce through business process configuration
Configure your Workday business processes to enforce your rules:
Remove position creation from manager self-service if using Strict Position Control
Add approval steps to position creation if using Manager-Initiated
Auto-create positions from requisition approval if using Just-in-Time
Do not rely on training and documentation alone. Configure Workday to make the wrong behavior impossible.
Expected Impact
Clear position creation rules reduce position proliferation by 60% to 80% within the first year.
One client reduced their position-to-worker ratio from 2.7:1 to 1.4:1 over 18 months by implementing Manager-Initiated position creation with HR approval.
Fix 2: Implement Position Lifecycle Automation
Manual position lifecycle management creates the data quality problems that make everyone hate Position Management.
The Problem
In most implementations, positions remain in “Filled” status after workers terminate. They remain in “Vacant” status after workers are hired. They accumulate in “On Hold” or “Frozen” statuses with no clear owner responsible for cleanup.
Finance allocates budget to positions showing as “Vacant” that have been filled for six months. HR Operations sees positions showing as “Filled” when the incumbent terminated three months ago.
Nobody trusts position data because position status never reflects reality.
The Fix: Automate Position Status Updates
Configure Workday to automatically update position status based on worker events:
Automation 1: Position Fills on Hire
When a worker is hired into a position:
Position status changes from “Vacant” to “Filled”
Position availability changes from “Available” to “Unavailable”
Position filled date updates to hire date
Position worker relationship is established
Workday configuration: Enable “Update Position on Hire” in your Hire business process.
Automation 2: Position Vacates on Termination
When a worker terminates from a position:
Position status changes from “Filled” to “Vacant”
Position availability changes from “Unavailable” to “Available” (if the position should remain open)
Position vacant date updates to termination date
Position worker relationship is ended
Workday configuration: Enable “Update Position on Termination” in your Terminate Employee business process.
Automation 3: Position Status Updates on Worker Job Change
When a worker moves to a new position:
Old position status changes from “Filled” to “Vacant”
New position status changes from “Vacant” to “Filled”
Old position becomes available for backfill
New position becomes unavailable
Workday configuration: Enable “Update Position on Job Change” in your Job Change business process.
Automation 4: Position Freezes on Elimination
When a position is eliminated:
Position status changes to “Frozen” or “Eliminated”
Position availability changes to “Unavailable”
Position budget can be reallocated
Position cannot be filled without unfreezing
Workday configuration: Create “Eliminate Position” business process with automatic status update.
Position Availability Logic
Position status and position availability are different fields that control different behaviors:
Position Status (informational):
Vacant
Filled
Frozen
Eliminated
Position Availability (controls hiring):
Available (can be filled through hiring)
Unavailable (cannot be filled)
Your automation should update both fields appropriately.
Example logic:
Filled position = Status “Filled”, Availability “Unavailable”
Vacant position approved for hire = Status “Vacant”, Availability “Available”
Vacant position on hiring freeze = Status “Vacant”, Availability “Unavailable”
Eliminated position = Status “Eliminated”, Availability “Unavailable”
Expected Impact
Lifecycle automation eliminates 90% of position status data quality issues.
One client had 450 positions with incorrect status before automation. Six months after implementing lifecycle automation, they had 12 positions with incorrect status (all explained by complex job sharing scenarios that required manual management).
Fix 3: Solve the Position Title Confusion
Position titles are one of the most frustrating aspects of Position Management for managers and workers.
The Problem
Workers are confused when their position title does not match their job title. Managers are confused when they see “Senior Software Engineer – Position 00347” on organizational charts instead of just “Senior Software Engineer.”
The root cause: Workday displays position ID and position title in many places where users expect to see job title.
Example of the confusion:
Worker name: Sarah Chen
Job: Senior Software Engineer
Position: Senior Software Engineer – Position 00347
Sarah sees “Senior Software Engineer – Position 00347” on her worker profile, organizational charts, and business cards. She reasonably asks: “Why does my title have a position number in it?”
The Fix: Standardize Position Titling Convention
Implement one of these three position titling strategies:
Strategy 1: Position Title Matches Job Title (Simplest)
Every position’s title exactly matches its job title.
Example:
Job: Senior Software Engineer
Position Title: Senior Software Engineer
Position ID: P-12847 (used for internal tracking only)
When to use this: Organizations where positions represent generic roles, not unique positions.
Pros: Workers see familiar job titles everywhere. No confusion.
Cons: Cannot distinguish between multiple positions with the same job title. Difficult to track specific positions for budgeting.
Strategy 2: Position Title Includes Location or Department (Balanced)
Position title includes job title plus identifying information.
Example:
Job: Senior Software Engineer
Position Title: Senior Software Engineer – Product Engineering
Position ID: P-12847
When to use this: Organizations that need to distinguish between positions in different locations or departments.
Pros: Clear identification of specific positions. Still readable and makes sense to workers.
Cons: Position titles become long. Requires consistent naming convention enforcement.
Strategy 3: Position Title Uses Descriptive Unique Identifier (Most Control)
Position title is completely unique and descriptive.
Example:
Job: Senior Software Engineer
Position Title: Lead Engineer – Payment Processing Platform
Position ID: P-12847
When to use this: Organizations with highly specialized positions where each position has unique responsibilities.
Pros: Maximum clarity about what each specific position does. Useful for succession planning and workforce planning.
Cons: Most complex to manage. Position titles may not align with external market titles. Requires significant governance.
Display Configuration
After choosing your titling strategy, configure what displays in common views:
Worker Profile: Display job title, not position title.
Organizational Charts: Display job title, not position title (unless position title is strategy 3 with descriptive information).
Headcount Reports: Include both job title and position ID (for HR and Finance), but default display to job title.
Position Budget Reports: Display position title and position ID (for Finance).
Expected Impact
Standardized position titling reduces position-related confusion tickets by 50% to 70%.
One client implemented Strategy 2 (job title plus department) and saw position titling questions drop from 30 tickets per month to 8 tickets per month.
Fix 4: Build Position Forecasting and Planning Tools
Position Management only creates value when it enables better workforce planning. Most organizations implement positions but never build planning tools.
The Problem
Organizations implement Position Management to support headcount planning and budget forecasting. Then they discover Workday does not automatically provide planning tools just because you enabled positions.
Finance wants to see position budget versus actual spend. HR wants to forecast hiring needs based on vacant positions. Executives want to see position fill rates and time-to-fill by department.
Without these reports and dashboards, Position Management becomes a compliance requirement that creates work without providing value.
The Fix: Create Position Planning Reports and Dashboards
Build these five essential position management reports:
Report 1: Position Budget vs. Actual Headcount
Purpose: Finance needs to reconcile position budget with actual headcount and spending.
Key fields:
Supervisory Organization
Position ID
Position Title
Position Status (Filled, Vacant, Frozen)
Position Budget FTE
Worker Name (if filled)
Worker Annual Salary
Budget Variance (Position Budget minus Actual Salary)
Frequency: Monthly
Primary audience: Finance, HR Operations
Report 2: Vacant Position Analysis
Purpose: HR needs to prioritize filling critical vacant positions and identify positions that should be eliminated.
Key fields:
Position ID
Position Title
Supervisory Organization
Position Vacant Date
Days Vacant
Position Budget
Requisition Status (if open requisition exists)
Last Worker Name (who previously held the position)
Purpose: Department heads need to forecast hiring needs and budget requirements.
Key fields:
Supervisory Organization
Total Positions (current)
Filled Positions (current)
Vacant Approved Positions (ready to hire)
Vacant Unapproved Positions (not ready to hire)
Frozen/Eliminated Positions
Forecasted New Positions (from planning process)
Total Forecasted Headcount (12 months forward)
Frequency: Quarterly
Primary audience: Department Heads, Finance, HR Business Partners
Dashboards and Visualizations
Reports alone are not enough. Create executive dashboards using Workday’s discovery boards or external visualization tools:
Executive Workforce Dashboard:
Fill rate trend line
Vacant positions by department (bar chart)
Average days to fill by department
Headcount actual vs budget (variance analysis)
HR Operations Dashboard:
Positions vacant over 90 days
Positions with data quality issues
Requisitions without positions
Recent position changes log
Department Manager Dashboard:
My team’s positions (filled and vacant)
My vacant positions awaiting requisition
My team’s budget vs actual
Hiring pipeline status
Expected Impact
Position planning tools increase Position Management value perception by 80% or more.
One client’s CFO went from saying “Position Management just creates extra work” to “Position Management is our single source of truth for workforce budgeting” after implementing these five reports and two executive dashboards.
Fix 5: Integrate Position Management with Recruiting
The disconnect between Position Management and Recruiting creates operational friction that frustrates everyone.
The Problem
In many implementations, Position Management and Recruiting operate as separate processes:
HR creates positions
Weeks later, someone creates a requisition
The requisition is not clearly linked to the position
The position is filled through hiring, but the requisition status does not update
Nobody knows which vacant positions have active recruiting efforts
Managers ask: “Which of my vacant positions are we actively recruiting for?”
Recruiters ask: “Which positions do I need to create requisitions for?”
HR asks: “Why do we have 200 vacant positions but only 80 open requisitions?”
The Fix: Tightly Integrate Position and Requisition Workflows
Implement one of these two integration strategies:
Integration Strategy 1: Position-First Workflow
Positions must exist before requisitions can be created.
Process flow:
Manager or HR creates position (or reuses vacant position)
Position status = “Vacant”
Position availability = “Available”
Manager creates requisition linked to the position
Requisition approval process completes
Recruiting begins
Candidate hired into the position
Position status automatically updates to “Filled”
Requisition status automatically updates to “Filled”
Workday configuration:
Make position selection required on Create Requisition business process
Enable automatic position update on Hire
Create report showing positions available but without requisitions
When to use this: Organizations using Strict Position Control or Manager-Initiated strategies (Fix 1). Organizations with formal budgeting where positions represent budget allocation.
Requisitions can be created first, and positions are created automatically.
Process flow:
Manager creates requisition with job and organization
Requisition approval process completes
System automatically creates position linked to requisition
Position status = “Vacant”
Position availability = “Available”
Recruiting begins
Candidate hired into the position
Position status automatically updates to “Filled”
Requisition status automatically updates to “Filled”
Workday configuration:
Enable automatic position creation on Requisition approval
Configure position naming convention for auto-created positions
Enable automatic position update on Hire
When to use this: Organizations using Just-in-Time position creation strategy (Fix 1). High-growth companies where hiring speed is critical.
Position-Requisition Status Synchronization
Regardless of which integration strategy you choose, implement status synchronization:
When requisition is approved:
Linked position availability updates to “Available”
When requisition is on hold:
Linked position availability updates to “Unavailable”
When requisition is filled:
Linked position status updates to “Filled”
Linked position availability updates to “Unavailable”
When requisition is cancelled:
Linked position availability updates to “Unavailable” (if position should be frozen)
Or remains “Available” (if position should be filled through a new requisition)
Reporting Integration
Create reports that show the position-requisition relationship:
Vacant Positions Without Requisitions Report:
Shows positions approved for hiring but no active recruiting effort. HR Operations uses this to prompt managers to create requisitions or inactivate unnecessary positions.
Requisitions Without Positions Report:
Shows requisitions approved but not linked to positions. Finance uses this to identify potential budget disconnects.
Expected Impact
Position-recruiting integration reduces time-to-fill by 20% to 30% by eliminating administrative delays.
One client reduced their average time-to-fill from 67 days to 48 days primarily by eliminating the lag between position approval and requisition creation through requisition-first integration.
Fix 6: Solve the Job vs. Position Confusion
The most common Position Management complaint is: “Why do I need a position AND a job? They seem like the same thing.”
The Problem
Most people do not understand the difference between a job and a position in Workday.
The technical definitions do not help:
Workday documentation says:
Job: A generic role (like “Software Engineer”)
Position: A specific instance of a job (like “Software Engineer position in the Product team”)
That explanation makes sense to Workday consultants. It makes no sense to hiring managers.
The confusion creates practical problems:
Managers do not know whether to change the job or the position when responsibilities change.
HR does not know whether to create a new position or change the position’s job when a role evolves.
Finance does not understand why budget is allocated to positions but compensation is tied to jobs.
The Fix: Create Clear Guidance on Job vs. Position
Develop simple, practical guidance that non-HR people can understand:
Simple Explanation:
Job = What you do (your role, responsibilities, job level) Position = Where you do it (which team, which budget, which headcount slot)
Examples that clarify:
Scenario 1: Two people doing the same work in different locations
Sarah and David are both Senior Software Engineers (same job) on different teams (different positions).
Role type changes (individual contributor becomes manager)
When to change the position:
Worker transfers to a different team
Worker moves to a different location
Worker’s budget allocation changes to a different cost center
Organizational restructure moves the position to a different reporting line
When to create a new position:
Headcount increase approved (new budget allocation)
Organizational expansion (new team, new location)
Backfill approval for a departed worker (if using position reuse strategy)
When to change both job and position:
Promotion with transfer (worker promoted and moves to new team)
Role change with team change (individual contributor becomes manager in a different organization)
Training Materials
Create visual decision trees that managers can reference:
Decision Tree: Do I need to change the job, position, or both?
Start: Something about this worker’s role is changing.
Question 1: Are their responsibilities or job level changing?
Yes → Job change needed
No → Continue to Question 2
Question 2: Are they moving to a different team, location, or reporting line?
Yes → Position change needed
No → Continue to Question 3
Question 3: Is their budget allocation or cost center changing?
Yes → Position change needed
No → No job or position change needed (might be compensation change, org assignment change, or other worker data change)
Expected Impact
Clear job versus position guidance reduces manager confusion tickets by 60% to 80%.
One client created a 2-page visual guide on job versus position and included it in manager onboarding. Position-related manager questions dropped from 45 tickets per quarter to 12 tickets per quarter.
Fix 7: Implement Position Data Quality Audits
Even with all the fixes above, position data quality degrades over time without active monitoring.
The Problem
Position data quality problems accumulate silently:
Positions showing as filled when workers terminated months ago
Positions showing as vacant when workers are actively working
Duplicate positions for the same role and team
Position titles that do not match job titles
Positions with outdated budget allocations
Frozen positions that should be eliminated
Eliminated positions that should be reopened
Nobody notices until Finance runs a budget report that shows 200 vacant positions with budget allocation when HR knows they only have 80 approved openings.
The Fix: Quarterly Position Data Quality Audits
Implement a recurring quarterly audit process:
Audit Checkpoint 1: Position Status Accuracy
Data quality check: Position status matches actual worker assignment.
Query logic:
Positions with status “Filled” but no worker assigned
Positions with status “Vacant” but worker is assigned
Positions with worker assigned but status is “Frozen” or “Eliminated”
Resolution:
Update position status to match reality
Investigate why automation failed (Fix 2 may need adjustment)
Identify positions that require manual status management (job sharing, complex scenarios)
Audit Checkpoint 2: Position-to-Worker Ratio
Data quality check: Position-to-worker ratio remains within target range.
Query logic:
Total positions ÷ Total active workers
Position-to-worker ratio by department
Departments with ratios exceeding 2:1
Resolution:
Identify departments with position proliferation problems
Work with department heads to eliminate unnecessary positions
Review position creation governance (Fix 1) if ratio is increasing
Target: Position-to-worker ratio should remain between 1.1:1 and 1.5:1 depending on your strategy from Fix 1.
Audit Checkpoint 3: Vacant Position Aging
Data quality check: Vacant positions are actively managed or eliminated.
Query logic:
Positions vacant for more than 180 days
Positions vacant without open requisitions
Positions with status “Frozen” for more than 365 days
Resolution:
Contact department heads about positions vacant over 180 days
Eliminate positions with no hiring plan
Unfreeze positions approved for hiring or permanently eliminate positions no longer needed
Audit Checkpoint 4: Position Budget Alignment
Data quality check: Position budget matches organizational budget allocation.
Query logic:
Positions with no budget allocation
Positions with budget allocation but status “Eliminated”
Total position budget versus total organizational budget (should match)
Resolution:
Update position budget to match approved headcount budget
Reallocate budget from eliminated positions
Investigate discrepancies between position budget total and organizational budget
Audit Checkpoint 5: Position Naming Consistency
Data quality check: Position titles follow your established convention from Fix 3.
Query logic:
Positions with titles not matching job titles (if using Strategy 1 from Fix 3)
Positions with generic titles like “Position 1” or “New Position”
Positions with titles containing “copy” or “test”
Resolution:
Rename positions to match your titling convention
Train HR Operations on proper position creation
Consider implementing position name validation in business process configuration
Audit Reporting and Accountability
Create a quarterly Position Data Quality Scorecard:
Metrics to track:
Total positions
Position-to-worker ratio
Positions with status accuracy issues (count and percentage)
Positions vacant over 180 days (count and percentage)
Positions with budget alignment issues (count and percentage)
Position data quality score (percentage of positions with zero issues)
Accountability:
Assign HR Operations ownership for overall position data quality
Assign department heads ownership for their department’s positions
Report scorecard to CHRO and CFO quarterly
Set improvement targets (e.g., 95% data quality score)
Expected Impact
Quarterly audits maintain position data quality above 95% accuracy.
One client started with 72% position data quality (28% of positions had at least one data issue). After four quarterly audits with clear accountability and remediation, they reached 96% position data quality.
Implementation Roadmap: Rolling Out These 7 Fixes
You cannot implement all seven fixes simultaneously. Here is a realistic implementation roadmap:
Quarter 1: Foundation (Fixes 1, 2, 3)
Month 1: Fix 1 – Position Creation Governance
Audit current position-to-worker ratio
Choose position creation strategy
Document position creation rules
Configure business process enforcement
Month 2: Fix 2 – Position Lifecycle Automation
Enable automatic position updates on hire, termination, job change
Test automation with representative scenarios
Train HR Operations on new automation
Monitor for edge cases requiring manual intervention
Month 3: Fix 3 – Position Title Standardization
Choose position titling strategy
Rename existing positions to match strategy (may require batch update)
Configure display preferences
Train stakeholders on new conventions
Expected outcome: Position creation is controlled, position status reflects reality, position titles make sense to workers.
Quarter 2: Value Creation (Fixes 4, 5)
Month 4: Fix 4 – Position Planning Reports (Part 1)
Build Report 1 (Position Budget vs. Actual)
Build Report 2 (Vacant Position Analysis)
Train Finance and HR on new reports
Month 5: Fix 4 – Position Planning Reports (Part 2)
Build Report 3 (Position Fill Rate Dashboard)
Build Report 4 (Position Lifecycle Audit)
Build Report 5 (Position Forecasting)
Create executive dashboards
Month 6: Fix 5 – Recruiting Integration
Choose position-requisition integration strategy
Configure business processes for integration
Enable status synchronization
Build integration reports
Train recruiters and hiring managers
Expected outcome: Position Management delivers tangible value through planning insights and recruiting efficiency.
Quarter 3: Sustainability (Fixes 6, 7)
Month 7: Fix 6 – Job vs. Position Guidance
Develop simple explanations and decision rules
Create visual decision trees
Build training materials
Deliver training to managers
Month 8: Fix 7 – Data Quality Audits (Setup)
Build audit reports for all five checkpoints
Create Position Data Quality Scorecard
Assign accountability
Set baseline metrics and targets
Month 9: Fix 7 – Data Quality Audits (First Execution)
Run first quarterly audit
Remediate identified issues
Refine audit queries based on findings
Establish recurring quarterly schedule
Expected outcome: Stakeholders understand Position Management, data quality is maintained systematically.
Ongoing: Continuous Improvement
Quarterly activities:
Run position data quality audit
Review position-to-worker ratio trends
Assess position planning report usage
Gather stakeholder feedback
Refine processes based on learnings
Annual activities:
Comprehensive review of position creation governance
Position title convention review and updates
Position budget alignment with annual planning
Position Management training refresher for all stakeholders
Common Objections (And How to Respond)
When you propose these fixes, you will encounter objections. Here is how to respond:
Objection 1: “This is too much governance. We need flexibility.”
Response: Position Management without governance creates chaos, not flexibility. You currently have 6,000 positions for 2,500 workers. That is not flexibility; that is data that nobody trusts. These fixes give you disciplined flexibility with accountability.
Objection 2: “We don’t have time to implement all this.”
Response: You are already spending time managing position chaos. Last quarter, your HR Operations team spent 120 hours investigating position data quality issues and answering manager questions. These fixes automate 80% of that work. You are not adding work; you are replacing chaotic reactive work with structured proactive work.
Objection 3: “Our organization is too complex for simple rules.”
Response: Every organization thinks they are too complex for simple rules. Then they implement simple rules and discover 90% of scenarios fit the rules perfectly. You can handle the other 10% as exceptions. Start simple. Add complexity only when genuinely needed.
Objection 4: “Finance will never agree to change the budgeting process.”
Response: Finance wants position data they can trust more than they want to maintain the current process. Show your CFO the current position-to-worker ratio and ask if they trust position budget numbers. They will support process changes that improve data quality.
Objection 5: “We already tried to fix Position Management and it didn’t work.”
Response: Most Position Management fixes fail because they address symptoms instead of root causes. These seven fixes address root causes systematically. Also, previous failures often occurred because fixes were implemented without stakeholder buy-in. This roadmap builds buy-in through phased implementation with visible results.
Measuring Success: Key Metrics
Track these metrics to demonstrate improvement:
Operational Efficiency Metrics:
Position-related HR tickets per month (target: 75% reduction)
Time spent on position data quality remediation (target: 80% reduction)
Position creation to approval time (target: 50% reduction)
Data Quality Metrics:
Position-to-worker ratio (target: 1.1:1 to 1.5:1)
Position data quality score (target: 95%+)
Positions with status accuracy issues (target: less than 5%)
Business Value Metrics:
Finance confidence in position budget data (survey-based, target: 8/10 or higher)
Manager understanding of position concepts (survey-based, target: 7/10 or higher)
Position planning report usage (target: 80% of eligible users accessing monthly)
Recruiting Efficiency Metrics:
Average days to fill (target: 20-30% reduction)
Time from position approval to requisition creation (target: less than 5 days)
Percentage of vacant positions with active requisitions (target: 90%+)
Conclusion: From Most Hated to Strategic Asset
Position Management gets a bad reputation because most organizations implement it poorly.
They enable the feature, create positions, and expect value to appear automatically. When chaos ensues, they blame Position Management.
But Position Management is not the problem. Lack of governance, automation, and planning tools is the problem.
The seven fixes in this guide transform Position Management from a compliance burden into a strategic workforce planning capability:
Fix 1 controls position proliferation through clear creation rules.
Fix 2 ensures position data reflects reality through lifecycle automation.
Fix 3 eliminates title confusion through standardized conventions.
Fix 4 delivers business value through planning reports and dashboards.
Fix 5 improves recruiting efficiency through tight integration.
Fix 6 reduces stakeholder confusion through clear guidance.
Fix 7 maintains data quality through systematic audits.
Implement these fixes systematically over three quarters, and Position Management will go from your most complained-about feature to a trusted strategic asset that Finance, HR, and executives actually use.
Tell Me Your Experience
What is your biggest Position Management frustration? Which of these seven fixes would have the most impact in your organization?
Have you successfully implemented Position Management? What worked for you?
Share your experiences in the comments below. We learn best from each other’s real-world challenges.
Most talent teams blame tools, dashboards, or “system limitations” when their recruiting numbers do not look right. But in many Workday tenants, the real problem is simpler and more dangerous: bad recruiting data. Duplicate candidates, overwritten stages, inconsistent statuses, and missing fields quietly distort every pipeline metric and hiring report.
You might have a great implementation of Workday Recruiting. You might have strong pipelines and carefully designed business processes. Yet if your data is messy, your reports will mislead you, your funnel analysis will be wrong, and your leaders will lose trust in Workday’s numbers.
Bad data is the silent killer of Workday recruiting analytics—not because Workday is weak, but because messy processes and integrations feed it the wrong inputs.
How Bad Recruiting Data Shows Up in Workday
Bad data in Workday Recruiting rarely announces itself. It sneaks in through everyday activity:
The same candidate appears multiple times under slightly different names or emails.
A background check tool pushes a candidate back to an earlier stage, overwriting recruiter progress.
Required fields are left blank, so you cannot filter, segment, or report properly.
Candidate sources are inconsistent, making it impossible to trust attribution and ROI.
On the surface, Workday still “works.” Recruiters can move candidates through stages, hiring managers can review applicants, and offers can be created. The damage only becomes visible when you try to answer questions like:
How many candidates did we really screen last quarter?
What are our conversion rates from application to offer by channel?
Which job boards or campaigns deliver the best hires?
If your underlying data is inconsistent or duplicated, these answers will be wrong—or impossible to get with confidence.
Where the Bad Data Often Comes From
In many Workday tenants, bad recruiting data comes from a combination of three sources:
Integrations that overwrite progress Job boards, CRMs, and background check tools sometimes update candidate records without respecting the recruiter’s current stage. For example, an integration might reset a candidate’s pipeline step or change a status based on external events, wiping out important history.
Manual shortcuts and inconsistent practices Recruiters may skip fields, reuse old requisitions, or manually move candidates in ways that do not match the intended process. Under time pressure, they prioritise speed over clean data.
Lack of validation and controls in Workday Business processes may allow hires when key fields are missing or background checks are incomplete. Without validation steps, bad or incomplete data passes through the system unnoticed.
None of these issues are unique to Workday. They are design and governance problems that can be solved once they are acknowledged.
Strengthening Data Quality Inside Workday Recruiting
To protect your recruiting analytics, you need Workday itself to help you prevent and flag bad data. There are several ways to do this:
Use Workday validation and BP steps wisely Include validation steps in your recruiting business processes that prevent hires when key data is missing or when background checks are incomplete. Require certain fields (like overall background check status or final disposition reason) before closing a requisition or moving a candidate past critical stages.
Standardise candidate stages and statuses Make sure your candidate pipeline stages and statuses are clearly defined, with simple guidance for when to use each one. This reduces “creative” status usage that breaks funnel reporting.
Build audit and quality reports Create audit reports that highlight candidates with missing critical fields, inconsistent statuses, or duplicated records. Run them regularly and assign owners to clean up issues.
These steps help Workday become an active guardian of your data, not just a passive container.
Smarter Integrations: Stop Overwriting Good Data
Integrations with job boards, CRMs, and background check systems are often the biggest contributors to messy candidate data if they are not designed thoughtfully.
Key integration principles include:
Do not blindly overwrite stages Inbound feeds should respect the candidate’s current state in Workday. Use timestamps and “last modified” logic to avoid rolling candidates back to earlier stages just because a third-party system sends an update.
Write back meaningful statuses from external tools Background check or assessment tools should update specific fields and trigger the right steps in Workday, rather than loosely changing a candidate’s overall status without context.
Use stable IDs and keys across systems Align on unique identifiers (for example, combinations of email, Workday ID, and external system ID) to reduce duplicates and ensure records truly match across platforms.
When integrations follow these principles, they enhance your recruiting data rather than quietly corrupting it.
Tackling Duplicate Candidates
Duplicates are one of the most visible and frustrating recruiting data issues. They cause confusion in pipelines, double work for recruiters, and inaccurate metrics at every stage.
To reduce duplicates:
Encourage candidates to use consistent emails and profiles Clear messaging on career sites and portals can reduce accidental duplicates.
Use Workday’s duplication and merge capabilities where available Leverage tools and processes that help you identify and merge duplicate candidates or prospects, keeping a single, clean record.
Align external systems with Workday IDs Feed Workday-generated candidate or worker IDs back into your CRM, talent community, and assessment tools so future interactions map to the right record.
Treating duplicate management as a continuous process, not a one-off cleanup, is key to keeping recruiting data usable.
Turning Bad Data into a Fixable Problem
The good news: messy Workday recruiting data is usually fixable with structured effort. A practical approach might include:
Baseline your data quality Use audit reports and analytics overlays to identify where your recruiting data is incomplete, inconsistent, or duplicated.
Prioritise the most important fields and metrics Focus first on the fields that drive your core metrics: time to hire, source of hire, conversion rates by stage, diversity metrics, and quality-of-hire indicators.
Clean historical data in waves Start with high-impact roles, regions, or time periods. Correct the worst issues, then move forward with better processes to prevent them from returning.
Educate recruiters and hiring teams Show them how their actions in Workday affect data quality and the downstream metrics leadership relies on. When they see the connection, they are far more likely to follow good practices.
Clean Recruiting Data = Better Hiring Decisions
Ultimately, the goal is not to have “perfect” data for its own sake. The goal is to make better decisions about where to source, how to move candidates through the pipeline, and how to allocate recruiting resources.
With clean Workday recruiting data, you can:
Trust your pipeline and funnel metrics.
See which channels, campaigns, and recruiters perform best.
Track diversity and quality-of-hire in meaningful ways.
Give leaders confidence that Workday reports reflect reality.
Bad data may be the silent killer of Workday recruiting analytics—but once you see it clearly, it becomes a problem you can systematically solve.
Designing your Workday HCM foundation is one of the most important decisions you will ever make in a tenant. Once you go live with supervisory orgs, positions, job profiles and cost centers, reversing bad design is painful, political and expensive. A clean foundation, on the other hand, makes every downstream process easier: hiring, transfers, security, reporting, integrations and even future modules like Time Tracking or Learning.
Start with a clear operating model
Before touching configuration, clarify how the business actually operates. In Workday terms, this means understanding who manages whom, how cost is tracked, how HR wants to report headcount and how finance wants to see labor cost. You will use those answers to decide the shape of supervisory orgs, whether you go position or job management, and which worktags (like cost centers) become mandatory.
Workday supervisory organizations represent management relationships and operational structure, not legal entities. Companies and entities represent legal and accounting structure, while cost centers and other worktags represent how cost is tracked and reported. Separating these concepts early prevents you from overloading supervisory orgs with finance responsibilities they were never designed to carry.
Designing supervisory orgs that do not collapse
A common mistake is to copy the HR org chart directly into Workday as dozens or hundreds of tiny supervisory orgs. That usually creates reporting complexity, security noise and constant maintenance whenever someone changes manager. A better pattern is to design supervisory orgs around stable management units: departments, teams or business units that change less frequently than individual manager assignments.
When designing supervisory orgs, ask:
Can this org survive manager changes without needing to be restructured every week?
Does this level of granularity help reporting and security, or just create clutter?
Is there a clear business purpose for this org beyond “we have a manager”?
Aim for a hierarchy that can support real-world approvals, headcount reporting and security boundaries, but is still simple enough that new HRIS analysts can navigate it confidently.
Positions vs jobs: choose consciously
Workday supports position management and job management, and the choice is foundational. Position management is best when you need rigorous headcount control, budget-to-position matching and clear tracking of vacancies. Job management is lighter and works well in fluid environments where individual seats are less important than overall staffing levels.
For position management, design patterns include:
Use positions anywhere headcount is tightly controlled, such as regulated functions or centralized operations.
Give positions meaningful, consistent titles that align with job profiles and not personal names.
Avoid creating “temporary” positions for one-off cases; these often become long-term clutter.
For job management, ensure you still have clear job profiles with compensation grades and worktags so that reporting and security do not depend on free-text job titles.
Job profiles as your talent backbone
Job profiles are the backbone of how Workday sees roles, qualifications, compensation and, in some tenants, learning and talent. Poorly designed job profiles lead to reporting chaos: dozens of variations for the same role, unclear grade mappings and confusing job histories for workers.
Strong job profile design usually includes:
A consistent naming pattern (e.g., “Analyst, HR Operations” instead of many variations).
Clear classification into job families and job profiles that align with how HR and talent teams think about roles.
Linkage to compensation grades and grade profiles so that pay ranges are consistent across markets.
When job profiles are clean, you can deploy performance, learning and career frameworks more easily, because everything hangs off a small number of well-maintained roles rather than hundreds of one-off titles.
Cost centers and worktags: think like finance
Cost centers and other worktags are how finance sees the world in Workday Financials, and even in HCM-only tenants they drive a lot of reporting. HR often underestimates how important it is to design cost centers that match finance’s management reporting rather than HR’s internal labels.
Good practices include:
Keep cost centers relatively stable and align them to budget owners or P&L responsibility.
Avoid duplicating cost centers just to represent small team differences; use supervisory orgs, locations or custom organizations for that.
Ensure default cost centers are set correctly at the position, worker or org level so payroll and financial postings are accurate without manual fixes.
When cost centers and worktags are clean, you can produce reliable reports like headcount by cost center, labor cost by business unit and budget versus actual staff cost with minimal reconciliation.
Putting it all together in real processes
The real test of your HCM foundation is not whether it looks neat in the configuration pages, but whether everyday processes run smoothly. When HR creates a new position, it should be obvious which supervisory org to use, which job profile to select and which cost center should default. When a manager initiates a transfer, the path through supervisory orgs and cost centers should be clear, and reporting should show the move without gaps or duplicates.
Think through core processes end to end:
Hire to retire: are orgs, positions and cost centers stable across promotions, transfers and international moves?
Security: can you grant HR partners and managers access based on supervisory orgs and cost centers without dozens of exceptions?
Reporting: can HR and finance quickly answer questions about headcount, vacancies and cost without manual spreadsheets?
When these scenarios work, you know the foundation is serving the business rather than the other way around.
Design for the next three years, not three months
Finally, design your Workday HCM foundation with a three-year horizon. Most organizations will go through reorganizations, new business lines and possibly new geographies in that time. Build supervisory org structures, position rules, job profiles and cost center hierarchies that can absorb that change without needing a full rebuild.
Document your design principles and decisions, not just your configuration. Future HRIS analysts, Workday consultants and auditors should be able to understand why the tenant looks the way it does. That documentation is part of the foundation, just as much as the orgs and positions themselves.
A strong Workday HCM foundation does not happen by accident. It is the result of deliberate choices about how to represent your organization, control headcount, classify roles and track cost. When you get those basics right, everything from security to payroll to analytics becomes simpler, more reliable and much easier to scale.
It was 9:47 AM on a Monday morning when my phone rang.
The Finance Director’s voice was tense: “The bi-weekly payroll reconciliation report keeps timing out. We need this to close payroll in three hours. Can you fix it?”
I logged into their Workday tenant and opened the report. What I saw made the problem immediately clear.
The report had 47 calculated fields, 8 related business objects, and no filters on the primary data source. The sorting configuration included 6 different fields, with two of them being calculated fields.
This report was pulling 15,000 workers, evaluating 47 calculations for each one, then sorting the entire result set multiple times. It had zero chance of completing before Workday’s 5-minute execution timeout limit.
But here is what surprised me most: This report had worked perfectly for 18 months.
What changed?
The organization had grown from 12,000 to 15,000 workers. That 25% headcount increase pushed the report just past its performance threshold, and suddenly a critical business process was broken.
I applied my 7-step diagnostic framework, identified four specific issues, made the corrections, and reduced execution time from 5 minutes 15 seconds (timeout) to 1 minute 50 seconds. A 65% performance improvement in 12 minutes of work.
Payroll closed on time that day.
Since then, I have used this same framework to fix timeout issues across more than 100 Workday tenants. These are not generic “best practices” you can find in Workday documentation. This is the exact sequence of diagnostic checks that identifies the root cause of 90% of report performance problems, usually within 15 minutes.
This guide will walk you through each step with specific instructions, real examples, and measurable performance impacts.
Understanding Workday Report Timeouts
Before we dive into diagnostics, you need to understand what actually causes report timeouts and why they often seem to appear randomly.
The 5-Minute Execution Limit
Workday enforces a 5-minute maximum execution time for reports.
When your report exceeds this limit, Workday terminates the process and returns an error message: “Report execution exceeded the maximum allowed time.”
This hard limit exists to protect tenant performance. Without it, a single poorly optimized report could consume excessive resources and impact all users in your tenant.
Why Timeouts Seem Random
Most timeout issues share these characteristics:
They appear suddenly. A report that worked reliably for months or even years starts failing consistently.
They are inconsistent. Sometimes the report completes successfully. Other times it times out. The unpredictability creates operational uncertainty.
They impact critical processes. Timeouts rarely affect test reports or ad-hoc analyses. They hit payroll processing, month-end financial close, compliance reporting, and executive dashboards.
They create operational urgency. Business processes stall while teams wait for that one critical report to complete.
Here is what actually happens beneath the surface:
Your report was always slow. It just was not slow enough to exceed the 5-minute timeout threshold. Then something small changed in your environment:
Headcount increased by 15% to 20%
Someone added three more calculated fields to capture additional data
An organizational restructure added 500 new positions to your hierarchy
A new benefit plan created additional multi-instance data relationships
A Workday release changed how certain data sources are indexed
Any of these small changes can push your report’s execution time from 4 minutes 30 seconds (acceptable) to 5 minutes 15 seconds (timeout).
The report configuration did not fundamentally break. It simply crossed a performance threshold.
The Compounding Problem
Report performance does not degrade linearly. It degrades exponentially.
When you have 10,000 workers and 20 calculated fields, you are performing 200,000 calculations.
When you grow to 15,000 workers (a 50% increase), you are now performing 300,000 calculations (a 50% increase in processing).
But if you also added 5 more calculated fields during that growth period, you are now performing 375,000 calculations. That is an 88% increase in processing load from seemingly small changes.
This exponential nature is why reports that worked fine suddenly fail catastrophically.
The 7-Step Diagnostic Framework
When a report times out, follow these steps in exact order. Each step takes between 2 and 5 minutes and targets specific root causes.
The sequence matters. Earlier steps identify high-impact issues that are quick to fix. Later steps address more complex optimization opportunities.
Step 1: Check the Data Source (2 minutes)
This is the single most impactful diagnostic check you can perform.
The Problem with Non-Indexed Data Sources
Non-indexed data sources are the number one cause of Workday report timeouts.
Understanding the difference between indexed and non-indexed data sources is critical:
Indexed data sources work like a book’s index or a dictionary with alphabetical ordering. When you search for specific data, Workday can jump directly to the relevant records without scanning the entire dataset.
Non-indexed data sources store data without this organizational structure. Workday must scan through every single record sequentially to find the data you need.
This performance difference is negligible when you have 500 records. It becomes catastrophic when you have 50,000 records.
As your organization grows and your data volume increases, non-indexed sources get progressively slower until they eventually exceed the 5-minute timeout limit.
How to Check Data Source Indexing
Follow these steps:
Open the report in Report Writer
Click on the Data Source at the top of your report definition
Look for the “Indexed” indicator in the data source properties
If it displays “Not Indexed” or shows no indexing indicator at all, you have identified a critical performance issue
Common Non-Indexed Data Sources
Be particularly careful with these commonly used non-indexed data sources:
All Workers: This data source is not indexed. Use “All Active Workers” instead, which is indexed and typically eliminates 30% to 50% of your worker population immediately (all terminated workers).
All Worker Job History: Not indexed. Use date-filtered versions like “Worker Job History – Current” or add aggressive effective date filters.
All Benefit Elections: Not indexed. Use “Current Benefit Elections” which is indexed and contains only active elections.
Custom data sources without explicit indexing: Any custom data source created without indexing configuration will not be indexed by default.
The Fix
Replace your non-indexed data source with an indexed equivalent.
Before: Data Source equals “All Workers”
After: Data Source equals “All Active Workers”
This single change eliminated 7,500 terminated worker records from processing in one of my client implementations.
Expected Performance Impact
Switching from a non-indexed to an indexed data source can reduce report execution time by 50% to 80%.
In one real example, a compensation analysis report dropped from 4 minutes 45 seconds to 1 minute 20 seconds simply by changing from “All Workers” to “All Active Workers.”
Pro Tip for Non-Indexed Requirements
Sometimes you genuinely need data that only exists in non-indexed sources.
In these cases, add aggressive filters immediately after selecting the data source to reduce your dataset before any other operations occur.
For example, if you must use “All Worker Job History,” immediately filter by:
Effective Date is greater than or equal to [Current Year Start Date]
Active Status equals Active
This reduces your dataset from potentially 10 years of history across 25,000 workers to just current-year active records before you perform any calculations or joins.
Step 2: Audit Your Filter Order (3 minutes)
Filter ordering is one of the most commonly overlooked performance optimization opportunities in Workday reporting.
Why Filter Order Matters
Filters are not evaluated simultaneously. Workday processes them sequentially from top to bottom.
Each filter operates on the result set produced by the previous filter. This means filter order directly determines how much data Workday must process through your entire report logic.
If your first filter only eliminates 100 records, and your second filter would eliminate 5,000 records, you are forcing Workday to process 4,900 unnecessary records through all subsequent filters, calculations, and operations.
How to Audit Filter Order
Follow these steps:
Open the report in Report Writer
Navigate to the Filters section
Review the order of filters from top to bottom
For each filter, estimate approximately how many records it would eliminate from your dataset
You do not need exact numbers. Rough estimates are sufficient to identify ordering problems.
The Golden Rule of Filter Ordering
Put the most restrictive filters first.
“Most restrictive” means the filter that eliminates the greatest number of records from your dataset.
Real Example of Wrong Filter Order
I encountered this filter configuration in a headcount report that was timing out:
Worker not in selection list [John Smith] (eliminates 1 record)
Worker not in selection list [Jane Doe] (eliminates 1 record)
Location equals Chicago (eliminates approximately 500 records)
Department equals Sales (eliminates approximately 2,000 records)
Active Status equals Active (eliminates approximately 5,000 records – all terminated workers)
With this ordering, Workday processes:
15,000 initial records
14,999 records after filter 1
14,998 records after filter 2
14,498 records after filter 3
12,498 records after filter 4
7,498 final records after filter 5
Workday processed over 59,000 filter evaluations to arrive at 7,498 records.
The Optimized Filter Order
Here is the corrected filter order:
Active Status equals Active (eliminates 5,000 records immediately)
Department equals Sales (eliminates 2,000 records)
Location equals Chicago (eliminates 500 records)
Worker not in selection list [John Smith] (eliminates 1 record)
Worker not in selection list [Jane Doe] (eliminates 1 record)
With this ordering, Workday processes:
15,000 initial records
10,000 records after filter 1
8,000 records after filter 2
7,500 records after filter 3
7,499 records after filter 4
7,498 final records after filter 5
Workday processed only 38,000 filter evaluations to arrive at the same 7,498 records.
That is a 35% reduction in processing load just from reordering filters.
Common High-Impact Filters to Position First
Always position these filters near the top of your filter list:
Active Status equals Active: This typically eliminates 30% to 50% of your worker population (all terminated workers and historical records).
Effective Date filters: Filters like “Effective Date is greater than or equal to [Start of Current Year]” eliminate all historical data outside your analysis period.
Organization filters: Filters that restrict to specific high-level organizations (like “Company equals US Operations”) eliminate entire divisions or geographies.
Worker Type filters: Filters distinguishing between Full-time, Contingent, Terminated, or other worker types often eliminate large populations.
Expected Performance Impact
Optimizing filter order typically reduces execution time by 30% to 60%.
The exact improvement depends on your data distribution and how poorly ordered your original filters were.
Step 3: Count Your Calculated Fields (2 minutes)
Calculated fields are powerful tools for deriving data that does not exist in standard Workday fields. They are also the most common source of report performance problems.
The Calculated Field Processing Cost
Every calculated field adds processing overhead to your report.
For each record returned in your report, Workday must evaluate every calculated field formula you have defined.
The math is straightforward:
10 records × 5 calculated fields = 50 calculations
1,000 records × 5 calculated fields = 5,000 calculations
10,000 records × 47 calculated fields = 470,000 calculations
This is why reports with many calculated fields perform acceptably in sandbox environments with 100 test workers but timeout in production with 15,000 workers.
The Multi-Level Calculated Field Problem
The performance problem multiplies when you create calculated fields that reference other calculated fields (multi-level calculations).
Workday must evaluate the first calculated field, store the result, then evaluate the second calculated field using that stored result. This creates a dependency chain that dramatically increases processing time.
How to Audit Calculated Fields
Follow these steps:
Open the report in Report Writer
Navigate to the Columns section
Count how many columns display the calculator icon (indicating calculated fields)
Click into each calculated field and check if the formula references other calculated fields
Calculated Field Count Benchmarks
Use these benchmarks to assess your calculated field usage:
Less than 10 calculated fields: This is generally acceptable for most reports.
10 to 20 calculated fields: Watch performance carefully, especially if your report returns more than 1,000 records.
20 to 30 calculated fields: High risk of timeout when returning 5,000 or more records.
More than 30 calculated fields: Almost guaranteed timeout with large datasets. Reports with 40 or more calculated fields rarely complete successfully in production environments with meaningful data volumes.
The Fix: Four Optimization Strategies
Strategy 1: Remove Unnecessary Calculated Fields
Ask your report’s business owner this critical question: “Which fields do you actually use to make decisions?”
In my experience, users typically use 10 to 15 fields from any report, even when the report contains 50 or more fields.
Remove calculated fields that are not actively used for analysis or decision-making.
Strategy 2: Replace Calculated Fields with Sub-Filters
If you created a calculated field solely for filtering purposes (not to display values in your report output), replace it with a sub-filter.
Example transformation:
Before: Calculated field “Has_Spouse_Dependent” that evaluates to Yes or No, then filter shows only “Yes” values.
After: Sub-filter on Related Business Object equals Dependents, Relationship Type equals Spouse.
The sub-filter achieves the same result without calculating a value for every worker in your dataset.
Strategy 3: Use Related Objects Instead of Calculations
Many calculated fields use complex Lookup Related Value functions to retrieve data from related business objects.
Check if you can add the field directly from the related object instead of calculating it.
Example transformation:
Before: Calculated field using Lookup Related Value to retrieve Manager Name from the worker’s supervisory organization.
After: Add field directly from Worker, Management Chain, Manager, Worker Name.
Strategy 4: Search for Workday-Delivered Fields
Before creating any calculated field, search thoroughly for existing Workday-delivered fields that might already provide the data you need.
Workday includes hundreds of pre-calculated fields for common business scenarios:
Tenure calculations (Years of Service, Months of Service)
Age calculations (Current Age, Age at Hire)
Time-based calculations (Months Since Last Promotion, Days Since Last Performance Review)
Status indicators (Is Manager, Is Terminated, Is On Leave)
Using Workday-delivered fields eliminates calculation overhead entirely while ensuring data consistency across your organization.
Expected Performance Impact
Each calculated field you remove typically reduces execution time by 5% to 15%.
If you remove 10 unnecessary calculated fields from a 30-field report, you can expect 50% or greater performance improvement.
Step 4: Review Related Business Objects (3 minutes)
Related business objects allow you to pull data from objects connected to your primary business object. Each additional related object creates database joins that increase processing complexity.
The Related Object Performance Cost
Every related business object you add creates additional database joins.
More joins equal more data retrieval operations, which equals longer execution time.
The relationship is not linear. Adding your third related object takes more processing power than adding your first related object because Workday must now join data across multiple relationships simultaneously.
The Cartesian Product Disaster
The worst-case scenario with related business objects is creating a Cartesian product.
This occurs when you join multi-instance related objects without proper instance filtering. The result is exponential row multiplication.
Here is a real example:
You start with 100 workers in your report. Each worker has:
5 position records (because they have held multiple positions over time)
3 compensation change records in your report period
Benefit Elections: Workers can be enrolled in multiple benefit plans (medical, dental, vision, life insurance, retirement).
Performance Ratings: Workers have ratings from multiple review cycles.
Learning Assignments: Workers have multiple training courses assigned and completed.
The Fix: Three Instance Management Strategies
Strategy 1: Limit to Single Instance
Use Workday’s instance filtering options to retrieve only the specific instance you need:
Compensation as of Effective Date: Retrieves only the compensation record effective on your report’s effective date, not the entire compensation history.
Position Most Recent: Retrieves only the most recent position, not all historical positions.
Performance Rating Current Review Period Only: Retrieves only ratings from the current review cycle, not all historical reviews.
Strategy 2: Remove Unnecessary Related Objects
Verify whether you truly need the related object or if you can source the data from your primary business object.
Real example I encountered:
A report builder added the “Position” related object solely to retrieve the worker’s location. However, Location also exists as a field directly on the Worker object (Current Location).
By removing the Position related object and using Worker Current Location instead, we eliminated an entire join operation.
Strategy 3: Split Into Multiple Reports
If you genuinely need multi-instance data across multiple dimensions, consider splitting into separate focused reports:
Report 1: Workers with compensation history over time
Report 2: Workers with position history over time
Report 3: Workers with performance rating history over time
Export each report and join the data in Excel, Tableau, or your analytics platform where you have more control over the joining logic.
This approach gives you the multi-dimensional analysis you need without forcing Workday to perform complex multi-instance joins that create Cartesian products.
Expected Performance Impact
Removing unnecessary related objects can reduce execution time by 40% to 70%.
In one client engagement, we reduced a benefits analysis report from 6 minutes (timeout) to 1 minute 45 seconds simply by changing “All Benefit Elections” (multi-instance, all history) to “Current Benefit Elections” (single instance per plan, active elections only).
Step 5: Examine Your Sorting Strategy (2 minutes)
Sorting is one of the most computationally expensive operations in report execution.
The Computational Cost of Sorting
When you sort data, the system must compare every record against every other record to determine the correct order.
The number of comparisons grows exponentially with your dataset size:
100 records require approximately 10,000 comparisons
1,000 records require approximately 1,000,000 comparisons
10,000 records require approximately 100,000,000 comparisons
Sorting on calculated fields is exponentially worse because Workday must first evaluate the calculated field formula for every record, then perform all the comparison operations on those calculated results.
How to Audit Sorting Configuration
Follow these steps:
Open the report in Report Writer
Navigate to the Sorting section
Count how many sort conditions you have configured
Identify whether any sort conditions use calculated fields
The Fix: Four Sorting Optimization Strategies
Strategy 1: Reduce Sort Conditions
Ask yourself honestly: Do you really need to sort on 6 different fields?
In my experience, most users care about only 1 to 2 primary sort orders. Additional sort conditions add computational cost without adding business value.
Common example: A headcount report sorted by Department, Location, Job Profile, Worker Name, Employee ID, and Hire Date.
Most users only care about Department and Worker Name. The other four sort conditions add processing overhead without meaningful benefit.
Strategy 2: Never Sort on Calculated Fields
This is a hard rule that should rarely be broken.
If you must sort on derived data, follow this process:
Remove the sort from your Workday report configuration
Export the report without sorting applied
Perform the sort in Excel, Tableau, or your analytics tool after export
Your external tools are optimized for sorting and can handle it much faster than Workday report execution.
Strategy 3: Sort on Simple Field Types
Sorting on simple text or numeric fields is significantly faster than sorting on complex objects or lookup relationships.
Cost Center (may require organization hierarchy traversal)
When possible, sort on codes or IDs rather than descriptions or hierarchical references.
Strategy 4: Remove Sorting for Large Exports
If you are exporting data to Excel for further analysis, skip sorting entirely in Workday.
Export the raw data as quickly as possible, then sort in Excel where you have much greater control and performance.
This is particularly important for reports returning 5,000 or more records.
Expected Performance Impact
Removing unnecessary sorting can reduce execution time by 20% to 40%.
In one real example, a compensation planning report dropped from 3 minutes 20 seconds to 2 minutes 10 seconds simply by reducing from 5 sort conditions to 2 sort conditions and eliminating sorting on a calculated “Total Compensation” field.
Step 6: Check Your Field Count (2 minutes)
Every field you include in your report increases data retrieval time and security validation processing.
The Cumulative Cost of Field Count
For each field in your report, Workday must perform multiple operations:
Retrieve the data from the appropriate data source
Check security permissions to verify the user running the report has access to this field
Format the field according to display settings
Return the field in the result set
More fields equal more operations, which equals longer execution time.
Field Count Benchmarks
Use these benchmarks to assess whether your field count is creating performance problems:
Less than 25 fields: This is optimal for most reports.
25 to 50 fields: Monitor performance. Reports in this range can perform acceptably if other optimization factors are well-managed.
50 to 75 fields: High risk category, especially when combined with calculated fields. Reports in this range frequently timeout with large datasets.
75 to 100 fields: Almost guaranteed timeout when returning more than 1,000 records.
More than 100 fields: This is the maximum limit for Composite Reports. Reports approaching this limit rarely perform acceptably in production environments.
How to Check Field Count
Follow these steps:
Open the report in Report Writer
Navigate to the Columns section
Count total fields (regular fields plus calculated fields)
The Fix: Create Focused Report Variants
Here is the critical question to ask your report’s business owner:
“Which fields do you actually use from this report?”
Most users only use 10 to 20 fields regularly, even when reports contain 50 or more fields.
Reports accumulate fields over time as different stakeholders request additions. Six months later, you have a 75-field report that takes 4 minutes to execute, but most users only look at 15 fields.
Instead of one bloated report, create three focused variants:
Basic Headcount Report (15 fields):
Worker Name
Employee ID
Department
Location
Position
Manager
Hire Date
Worker Type
Active Status
Cost Center
Used for: Quick headcount checks, organizational charts, directory lookups.
Compensation Analysis Report (20 fields):
Worker Name
Employee ID
Job Profile
Base Salary
Bonus Target
Total Cash Compensation
Last Merit Increase Date
Last Merit Increase Percentage
Compa-Ratio
Market Reference Point
Used for: Compensation planning, market analysis, equity reviews.
Full Detail Report (50 fields): All fields from both reports above plus additional fields for special analyses.
Used for: Quarterly deep dives, annual planning, audit requests.
This approach gives users fast access to the fields they use daily, while maintaining a comprehensive report for periodic detailed analysis.
Expected Performance Impact
Reducing from 75 fields to 25 fields can reduce execution time by 30% to 50%.
Step 7: Review Prompts and Their Defaults (3 minutes)
Prompts make reports flexible by allowing users to specify parameters at runtime. They also create opportunities for users to accidentally trigger massive data pulls that timeout.
The Dangerous Default Problem
The risk occurs when prompt defaults allow users to pull entire datasets without realizing it.
If your prompt defaults to “All Workers” or “All Time,” users who click OK without carefully reviewing their selections will trigger full dataset queries that timeout.
How to Audit Prompt Configuration
Follow these steps:
Open the report in Report Writer
Navigate to the Prompts section
Review each prompt’s default value
Mentally simulate what happens if a user clicks OK without changing any prompt values
Common Dangerous Prompt Configurations
Date Range Prompts with No Default
Configuration: Start Date and End Date prompts with no default values.
Risk: User does not enter dates. Report pulls all historical data spanning 10 or more years. Timeout.
Organization Prompts Defaulting to Top Level
Configuration: Organization prompt that defaults to the top-level supervisory organization.
Risk: User does not select a specific department. Report pulls entire company (15,000 workers). Timeout.
Worker Prompts with No Required Selection
Configuration: Worker prompt that is optional with no default.
Risk: User does not select specific workers. Report pulls everyone. Timeout.
The Fix: Four Prompt Safety Strategies
Strategy 1: Set Safe Defaults
Configure your prompts with sensible defaults that limit data volume:
Date Range defaults:
Start Date: First day of current year
End Date: Current date
Or: Start Date: 90 days ago, End Date: Current date
Organization defaults:
Default to the user’s own supervisory organization (not top level)
Or: Require user to make an explicit selection
Worker defaults:
Default to workers in the user’s supervisory organization
Or: Require user to make an explicit selection
Strategy 2: Make Critical Prompts Required
For prompts that significantly impact data volume, make them required so users must make an explicit selection.
Users cannot click OK without entering values, forcing them to think about their data scope.
Strategy 3: Add Prompt Validation and Warnings
Implement validation logic that warns users about potentially dangerous selections.
Example: If the user selects a date range exceeding 365 days, display a warning message:
“Large date ranges may cause report timeout. We recommend limiting your analysis to 90 days or less. Are you sure you want to continue?”
Strategy 4: Create Bounded Report Variants
Instead of one highly flexible report with dangerous prompts, create multiple pre-filtered variants with fixed parameters:
Monthly Turnover Report: Always pulls last month’s data. No date prompt.
Quarterly Compensation Report: Always pulls last quarter’s data. No date prompt.
Annual Review Report: Always pulls current review period. No date prompt.
Department Headcount Report: Prompts for department selection (required). No option to pull entire company.
This approach eliminates the flexibility that creates timeout risk while still providing the specific analyses your business users need.
Expected Performance Impact
Safe prompt defaults can prevent 50% or more of timeout incidents.
In one client environment, we discovered that 60% of report timeout incidents were caused by users clicking OK on date range prompts without entering specific dates, causing the report to pull 8 years of historical data.
After implementing 90-day default date ranges, timeout incidents dropped by 65%.
The Complete Diagnostic Checklist
Print this checklist and keep it accessible for the next time a report times out.
Report Timeout Diagnostic Checklist
Step 1: Data Source (2 minutes)
Is the data source indexed?
Can I replace it with an indexed alternative?
If non-indexed is required, have I added aggressive filters immediately after data source selection?
Step 2: Filter Order (3 minutes)
Are filters ordered from most to least restrictive?
Is “Active equals Yes” or effective date filtering positioned near the top?
Have I eliminated filters that only exclude 1 to 5 records from the top of the list?
Step 3: Calculated Fields (2 minutes)
Do I have more than 20 calculated fields?
Are any calculated fields referencing other calculated fields (multi-level)?
Can any calculated fields be replaced with sub-filters?
Can any calculated fields be replaced with related object fields?
Have I searched for Workday-delivered fields before building custom calculations?
Step 4: Related Business Objects (3 minutes)
How many related objects am I joining? (Count them)
Are any multi-instance without proper instance filtering?
Am I creating a Cartesian product by joining multiple multi-instance objects?
Can I get the same data from my primary business object without the join?
Step 5: Sorting (2 minutes)
Am I sorting on more than 2 fields?
Am I sorting on any calculated fields?
Can I remove sorting and sort in Excel after export instead?
Am I sorting on complex objects or lookups when simple fields would work?
Step 6: Field Count (2 minutes)
Do I have more than 50 fields in my report?
Does my business owner actually use all these fields?
Can I create focused variants (Basic, Detailed, Comprehensive) instead of one large report?
Step 7: Prompts (3 minutes)
What happens if a user clicks OK without changing any default prompt values?
Are my default date ranges safe (90 days or less)?
Should I make critical prompts required instead of optional?
Should I create bounded variants instead of flexible prompts?
Result
In my experience, 90% of timeout issues are resolved by fixing 1 to 3 items on this checklist.
Real-World Case Study: The Monday Morning Payroll Crisis
Let me walk you through the complete diagnostic process using the real payroll report that opened this guide.
The Initial Problem
Finance Director: “The bi-weekly payroll reconciliation report keeps timing out. We need this to close payroll in 3 hours.”
Report configuration:
Data Source: All Workers
47 calculated fields
8 related business objects
6 sort conditions (including 2 calculated fields)
78 total fields
No effective filters on primary data source
Execution time: 5 minutes 15 seconds (timeout)
The Diagnostic Process
I worked through the 7-step checklist and found four critical issues:
Issue 1: Non-Indexed Data Source
Finding: Data Source was set to “All Workers” (not indexed).
Fix: Changed to “All Active Workers” (indexed).
Impact: Immediately eliminated 7,500 terminated worker records from processing. Reduced execution time by approximately 40%.
Issue 2: Excessive Calculated Fields
Finding: Report contained 47 calculated fields. I asked the Finance Director which fields she actually used. She identified 15 critical fields. The other 32 were added over 18 months by various stakeholders but were never used in payroll close processes.
Fix: Removed 15 unused calculated fields after confirming with stakeholders they were not critical. Kept 32 calculated fields that were actively used.
Impact: Reduced execution time by approximately 25%.
Issue 3: Sorting on Calculated Fields
Finding: Report was sorting on 6 fields, including “Total Compensation” and “Hours YTD” (both calculated fields).
Fix: Reduced to 2 sort conditions (Department and Worker Name, both simple fields). Removed calculated field sorting entirely. Finance Director confirmed she always re-sorted in Excel anyway based on her specific analysis needs.
Impact: Reduced execution time by approximately 20%.
Issue 4: Wrong Filter Order
Finding: Filter list started with “Worker not in selection list [Contractors]” which only excluded 200 records. The filter “Active equals Yes” was positioned as the fourth filter.
Fix: Moved “Active equals Yes” to the top position. Moved contractor exclusion to the bottom.
Impact: Reduced execution time by approximately 10%.
The Results
Original configuration:
Execution time: 5 minutes 15 seconds (timeout)
Records processed: 15,000 workers
Calculated fields: 47
Sort conditions: 6
Optimized configuration:
Execution time: 1 minute 50 seconds
Records processed: 7,300 active workers (terminated workers eliminated by indexed data source)
Calculated fields: 32
Sort conditions: 2
Total improvement: 65% reduction in execution time
Time invested in optimization: 12 minutes
Payroll closed on time that Monday.
When These 7 Steps Do Not Fix the Problem
If you have systematically worked through all 7 diagnostic steps and your report still times out, you are in the 10% of cases with deeper structural issues.
Tenant-Wide Performance Issues
Sometimes the problem is not your specific report. It is your tenant’s overall performance state.
Symptoms:
Multiple reports timing out simultaneously
Reports that normally complete successfully are now timing out intermittently
Tenant-wide resource constraints during peak usage periods
Workday infrastructure incidents affecting your data center
Action: Contact Workday Support with specific details about timing patterns and affected reports.
Data Volume Beyond Report Writer Capacity
Some data requirements genuinely exceed what Report Writer can handle efficiently.
Symptoms:
Report must return 50,000 or more records
Report requires complex calculated fields across multi-instance objects
Report joins 10 or more related business objects
Action: Consider these alternatives to standard Report Writer:
Workday Prism Analytics: Purpose-built for high-volume data analysis with external data integration capabilities.
Integration-Based Reporting: Use Workday integrations (EIB or Studio) to extract data to an external data warehouse where you have more control over query optimization.
Scheduled Batch Reports: Convert from on-demand to scheduled delivery. Batch processes have more generous resource allocations.
Report Type Mismatch
Sometimes you are using the wrong report type for your requirements.
Symptoms:
Advanced Report struggling to join multiple business objects
Composite Report being used for simple list that could be a Standard Report
Matrix Report with excessive pivoting dimensions
Action: Rebuild the report using the appropriate report type:
Simple Reports: Best for straightforward lists from a single business object with simple related objects.
Advanced Reports: Best for complex multi-object joins with sophisticated filtering.
Matrix Reports: Best for cross-tabulated data with row and column groupings.
Composite Reports: Best for combining multiple report types or displaying complex multi-instance relationships.
Using the wrong report type creates unnecessary processing overhead.
Complex Business Logic Requirements
Occasionally, business requirements genuinely need 40 or more calculated fields across multiple multi-instance objects.
Symptoms:
Business requirements explicitly need all fields
Calculated field logic cannot be simplified
Multi-instance data relationships are necessary for the analysis
Action: Consider these alternatives:
Workday Studio Custom Report: Studio provides more control over query optimization and can handle more complex logic than Report Writer.
Scheduled Batch Delivery: Convert the report to scheduled delivery instead of on-demand. Run it during off-peak hours (2 AM) when tenant resources are more available.
Multi-Report Strategy: Split the analysis into multiple focused reports that users combine in their analytics tool.
Prevention: Building a Performance-First Culture
The best way to fix timeout issues is to prevent them from occurring in the first place.
Build Performance Discipline Into Report Creation
Implement these practices during report development, not after timeouts occur:
Test with Production Data Volumes
Never test reports only in sandbox environments with 100 test records.
Before publishing any report to production:
Copy the report to your production tenant
Test with actual production data volumes
Run with worst-case prompt values (largest date range, largest organization)
Document actual execution time in the report description field
If the report takes more than 2 minutes to execute, optimize before publishing.
Document Execution Time Standards
Include expected execution time in your report’s description:
“Expected execution time: 45 seconds for department-level analysis, 2 minutes for company-wide analysis.”
This sets user expectations and helps you identify when performance degrades over time.
Set Performance Thresholds
Establish clear performance standards before publishing reports:
Simple Reports: Less than 30 seconds
Advanced Reports: Less than 60 seconds
Matrix Reports: Less than 90 seconds
Composite Reports: Less than 2 minutes
Any report exceeding these thresholds requires optimization review before publishing.
Implement Quarterly Report Performance Audits
Do not wait for reports to break. Proactively identify performance issues before they become timeout incidents.
Quarterly audit process:
Export report inventory with metrics
Report name
Report type
Average execution time
Maximum execution time
Number of runs in last 90 days
Last run date
Flag at-risk reports
Average execution time exceeds 90 seconds
Maximum execution time exceeds 3 minutes
Execution time increasing over previous quarters
Apply 7-step diagnostic
Work through the diagnostic checklist for each flagged report
Document findings and optimization opportunities
Optimize proactively
Fix issues before they cause timeouts
Communicate changes to report owners
Track performance improvements quarter over quarter
This proactive approach prevents the Monday morning panic calls.
Establish Report Governance
Implement governance processes that prevent performance problems from being introduced:
Report Approval Workflow
Require approval before publishing custom reports:
Business owner confirms need (prevents duplicate reports)
Data steward validates data sources and security
Workday admin validates performance and naming conventions
Final approver publishes to production
Performance Review Checkpoints
Include these questions in your approval workflow:
Has this report been tested with production data volumes?
What is the execution time with maximum data scope?
Are there more than 20 calculated fields? If yes, why?
Are there more than 3 related business objects? If yes, are they all necessary?
Is the data source indexed?
Ongoing Ownership
Assign a business owner to every report who is responsible for:
Annual review to confirm report is still needed
Validation after Workday releases
Performance monitoring
Deletion when no longer needed
Conclusion: Systematic Diagnosis Over Random Fixes
Report timeouts are not mysterious technical failures. They are symptoms of specific, fixable configuration issues.
The difference between effective and ineffective troubleshooting is methodology.
Ineffective approach: Try random fixes until something works or you give up.
Effective approach: Work systematically through the 7-step diagnostic framework to identify the specific root cause.
Most Workday administrators waste hours trying random optimizations when the real problem could be identified in 15 minutes with systematic diagnosis.
The next time a report times out, do not panic. Open this guide, work through the 7-step checklist, and fix the actual problem.
Your Monday mornings will be much calmer.
Tell Me Your Experience
What is the longest a Workday report has ever taken to run in your tenant? What was causing the problem?
Have you used this diagnostic framework to fix a timeout? What did you find?
Share your experiences in the comments below. We learn best from each other’s real-world challenges and solutions.
It’s 8:47 AM on Monday morning. Sarah’s first day.
She arrives at reception, excited and nervous. The receptionist searches for her name in the visitor log. Nothing. After 15 minutes of phone calls, someone from IT appears with a laptop. Wrong laptop—it’s configured for the previous new hire from three weeks ago.
By 10:30 AM, Sarah still doesn’t have system access. Her manager is in back-to-back meetings until 2 PM. No one told Facilities to set up her desk. The team didn’t know she was starting today.
By lunch, Sarah’s questioning whether she made the right choice accepting this job.
This isn’t fiction. This happens every single week at companies that haven’t configured proper onboarding workflows in Workday.
Here’s what’s frustrating: Workday has all the tools you need to prevent this disaster. Workday Journeys, Onboarding Tasks, automated assignments via Business Process Framework, preboarding self-service—it’s all there. Most companies just don’t use it correctly.
This guide shows you how to configure Workday Onboarding that makes new hires feel like you actually planned for their arrival. We’ll build tasks, create journey templates using Workday Journeys, configure the Hire business process, and create an experience that starts before day one and extends through the first 90 days.
Understanding Workday Onboarding Terminology
Before we dive in, let’s clarify Workday’s onboarding terminology:
Workday Onboarding Plans vs. Workday Journeys
Workday Onboarding Plans: Workday’s marketing name for the overall onboarding product/feature set. This is what you see on Workday.com product pages and sales materials.
Workday Journeys (Onboarding): The technical framework used to build onboarding experiences in your tenant. This is what you actually configure.
In Practice: When configuring, you’ll work with “Workday Journeys” and select “Journey Type: Onboarding.” When discussing with stakeholders or reading Workday marketing materials, you’ll see “Onboarding Plans.”
They refer to the same functionality.
Pre-Hire vs. Preboarding – What’s the Difference?
Pre-Hire (Workday Recruiting): In Workday Recruiting, “Pre-Hire” is a candidate status for those who have accepted offers but haven’t started yet. This is the recruiting-side status.
Preboarding (Workday HCM): The phase where new hires access Workday before their official hire date to complete tasks like I-9, benefits enrollment, and paperwork. This is the HCM-side functionality.
How They Connect: If you use Workday Recruiting, the Pre-Hire status automatically transitions to an active worker in HCM on the hire date, enabling seamless preboarding access. If you use an external recruiting system, you’ll manually create worker records to enable preboarding.
Let’s talk about what happens when onboarding works versus when it doesn’t.
When Onboarding Breaks
Week Before Start Date: No communication. New hire wonders if the offer was real.
Day 1: Scrambling to find laptop, create email, assign desk. New hire waits awkwardly.
Week 1: No structured training. Manager too busy. New hire feels lost.
Day 30: New hire still unclear on expectations, hasn’t met half the team, considering other offers.
Day 90: New hire quits. You’re back to recruiting. Cycle repeats.
When Workday Journeys Works
Week Before Start Date: New hire receives personalized welcome email with link to Workday tenant. Completes preboarding tasks via self-service portal: I-9, benefits enrollment, uploads documents from home.
Day 1: Laptop ready, email active, desk set up. Manager greets new hire at 9 AM sharp. Team welcome lunch scheduled.
Week 1: Structured Workday Journey guides new hire through orientation, training, system access. Daily check-ins with assigned buddy. Clear expectations set.
Day 30: New hire has completed role-specific training, met all stakeholders, contributed to first project. Manager conducts formal 30-day review.
Day 90: New hire fully productive, integrated into team, happy they joined. Retention risk: low.
The difference? Configuration in Workday HCM using Workday Journeys. Someone took the time to build onboarding workflows using Business Process Framework, Journey templates, and Task Management instead of relying on spreadsheets.
Understanding Workday Onboarding Architecture
Before configuring, understand how Workday Onboarding components work together.
Core Components
1. Onboarding Tasks Individual action items assigned to workers, managers, or administrators (e.g., “Complete I-9”, “Provision Laptop”, “Assign Buddy”).
2. Workday Journeys (Onboarding Framework) Collections of tasks organized into phases with timeline visibility and progress tracking. Journeys provide the structured experience framework that guides new hires through their onboarding process.
3. Business Process: Hire The automated workflow that triggers when a new worker is hired. This is where you configure automatic journey assignment, notifications, and approvals.
4. Worker Sub-Process: Onboarding A specialized sub-process within the Hire business process specifically for onboarding-related tasks and data collection.
5. Preboarding (Pre-Hire Access) Functionality that allows workers to access Workday self-service before their official hire date to complete tasks.
6. Task Templates Reusable task definitions that can be assigned across multiple journeys or business processes.
Phase-Based Onboarding Framework
Workday Journeys follows a three-phase journey structure:
Phase 1: Preboarding (Offer Acceptance → Day 0)
Workday Term: Preboarding Phase
What Happens: New hire completes paperwork, enrolls in benefits, learns about company culture—all before their Hire Date (Original Hire Date field).
Workday Functionality:
Worker Status: Pre-Hire (in Recruiting) or contingent status (in HCM)
Preboarding Portal: Self-service access to Workday for completing assigned tasks
Task Visibility: Only preboarding-enabled tasks appear
Milestone Tasks: Tasks triggered on specific days (30, 60, 90)
Performance Enablement Integration: Connect onboarding to goal setting
Completion Tracking: Dashboard showing onboarding progress by cohort
Before You Configure: Design the Experience
Don’t open Workday yet. Seriously. Put down the mouse.
Before you touch any configuration, you need to design the experience. Grab a whiteboard (or Miro board) and map out what you want new hires to experience.
The Experience Design Workshop
Schedule a 2-hour session with these stakeholders:
Note on Task Categories: Depending on your Workday version, task organization may use Onboarding Categories (as described here), Task Tags, or Journey Phase grouping. Check your tenant’s Workday release version for version-specific configuration paths.
Why Categories Matter: They help new hires and admins see onboarding progress at a glance in the Workday Journeys view. “I’ve completed 5 of 6 Administrative Tasks. Still need to finish benefits enrollment.”
Step 3: Create Onboarding Task Templates
Task Templates are reusable task definitions that can be assigned to workers, managers, or administrators.
Note on Task Configuration: Task configuration varies by Workday release. In some tenants, you’ll see:
“Onboarding Task” (tasks specific to onboarding)
“To Do” (general task framework integrated with Journeys)
Tasks configured within Workday Journeys framework directly
Consult your Workday release notes for exact task configuration paths in your tenant version.
Navigate to Task Template Creation
Search for Create Onboarding Task Template (or Create To Do if using To Do framework)
Complete Section 1 of Form I-9 to verify your identity and employment authorization.
You'll need to provide original documents on your first day for Section 2 verification: - Option 1: Passport (establishes both identity and employment authorization) - Option 2: Driver's License + Social Security Card + Birth Certificate - Option 3: See I-9 acceptable documents list for other combinations
Upload your Section 1 completion in Workday. HR will verify Section 2 on Day 1.
Task Owner Type: Worker (task assigned to the new hire)
Due Date Offset Configuration:
Calculate From: Hire Date (Original Hire Date)
Offset: -3 days (complete 3 days before hire date)
Task Completion Method: Complete Benefits Enrollment in Workday
Integration with Workday Benefits: Task can be configured to auto-complete when worker submits benefits elections in Workday Benefits module. This requires specific configuration linking the task completion rule to the benefits enrollment event.
Note: Auto-completion from Workday Benefits may require custom configuration depending on your Workday version.
Attachments:
Benefits Summary PDF
Benefits Enrollment Video (link to Workday Learning course)
Conditional Display Logic:
IF Worker Type = Employee AND Time Type = Full Time
THEN Assign this task
(Part-time and contractors may have different eligibility)
Click OK to save.
Task Template 3: IT Equipment Provisioning
Task Template Name: Provision Laptop and System Access
Task Category: Equipment & System Provisioning
Task Description:
Provision hardware and system access for new hire:
HARDWARE: - MacBook Pro 14" (Engineering, Product, Design) - MacBook Air 13" (Marketing, Sales, HR) - Dell Latitude (Finance, Operations)
SOFTWARE & ACCESS: - Create Workday email address - Assign to Security Groups: All Employees, Department-Specific - Configure Domain Security Policies for appropriate access - Grant access: Google Workspace, Slack, JIRA, Salesforce - Install standard software package
Laptop should be configured and ready at new hire's desk by 8:00 AM on hire date.
Task Owner Type: Security Group
Assigned To: IT Administrators (Security Group)
Due Date Offset:
Calculate From: Hire Date
Offset: -2 days (complete 2 days before hire date)
Allow in Preboarding: No (background task, not visible to new hire)
Task Completion Method: Manual completion by IT admin
☐ Assigned to appropriate Security Groups in Workday
☐ Domain Security Policies grant correct access permissions
☐ All application access granted
☐ Equipment placed at assigned desk
Notification:
Task Assigned: Email to IT Administrators Security Group when hire is confirmed
Task Overdue: Escalate to IT Manager if incomplete 1 day before hire date
Click OK to save.
Task Template 4: Assign Onboarding Buddy
Task Template Name: Assign Onboarding Buddy
Task Category: Team & Stakeholder Introductions
Task Description:
Assign an onboarding buddy from the new hire's immediate team.
BUDDY RESPONSIBILITIES: - Reach out before Day 1 to welcome new hire - Greet new hire on arrival (meet at reception or their desk) - Answer questions about team norms, company culture, logistics - Weekly check-ins during first month - Be available for informal questions
IDEAL BUDDY PROFILE: - Same or similar role (peer-level) - 1+ year tenure at company - Strong culture fit - Willing participant (don't voluntell)
After selecting buddy, Workday will automatically notify them and assign buddy tasks.
Task Owner Type: Manager (assigned to new hire’s manager)
Due Date Offset:
Calculate From: Hire Date
Offset: -7 days (assign one week before start)
Allow in Preboarding: No
Task Completion Method: Select Related Worker (buddy)
Automatic Trigger: When manager completes this task by selecting a buddy, Workday automatically:
Assigns buddy-specific tasks to the selected buddy
Sends notification to buddy with their responsibilities
Creates relationship in Workday: New Hire ←→ Onboarding Buddy
Buddy Tasks Auto-Assigned:
“Send welcome message to new hire” (Due: Day -3)
“Greet new hire on Day 1” (Due: Day 1)
“Weekly check-in with new hire” (Due: Days 7, 14, 21, 30)
Click OK to save.
Task Template 5: Complete Compliance Training
Task Template Name: Complete Required Compliance Training
Task Category: Orientation & Learning
Task Description:
Complete all mandatory compliance training in Workday Learning:
REQUIRED COURSES (Estimated Time: 2 hours): 1. Code of Conduct & Ethics (30 min) 2. Harassment Prevention & Respect in Workplace (45 min) 3. Data Security & Privacy (30 min) 4. Information Security Awareness (15 min)
All courses must be completed by end of Week 1 (Day 7).
Access courses: Workday Home > Learning > My Learning
Task Owner Type: Worker
Due Date Offset:
Calculate From: Hire Date
Offset: +7 days (complete within first week)
Allow in Preboarding: No (complete after hire date)
Task Completion Method: Integration with Workday Learning
Workday Learning Integration: Tasks can be configured to auto-complete when Learning campaigns are finished, but this requires:
Learning Campaign assignment as part of onboarding
Task completion rule linked to Learning Campaign completion status
May require custom configuration or Workday Extend depending on complexity
Alternative: Create separate Workday Learning assignments and manual task completion verification by manager.
Conditional Assignment:
All worker types require base compliance training
IF Job Profile = Manager THEN also assign “Manager Compliance Training” campaign
Notification:
Task Assigned: Email on Day 1 with links to courses
Reminder: Email on Day 5 if not started
Escalation: Email to Manager on Day 8 if incomplete
Click OK to save.
Step 4: Create Journey Templates Using Workday Journeys
Workday Journeys provide the structured framework that organizes tasks into phases with visual timeline tracking.
Using Workday-Delivered Journey Templates
Before building journeys from scratch, check if Workday provides pre-built templates:
Navigate to Browse Workday Journeys Templates
Review available templates:
New Hire Onboarding
Manager Transition
Open Enrollment
Offboarding
Role Change
Select a template that matches your use case
Customize the template for your organization:
Add/remove tasks
Adjust due dates
Modify task descriptions
Add company-specific content
Advantages of Using Workday Templates:
Faster implementation (weeks instead of months)
Workday best practices built-in
Maintained and updated by Workday with each release
When to Build Custom:
Workday template doesn’t fit your process (< 70% match)
Highly unique organizational requirements
Integration with custom systems
Navigate to Journey Configuration
Search for Create Journey
Select Journey Type: Onboarding
Journey 1: Standard Employee Onboarding Journey
Journey Name: Standard Employee Onboarding
Journey Description: Complete onboarding experience for all new employees from preboarding through day 90.
Applicable To (Eligibility):
Worker Type = Employee
Exclude: Interns, Executives (they have custom journeys)
Journey Phases:
Click Add Phase to create each phase:
Phase 1: Preboarding (Before You Start)
Phase Name: Preboarding – Before You Start
Phase Description: “Welcome! Complete these tasks before your first day to hit the ground running.”
Phase Timeline:
Start: Hire event confirmed (when Business Process: Hire completes)
End: Hire Date – 1 day
Tasks in This Phase:
Add tasks by clicking Add Task and selecting from Task Templates:
Review Welcome Email
Due Date Offset: Hire Date – 7 days
Owner: New Hire
Required: Yes
Complete I-9 Section 1
Due Date Offset: Hire Date – 3 days
Owner: New Hire
Required: Yes
Complete Tax Forms (W-4/State)
Due Date Offset: Hire Date – 3 days
Owner: New Hire
Required: Yes
Enroll in Benefits
Due Date Offset: Hire Date + 30 days (can start in preboarding, complete after start)
Owner: New Hire
Required: Yes
Update Emergency Contacts
Due Date Offset: Hire Date – 3 days
Owner: New Hire
Required: Yes
Review Employee Handbook
Due Date Offset: Hire Date – 3 days
Owner: New Hire
Required: No (informational)
Provision Equipment
Due Date Offset: Hire Date – 2 days
Owner: IT Administrators (Security Group)
Required: Yes
Visibility: Hidden from new hire (background task)
Assign Buddy
Due Date Offset: Hire Date – 7 days
Owner: Manager
Required: Yes
Visibility: Hidden from new hire
Prepare Workspace
Due Date Offset: Hire Date – 2 days
Owner: Facilities (Security Group)
Required: Yes
Visibility: Hidden from new hire
Click OK to save the phase.
Phase 2: Day 1 – Welcome to the Team!
Phase Name: Day 1 – Welcome to the Team!
Phase Description: “Your roadmap for day one. We’re excited to have you!”
Phase Timeline:
Start: Hire Date (Day 0)
End: Hire Date (Day 0)
Tasks:
Arrive at Reception
Due Date: Day 1, 9:00 AM
Owner: New Hire
Task Type: Informational (with directions to building/floor)
Meet Your Buddy
Due Date: Day 1, 9:15 AM
Owner: Buddy
Completion: Buddy marks complete after greeting new hire
Office Tour
Due Date: Day 1, 9:30 AM
Owner: Buddy
IT Equipment Pickup & Setup
Due Date: Day 1, 10:00 AM
Owner: IT + New Hire
Completion: New hire verifies laptop, email, system access working
Verify System Access
Due Date: Day 1, 10:30 AM
Owner: New Hire
Checklist: Test email, Slack, Workday, key systems
Welcome Meeting with Manager
Due Date: Day 1, 11:00 AM
Owner: Manager + New Hire
Integration: Auto-creates Workday Calendar event
Team Welcome Lunch
Due Date: Day 1, 12:00 PM
Owner: Team
Integration: Auto-creates Calendar event, invites team
HR Orientation Session
Due Date: Day 1, 2:00 PM
Owner: HR + New Hire
Integration: Auto-enrolls in Workday Learning orientation course
Review First Week Plan
Due Date: Day 1, 4:00 PM
Owner: Manager + New Hire
Click OK to save.
Phase 3: Week 1 – Getting Oriented
Phase Name: Week 1 – Getting Oriented
Phase Timeline:
Start: Hire Date + 1 day (Day 2)
End: Hire Date + 7 days (Day 7)
Tasks:
Complete Compliance Training
Due Date: Day 7
Owner: New Hire
Integration: Workday Learning (manual verification or auto-complete if configured)
Attend Company Overview Presentation
Due Date: Day 2
Owner: New Hire
Meet with Key Stakeholders
Due Date: Days 2-5
Owner: New Hire
Task Details: List of 5-7 people to meet
Complete Systems Training
Due Date: Days 3-4
Owner: New Hire
Integration: Workday Learning courses
Daily Check-ins with Manager
Due Date: Each day (Days 2-7)
Owner: Manager
Creates 5 separate calendar events
Shadow Team Member
Due Date: Day 4
Owner: New Hire
Review Role Expectations Document
Due Date: Day 5
Owner: New Hire
Document attached in Workday
Click OK to save.
Phase 4: First 30/60/90 Days – Milestones & Goals
Phase Name: Your First 90 Days – Milestones & Goals
Phase Timeline:
Start: Hire Date + 8 days
End: Hire Date + 90 days
Milestone-Based Tasks:
30-Day Milestone:
Complete Role-Specific Training
Due Date: Day 30
Owner: New Hire
Start First Project
Due Date: Day 15
Owner: New Hire + Manager
30-Day Check-In with Manager
Due Date: Day 30
Owner: Manager + New Hire
Integration: Auto-creates Calendar meeting
Complete Onboarding Experience Survey
Due Date: Day 30
Owner: New Hire
Integration: Links to Workday Survey
60-Day Milestone:
Lead First Team Meeting
Due Date: Day 45
Owner: New Hire
60-Day Performance Review
Due Date: Day 60
Owner: Manager + New Hire
Integration: Creates Performance Review in Workday
90-Day Milestone:
Submit First Quarter Goals
Due Date: Day 75
Owner: New Hire
Integration: Creates Goals in Performance Management
90-Day Review & Onboarding Completion
Due Date: Day 90
Owner: Manager + New Hire
Onboarding Graduation Celebration
Due Date: Day 90
Owner: Team
Task Type: Informational (celebrate new hire’s successful integration!)
Click OK to save the phase.
Complete Journey Configuration
Journey Summary Screen:
Review all phases and tasks. Verify:
Task sequence makes sense
Due dates are appropriate
Task owners are correct
Required vs. optional designation is accurate
Journey Settings:
Enable Journey Progress Tracking: Yes (new hires can see their completion percentage)
Show Completed Tasks: Yes (builds sense of accomplishment)
Allow Task Reordering: No (maintain structured sequence)
Journey Owner: HR Operations (Security Group that monitors journey completion)
Click OK to save the complete Journey.
Step 5: Configure Business Process: Hire to Auto-Assign Journeys
Now configure the Hire business process to automatically assign Workday Journeys when workers are hired.
Navigate to Business Process Configuration
Search for View Business Process
Type: Hire
Click Hire Employee business process
Edit Business Process
Click Business Process > Edit Process Definition
Add Business Process Step: Assign Journey
Scroll to the section after Manager Approval and before Complete Hire.
Click Add Step
Step Name: Assign Journey
Step Type: Automated (no human intervention)
Step Executes: After hire is confirmed (manager has approved)
Step Action: Assign to Worker
Journey Assignment Configuration:
Click Configure Journey Assignment
Journey Template: Standard Employee Onboarding
Assignment Criteria (Conditions):
IF Worker Type = Employee
AND Time Type = Full-Time
AND Job Profile does NOT contain “Intern” or “Executive”
THEN Assign “Standard Employee Onboarding” Journey
Journey Start Date: Immediately upon hire confirmation (enables preboarding)
Notification Configuration:
Send to Worker: Yes (email notification with link to access Workday preboarding portal)
Send to Manager: Yes (notification that worker’s onboarding journey has begun)
Send to HR: No (HR can monitor via dashboard)
Click OK to save step.
Add Conditional Journey Assignments (Optional)
For Different Employee Types:
Add additional conditional steps:
Step: Assign Manager Onboarding Journey
Assignment Criteria:
IF Job Profile contains “Manager” or “Director” or “VP”
THEN Assign “Manager Onboarding Journey” (includes leadership training)
Step: Assign Executive Onboarding Journey
Assignment Criteria:
IF Job Profile contains “Chief” or “President” or job level = Executive
THEN Assign “Executive Onboarding Journey”
Step: Assign Remote Employee Onboarding Journey
Assignment Criteria:
IF Location contains “Remote” or “Work from Home”
THEN Assign “Remote Employee Onboarding Journey” (includes home office setup)
Step: Assign Intern Onboarding Journey
Assignment Criteria:
IF Worker Type = Contingent Worker AND Job Profile contains “Intern”
THEN Assign “Intern Onboarding Journey” (shorter duration, academic calendar aligned)
Save Business Process Changes
Click Done to save all changes to the Hire business process.
Activate Pending Security Policy Changes
Search for Activate Pending Security Policy Changes
Review changes (you should see Business Process: Hire updates)
Click OK to activate
Changes take effect immediately. All future hires will automatically receive Workday Journeys.
Allow new hires to access Workday self-service before their Hire Date (Original Hire Date) to complete preboarding tasks.
Understanding Pre-Hire in Workday
If You Use Workday Recruiting: When a candidate accepts an offer in Workday Recruiting, their status changes to “Pre-Hire”. This Pre-Hire record can automatically create an HCM worker record (if configured), enabling seamless preboarding access.
Recruiting to HCM Transition:
Candidate receives offer in Workday Recruiting
Candidate accepts offer → Status changes to “Pre-Hire”
Pre-Hire record automatically creates HCM worker record (if integration configured)
Workday Journeys auto-assigns based on Business Process
Pre-hire receives email with Workday preboarding access
If You Use External ATS: You’ll need to manually create worker records or use integration to push hire data from your ATS to Workday HCM. Workers are created with a contingent status or custom status that allows Workday access before the official hire date.
Configure Worker Status for Preboarding
For HCM preboarding access, workers need a status that allows system access before their hire date.
Option 1: Use Pre-Hire Status (if available in your tenant)
Search for Maintain Worker Statuses
Verify Pre-Hire status exists
Ensure Allow Workday Access: Yes (critical for preboarding)
Option 2: Use Contingent Worker Status
Some implementations use Contingent Worker as the preboarding status, then transition to Employee on hire date.
Configure Security for Preboarding Workers
Preboarding workers need limited access to complete onboarding tasks but shouldn’t see sensitive company data.
Create Security Group: Preboarding Workers
Search for Create Security Group
Security Group Type: Condition-Based
Security Group Name: Preboarding Workers
Condition:
Worker Status = Pre-Hire (or your preboarding status)
Automatically includes all workers with preboarding status
Configure Domain Security Policies for Preboarding
Search for Domain Security Policies for Functional Area: Workday Access
Click View Domain > Worker Data: Personal Information
Click Edit
Add Preboarding Workers security group to allowed groups
Grant permissions:
Get: Own worker data only (can view their own profile)
Put: Own personal data, emergency contacts, benefits elections
Complete: Onboarding tasks assigned to them
View: Employee Handbook, Company Policies (view-only documents)
Restrict Access:
Cannot view: Other employees, organizational data, financial data
WHAT TO DO NOW: 1. Log in to Workday using the credentials above 2. You'll be prompted to change your password 3. Complete your preboarding checklist (I-9, tax forms, benefits enrollment) 4. Watch our welcome video to learn more about [Company]
MOBILE ACCESS: Download the Workday app from the App Store or Google Play to complete tasks on the go!
NEED HELP? Email: hr@company.com Phone: (555) 123-4567
We look forward to seeing you on [Hire Date] at [Start Time]!
Best regards, [Company Name] HR Team
Attachments:
New Hire Welcome Packet PDF
First Day Instructions PDF
Building Directions & Parking Information
Click OK to save notification.
Step 7: Configure SMS Messaging for Preboarding (Optional)
Workday supports personalized SMS messages to welcome pre-hires before their start date.
Note: SMS functionality may require additional Workday licensing, Workday Extend, or third-party SMS provider integration.
Enable SMS for Onboarding
Verify SMS capability is enabled in your tenant (contact Workday support if unsure)
Configure SMS provider integration (if using third-party service)
Create SMS message templates
Create SMS Welcome Message
Trigger: Worker status = Pre-Hire
SMS Content (160 characters max):
Hi [First Name]! We're excited for your start on [Hire Date]. Check your email for Workday login. Welcome to [Company Name]!
Timing: Send 3-5 days before hire date
Follow-Up SMS (Day Before Start):
Tomorrow's the big day! Arrive at [Building Address] at [Start Time]. Your buddy [Buddy Name] will meet you at reception. See you soon!
Configure SMS Notifications in Business Process
Add SMS notification steps to the Hire Employee business process:
Step: Send Preboarding SMS (Day -5)
Step: Send Day Before Reminder SMS (Day -1)
Note: SMS configuration specifics vary based on your integration method. Consult Workday Community or your implementation partner for detailed SMS setup guidance.
Step 8: Enable Mobile Access for Onboarding
New hires can complete onboarding tasks via Workday mobile app.
Mobile App Features for Onboarding
What New Hires Can Do on Mobile:
View Workday Journeys timeline and progress
Complete tasks on mobile device
Upload documents (I-9, ID photos) via camera
Receive push notifications for task reminders
Access company information and videos
Complete Workday Learning courses
Configuration
No additional configuration needed if Workday mobile app is enabled for your tenant. Onboarding tasks automatically appear in mobile app when:
Worker has Workday access
Workday Journeys assigned to worker
Tasks have mobile-friendly completion methods (acknowledgment, document upload, etc.)
Best Practice: Include Mobile Instructions
Add mobile app download instructions in preboarding welcome email:
MOBILE ACCESS: Complete your onboarding on the go! Download the Workday app: - iPhone: App Store (search "Workday") - Android: Google Play (search "Workday")
Login with the same credentials provided above.
Step 9: Configure Notifications and Reminders
Ensure tasks don’t fall through the cracks with automated notifications.
Task-Level Notifications
Edit each Onboarding Task Template to add notifications:
Search for Edit Onboarding Task Template
Select a task (e.g., “Complete I-9”)
Navigate to Notifications tab
Notification 1: Task Assigned
Event: Task is assigned to worker/manager/admin
Recipient: Task Owner
Timing: Immediately
Email Subject: New Onboarding Task: [Task Name]
Email Body:
Task description
Due date
Link to complete task in Workday
Instructions
Notification 2: Task Due Soon
Event: Task approaching due date
Recipient: Task Owner
Timing: 1 business day before due date (if incomplete)
✅ 100% completion triggers graduation notification and plan closure
Measuring Onboarding Success in Workday
Key Metrics to Track
1. Preboarding Completion Rate
Metric: % of new hires who complete all preboarding tasks before hire date
Data Source: Onboarding Plans – Preboarding Phase Progress
Goal: 90%+ reach 100% preboarding progress before Day 1
How to Use: Low completion rates indicate preboarding communication issues or tasks that are too complex. Review which specific tasks have lowest completion.
2. Average Progress at Key Milestones
Metric: Average progress bar % at Day 1, Day 7, Day 30, Day 90
Data Source: Onboarding Plan Progress report
Benchmark:
Day 1: 30% complete (preboarding + first day)
Day 7: 50% complete
Day 30: 80% complete
Day 90: 100% complete
How to Use: Track by cohort to identify trends. If average Day 7 progress is only 35%, tasks are too heavy or workers need more support.
3. Time to 100% Completion
Metric: Average days from plan assignment to 100% progress
Data Source: Onboarding Plans completion tracking
Goal: 90 days or less for standard employees
How to Use: Faster completion = better engagement. Workers completing in 75 days are likely more productive than those taking 100+.
4. Task Completion SLA
Metric: % of tasks completed by due date (not overdue)
Data Source: Onboarding Tasks
Goal: 95%+ on-time completion
How to Use: Identify which tasks consistently go overdue. Adjust due dates, simplify requirements, or provide more support.
5. At-Risk Plans Count
Metric: Number of active onboarding plans flagged “at risk”
Data Source: Onboarding Advisories report
Goal: <5% of active plans at risk
How to Use: At-risk status indicates multiple overdue tasks or low progress. Requires immediate HR intervention and manager coaching.
6. Manager Task Completion
Metric: % of manager-assigned tasks completed on time
Data Source: Onboarding Tasks, filter by Task Owner Type = Manager
Goal: 98%+ on-time completion
How to Use: Hold managers accountable. Low scores indicate manager capacity issues or unclear expectations. Consider reducing manager task load or providing manager training.
7. IT/Facilities Readiness
Metric: % of equipment provisioning and workspace setup tasks completed before hire date
Data Source: Onboarding Tasks, filter by Task Category = Equipment & Systems Access
Goal: 100% completion by Day -1
How to Use: Critical for positive Day 1 experience. Track IT and Facilities performance separately. Escalate persistent failures to department heads.
8. New Hire Satisfaction (Onboarding Experience)
Metric: Average score from 30-day onboarding survey
Data Source: Workday Survey responses (survey task embedded in 30-day phase)
Goal: 4.5+ out of 5
Survey Questions:
How prepared did you feel on Day 1? (1-5)
How clear were your onboarding tasks and expectations? (1-5)
How helpful was the progress bar in tracking your onboarding? (1-5)
How helpful was your onboarding buddy? (1-5)
How would you rate your overall onboarding experience? (1-5)
9. 30/60/90 Day Retention
Metric: % of new hires still employed at 30, 60, 90 days
Data Source: Workers (hired in last 90-180 days, current employment status)
Goal: 95%+ retention at each milestone
How to Use: Early departures often indicate onboarding failures. Correlate departures with:
Onboarding satisfaction scores
Progress bar completion rates
Manager task completion (did manager engage?)
10. Time to First Contribution
Metric: Days from hire date to completion of “First Project” task
Data Source: Onboarding Tasks, filter by Task Name contains “First Project”
Goal: Varies by role (30-60 days typical)
How to Use: Faster time to contribution = better onboarding ROI. Compare to benchmark for role/department.
Create Executive Onboarding Scorecard
Build executive-level scorecard showing:
Metric
Current Month
Goal
Status
Trend
New Hires Onboarded
28
30
✅ On Track
↗️ +12% MoM
Preboarding Progress (Avg at Day 0)
87%
90%
⚠️ At Risk
↘️ -5% MoM
Progress Bar: Day 7 Average
52%
50%
✅ Exceeds
↗️ +3% MoM
Progress Bar: Day 30 Average
81%
80%
✅ On Track
→ Flat
Task SLA (On-Time Completion)
96%
95%
✅ On Track
↗️ +2% MoM
Manager Task Completion
99%
98%
✅ Exceeds
↗️ +1% MoM
IT Readiness (Day 1 Equipment)
100%
100%
✅ On Track
→ Flat
At-Risk Plans
3
<5
✅ On Track
↘️ -2 MoM
30-Day Satisfaction Score
4.6/5
4.5/5
✅ Exceeds
↗️ +0.1 MoM
90-Day Retention
94%
95%
⚠️ At Risk
↘️ -2% MoM
Avg Days to 100% Complete
88
90
✅ Exceeds
↗️ -3 days MoM
Share monthly with HR leadership and executives.
Common Mistakes and How to Avoid Them
Mistake 1: Progress Bar Doesn’t Update
Problem: Worker completes tasks but progress bar stays at same percentage.
Causes:
Task completion not properly recorded in system
Phase weights not configured correctly (don’t total 100%)
Check task completion method is properly configured
Mistake 2: Not Granting Preboarding Access
Problem: New hires can’t access Workday before hire date because preboarding status doesn’t have security permissions configured.
Symptoms:
New hires receive welcome email but can’t log in
“Access denied” error when trying to access Workday
Preboarding tasks not visible
Progress bar shows 0% and never advances
Fix:
Configure Domain Security Policies for preboarding status workers
Verify “Allow Workday Access” is enabled for preboarding worker status
Test with sample worker in sandbox before deploying to production
Mistake 3: Wrong Onboarding Plan Assigned
Problem: Standard employee receives manager plan, or remote employee receives in-office plan.
Cause: Targeted Audience Rules not configured correctly.
Fix:
Review assignment criteria in Business Process: Hire
Test each worker type in sandbox
Ensure “IF/THEN” logic doesn’t have overlapping conditions
Use mutually exclusive conditions (manager plan should exclude non-managers)
Mistake 4: External Preboarding Site Not Delivering Content
Problem: Recruiting candidates don’t receive External Preboarding Site access.
Causes:
External Preboarding Site not enabled in tenant
Not using Workday Recruiting (external ATS customers can’t use this feature)
Content not uploaded to site
Offer acceptance trigger not configured
Fix:
Verify you have Workday Recruiting (not external ATS)
Enable External Preboarding Site in tenant configuration
Upload welcome content (videos, PDFs, images)
Configure Business Process: Offer to trigger site access on acceptance
Test with sample candidate in Recruiting sandbox
Mistake 5: Progress Bar Shows >100% or Negative %
Problem: Progress bar displays 110% or -5% (impossible values).
Cause: Phase weight misconfiguration or duplicate task counting.
Fix:
Verify phase weights total exactly 100% (not 110% or 95%)
Check for duplicate tasks accidentally added to plan
Ensure tasks aren’t counted twice (e.g., in both preboarding and Day 1 phases)
Review task “Required” settings (all should be consistently Yes or No)
Mistake 6: Mobile App Doesn’t Show Progress Bar
Problem: Desktop shows progress bar, but mobile app doesn’t.
Causes:
Mobile app not updated to latest version
Tenant not on Workday 2025 R1 or later
Mobile access not enabled for onboarding plans
Fix:
Verify tenant is on Workday 2025 R1+ (progress bar is 2025 feature)
Update Workday mobile app to latest version
Enable mobile access in plan settings
Test on both iOS and Android devices
Mistake 7: Information Overload on Day One
Problem: You assign 40 tasks due on day one. New hire is overwhelmed, completes nothing, progress bar stuck at 20%.
Symptoms:
Low Day 1 task completion rates
New hire satisfaction scores drop
New hires report feeling stressed and confused
Progress bar barely moves during first week
Fix:
Space tasks across first week, first month, first quarter
Day one should be 5-7 tasks maximum (mostly meet people, get oriented)
Move administrative tasks to preboarding phase (increases preboarding progress %)
Move training to Week 1 phase
Prioritize relationship-building and equipment setup on Day 1
Test: Can one person realistically complete all Day 1 tasks in 8 hours?
Mistake 8: No Accountability for Background Tasks
Problem: You create tasks for IT, Facilities, Manager. Nobody completes them. New hire shows up, nothing ready. Progress bar stuck because preboarding phase incomplete.
Symptoms:
Equipment not ready on Day 1
Desk not set up
Buddy not assigned
New hire waiting hours for basics
Preboarding progress stuck at 60% (waiting on IT/Facilities tasks)
Fix:
Configure email notifications when tasks assigned to IT/Facilities/Manager
Escalate overdue tasks to department heads
Create dashboard showing background task completion by department
Review “Onboarding Advisories” report daily
Hold IT/Facilities managers accountable in their performance goals
Don’t count background tasks in visible progress % (hide from new hire view)
Mistake 9: Plans Never Get to 100%
Problem: Workers complete all visible tasks but progress bar stuck at 95%.
Causes:
Hidden background tasks never marked complete
Optional tasks counted in progress calculation
Tasks assigned to terminated buddies/managers (orphaned tasks)
90-day tasks not completed (worker moved to regular work)
Fix:
Review which tasks are preventing 100% completion
Mark background tasks complete when verified (IT equipment, desk setup)
Set optional tasks to NOT count toward progress percentage
Automate 90-day task completion if worker reaches Day 91 (don’t block graduation)
Allow HR to manually mark plans 100% complete after review
Mistake 10: Forgetting the Manager’s Role
Problem: Onboarding Plan focuses on HR/IT tasks. Manager isn’t included. New hire completes paperwork but has no relationship with manager. Progress bar advances but experience is poor.
Symptoms:
New hires report unclear expectations
Manager doesn’t know what onboarding tasks exist
No manager check-ins during first 30 days
New hire feels disconnected from team
High satisfaction with “process” but low satisfaction with “experience”
Fix:
Manager tasks in every plan phase:
Preboarding: Send welcome message (Day -3)
Day 1: Welcome meeting, set expectations (Day 1, 11 AM)
Week 1: Daily 15-minute check-ins (Days 1-5)
Day 30/60/90: Formal review meetings
Send manager summary email when plan assigned (“Your new hire starts in 7 days. Here’s their onboarding plan and your tasks.”)
Show managers their direct reports’ progress bars in Manager Dashboard
Hold managers accountable for completing their tasks
Include manager task completion in manager performance evaluations
What Great Workday Onboarding Looks Like in 2026
When you configure Onboarding Plans correctly with progress tracking, here’s what happens:
New Hire Perspective
“A week before I started, I got a welcome email and text message. I clicked the link and logged into Workday. My onboarding plan was right there with a progress bar: ‘Preboarding – 0% Complete’.
I completed my I-9 and tax forms from my couch. Each time I finished a task, the progress bar moved: 15%… 35%… 60%. It felt like a game! By the night before I started, I hit ‘Preboarding – 100% Complete’ and got a congratulations message.
My buddy sent me a message two days before I started, introducing himself. That made me feel so welcomed.
On my first day, my laptop was on my desk, fully configured. My email worked. My manager greeted me at reception at exactly 9 AM with a smile and a coffee. The whole day was planned—I knew exactly where to be and what to do.
On my phone, I could see the progress bar: ‘Day 1 – 0%’ at 9 AM, then ‘Day 1 – 100%’ by 4 PM. So satisfying!
By the end of Week 1, I was at 65% overall. By Day 30, 85%. By Day 90, I hit 100% – Onboarding Complete! and the whole team celebrated.
The progress bar kept me motivated. I always knew exactly where I stood and what was next. Best onboarding I’ve ever experienced.”
Manager Perspective
“I used to spend hours coordinating new hire logistics—emailing IT, chasing Facilities, creating training schedules. Now Workday handles 80% of it automatically.
When I approve a hire, the Onboarding Plan assigns automatically. I get a notification with my tasks clearly listed. I can see my new hire’s progress bar in real-time: Oh, they’re at 45% – right on track for Day 7.
If the progress stalls at 35% and tasks go overdue, I get an alert. I can reach out and help remove blockers.
The progress bar makes it so easy to check in: ‘Hey, I see you’re at 70% – great progress! Need any help with the remaining tasks?’
Onboarding went from chaos to a smooth, repeatable process with clear accountability.”
HR Perspective
“We onboard 20-30 people per month. Before Onboarding Plans with progress tracking, it was manual chaos—spreadsheets, email reminders, hoping nothing was forgotten.
Now every new hire gets a consistent, high-quality experience. I can see all new hires’ progress bars in one dashboard. Filtering by <50% progress immediately shows me who needs help.
The Onboarding Advisories report flags at-risk plans automatically. I don’t have to manually check—Workday tells me exactly who to call.
My executive scorecard shows average progress at Day 7, Day 30, and Day 90. I can prove our onboarding is working: ‘Average Day 30 progress: 83% – up from 68% last year.’
First-year turnover dropped 15% after we implemented structured onboarding with progress tracking. New hires feel welcomed, prepared, and valued from day negative-seven through day ninety.
And when they hit 100% Complete, we celebrate with the whole team. It’s a real milestone.”
That’s the power of properly configured Workday Onboarding Plans with progress tracking.
Your Onboarding Configuration Checklist
Before you declare onboarding “done,” verify:
Workday Onboarding feature enabled in tenant
Progress bar tracking enabled (2025 R1+ feature)
Task categories created (Administrative, Equipment, Training, Integration, Role-Specific)
Individual task templates built with clear descriptions, due dates, and owners
Onboarding Plans assembled for preboarding, day 1, week 1, and 30/60/90 days
Phase weights configured to total exactly 100%
Automatic plan assignment configured in Business Process: Hire or Offer
Targeted Audience Rules configured for role-based plan variations
Preboarding access configured so new hires can log in before hire date
Domain Security Policies configured for preboarding workers
Preboarding welcome email automated via business process notification
SMS messaging configured (optional)
External Preboarding Site set up (Recruiting customers only)
Mobile app access verified for onboarding tasks and progress bar
Task notifications configured for assignment, reminders, overdue escalation
Plan-level notifications configured for phase completion, at-risk alerts, 100% graduation
Buddy assignment process included with auto-task assignment
Manager tasks included at each phase with accountability
Workday Learning integration configured (if using auto-completion)
Security Group assignments automated for IT provisioning
Dashboard/reports configured (delivered reports or custom)
Testing completed in sandbox with all scenarios including progress bar validation
Workday Recruiting integration configured (if using Workday Recruiting)
Documentation created for HR team on managing onboarding plans
Quarterly review scheduled to update plans as company evolves
Progress bar tested on desktop, mobile (iOS), mobile (Android)
Your Implementation Timeline
Week 1: Design & Discovery
Stakeholder workshop (HR, IT, Facilities, Managers, Recent New Hires)
Map current onboarding experience (what works, what doesn’t)
Design future state journey map (preboarding through Day 90)
Define progress bar milestones (what % at Day 7, 30, 90?)
Identify tasks, owners, due dates, dependencies
Define success metrics including progress tracking goals
Set up External Preboarding Site (Recruiting customers)
Week 6: Reporting & Dashboard
Access Workday delivered Onboarding reports
Configure Onboarding Advisories alerts
Build custom reports if needed (supplemental)
Set up scheduled dashboard delivery
Define KPIs including progress bar benchmarks
Create executive scorecard
Week 7: Comprehensive Testing
Test all scenarios in sandbox (see Testing section)
Test progress bar accuracy on desktop and mobile
Test with multiple employee types (standard, manager, remote, intern)
Test preboarding access and transition to active
Test External Preboarding Site (Recruiting)
Test notifications and escalations
Test Targeted Audience Rules assignment
Fix any issues identified
Week 8: Deployment & Monitoring
Deploy configuration to production tenant
Activate pending security policy changes
Communicate to stakeholders (HR, IT, Facilities, Managers)
Create user documentation highlighting progress bar feature
Train HR team on monitoring Onboarding Advisories
Monitor first cohort of new hires closely
Gather feedback and iterate
Ongoing: Continuous Improvement
Review metrics monthly (dashboard and scorecard)
Monitor average progress % at key milestones
Gather feedback from recent new hires (30-day survey including progress bar helpfulness)
Quarterly plan review and updates
Annual comprehensive audit of onboarding experience
Benchmark against industry standards
Track time to 100% completion trends
Final Thoughts
Onboarding is your company’s first real impression on new employees. Get it right, and you build loyalty, accelerate productivity, and reduce turnover. Get it wrong, and you lose talent before they even start contributing.
The good news? Workday gives you everything you need to build world-class onboarding. With 2025’s progress bar feature, you can now give new hires clear visibility into their onboarding journey, making the experience feel like a guided achievement rather than an overwhelming checklist.
The hard part isn’t the technology—it’s the thoughtful design of the experience.
Map the journey first. What should new hires feel, learn, and accomplish at each phase? What progress should they see at Day 7? Day 30? Day 90?
Build the configuration second. Use Onboarding Plans, task templates, Targeted Audience Rules, and Business Process Framework to automate the experience you designed.
Leverage the progress bar. Visual tracking transforms onboarding from a passive checklist into an engaging journey. “0% → 100%” is motivating. Use it.
Measure the results always. Track completion rates, progress at milestones, satisfaction scores, and retention metrics. Iterate and improve.
Because Sarah’s first day should feel like this:
She arrives at 9 AM. Her buddy is waiting at reception with a smile and a coffee. Her laptop is ready. Her manager welcomes her warmly and walks her through a clear first-day agenda.
By lunch, she’s met her team and checks her phone: “Day 1 – 75% Complete.” By 4 PM: “Day 1 – 100% Complete – Great job!”
By Week 1: “Overall Progress: 52% – You’re ahead of schedule!”
By Day 30: “30-Day Milestone Reached – 84% Complete!”
By Day 90: “Onboarding Complete – 100% – Welcome to the team!”
That’s the onboarding experience you can build in Workday with Onboarding Plans and progress tracking.
Now go build it.
Disclaimer: This guide represents original content based on Workday implementation experience and publicly available Workday official documentation. Configuration steps reflect Workday best practices and include 2025 R1 features (Progress Bar, Targeted Audience Rules, External Preboarding Site, Onboarding Advisories). Configuration may vary based on your tenant version, industry, and organizational requirements. Always consult Workday Community, official documentation, and your Workday Account Team for version-specific guidance. Test all configurations thoroughly in sandbox environments before deploying to production.
Most tenants treat Workday Learning like a file cabinet for SCORM files and compliance videos. The result is predictable: low completion, annoyed learners, and business leaders who do not see value. The mindset shift is to treat Workday Learning like a product: structured, branded, targeted and measured. The core building blocks are Courses, Programs and Learning Campaigns, supported by good Topics, Audiences and reporting.
This guide walks through how to structure Workday Learning so people actually use it.
Start with a product mindset for learning
Before creating any content, answer a few product-style questions:
Who is the audience for this learning: new hires, frontline managers, HR, finance, individual contributors?
What problem does this learning solve in their day-to-day work?
What is the smallest set of content that gets them from “stuck” to “confident”?
How will you measure success – completion, reduced tickets, improved process adoption, certification rates?
Workday Learning can deliver Required Learning, skill development, or “in the flow of work” guidance, but only if content is designed around real workflows and not just course titles.
Structure Courses that feel focused, not bloated
In Workday Learning, Courses are structured learning experiences that bring together Lessons (videos, documents, quizzes, etc.).
Design principles for Courses:
Keep each course focused on a single outcome, such as “Approve Time in Workday”, “Create Job Requisition”, or “Run Headcount Report”.
Use digital courses for self-paced content and blended courses when you need instructor-led sessions with Offerings.
Combine 3–7 short lessons rather than one long video; people prefer snackable units they can complete between tasks.
In configuration:
Use Topics (e.g., “Workday for Managers”, “HR Processes”, “Compliance”) so courses are easy to discover.
Make key lessons mandatory within the course where completion really matters (for example, policy content or core process steps).
Add simple assessments or knowledge checks where you truly need proof of understanding, not just for the sake of a quiz.
Think of Courses as “features”: each one should solve a clear learner problem in 10–30 minutes.
Use Programs as learning journeys, not dumping grounds
Learning Programs in Workday bundle multiple Courses and other learning items into a sequence or pathway.
Good use cases for Programs:
Onboarding paths: a sequence for new hires (e.g., “Welcome to Company”, “Workday Basics”, “Security & Compliance”).
Certification journeys: modules that lead up to an internal certification or badge.
Design tips:
Limit each Program to a realistic volume of content – for example, 2–6 hours spread across several weeks instead of a huge one-time demand.
Use prerequisites and optional items to differentiate between “must-do” and “nice-to-have” learning.
Consider scheduling Dates or time windows (e.g., modules by week) for leadership or cohort-based programs to create momentum.
Programs are your “learning journeys”. If you build them as curated sequences with clear outcomes and timelines, they feel like real products, not playlists of random courses.
Learning Campaigns: your marketing engine inside Workday
Even good content fails without promotion. Learning Campaigns are how you market learning inside Workday – pushing specific content to targeted Audiences with notifications and dashboard placements.
What Learning Campaigns can do:
Promote content on learners’ Learning app home page (for example, in Required for You or Announcements areas).
Send notifications about new or required learning, with one-time or recurring schedules.
Target specific Audiences based on attributes like Company, Location, Role, or even dynamic criteria (for example, new hires in the last 30 days).
Patterns that work:
Required learning campaigns for compliance or critical change training. Pair a Required campaign with a “required” Audience so items appear in the “Required for You” worklet.
Adoption campaigns around key Workday releases, new processes or seasonal events (e.g., performance review season, open enrollment).
Onboarding campaigns that run on a daily or weekly recurrence and automatically pick up new hires based on a dynamic Audience.
Treat campaigns as ongoing “product marketing” for learning: each campaign should have a clear message, target audience and timeline.
