Most Workday Calculated Field issues are not about syntax.
They’re about multi-instance data and effective dating.
If you’ve ever built a report that shows the wrong Cost Center, the wrong Manager, or blank values for workers with multiple jobs, you’re not alone. This is the most frequently asked Calculated Field problem across Workday Community forums, Reddit threads, and consultant Slack channels.
The issue isn’t that Workday is broken. The issue is that most report writers are trying to pull data directly from the Worker object without understanding how Workday handles one-to-many relationships and time-based changes.
Let me show you the proven pattern that fixes this and why it works.
The Business Problem: Finance Wants “Simple” Data
Here’s a real scenario that breaks reports every time:
Finance Request: “We need a monthly report with Worker ID, Primary Job Cost Center, and Manager—as of payroll close date (the 25th of each month).”
Sounds simple, right?
But workers in Workday can have:
Multiple jobs (primary + additional assignments)
Job history (transfers, promotions, department changes)
Future-dated changes (someone accepted a promotion starting next month)
When you create a Calculated Field and try to use Lookup Related Value (LRV) directly from Worker to Cost Center, Workday doesn’t know:
Which job to pull from (primary? additional? terminated?)
Which effective date to use (today? historical? future?)
Result: The report shows:
Blank Cost Centers for workers with multiple jobs
The wrong Cost Center (it grabbed the additional job instead of primary)
Future Cost Centers when you wanted historical data
Terminated job data when the worker is still active
This isn’t a Workday bug. This is a multi-instance data problem, and it requires a specific Calculated Field pattern to solve.
The Pattern That Works: ESI → LRV → LVAOD
Here’s the three-step pattern that Workday experts use to handle multi-job, time-based reporting:
Step 1: ESI (Extract Single Instance)
Identify the correct job instance
Step 2: LRV (Lookup Related Value)
Pull values from that job
Step 3: LVAOD (Lookup Value As Of Date)(optional)
Handle time-based reporting (historical or future-dated)
Let’s break down each step with the exact Workday configuration.
Step 1: Extract Single Instance (ESI) – Find the Right Job
The first mistake most people make is trying to pull Cost Center directly from Worker. Workday sees:
Worker → Jobs (relationship) → multiple job rows
Workday doesn’t know which one to use. So it either:
Returns the first one it finds (often wrong)
Returns blank (if there’s ambiguity)
Returns multiple rows (breaking your report structure)
Solution: Use Extract Single Instance to isolate exactly one job.
Calculated Field: Primary Active Job
Field Name: Primary Active Job Return Type: Worker’s Job Formula:
Filters for Active = True (excludes terminated positions)
Returns exactly one job instance
Why “Active” Matters: If you only filter by Is_Primary_Job = True, you might get:
A terminated primary job (if worker hasn’t been removed from system)
A future-dated primary job (if effective dating is enabled)
Adding Is_Active = True ensures you get the current active primary job.
Common Mistake: Many report writers create an ESI with only Is_Primary_Job = True. This works 90% of the time—until someone terminates, gets rehired, or has a future-dated job change. Then the report breaks.
Takes the single job instance from Step 1 (Primary_Active_Job)
Looks up the Cost Center tied to that job
Returns a clean Cost Center value
Why This Works: You’re no longer looking up from Worker (which has multiple jobs). You’re looking up from a specific job instance that you isolated in Step 1.
Scenario: You’re building an integration that only sends changed workers (delta logic), but you also wrap everything in LVAOD.
Problem: LVAOD evaluates data “as of” a specific date. Delta logic evaluates data based on changes since last run. These two concepts conflict.
Fix:
Use LVAOD for reporting (Finance wants historical snapshots)
Use delta filters for integrations (only send changed records)
Don’t mix them in the same Calculated Field
Mistake 4: Not Testing Edge Cases
Most Calculated Fields work fine in production for 6 months—then break when:
Someone gets rehired (multiple hire dates)
Someone has a future-dated promotion (job change not yet effective)
Someone terminates but stays in the system (data retention policy)
Test These Scenarios:
Worker with 2 jobs (Primary + Additional)
Worker with terminated job still in system
Worker with future-dated job change (effective next month)
Worker on Leave of Absence (Is_Active might be False)
Rehired worker (multiple position history rows)
If your ESI → LRV pattern handles all of these, you’re good.
The Mental Model That Makes This Click
Think of Workday data like a tree:
textWorker (trunk)
├─ Job 1 (branch) → Cost Center A, Manager X
├─ Job 2 (branch) → Cost Center B, Manager Y
└─ Job 3 (terminated, branch) → Cost Center C, Manager Z
When you use LRV directly from Worker, you’re asking: “What’s the Cost Center?”
Workday responds: “Which branch? There are three.”
When you use ESI → LRV, you’re saying: “First, give me the Primary Active branch. Then, tell me its Cost Center.”
Workday responds: “Got it. Here’s Cost Center A from Job 1.”
That’s the difference.
Why This Pattern Matters
If you master ESI → LRV → LVAOD, you unlock:
Accurate multi-job reporting (no more blank Cost Centers)
Time-based snapshots (Finance gets November data, not December data)
Designing Absence in Workday is one of those areas where small setup decisions can haunt HR and payroll for years. A messy mix of Time Off Plans, Leave of Absence types, ad-hoc eligibility rules and unclear accrual logic quickly turns into employee disputes, manual payroll fixes and constant “can you fix my balance?” tickets. The goal is simple: build Time Off and Leave plans that are compliant, predictable and easy to explain to employees and managers.
Start with policies, not pages in Workday
Before creating any Time Off Plan in Workday, capture the real-world policy in plain language. For each policy, clarify:
What is the absence type? (e.g., Vacation, Sick, Casual, Parental Leave).
Is it Time Off (short-term) or Leave of Absence (longer-term, usually job-protected)?
How is entitlement earned: front-loaded, per period accrual, or no accrual (e.g., unpaid leave)?
Who is eligible and from when: on hire, after probation, based on Worker Type, Location, or Company?
What happens at year end: carryover limit, forfeiture, or payout?
Treat this as your functional design. Then map each policy to Workday configuration objects like Time Off Type, Time Off Plan, Leave Type, Absence Plan and Eligibility Rules.
Time Off vs Leave: use the right tool
In Workday Absence Management, Time Off and Leave of Absence exist for different use cases.
Use Time Off Plans for day-level or hour-level absences such as vacation, sick days, casual leave, floating holidays or compensatory time.
Use Leave of Absence for extended, often job-protected absences such as maternity/paternity leave, long-term medical leave, sabbaticals and unpaid extended leave.
Typical mistakes include:
Implementing long parental leave as a large Time Off balance instead of a Leave with clear start/end and impact on benefits and payroll.
Using Leave for short absences where employees actually need partial-day bookings and clear Time Off balances.
Being strict about which bucket each policy belongs to will keep your reporting, balances and integrations much cleaner.
Designing Time Off Plans that behave like policy
When configuring a Time Off Plan, walk through the fundamentals:
Unit and frequency: Decide if the plan is in Hours or Days, and whether accruals are per pay period, monthly, quarterly or yearly.
Accrual rule: Configure how workers earn time – fixed amount per period, tenure-based tiers, or pro-rated based on FTE and Hire Date.
Scheduling and period dates: Align Time Off Plan periods to your Calendar (e.g., calendar year vs fiscal year), as this drives carryover and balance reset.
Validation rules:
Minimum and maximum units per request.
Maximum negative balance allowed (or no negative balance).
Whether weekends and holidays count, using Holiday Calendars and Work Schedules.
This is where Workday’s rules engine is powerful but unforgiving. If your accrual and validation logic does not mirror the written policy, users will find edge cases in days.
Getting eligibility right the first time
Eligibility Rules determine who can enroll in a given Time Off Plan or Leave Type. Instead of hard-coding multiple versions of the same plan, design reusable rules based on:
Company or Country (for country-specific regulations).
Location or Region (for state or province variations).
Worker Type, Employee Type or Job Profile (for different entitlements by grade or union).
Good patterns:
Build generic plans (e.g., “Vacation – Global”) with country-specific Eligibility Rules and different Accrual configurations when required.
Use clear, documented naming for rules, such as “EL – India – Vacation – Regular FT”, instead of cryptic codes only one consultant understands.
Poor eligibility design is a top reason HR “regrets” absence configuration later, because fixing it means unwinding enrollments and recalculating balances.
Carryover, forfeiture and payout: the regret zone
Nothing generates more escalation than employees losing or gaining unexpected Time Off at year end. When designing carryover and forfeiture rules:
Define the maximum carryover per plan in the policy first (e.g., “carry up to 10 days to next year”).
In Workday, configure Carryover Limit, Forfeiture, and, where applicable, Payout rules that match the policy line by line.
Decide whether carryover happens on a fixed date (e.g., January 1) or based on worker-specific dates (e.g., work anniversary).
Always test these rules with edge-case workers:
Mid-year hires.
Employees changing Work Schedule or FTE during the year.
Workers moving between countries or companies with different plans.
HR regrets absence design when year-end jobs run and hundreds of balances look “wrong”. Robust testing and clear communication can prevent that.
Integrations with Time Tracking and Payroll
Absence Management does not live alone. It needs to work with Time Tracking and Payroll (Workday or third-party).
Key integration checkpoints:
Ensure Time Off Types map correctly to Time Entry Codes if you are using Time Tracking, so time-off hours flow consistently into timesheets and reports.
Confirm which Time Off Plans impact pay and how – for example, paid vs unpaid leave, and how they should feed Earnings and Deductions in payroll.
Check that export integrations to third-party payroll or leave systems receive clear indicators for Time Off, Leave, and Leave Status (e.g., Active, Returned Early).
If payroll teams cannot easily reconcile Time Off and Leave with pay results, they will pressure HR to simplify or manually override the system – which defeats the purpose of a clean design.
Make it easy for employees and managers
A technically perfect configuration still fails if employees and managers cannot use it intuitively.
Focus on:
Absence Calendar: Make sure the employee calendar shows clear balances, upcoming holidays and approved absences.
Intuitive Time Off Types naming, such as “Vacation – India” or “Sick – US”, instead of internal abbreviations.
Simple Business Processes for Request Absence and Request Leave of Absence with minimal approval steps and clear notifications.
From a practitioner view, “HR won’t regret it” when:
Employees self-serve correctly most of the time.
Managers approve with confidence, without asking HR which option to pick.
HR and payroll see the same truth on balances and leave dates.
Testing and ongoing monitoring
Before go-live, always run a structured test cycle for Absence:
Simulate a full year of accruals, carryover and forfeiture for representative workers.
Test real scenarios: partial-day vacation, long sick leave, maternity leave overlapping with public holidays, and retroactive changes.
Validate key absence reports: balances by worker, time off taken by period, people on leave by type and date.
Post go-live, monitor:
Top absence-related tickets raised to HRIS.
Patterns of manual adjustments to balances.
Feedback from HR business partners and payroll on pain points.
Then iterate your Time Off Plans, Leave Types and Eligibility Rules in controlled, well-communicated changes instead of constant one-off fixes.
Designing Absence in Workday the right way is less about clever rules and more about alignment: aligning configuration to policy, to payroll, and to how people actually request time away. When Time Off and Leave plans are clean and predictable, HR can stop firefighting balances and focus on strategic workforce planning instead.
Every Workday tenant eventually faces the same question: “How do we move people data in and out of Workday without breaking things?” The answer usually involves a mix of EIB, Core Connector: Worker (CCW) and payroll interfaces like PECI and PICOF. Each tool solves different problems: quick one‑off loads, event‑driven deltas, or structured feeds to third‑party payroll. When you understand their patterns, you stop treating integrations as mysterious black boxes and start designing clean, predictable data flows.
This playbook explains where each tool fits and how to combine them into practical patterns.
The core tools in your Workday integration toolbox
At a high level, Workday HCM data can move via three main integration approaches for HR and payroll:
Enterprise Interface Builder (EIB)
A guided, configuration‑friendly way to build inbound (into Workday) and outbound (from Workday) integrations.
Supports formats like CSV and XML, and can be scheduled or launched manually.
Core Connector: Worker (CCW)
A pre‑configured Connector that detects worker‑related changes and outputs “delta” data based on events or schedules.
Ideal for ongoing, event‑driven integrations with downstream systems that need near real‑time updates.
Payroll Interface templates – PECI and PICOF
PECI (Payroll Effective Change Interface): sends all effective‑dated changes for workers in a pay period to a payroll provider.
PICOF (Payroll Interface Common Output File): sends a “top‑of‑stack” snapshot of current values for each worker.
Think of EIB as your Swiss Army knife, CCW as your event‑driven delivery truck, and PECI/PICOF as specialized payroll trucks with strict manifests.
When to use EIB
EIB shines when you need simple, structured data movement and can tolerate batch runs.
Common use cases:
Data loads into Workday
Mass updates for workers, positions, organizations or compensation using inbound EIBs.
Initial data migration for go‑live or new modules.
Outbound data extracts
HR data exports to analytics tools, data warehouses, or vendor systems that can consume CSV/XML on a schedule.
Audit or snapshot files for regulatory or internal control purposes.
Patterns:
Use EIB when:
The integration is periodic (daily, weekly, monthly).
Change detection can be handled using effective dates or report filters instead of continuous event logic.
The consumer system is comfortable with full or filtered extracts.
EIB is often 20–30% of a mature tenant’s integrations: quick to build, transparent to support, and flexible enough for many HR use cases.
When to use Core Connector: Worker (CCW)
Core Connector: Worker is built for ongoing worker data feeds to downstream systems like LMS, IAM, security badges, or benefits platforms.
Key characteristics:
Event‑driven deltas
CCW can be triggered by worker events (hire, terminate, job change, compensation change) or run on a schedule.
Outputs only the records that changed, not the whole population, improving performance and efficiency.
Configurable output
You choose which worker attributes to include, and can leverage Calculated Fields to derive additional outputs such as full names, tenure, or custom flags.
Flexible formats
Supports XML, JSON, CSV and transformations via XSLT.
Patterns:
Use CCW when:
A downstream system needs near real‑time or frequent worker updates.
You want delta‑only outputs instead of full extracts.
You can define a stable integration contract (fields, formats, triggers).
Examples: outbound feeds to identity providers, benefits vendors, or internal HR data hubs that must stay synchronized with Workday.
PECI vs PICOF: which payroll interface to pick?
For payroll, PECI and PICOF are the main templates that Workday customers use with third‑party payroll engines.
PICOF – Payroll Interface Common Output File
Sends one consolidated snapshot of current values for each worker in scope.
“Top‑of‑stack” logic: only the latest value per field per worker is sent.
Simpler to consume but does not show the full sequence of changes in a period.
PECI – Payroll Effective Change Interface
Sends a sequence of effective‑dated changes for each worker across the pay period.
Captures hires, terminations, salary changes, and other updates as separate transactions, with timestamps.
Provides higher data integrity, better auditability and automated corrections.
Real‑world pattern:
PICOF behaves like “send me where the worker ended up this period”.
PECI behaves like “send me every change the worker went through this period”.
Many organizations are moving from PICOF to PECI to improve automation, compliance, and reduce manual corrections.
Choosing the right pattern
From a practitioner angle, choose your integration pattern based on:
Frequency and volume
Low frequency, flexible volume → EIB.
High frequency, event‑driven → Core Connector: Worker.
Pay‑cycle driven with detailed change history → PECI.
Pay‑cycle driven where snapshot is enough → PICOF.
Data semantics
Do consumers need just current values, or the full change history?
Are they using the feed to run transactions (payroll) or to maintain a reference copy (LMS, IAM)?
Error handling and audit
PECI offers richer visibility into transaction sequences across pay periods.
PICOF is simpler but relies more on external system logic for audit.
Mapping this out in an “integration architecture” diagram helps explain choices to HR, payroll and IT stakeholders.
Practical patterns you can reuse
Some common patterns for moving people data:
HR data to analytics / data warehouse
Use Outbound EIB or report‑based integrations to push worker, org and comp data nightly.
Support ad‑hoc extracts via secured custom reports.
Worker data to downstream HR systems
Configure Core Connector: Worker with event triggers for hires, job changes, terminations.
Use Calculated Fields and XSLT to shape outputs for each consumer.
Global payroll integration
Use PECI to send effective‑dated worker changes per pay group and pay period.
Pair with inbound files that load pay results or statuses back into Workday for reporting.
Bulk corrections or backloads
Use Inbound EIB for one‑time or periodic corrections (for example, mass cost center changes, job code realignments).
For payroll, use PECI’s corrections capabilities where supported to avoid one‑off manual fixes.
These patterns keep integrations consistent and easier to support over time.
Governance, monitoring and “integration hygiene”
Integrations are not “set and forget”. Good tenants treat them like critical infrastructure.
Key practices:
Inventory and ownership
Maintain an inventory listing each EIB, CCW, PECI/PICOF integration, its purpose, schedule, and owner.
Monitoring and alerts
Use Workday’s integration monitoring to track statuses, errors and runtimes.
Set up alerts so failures for payroll‑critical interfaces (PECI/PICOF, CCW to IAM) are acted on immediately.
Change control
Version and test changes to Calculated Fields, field mappings, or triggers carefully; a small change can break downstream files.
Coordinate with vendors when altering PECI/PICOF layouts or logic.
Security
Restrict who can view payloads that contain sensitive PII and comp data.
Ensure SFTP/API endpoints use secure protocols and proper key rotation.
With clear patterns, strong governance and the right tool for each job, moving people data in and out of Workday stops being a risky art and becomes a repeatable discipline. EIB, Core Connector: Worker, PECI and PICOF then work together as part of a coherent integration architecture rather than isolated projects.
Composite Reports Everywhere: A Hidden Workday Problem
If you’ve spent time in a mature Workday tenant, you have probably seen it: a library full of Composite Reports that are slow to run, hard to edit, and understood by only one or two people. Any time someone asks for a new slice of data, the default response seems to be, “Let’s build a Composite.”
This pattern is common, especially in environments where reporting was treated as a “technical” activity instead of a core part of how HR and Finance work. Composite Reports absolutely have their place. But overusing them creates complexity, performance issues, and a real dependency on a small group of “report wizards.”
The real skill in Workday reporting is not knowing how to build the most complex report. It is knowing which report type is the simplest, most sustainable way to answer a business question.
A Quick Reminder: Workday Report Types in Plain Language
Workday provides several report types, each suited to different needs.
Simple reports Great for straightforward lists with basic filters. Think of them as quick views or ad-hoc extracts.
Advanced reports Flexible, support calculated fields, joins, and richer filtering. Most custom reporting needs can be handled here.
Matrix reports Excellent when you want cross-tab views—rows and columns—for comparisons such as headcount by location and time.
Composite reports Designed for complex scenarios: combining multiple report results, multiple time periods, or different business objects into a single output.
Composite Reports are not “better” than other types; they are just more specialized. Treating them as the default option is like using a chainsaw to cut paper.
Why Teams Overuse Composite Reports
There are several reasons why Composite Reports become overused in Workday tenants:
Misunderstanding of report types. Many admins and analysts learn Composite Reports early and assume they are the “advanced” or “professional” choice for all complex needs.
Copy-paste reporting culture. Instead of improving existing advanced or matrix reports, teams clone an old Composite and keep adding logic.
Pressure to deliver quickly. When deadlines are tight, it can feel faster to “just throw everything into one Composite” rather than step back and design a simpler solution.
Lack of reporting strategy. Without clear guidelines on which report type to use when, every new request becomes a one-off decision.
Over time, this leads to a reporting landscape that is powerful, but fragile: if the one person who understands all the Composite Reports leaves, the organization feels stuck.
When a Composite Report Is the Right Choice
Composite Reports are valuable when:
You truly need to combine multiple report results or data sources that are not easy to join in a single advanced report.
You must compare data across multiple time periods in one output.
You need more control over layout, formatting, or multi-section outputs than other report types provide.
Examples include:
Year-end audit reports that combine time, time off, and leave data into one view.
Complex financial statements that compare plan vs actual across multiple structures.
Executive-ready outputs where you want multiple sections, subreports, and formatted layouts.
In these cases, a Composite Report can save time and reduce manual work in Excel by bringing everything into one place.
When Composite Reports Are Overkill
However, many real-world reporting needs do not require a Composite. For example:
A monthly headcount trend by location or cost center.
A list of employees with a specific status and a few key attributes.
A time-off summary by department for a given period.
In these cases, an advanced report, sometimes combined with a calculated field or a matrix view, is usually enough. Overusing Composite Reports here can cause:
Performance issues. Composite Reports often run slower, especially when they reference multiple subreports and large datasets.
Maintenance headaches. Debugging a problem inside a Composite with multiple subreports is much harder than fixing a single advanced report.
Lower adoption. If reports are slow, brittle, or confusingly named, HR and Finance users will avoid them and export data to spreadsheets instead.
A good rule of thumb: if an advanced or matrix report can answer the question, use that first.
A Simple Decision Framework for Report Types
To reduce Composite Report overuse, introduce a simple decision framework for your reporting team:
Start with the question. What business question are we trying to answer? Who is the audience—HR, Finance, leadership?
Try standard reports first. Check whether Workday already delivers a standard report that can be slightly filtered or adjusted.
Use advanced reports for most custom needs. If standard reports are not enough, design an advanced report with clear prompts, calculated fields, and security alignment.
Use matrix reports for comparisons. When the main value is comparing categories (e.g., departments vs months), consider a matrix report.
Reserve Composite for true multi-source or multi-period complexity. Only move to Composite when you genuinely need to combine multiple reports or time slices in ways other report types cannot handle.
This framework alone will prevent many unnecessary Composite Reports from being built.
Designing Reports HR and Finance Will Actually Use
Regardless of report type, the way your reports are designed determines whether HR and Finance teams will trust and use them:
Use prompts instead of hard-coded filters. Allow users to change date ranges, organizations, and other parameters without editing the report definition.
Name reports clearly and consistently. Avoid names like “Composite_Report_3_Final_v2”. Use patterns such as “Headcount – Monthly Trend” or “Time Off Summary – By Department”.
Align security early. Ensure the right people can run the report without raising access tickets every time.
Document the logic. For any complex report, especially Composites, keep a brief design note describing inputs, filters, and key calculations.
These practices make your reporting layer simpler and more resilient, even as your tenant grows in complexity.
Cleaning Up an Existing Composite-Heavy Environment
If your Workday tenant already has “Composite everywhere syndrome,” you can still improve things gradually:
Inventory existing reports. Identify Composite Reports in use and understand which ones are truly needed.
Find candidates for simplification. Look for Composites that could be replaced by one or two advanced or matrix reports.
Refactor slowly, starting with high-impact reports. Focus first on the slowest, most frequently used reports; redesign them using simpler types where possible.
Educate your reporting community. Share your report type guidelines and run short sessions for HR, Finance, and admins on “choosing the right report type.”
Over time, this reduces technical debt and makes it easier for new team members to manage Workday reporting.
Composite Reports as Part of a Balanced Reporting Strategy
Composite Reports are not the villain. They are a powerful tool in the Workday reporting toolbox. The problem is when they are treated as the only tool, or as a shortcut for every complex question.
The goal is a balanced reporting strategy where:
Standard, simple, and advanced reports handle most day-to-day needs.
Matrix reports provide clear comparisons for HR and Finance leaders.
Composite Reports are reserved for genuinely complex, multi-source, or formatted outputs.
When your team chooses report types intentionally, Workday reporting becomes faster, more maintainable, and more trusted. That’s a key step in simplifying Workday for HR and Finance.
Workday dashboards are one of the most visible parts of your analytics experience. Leaders log in, see tiles and charts, and quickly decide whether they trust the system or not. Yet in many tenants, dashboards are treated as a dumping ground for every “important” report rather than as carefully designed decision tools.
If your Workday dashboards are slow, cluttered, or ignored by HR and Finance leaders, the issue is rarely technical. It’s usually a design and intent problem: too many reports, not enough focus, and no clear story.
Dashboards Are Not Just “Report Collections”
A common pattern looks like this: a stakeholder asks for a dashboard, the team gathers a list of “key reports,” and all of them are added to a single page. Over time, more and more tiles appear, each corresponding to another custom report. Soon:
No one remembers which tile is truly important.
Different tiles show similar data with slight variations.
Performance slows because too many complex reports load at once.
Leaders stop clicking into details because they feel overwhelmed.
In other words, the dashboard becomes a cluttered homepage instead of an analytical cockpit.
A true Workday dashboard should be designed around a set of questions and decisions, not around a list of reports you happen to have.
Start with Questions, Not Charts
The most effective dashboards begin with a simple question: “What decisions does this person need to make, and how often?”
For example, an HR leader might need to answer:
Are we on track with headcount and hiring?
Where are we seeing higher turnover or absenteeism?
Which departments need attention this month?
A Finance leader might ask:
How are labour costs trending vs budget?
Which cost centres or companies need a closer look?
Where are there anomalies in overtime or allowances?
Once you have the questions, you can design dashboard sections and tiles that align directly to those decisions instead of randomly combining reports.
Designing Dashboards for Specific Roles
Many Workday tenants have generic “HR Dashboard” or “Finance Dashboard” pages that try to serve everyone at once. A more effective approach is to build dashboards tailored to roles:
HR Director Dashboard – strategic view of headcount, hiring, turnover, and critical risks.
HR Operations Dashboard – focus on transactions, backlogs, SLA compliance, and data quality.
Finance Leader Dashboard – focus on labour costs, budget vs actuals, and key variances.
Talent Acquisition Dashboard – focus on pipeline health, time-to-fill, and recruiter performance.
Each dashboard should contain a small number of high-value tiles, not every report you’ve ever built. This makes it easier for each role to understand what they are seeing and act on it.
Less Is More: Curate Your Tiles
A Workday dashboard with 6–10 well-designed tiles is usually more effective than one with 25 tiles. When curating content:
Prioritise metrics over raw lists. Use charts, KPIs, and summaries for the main view, and let users drill into detailed reports when needed.
Group related tiles. For example, group headcount, hires, and exits together, or labour cost and overtime together, so the story is clear.
Remove low-value tiles. If a tile is rarely opened or no longer used for decisions, retire it. Dashboards should evolve, not accumulate clutter.
Align with how often decisions are made. Monthly or quarterly metrics do not need daily prominence; daily operational metrics might.
This curation step is often skipped but is critical for adoption: people are more likely to use a dashboard that respects their time and attention.
Make Dashboards Actionable, Not Just Interesting
Pretty charts that no one acts on do not justify the effort. For each tile or visual, ask:
What action could someone take based on this?
Does the dashboard make it easy to take that next step?
Some practical tactics to increase actionability:
Link from tiles to relevant tasks or reports. For example, a tile showing “Open Requisitions Past SLA” should link directly to a detailed report where recruiters can triage them.
Use prompts and filters intelligently. Allow users to quickly switch organization, time period, or population without rebuilding the report.
Highlight thresholds and exceptions. Use visual cues (e.g., colours, bands, or markers) to show when a metric is outside the desired range.
The goal is for leaders to move from “interesting chart” to “I know exactly what to do next” in as few clicks as possible.
Performance and Maintenance: The Hidden Costs of Bad Dashboards
Overloaded dashboards do more than just annoy users—they strain your system and your reporting team.
Performance issues Dashboards that load many complex advanced or composite reports at once can become slow, causing timeouts or long waits. Users quickly give up and export data to spreadsheets instead.
Maintenance overhead Each tile points to a report. When you need to change logic or fields, you may have to update multiple reports and tiles across several dashboards. Without a clear design, this becomes error-prone.
Version confusion Multiple tiles showing similar metrics using different report versions create disputes. Stakeholders argue about which tile is “correct” instead of focusing on the insight.
Investing in a clean dashboard design now saves time and frustration later.
A Practical Framework to Redesign Your Dashboards
If you suspect your Workday dashboards are “report dumps,” you can redesign them with a simple framework:
Pick one audience per dashboard. Decide exactly who this dashboard is for and what decisions they make.
List their top 5–10 questions. Work with real users to understand what they truly need to see and how often.
Map each question to 1–2 visuals. Choose charts, KPIs, or tables that answer each question directly.
Limit total tiles and group them. Aim for a clean layout with logical sections and minimal scrolling.
Connect tiles to actions. Ensure users can click through to more detailed reports or relevant tasks from key tiles.
Measure usage and iterate. Monitor which tiles are used, gather feedback, and adjust periodically.
This approach turns dashboards from static collections into living tools that improve over time.
Educating HR and Finance on “Good Dashboard Use”
Finally, dashboard success is not just about design; it is about user behaviour. Help HR and Finance leaders understand:
Which dashboard is “the source of truth” for a given topic.
How often they should review it (daily, weekly, monthly).
What actions they are expected to take based on what they see.
Where to go if they have questions or feedback on metrics.
Short enablement sessions, quick Loom-style walkthroughs, or written guides can go a long way in increasing adoption and trust.
When users see dashboards as trustworthy, focused tools rather than confusing walls of charts, they will log in more often—and rely on Workday rather than offline spreadsheets.
You’ve been tasked with setting up Absence Management in Workday. Your company needs to track vacation, sick leave, and personal time off. Employees need to see accurate balances. Managers need to approve requests. Payroll needs to process time off correctly.
Where do you start?
This guide walks you through the entire Absence Management setup process from blank tenant to fully functional time off tracking. We’ll cover policy decisions, configuration steps, testing procedures, and common pitfalls to avoid.
By the end of this guide, you’ll have a working Absence Management system that employees trust and HR can maintain.
Part 1: Before You Touch Workday
Gather Your Requirements
Don’t start configuring until you’ve answered these questions. Schedule a requirements gathering meeting with stakeholders from HR, Finance, Legal, and Payroll.
Policy Questions to Answer:
1. What types of time off do you offer?
Vacation (Paid Time Off)
Sick Leave
Personal Days
Bereavement Leave
Parental Leave (Maternity/Paternity)
Jury Duty
Military Leave
Sabbatical
Unpaid Leave
Document each type and whether it’s paid or unpaid.
2. How much time off do employees get?
Does everyone get the same amount, or does it vary?
By tenure? (e.g., 15 days for 0-2 years, 20 days for 3-5 years)
By job level? (e.g., executives get more)
By location? (e.g., US vs. UK vs. India)
By employment type? (e.g., full-time vs. part-time)
Create a matrix showing accrual amounts for each employee group.
3. How do employees earn time off?
Monthly accruals? (e.g., 1.25 days per month)
Per pay period? (e.g., 0.577 days every paycheck)
Annual grant? (e.g., 15 days on January 1st)
Continuous accrual? (e.g., 0.0385 days per hour worked)
4. When can new hires start using time off?
Immediately?
After 90 days?
After 6 months?
Do they accrue during the waiting period, or does accrual also wait?
5. What happens to unused time at year-end?
Unlimited carryover?
Capped carryover? (e.g., maximum 5 days)
Use-it-or-lose-it?
Cash-out option?
Grace period to use prior year balance?
6. Are there balance caps?
Can employees accrue indefinitely?
Is there a maximum balance? (e.g., 30 days)
What happens when they hit the cap? (stop accruing until they use time)
7. Can employees go negative?
Can they borrow against future accruals?
How much can they borrow? (e.g., maximum -5 days)
How is the negative balance recovered?
Create Your Policy Document
Based on the answers above, document your policies clearly. Here’s a template:
US Vacation Plan Policy
Eligibility: All US-based regular full-time employees
Accrual Rates:
Years 0-2: 15 days per year (1.25 days per month)
Years 3-5: 20 days per year (1.67 days per month)
Years 6+: 25 days per year (2.08 days per month)
Accrual Method: Monthly on the first day of each month
New Hire Rules:
Accruals begin on hire date
First month accrual is prorated based on days worked
Employees can use time off after completing 90 days of employment
Year-End Rules:
Employees can carry over up to 5 days to the next year
Balances exceeding 5 days are forfeited on December 31st
No cash-out option
Balance Cap: 30 days maximum accrual
Negative Balance: Not allowed
Part 2: Configure Your First Time Off Plan
Let’s configure a complete Vacation plan using the policy above.
Step 1: Access the Create Time Off Plan Task
Log into Workday
In the search bar, type: Create Time Off Plan
Click the task to open it
Step 2: Name Your Plan
Time Off Plan Name: US Vacation Plan
Use clear, descriptive names that include:
Location (US, UK, India)
Type (Vacation, Sick, Personal)
Any distinguishing features (if you have multiple vacation plans)
Plan ID (Reference ID): PLAN-US-VAC
This is your external code for integrations and EIB loads. Use consistent naming conventions:
PLAN-[COUNTRY]-[TYPE]
Example: PLAN-US-VAC, PLAN-UK-SICK, PLAN-IN-PTO
Time Off Type: Vacation
Select from the dropdown. Workday provides standard types. You can create custom types if needed.
Effective Date: January 1, 2025
When does this plan become active? Usually your go-live date or start of fiscal year.
Click OK to create the plan shell.
Step 2.5: Assign Period Schedule (Mandatory)
Every Time Off Plan requires a Period Schedule to define accrual calculation periods.
What is a Period Schedule? A Period Schedule defines the time boundaries for accrual calculations (monthly, quarterly, annually). It determines when accrual periods start and end, which drives when balances update.
Configuration:
From the Edit Time Off Plan screen, navigate to the Calculations tab
Locate Period Schedule field
Select an existing schedule from the dropdown:
Calendar Monthly Period Schedule (most common for monthly accruals)
Fiscal Monthly Period Schedule (if your accruals align with fiscal calendar)
Pay Period Schedule (for per-pay-period accruals)
For this example: Select Calendar Monthly Period Schedule
This schedule defines January 1-31, February 1-28/29, etc. as accrual periods. Accruals will process on the first day of each calendar month.
Creating a Custom Period Schedule (Advanced):
If Workday’s delivered schedules don’t match your needs, you can create custom schedules:
Navigate to Create Period Schedule
Define period start and end dates
Assign to your Time Off Plan
Most implementations use Workday’s delivered Calendar Monthly Period Schedule.
Click OK to save.
Step 3: Configure Accrual Rules
Now you’ll define how employees earn time off. We need three accrual rules (one for each tenure tier).
From the Time Off Plan screen, navigate to the Accruals tab and click Add Accrual Rule.
Accrual Rule 1: First Tier (0-2 Years)
Rule Name: 0-2 Years Tenure
Use descriptive names that explain what the rule does.
Accrual Amount: 1.25
Unit of Time: Days
This means employees earn 1.25 days per accrual period.
Accrual Period: Monthly
Accrual Period Timing: Beginning of Period
Employees accrue on the 1st of each month. Other options include:
End of Period (accrues on last day of month)
Based on Period Schedule Start Date
Tenure Requirement Configuration:
Minimum Tenure: 0 years Maximum Tenure: 2 years
This rule applies to employees from hire date through their second anniversary.
Proration Rules:
Prorate First Period: Yes (checkbox enabled)
If an employee is hired mid-month, prorate their first accrual.
Proration Method: Calendar Days in Period
If Sarah is hired on March 15th:
March has 31 days
Sarah worked 17 days (March 15-31)
First accrual: 1.25 days × (17 ÷ 31) = 0.68 days
Accrual Start Date Calculation Rule: Hire Date
Employees begin accruing on their first day of work. Other options include:
First Day of Month Following Hire
First Day of Pay Period Following Hire
Accrual Cutoff Rule (Advanced): Defines when accruals stop if employment ends mid-period. Common options:
Termination Date (accrue through last day worked)
End of Period (accrue through end of month even if termed mid-month)
For this example, select Termination Date.
Click OK to save the rule.
Accrual Rule 2: Second Tier (3-5 Years)
Click Add Accrual Rule again.
Rule Name: 3-5 Years Tenure
Accrual Amount: 1.67 days
Unit of Time: Days
Accrual Period: Monthly
Accrual Period Timing: Beginning of Period
Minimum Tenure: 3 years Maximum Tenure: 5 years
This rule activates automatically on the employee’s third anniversary.
Proration: Not applicable for tenure tier transitions (no proration needed when transitioning between tiers)
Accrual Start Date Calculation Rule: Tenure Milestone Date (3-year anniversary)
Click OK.
Accrual Rule 3: Third Tier (6+ Years)
Click Add Accrual Rule again.
Rule Name: 6+ Years Tenure
Accrual Amount: 2.08 days
Unit of Time: Days
Accrual Period: Monthly
Accrual Period Timing: Beginning of Period
Minimum Tenure: 6 years Maximum Tenure: Leave blank (applies indefinitely)
Click OK.
You now have three accrual rules configured:
Rule
Tenure
Monthly Accrual
Annual Total
0-2 Years
0-2 years
1.25 days
15 days
3-5 Years
3-5 years
1.67 days
20 days
6+ Years
6+ years
2.08 days
25 days
Step 4: Configure the Waiting Period
Employees accrue from Day 1 but can’t use time off until Day 91. We’ll configure a Usage Waiting Period.
From the Time Off Plan screen, navigate to the Waiting Periods tab and click Add.
Waiting Period Type: Usage Waiting Period
This means employees can see their balance growing but can’t request time off yet.
Alternative option: Accrual Waiting Period (blocks accrual entirely until waiting period ends)
Waiting Period Duration: 90 days
Waiting Period Start Date: Hire Date
Other options include:
First Day of Month Following Hire
First Day of Pay Period Following Hire
Date of Eligibility Event (for benefit-driven waiting periods)
Allow Accrual During Waiting Period: Yes (checkbox enabled)
Employees build their balance during the 90 days.
Example: John hired on January 15th:
February 1: Accrues 0.68 days (prorated January)
March 1: Accrues 1.25 days (balance = 1.93 days)
April 1: Accrues 1.25 days (balance = 3.18 days)
April 15 (Day 91): Waiting period ends, John can now request time off
Click OK to save.
Step 5: Configure Carryover Rules
Employees can carry over up to 5 days. Excess is forfeited.
From the Time Off Plan screen, navigate to the Carryover tab and click Add Carryover Rule.
Carryover Type: Capped
Maximum Carryover Amount: 5 days
Carryover Calculation Date: Based on Balance Period End Date
The Balance Period End Date is defined in your Period Schedule (typically December 31 for calendar year plans).
What Happens to Excess: Forfeit
Balances above 5 days are lost.
Carryover Transfer Method: Automatic
Workday automatically processes carryover on the Balance Period End Date.
Example: Sarah’s balance on December 31, 2024:
Total balance: 18 days
On January 1, 2025:
Carried over: 5 days
Forfeited: 13 days
New starting balance: 5 days (will accrue normally throughout 2025)
Optional: Carryover Expiration (Grace Period)
Enable Carryover Expiration: Yes (checkbox)
Carryover Expiration Date: March 31 of following year
If enabled, employees must use carried-over days by March 31st or they forfeit.
For this example, leave unchecked (no expiration on carried-over days).
Click OK to save.
Step 6: Configure Balance Upper Limit
Stop accruals when employees reach 30 days to prevent excessive hoarding.
From the Time Off Plan screen, navigate to the Calculations tab.
Unit: Days (or Hours if you track time off in hours)
Accrual Behavior When Limit Reached: Stop accruals until balance drops below limit
Alternative option: Continue accruing but cap balance at limit (excess accruals are forfeited)
Resume Accruals When Balance Falls Below: 30 days
Example: Mike has 30 days of vacation (at the cap). On June 1st, he doesn’t accrue his normal 1.25 days because he’s at the cap. In August, he takes a 10-day vacation. His balance drops to 20 days (below the cap). On September 1st, he resumes accruing 1.25 days per month.
Click OK to save.
Step 7: Configure Eligibility Rules
Define who gets assigned to this plan.
From the Time Off Plan screen, navigate to the Eligibility tab and click Add Eligibility Rule.
Eligibility Rule Name: US Full-Time Employees
Eligibility Criteria:
Use the condition builder to define who qualifies:
Condition 1: Location = United States (any US location) AND Condition 2: Worker Type = Employee (exclude contractors) AND Condition 3: Time Type = Full-Time (exclude part-time)
Assignment Method: Automatic
Workday automatically assigns workers who meet the criteria.
Assignment Effective Date: Hire Date
The plan assigns to new hires on their first day.
Assignment Event: Hire (trigger assignment on hire event)
What about workers hired before the plan effective date?
If you’re implementing Workday mid-year with existing employees, you’ll need to load opening balances separately (covered in Part 4).
Click OK to save.
Step 8: Enable Team Absence Calendar Visibility (Optional)
Allow approved time off to appear on team calendars for coverage planning.
From the Time Off Plan screen, navigate to the Display tab.
Visible for Team Absence: Yes (checkbox enabled)
This makes approved time off visible on:
Manager’s team calendar
Department absence calendar (if configured)
Organization absence calendar
Time Off Display Color: Select a color (e.g., blue for vacation, green for sick leave)
This helps differentiate time off types on visual calendars.
Click OK.
Step 9: Review and Activate
Your US Vacation Plan is now fully configured. Review the summary screen:
✅ Period Schedule: Calendar Monthly assigned ✅ Accrual Rules: 3 tenure tiers configured ✅ Waiting Period: 90-day usage wait ✅ Carryover: 5 days max ✅ Balance Upper Limit: 30 days ✅ Eligibility: US Full-Time Employees ✅ Team Absence Visibility: Enabled
Click Submit to save the Time Off Plan.
Part 3: Test Before You Deploy
Never roll out a Time Off Plan without testing. Create test employees and validate calculations.
Test Scenario 1: New Hire on First of Month
Test Case: Employee hired January 1, 2025
Expected Results:
February 1: Balance = 1.25 days
March 1: Balance = 2.50 days
April 1: Balance = 3.75 days
April 2: Can request time off (90-day wait over)
How to Test:
Create a test employee with hire date January 1, 2025
Assign to US Vacation Plan
Navigate to View Time Off for the employee
Check Accrual History tab
Validate balance on February 1 matches expected (1.25 days)
Try to submit Request Time Off on January 15 (should be blocked by waiting period)
Try to submit Request Time Off on April 2 (should be allowed)
Test Scenario 2: Mid-Month Hire (Proration)
Test Case: Employee hired March 15, 2025
Expected Results:
April 1: Balance = 0.68 days (prorated: 1.25 × 17/31)
May 1: Balance = 1.93 days (0.68 + 1.25)
June 1: Balance = 3.18 days (1.93 + 1.25)
June 14: Can request time off (90 days after March 15)
How to Test:
Create test employee hired March 15, 2025
Navigate to View Time Off
Check Accrual History on April 1
Validate proration calculation: 1.25 × (17 days worked ÷ 31 days in March) = 0.68 days
Confirm waiting period calculation (90 days from March 15 = June 13)
Test Scenario 3: Tenure Tier Transition
Test Case: Employee hired January 1, 2022 (approaching 3-year anniversary)
Expected Results:
December 2024: Accruing 1.25 days/month (Tier 1: 0-2 years)
January 1, 2025: Transitions to Tier 2 (3 years tenure)
February 2025: Accrues 1.67 days/month (Tier 2: 3-5 years)
How to Test:
Create test employee with backdated hire date January 1, 2022
Navigate to View Time Off
Check Accrual History for December 2024 (should show 1.25 days)
Check January 2025 accrual (should NOT show accrual on January 1 because that’s the exact transition date)
Check February 1, 2025 (should show 1.67 days accrued at new Tier 2 rate)
Important: Workday transitions to the new tier on the anniversary date, but the first accrual at the new rate occurs on the next scheduled accrual date (February 1 in this case).
Test Scenario 4: Balance Upper Limit
Test Case: Employee with 28 days accrued takes no vacation
Expected Results:
June 1: Balance = 28 days, accrues 1.25 → balance = 29.25 days
July 1: Balance = 29.25 days, accrues 1.25 → balance = 30 days (at cap)
August 1: Balance = 30 days, no accrual (capped)
Employee takes 5 days off → balance = 25 days
September 1: Accrues 1.25 days → balance = 26.25 days (cap no longer blocking)
How to Test:
Create test employee
Navigate to Enter Time Off Event
Manually add balance to 28 days using Balance Adjustment
Run accrual calculation (or wait for scheduled accrual processing)
Verify cap behavior in View Time Off > Accrual History
Test Scenario 5: Year-End Carryover
Test Case: Employee with 18 days balance on December 31
Expected Results:
January 1: Balance = 5 days (carried over)
Forfeited: 13 days
How to Test:
Create test employee with 18 days balance (use Enter Time Off Event to set balance)
Run Process Time Off Carryover task for year-end
Check balance on January 1
Navigate to View Time Off > Balance History
Verify:
Carryover event showing +5 days
Forfeiture event showing -13 days
New starting balance = 5 days
Record Your Test Results:
Test Scenario
Expected
Actual
Pass/Fail
Notes
New hire Feb 1 accrual
1.25 days
1.25 days
✅ Pass
Mid-month hire proration
0.68 days
0.68 days
✅ Pass
Tenure tier transition
1.67 days
1.67 days
✅ Pass
Transitions Feb 1, not Jan 1
Balance cap at 30 days
Stop accruing
Stopped
✅ Pass
Carryover 18 → 5 days
5 days
5 days
✅ Pass
All tests pass? You’re ready to deploy.
Part 4: Build Additional Time Off Plans
Once your Vacation plan works perfectly, replicate the pattern for other time off types.
Sick Leave Plan
Key Differences from Vacation:
No Waiting Period: Employees can use sick leave immediately
Unlimited Carryover: Most sick leave plans allow unlimited carryover
Higher Balance Upper Limit: 60-90 days typical
Configuration Steps:
Navigate to Create Time Off Plan
Name: US Sick Leave Plan
Time Off Type: Sick
Period Schedule: Calendar Monthly Period Schedule
Accrual Rule:
Accrual Amount: 1 day
Accrual Period: Monthly
Accrual Period Timing: Beginning of Period
No tenure tiers (everyone accrues 12 days annually)
Waiting Period: None (delete or don’t configure)
Carryover:
Carryover Type: Unlimited (or very high cap like 999 days)
No forfeiture
Balance Upper Limit: 60 days
Eligibility: Same as vacation (US Full-Time Employees)
Team Absence Visibility: Typically disabled for sick leave (privacy)
Personal Days Plan
Typical Configuration:
Annual Grant: 3-5 days per year (granted on January 1st, not monthly accrual)
Configuration:
Name: US Personal Days Plan
Time Off Type: Personal
Period Schedule: Calendar Yearly Period Schedule (not monthly)
Accrual Rule:
Accrual Method: Annual Grant
Accrual Amount: 3 days
Accrual Period: Yearly
Accrual Period Timing: Beginning of Period (January 1)
New Hire Proration: Yes
If hired in July, prorate: 3 days × (6 months remaining ÷ 12 months) = 1.5 days
Waiting Period: None (or 90 days if company policy requires)
Carryover: None (use-it-or-lose-it by December 31)
Balance Upper Limit: 3 days (can’t exceed annual grant)
Eligibility: US Full-Time Employees
Note: For annual grant plans, employees receive their full year allocation on January 1st (or prorated amount on hire date), not monthly accruals.
Unpaid Leave Plan
Configuration:
Name: Unpaid Leave Plan
Time Off Type: Unpaid
Period Schedule: Not required (no accruals)
Accrual Rules: None (no accruals, request-based only)
Waiting Period: None
Carryover: Not applicable (no balance to carry over)
Balance Upper Limit: Not applicable
Eligibility: All employees
Approval: Manager approval required (configure in Request Time Off business process)
How It Works: Employees submit time off requests for unpaid leave. No balance tracking occurs. Manager approves based on business need. When approved, the absence is processed by payroll as unpaid time.
Part 5: Configure the Request Time Off Workflow
Time Off Plans define balances and accruals. The Request Time Off Business Process defines how employees actually use their time off.
Step 1: Navigate to the Business Process
Search for View Business Process
Type: Request Time Off
Click to open the Business Process configuration
Step 2: Configure Security (Who Can Request)
Scroll to Security Policy Configuration and click Edit.
Initiators (Who Can Submit Time Off Requests):
Employee as Self (employees request their own time off)
Manager (managers can request time off on behalf of their team)
HR Partner (HR can submit requests for workers in their assigned orgs)
Approvers (Who Can Approve Steps):
Configure in process steps (next section)
Viewers (Who Can View Requests):
Employee as Self (see their own requests)
Manager (see their team’s requests)
HR Partner (see all requests in their assigned orgs)
Cancel/Rescind Permissions:
Rescind: Employee as Self (workers can cancel their own requests before approval)
Cancel: Manager, HR Partner (managers and HR can cancel requests after approval)
Click OK to save.
Step 3: Configure Approval Routing
Click Edit Process (or Configure button) to configure workflow steps.
Step 1: Manager Approval
Click Add Step.
Step Type: Approval
Step Name: Manager Approval
Assignee Type: Manager
Routing: Supervisory Organization Manager
This routes to the employee’s direct manager based on their Supervisory Organization assignment.
Due Date: 3 business days
Manager has 3 days to approve or deny.
Allow Delegation: Yes (checkbox enabled)
If manager is out of office, they can delegate to another manager.
Step Required: Yes (transaction cannot complete without this approval)
Click OK to save the step.
Step 2: Notification to Employee (Approved)
Click Add Step.
Step Type: Notification
Step Name: Notify Employee – Approved
Assignee: Initiator (the employee who requested time off)
Step Activation Criteria: Configure conditions: Only execute this step if Manager Approval step result = Approved
Notification Method: Email
Email Template: Use Workday default template or create custom template
Email Subject: “Your Time Off Request Was Approved”
Email Body: Include approved dates, time off type, remaining balance
Click OK.
Step 3: Notification to Employee (Denied)
Click Add Step.
Step Type: Notification
Step Name: Notify Employee – Denied
Assignee: Initiator
Step Activation Criteria: Configure conditions: Only execute if Manager Approval step result = Denied
Notification Method: Email
Email Subject: “Your Time Off Request Was Denied”
Email Body: Include denial reason, instructions to contact manager
Amount depends on tenure (15, 20, or 25 days per year)
New hires: accruals start immediately, can use after 90 days
Sick leave accrues 1 day per month, can use immediately
4. What happens at year-end
Maximum 5 days carryover to next year
Balances exceeding 5 days forfeit on December 31st
Plan vacation accordingly (use November/December to burn excess)
5. Using Workday Assistant
Type natural language queries in the search bar:
“What’s my vacation balance?”
“Request 3 days off next week”
“Show my team’s time off calendar”
Workday Assistant launches the appropriate task automatically.
Training Delivery Methods:
Email announcement with screenshots and step-by-step instructions
Live webinar or recorded video tutorial
Quick reference guide (1-page PDF)
Office hours for questions (first two weeks after go-live)
Manager Training
What Managers Need to Know:
1. How to approve time off requests
Check inbox for Time Off Request approval tasks:
Review requested dates
Check team calendar for coverage conflicts
Approve or deny with clear explanation
Managers can approve/deny from:
Email notification (click approve/deny link)
Workday inbox (Approval Tasks)
Workday mobile app
2. How to view team balances
Navigate to Team Time Off Balances:
See all team members’ current balances
Identify employees with high balances (encourage them to take time off)
Plan coverage for scheduled absences
3. How to view team absence calendar
Navigate to Team Absence Calendar:
Visual calendar showing all approved time off
Filter by team member, time off type, date range
Identify coverage conflicts before approving new requests
4. How to handle delegation
When going on vacation, delegate approvals to another manager:
Navigate to Delegate Workday Tasks
Select tasks to delegate (e.g., Approve Time Off)
Select delegate (backup manager)
Set date range (your vacation dates)
Delegated manager receives approval tasks during your absence
Training Delivery:
Manager webinar (separate from employee training)
Hands-on practice in sandbox tenant
Manager quick reference guide
One-on-one coaching for new managers
Part 8: Month-End Monitoring
After go-live, monitor Absence Management closely for the first few months.
Week 1 Checklist
✅ Run Time Off Balances report for all employees ✅ Spot-check 20 employees (various hire dates, tenure levels) ✅ Validate balances match expected calculations:
New hires: prorated first accrual correct?
Mid-tenure employees: accruing at correct rate?
Senior employees: correct tenure tier applied?
✅ Investigate zero balances or incorrect amounts:
Is employee assigned to correct Time Off Plan?
Did accrual process run successfully?
Is waiting period blocking accruals?
✅ Check that waiting periods are working correctly:
Can new hires under 90 days request time off? (should be blocked)
Test with sample requests
Week 2 Checklist
✅ Review Outstanding Business Processes for stuck requests:
Navigate to Business Process History
Filter for Time Off Request processes
Check for processes stuck in approval step
✅ Validate requests routing to correct managers:
Sample 10 recent requests
Verify they routed to worker’s Supervisory Organization manager
Send brief survey: “How is Absence Management working for you?”
Common pain points? Confusing features?
Use feedback to improve training and documentation
✅ Document lessons learned for future improvements:
What configuration issues surfaced?
What training gaps exist?
What would you do differently next time?
Part 9: Troubleshooting Common Issues
Issue: Employee Balance Shows Zero
Symptoms: Employee checks balance, sees 0.00 days despite being employed for several months.
Debug Steps:
Step 1: Check Plan Assignment
Navigate to View Time Off for the employee
Look for Plan Assignments section
Is the employee assigned to the correct Time Off Plan?
If No plan assigned: Eligibility rule may not match employee
If Wrong plan assigned: Eligibility rule needs correction
Step 2: Check Accrual History
In View Time Off, navigate to Accrual History tab
Has any accrual processed?
If No accruals at all: Check accrual start date configuration
If Accruals stopped: Check balance upper limit (may be capped)
Step 3: Review Accrual Start Date
Navigate to Edit Time Off Plan > Accruals tab
Check Accrual Start Date Calculation Rule
If set to “First Day of Month Following Hire,” employee hired March 15 doesn’t accrue until April 1
Change to “Hire Date” if you want immediate accrual
Step 4: Check Waiting Period
In Edit Time Off Plan, check Waiting Periods tab
Is there an Accrual Waiting Period (blocks accrual entirely)?
If yes, employee won’t accrue until waiting period ends
Change to Usage Waiting Period to allow accrual but block usage
Resolution:
If not assigned, check eligibility rule criteria (Location, Worker Type, Time Type)
If accrual start date wrong, correct in plan configuration or manually adjust balance
If waiting period blocking, inform employee when accruals will start
Issue: Accrual Amount Incorrect
Symptoms: Employee accrued 0.85 days but policy says 1.25 days per month.
Debug Steps:
Step 1: Calculate Expected Accrual Manually
Example: Employee hired March 15, 2025
March has 31 days
Employee worked 17 days (March 15-31)
Expected first accrual (if prorated): 1.25 days × (17 ÷ 31) = 0.68 days
Step 2: Check Actual Accrual
Navigate to View Time Off > Accrual History
Check accrual amount on April 1
Does it match expected calculation?
Step 3: Review Proration Settings
Navigate to Edit Time Off Plan > Accruals tab
Select the accrual rule
Check:
Prorate First Period: Is it enabled?
Proration Method: Is it “Calendar Days in Period”?
Other methods: “Pay Period Days,” “Custom Formula”
Step 4: Check Period Schedule
Navigate to View Period Schedule (the one assigned to your Time Off Plan)
Verify period boundaries:
Does March period run March 1-31?
Or does it run March 16-April 15? (could cause unexpected proration)
Resolution:
Correct proration configuration if wrong
Manually adjust balance if needed using Enter Time Off Event (Balance Adjustment)
Document resolution for future reference
Issue: Employee Can’t Request Time Off
Symptoms: Employee tries to submit Request Time Off, receives error or validation message.
Debug Steps:
Step 1: Check Available Balance
Navigate to View Time Off for the employee
Check Available Balance (not Total Balance)
Available Balance = Total – Scheduled – Pending
Does employee have enough available balance for the request?
Example: Employee has:
Total Balance: 10 days
Scheduled (approved future vacation): 7 days
Pending (awaiting approval): 2 days
Available Balance: 10 – 7 – 2 = 1 day
Employee tries to request 3 days → Workday rejects (only 1 day available).
Step 2: Check Waiting Period
Navigate to View Time Off > Plan Assignments
Check Waiting Period Status
Has usage waiting period ended?
If employee hired April 1, waiting period = 90 days
Waiting period ends June 30
Employee cannot request time off until July 1
Step 3: Check Business Process Security
Navigate to View Business Process > Request Time Off
Check Security Policy Configuration > Initiators
Can employee initiate Request Time Off?
Should include Employee as Self security group
If missing, add and activate pending security policy changes
Step 4: Check for Blackout Dates
Navigate to Edit Time Off Plan > Restrictions tab (if applicable)
Are there blackout dates configured?
Example: December 20-31 blocked for year-end processing
Employee trying to request time during blackout → rejected
Resolution:
If insufficient balance, explain available balance calculation to employee
If waiting period active, inform employee when they can request (waiting period end date)
If security issue, grant appropriate permissions and activate
If blackout dates, employee must select different dates
Issue: Carryover Didn’t Process Correctly
Symptoms: December 31 passed, but employee balances didn’t carry over (or carried over incorrectly).
Debug Steps:
Step 1: Verify Carryover Rule Configuration
Navigate to Edit Time Off Plan > Carryover tab
Check:
Carryover Type: Capped, Unlimited, or None?
Maximum Carryover Amount: Correct? (e.g., 5 days)
Carryover Calculation Date: Based on Balance Period End Date
Step 2: Check Period Schedule End Date
Navigate to View Period Schedule (assigned to your Time Off Plan)
Check Balance Period End Date
For calendar year plans, should be December 31
For fiscal year plans, might be June 30 or September 30
Carryover processes on this date
Step 3: Check if Carryover Process Ran
Navigate to View Time Off for affected employees
Check Balance History tab
Look for carryover events on January 1:
“Carryover from Prior Year” (+5 days)
“Year-End Forfeiture” (-13 days)
If no carryover events, process didn’t run
Step 4: Manually Process Carryover (If Needed)
Navigate to Process Time Off Carryover task
Select the Time Off Plan
Select the Balance Period End Date (December 31, 2024)
Click OK to run carryover calculation
Resolution:
If carryover rule was missing, add it and manually process carryover
If carryover cap was wrong, correct and reprocess
If process didn’t run automatically, investigate scheduled job configuration
Communicate with affected employees about corrected balances
Part 10: Advanced Configuration Scenarios
Scenario 1: Allow Negative Balances (Borrowing)
Some companies let employees borrow against future accruals (go negative).
Business Case: New hire plans a vacation 60 days after starting. Has only accrued 2 days. Needs 5 days. Allow them to borrow 3 days, which will be recovered through future accruals.
Configuration:
Navigate to Edit Time Off Plan > Calculations tab
Scroll to Balance Lower Limit section
Enable Balance Lower Limit: Yes (checkbox)
Minimum Balance (Lower Limit): -5 days
Recovery Method: Automatic (future accruals repay the debt)
How It Works:
Employee has 2 days accrued
Requests 7 days off
Balance goes to -5 days (borrowed 5 days)
Over next 4 months, monthly accruals (1.25 days each) repay the negative balance:
Month 1: -5 + 1.25 = -3.75
Month 2: -3.75 + 1.25 = -2.50
Month 3: -2.50 + 1.25 = -1.25
Month 4: -1.25 + 1.25 = 0
Month 5: Normal accruals resume (0 + 1.25 = 1.25)
Use Case: Common for new hires with pre-planned vacations (weddings, family commitments).
Scenario 2: Different Plans for Different Locations
US employees get 15-25 days (tenure-based). UK employees get 28 days (statutory minimum).
Configuration:
Plan 1: US Vacation Plan
Eligibility: Location = United States
Accrual: 15-25 days annually (tenure-based tiers)
Accrual Method: Monthly
Carryover: Maximum 5 days
Plan 2: UK Holiday Plan
Eligibility: Location = United Kingdom
Accrual: 28 days annually
Accrual Method: Annual Grant (all 28 days granted January 1)
No tenure tiers (statutory minimum applies to all)
Carryover: None (use-it-or-lose-it by December 31, per UK custom)
Note: Some UK employers allow unlimited carryover
Each employee automatically gets assigned to the correct plan based on their Location field.
Testing: Create test employees in both US and UK locations, verify correct plan assignment.
Scenario 3: Part-Time Proration by FTE
Part-time employees get prorated time off based on FTE (Full-Time Equivalency).
Example: 0.5 FTE employee gets 50% of full-time vacation accrual.
Configuration Option 1: Separate Plan
Create: US Vacation – Part-Time Plan
Accrual Amount: 0.625 days/month (50% of full-time 1.25 days)
Eligibility: Time Type = Part-Time AND FTE = 0.5
Pros: Simple, clear separation Cons: Need separate plans for each FTE level (0.5, 0.6, 0.75, etc.)
Accruals based on actual hours worked (from timesheets)
No accrual if employee doesn’t work (unpaid leave)
Final Checklist: Is Your Absence Management Ready?
Before you declare Absence Management “done,” verify:
✅ All Time Off Plans configured (Vacation, Sick, Personal, etc.) ✅ Period Schedules assigned to all plans ✅ Accrual rules tested (new hires, mid-month, tenure transitions, proration) ✅ Waiting periods working (employees can’t use time too early) ✅ Carryover rules tested (year-end simulation completed, balances carry over correctly) ✅ Balance Upper Limits working (employees stop accruing at cap) ✅ Eligibility rules correct (right employees assigned to right plans) ✅ Request Time Off workflow tested (approval routing works, notifications send) ✅ Team Absence Calendar visibility configured (approved time off visible for planning) ✅ Historical balances migrated (legacy balances loaded and validated) ✅ Employees trained (know how to check balance, request time, use Workday Assistant) ✅ Managers trained (know how to approve, view team calendar, delegate tasks) ✅ Monitoring in place (weekly balance checks, request tracking, issue escalation process) ✅ Integration with Payroll tested (time off flows to payroll correctly, earnings codes mapped) ✅ Documentation complete (configuration guide, training materials, troubleshooting runbook)
What You’ve Accomplished
If you’ve followed this guide, you now have:
Fully configured Time Off Plans for each time off type with proper Period Schedules
Accurate accrual calculations that handle tenure, proration, and balance upper limits
Carryover rules that protect balances or enforce use-it-or-lose-it policies based on Balance Period End Dates
Working approval workflows that route to managers and notify employees via email
Team Absence Calendar visibility for coverage planning
Migrated historical balances from your legacy system
Trained users who understand how to request and approve time off using Workday Assistant
Monitoring processes to catch issues early
Your employees can now check their balances with confidence. Managers can approve time off knowing coverage is planned. Payroll can process leave accurately using mapped earnings codes. And HR isn’t buried in manual balance adjustments.
That’s a successful Absence Management implementation.
Every Workday tenant reaches the same point: the delivered reports are not enough, spreadsheets are multiplying, and leaders want real‑time answers to tough HR questions. Workday’s reporting stack – from Simple to Composite Reports, powered by Calculated Fields – is designed to solve exactly that, if you treat it like a reporting architecture instead of a random collection of custom reports.
This playbook walks through when to use each report type and which Calculated Fields almost every HR tenant should build.
Know your Workday report types
Workday offers multiple custom report types, each built on a Business Object such as Worker, Position, Organization or Job Application.
At a minimum, understand these:
Simple Reports
Best for basic lists on a single business object (for example, workers with key fields).
Limited filtering and no advanced joins, but quick to build and great for operational lists.
Advanced Reports
Your main workhorse for HR analytics.
Support complex filters, multiple prompts, sub‑filters and usage of most Calculated Fields.
Matrix Reports
Pivot‑style reports with row and column groupings, aggregations and charts.
Great for headcount by org, diversity metrics, or comp by grade and location.
Composite Reports
Bring together multiple Matrix (and related) reports into one output for multi‑period or multi‑subject analytics.
Ideal for dashboards, trend analysis and cross‑domain insights (for example, headcount + turnover + internal movement).
The rule of thumb:
Start with Simple for quick, one‑object lists.
Move to Advanced for “real” HR reporting.
Use Matrix when you want to slice and aggregate.
Use Composite when you want to tell a story across time or subject areas.
Design a layered reporting approach
Instead of dozens of one‑off reports, design a layered approach:
Operational layer (Simple / Advanced)
Examples: “Active Workers”, “Open Positions”, “Pending Hires”, “Workers on Leave”.
Used daily by HR operations and HRBPs.
Analytics layer (Advanced / Matrix)
Examples: “Headcount and FTE by Org”, “Turnover by Manager and Tenure”, “Comp by Grade and Gender”.
Executive layer (Composite + Dashboards)
Executive dashboards built on Composite Reports combining key metrics and trends.
Examples: Workforce overview, diversity scorecard, HC cost and movement.
By reusing the same core datasets as sub‑reports (Advanced/Matrix) inside Composite Reports, you keep logic consistent and easier to maintain.
Calculated Fields: your secret reporting weapon
Calculated Fields (CFs) are where Workday reporting becomes powerful. They let you transform, derive and combine data without code.
Common types include:
Date Calculations – tenure, age, days since event.
Text Fields – concatenated names, formatted IDs.
Boolean / Conditional – true/false flags like “Is Terminated?”, “Is Manager?”, “Is High Risk?”.
Lookup and Related Object – pull attributes from related business objects (for example, worker’s manager’s organization).
Aggregations – counts, sums, minima/maxima across related data.
Think of Calculated Fields as your reusable logic library: build once and use across reports, dashboards and even integrations.
Essential HR calculated fields every tenant should have
While specifics vary, most HR tenants benefit from a core set of Calculated Fields on the Worker and related objects. Examples:
Worker Tenure
Business case: segment turnover, eligibility, and recognition.
CF type: Date difference between Hire Date (or Original Hire) and Current Date, expressed in years/months.
Age and Age Band
Business case: workforce demographics and eligibility (for certain benefits or policies).
CF type: Date difference between Birth Date and Current Date, plus a conditional field assigning bands (e.g., “<30”, “30–39”, etc.).
Headcount Flag
Business case: define what counts as “headcount” in your reports.
CF type: Boolean that returns “True” only for Active, non‑contingent workers meeting your criteria.
Termination Risk Window
Business case: track leavers by tenure or after certain events.
CF type: Conditional on Termination Date minus Hire Date or last event.
Manager Chain Attributes (for example, “Top‑Level Organization”, “Level‑2 Manager Name”)
Business case: slice reports cleanly by different leadership levels.
CF type: Related Business Object / Lookup fields walking up the supervisory hierarchy.
Diversity Attributes (normalized)
Business case: DEI reporting with consistent categories.
CF type: Text or Conditional to map raw demographic fields into standard buckets used in analytics.
Each of these can be reused in Advanced, Matrix and Composite reports, which avoids re‑implementing logic in filters or Excel.
From Simple to Composite: practical HR examples
To make the progression tangible, consider a common HR need: headcount and turnover by organization over time.
Step 1 – Simple Report
Build a “Workers – Current Snapshot” Simple report listing Active workers with org, job and location.
Step 2 – Advanced Reports
Create an Advanced report “Headcount by Org and Month” using Effective Date prompts and your Headcount Flag CF.
Create another Advanced report “Terminations by Org and Month” using the terminations data source and a tenure CF.
Step 3 – Matrix Reports
Convert each into a Matrix report to group by Org (rows) and Month (columns), with counts as measures.
Step 4 – Composite Report
Build a Composite report that combines the two matrix reports into a single output with headcount, terms and turnover rate.
Use formatting and sections so leaders see a clean summary plus drill‑downs.
Now you have a reusable HR analytics asset instead of ad‑hoc Excel snapshots. The same pattern works for internal mobility, learning impact or compensation analytics.
Security and performance: silent success factors
Two often overlooked aspects of reporting success are report security and performance.
Report/Data Source Security
Ensure report writers have the right Report Writer and domain permissions, but limit access to sensitive data.
Use Workday security to ensure managers see only their teams; avoid hard‑coding security filters into reports where possible.
Performance
Avoid unnecessary fields and prompts; each join and CF can add load time.
Use prompts for date ranges and organizations to reduce dataset size for big reports.
Where possible, reuse CFs instead of building “report‑specific” ones that duplicate logic.
Good security and performance make reports usable in real life – otherwise, people will export data and go back to spreadsheets.
Building your HR reporting playbook
Treat Workday reporting like a product with its own playbook:
Document core reports (Simple, Advanced, Matrix, Composite) and their purpose: who uses them, how often, for what decisions.
Maintain a Calculated Field catalog with ownership, description and examples. This prevents duplication and confusion.
Provide basic training for HRBPs and analysts on report types, prompts and how to export responsibly instead of rebuilding Excel every time.
When you design HR reporting in Workday as an intentional architecture – moving from Simple to Composite reports, powered by a curated set of Calculated Fields – your tenant stops being just a transaction system and becomes a true analytics platform for people decisions.
Workday Gives You Many Fields. The Question Is: Which Ones Matter?
One of the first surprises for new Workday project teams is just how many fields are available in the system. For almost any object—workers, positions, jobs, organizations, transactions—Workday provides a large set of standard fields plus the option to add custom ones. It can feel like standing in front of a giant buffet: everything looks useful, and it is tempting to take a bit of everything.
But in daily use, the opposite is true. HR and Finance users do not want every possible field. They want the right fields, in the right places, with clear labels and obvious value. When every screen is full of optional fields that no one understands, Workday starts to feel heavy and complicated instead of helpful.
The Risk of “Collect Everything” Thinking
During implementation, it is common for project teams to hear requests like:
“Let’s capture this field, we might need it later.”
“Legal might ask for this data one day.”
“Our legacy system had this field, so we should bring it over.”
Individually, each request sounds reasonable. Together, they create:
Crowded data entry pages where users scroll past dozens of fields they never touch.
Inconsistent data because some fields are optional and rarely filled in correctly.
Confusing reports that include fields no one knows how to interpret or trust.
Instead of being a clean, focused system, Workday becomes a mirror of every “just in case” decision made during implementation.
A Better Question: What Decisions Will This Field Support?
A more effective way to choose which fields to use is to start from decisions, not from the system’s capabilities. For each field you are considering, ask:
Which business decision does this field help us make?
Who will use this data, and how often?
What happens if we do not capture it?
Can we get this information from another trusted source instead?
If a field does not clearly support a decision, a process, or a legal requirement, you should question whether it is worth adding to every screen, task, and report.
Designing Workday Pages for Real Users
Remember that most HR and Finance users interact with Workday through specific tasks and pages, not through configuration screens. Page layout, field order, and visual clarity matter as much as which fields are technically available.
When designing pages:
Prioritize essential fields at the top. Make sure the fields that must be filled in for a process to work are clearly visible and easy to understand.
Group related fields together. Keep job-related fields, compensation fields, and organizational fields grouped so they make sense in context.
Hide or collapse rarely used fields. If a field is only relevant in special cases, consider collapsing it into an expandable section or removing it from most users’ view.
Use clear labels and help text. If a field is not self-explanatory, add short help text that describes when and how it should be used.
The goal is to make Workday tasks feel quick and focused, not like filling out endless forms.
Balancing Standard and Custom Fields
Workday standard fields cover a wide range of typical HR and Finance needs. However, every organization has unique data requirements, which is where custom fields come in. The danger is adding custom fields for every request without thinking about long-term maintenance.
To balance standard and custom fields:
Use standard fields whenever they reasonably fit. Standard fields are more likely to be supported in delivered reports, updates, and integrations.
Create custom fields only when there is a clear, ongoing use case. For example, tracking a specific internal classification that truly matters for reporting or compliance.
Review custom fields regularly. Remove or retire fields that are no longer used or that have been replaced by better structures.
This reduces clutter and helps keep your data model understandable for both current and future admins.
Field Governance: Small Rules, Big Impact
You do not need a complex governance framework to manage fields effectively. A few simple rules can dramatically improve your Workday experience:
Approval for new fields. Require a short justification (what decision it supports, who will use it) before adding new custom fields.
Clear ownership. Assign an owner for important fields, especially those that drive reporting and compliance.
Standards for naming and help text. Use consistent naming patterns and simple language so users can quickly understand what each field means.
Periodic cleanup. Schedule regular reviews to identify fields that are unused or duplicated and decide whether to hide, retire, or consolidate them.
These practices turn field management from a one-time implementation activity into an ongoing, controlled process.
Helping HR and Finance See the Value in Fields
Fields are not just boxes to fill in; they are commitments of time and attention from HR, Finance, and other business users. To get buy-in, show them how fields connect to outcomes they care about:
Better headcount or cost reports.
Faster approvals and fewer errors.
More reliable analytics for planning and budgeting.
Easier compliance and audit reporting.
When users understand why a field exists and how it is used, they are more likely to enter accurate data and less likely to complain about “yet another thing to fill in.”
Simplifying Workday by Designing Fields Intentionally
Workday’s flexibility is powerful, but without intentional design, that flexibility can become noise. Instead of asking, “How many fields does Workday give us?” the better questions are:
Which fields do our HR and Finance teams actually need on screen?
Which fields support critical decisions and reporting?
How can we keep pages clean, consistent, and easy to use?
By choosing, designing, and governing fields carefully, you turn Workday from a complex data collection tool into a clear, focused system that truly supports your people and processes. That is a key part of simplifying Workday for HR and Finance.
A frictionless recruiting funnel in Workday starts long before the first candidate applies. It starts with how you design Job Requisitions, Job Posts and your Recruiting Business Processes so recruiters and hiring managers never have to fight the system. When those foundations are weak, pipelines stall at approvals, candidates get stuck in stages and reporting becomes impossible to trust. When they are strong, Workday Recruiting feels like a single, end-to-end engine from “Create Job Requisition” to Hire.
This blueprint walks through how to design a recruiting funnel that does not break in real life.
Start with a clear recruiting operating model
Before changing configuration, get clarity on how recruiting actually works in your organization:
Who owns Job Requisitions – hiring managers, HR partners, recruiters?
Which approvals are mandatory: headcount, budget, HR, DEI, leadership?
Where do you post jobs: internal career site, external career site, job boards via integrations, referrals?
How many interview steps do most roles need?
Use these answers to design your Recruiting Business Processes, Job Requisition defaults and standard pipelines. Workday Recruiting is flexible enough to support almost any process, but that flexibility is dangerous if you let every team design their own funnel.
Designing Job Requisitions that don’t confuse managers
In Workday, the Job Requisition is the anchor of your funnel. It ties together Position / Job Profile, Organizations, Compensation, Job Posting and the candidate pipeline.
Key setup decisions for Job Requisitions:
Staffing Model alignment
In Position Management, requisitions typically tie to a Position or set of Position Restrictions.
In Job Management, they rely more on Job Profile and Recruiting Restrictions.
Primary Recruiter, Hiring Manager, and any local roles such as Search Chair or Recruiting Coordinator.
Templates and rules
Use Job Requisition Templates so things like qualifications, job description skeleton, and posting options default correctly.
Use Recruiting Condition Rules so data flows from Job Profile and Position into the requisition automatically instead of relying on manual entry every time.
If managers see a clean, guided Create Job Requisition experience with smart defaults, they move quickly and accurately. If the form is long, inconsistent or full of unknown fields, they delay or raise tickets.
Job Posts that convert, not just exist
Once a requisition is approved, your Job Posting drives candidate traffic. In Workday Recruiting, you can create Internal and External Job Posts, assign posting sites, and manage effective dates.
Design patterns for Job Posts:
Separate content for internal vs external
Internal posts can use more internal language and reference internal mobility.
External posts should be candidate-centric and optimized for conversion.
Primary Posting and multiple sites
In Workday, you can designate a Primary Job Posting and post to multiple external sites. The primary posting URL is used in notifications and referrals.
Keep your posting options standardized (for example, “Internal + External” vs “Internal Only”) so reporting and funnels are comparable.
Consistent structure
Use a standard structure for job descriptions: role summary, responsibilities, requirements, location/hybrid details, and benefits overview.
Tie key fields (job category, location, seniority) to reporting rather than burying them in free-text.
A frictionless funnel depends on posts that are easy to maintain and easy for candidates to understand, not just technically present on the career site.
Designing pipelines that don’t break under load
The candidate pipeline in Workday is managed via stages in the Recruiting Business Process, shown visually in the pipeline view. This is where many implementations overcomplicate things and create bottlenecks.
Best practices for pipeline stages:
Keep the pipeline lean: focus on core stages like Applied, Screen, Interview, Offer, Background Check, Ready for Hire, Hired.
Avoid splitting every micro-task into its own stage (e.g., “Schedule Interview”, “Interview Feedback”, “Offer Draft”, “Offer Approve”, “Offer Send”). Use checklists and tasks within a stage instead.
Design reporting pipeline categories behind the scenes so variations (Technical Interview, Panel Interview, VP Interview) still roll up to a core “Interview” stage in reporting.
From a practitioner view, the pipeline should answer at a glance:
Where are candidates stuck?
How many are at each stage by requisition, recruiter, business unit?
How long do candidates spend in each stage?
Workday’s pipeline view and reports support this, but only if your stages are meaningful and consistent across similar job types.
Moving candidates smoothly through requisitions
Once candidates apply or are sourced, the day-to-day work is moving them through the requisition.
Key points:
Use Move Candidate actions within the requisition to keep history and reporting accurate.
Standardize your disposition reasons (Not Qualified, Withdrew, Salary Expectations, Culture Add Concerns, etc.) so recruiting analytics can surface real insights.
Ensure the Recruiting Business Process routes the right tasks at each stage: assessments, interview scheduling, feedback forms, offer approvals, background checks.
A funnel “breaks” when:
Candidates sit in a stage with no owner or task.
Recruiters use manual status notes instead of moving candidates.
Approvals are unclear, causing offers to stall.
Design your process so each stage has a clear owner (Recruiter, Hiring Manager, TA Partner) and clear system tasks.
Automation, messaging and candidate experience
Frictionless recruiting is not just about internal process; it is also about how candidates experience the funnel. Workday provides candidate communications, notifications and integration options to support this.
Ideas to implement:
Use automated emails for key events: application received, moved to interview, not selected, offer sent.
Keep message templates human and brand-aligned, not just system boilerplate. Include recruiter contact details where appropriate.
Use tags, questionnaires, or custom fields to capture candidate segments (e.g., alumni, silver-medalist candidates) for future pipelines, instead of creating extra pipeline stages.
Candidates judge your process by communication and speed. If Workday is configured to send timely updates and keep recruiters on top of their tasks, the system becomes a competitive advantage rather than a black box.
Governance, reporting and continuous improvement
Finally, treat your Workday recruiting funnel as a product you continuously improve.
Governance practices:
Maintain a Recruiting Design Guide covering Job Requisition templates, Job Posting standards, pipeline stages and disposition reasons.
Restrict who can create new stages, templates and posting sites; uncontrolled customization is how funnels become fragile.
When you see a stage where candidates routinely stall, ask whether it is a process issue, a configuration issue, or both. Then adjust your Recruiting Business Processes, Requisition defaults or pipeline stages accordingly rather than adding more complexity.
A frictionless recruiting funnel in Workday comes from intentional design: clean Job Requisitions, conversion-friendly Job Posts, lean and consistent pipelines, and clear ownership at every stage. Done right, recruiters spend less time fighting workflows and more time closing great hires.
Time Tracking is where HR, operations and payroll all meet your Workday configuration. If Time Tracking is messy, you will feel it every single pay period in the form of corrections, overrides and frustrated managers. A clean design for Time Entry Methods, Time Entry Codes, Time Code Groups, Time Entry Templates and Work Schedules gives you predictable timesheets and reliable payroll integration.
Start with how the business really works
Before you build anything in Workday Time Tracking, map how people actually work:
Do workers track in/out time, or just total hours per day?
Are shifts fixed, rotating or highly flexible?
Do workers charge time to Projects, Cost Centers or other Worktags?
Which time events drive extra pay – overtime, shift differential, call-out, on-call?
Use these answers to drive your decisions on Time Entry Method, the set of Time Entry Codes you need, and how complex your Time Calculations should be.
Choose the right Time Entry Methods
In Workday you can configure different Time Entry Methods such as:
Enter Time by Week or Enter Time by Day (elapsed hours).
In/Out entry (clock-style time with start and end).
Time Clock Events (check-in/checkout, potentially with geofencing).
Good practice:
Use In/Out for environments where labor laws and break tracking are strict (manufacturing, retail, healthcare).
Use by Week/Day for professional services or salaried populations who track hours mainly for cost allocation and utilization.
Avoid mixing too many methods for similar workers; it complicates training, reporting and support.
The key is consistency: workers in the same Time Tracking Configuration should have similar time entry experiences and rules.
Design Time Entry Codes that make sense
Time Entry Codes are the building blocks on the timesheet. They represent things like Regular Hours, Overtime, Training, Travel, or On Call.
Map each code to the right Time Type and related Worktags (such as Cost Center, Project, Location) so reporting and payroll know how to treat the hours.
Only create a new Time Entry Code when it truly has different behavior (calculation, posting, or reporting) – not just a different label.
Too many codes on the timesheet will confuse employees and lead to mis-classified hours. A smaller, well-designed set of codes keeps Time Tracking clean and sustainable.
Group workers with Time Code Groups
Instead of assigning every Time Entry Code directly to workers, use Time Code Groups. These are collections of codes workers are eligible to use.
Patterns that work well:
Create Time Code Groups by population, such as “TCG – Salaried – Global”, “TCG – Hourly – US Retail”, “TCG – Contractors – IT”.
Tie Time Code Groups to Eligibility Rules using criteria like Company, Location, Worker Type and Pay Group.
Make sure each group has only the codes that population actually needs; fewer options on the timesheet means fewer mistakes.
From a practitioner view, Time Code Groups are your main control over what employees see when they click Enter Time. Design them intentionally, not as an afterthought.
Build clean Time Entry Templates
Time Entry Templates define the layout and options of the timesheet itself – what fields show up, which columns are there, and how workers enter time.
When configuring Time Entry Templates:
Choose the right layout:
Simple grid for “hours per day” style.
In/Out style with Start Time, End Time, and Meal Break fields.
Project-based layout when workers must enter Project, Task, or other worktags on each time block.
Include only necessary fields: Position, Worktags, Comments – avoid cluttering the screen.
Enable features like Autofill from Prior Week or Autofill from Schedule when appropriate to reduce manual entry for regular patterns.
Think of Time Entry Templates as the UX layer of Time Tracking. A clean template can cut time-to-complete and errors significantly.
Configure Work Schedules and Period Schedules correctly
Work Schedules and Period Schedules drive how Workday expects employees to work and how timesheets are broken into periods.
Key components:
Period Schedules: Define the time entry period (weekly, biweekly, semi-monthly) and align to payroll cycles where possible.
Work Schedules: Define expected working days and hours per day for different groups (e.g., Mon–Fri 9–5, 4-on-4-off shifts).
Use Work Schedule Calendars or groups where you need shift patterns for overtime or shift premiums.
Well-designed schedules enable:
Accurate validation (e.g., maximum hours per day).
Better reporting on variance between scheduled and actual hours.
Cleaner calculations for overtime and holiday pay.
Build smart Time Calculations, not monsters
Time Calculations and Time Calculation Groups tell Workday how to transform raw time blocks into paid hours, overtime, premiums, and other pay-related metrics.
Best practices:
Start with simple rules: e.g., “Hours above 40 in a week go to Overtime 1.5x”.
Use Time Calculation Groups that match your business rules, such as a group for US hourly workers and another for EU shift workers.
Avoid building a separate calculation group for every micro-scenario; instead use conditions within shared groups wherever possible.
Overly complex Time Calculations are hard to test, explain and maintain. Aim for rule sets that a new Workday Time Tracking admin can understand within an hour.
Connect Time Tracking with Absence and Payroll
Time Tracking rarely stands alone. It should work seamlessly with Absence Management and Payroll (Workday or external).
Integration points to check:
How Time Off entries display on the timesheet for Time Tracking workers, and how they impact payable hours.
Mapping of Time Entry Codes to Earnings / Pay Components in payroll, ensuring regular, overtime, differential and unpaid hours flow correctly.
Handling of exceptions like missing punches, late time submissions and retro corrections, and how these flow into payroll runs.
When Time Tracking and Payroll disagree, payroll will resort to manual overrides. The more alignment you build upfront, the fewer fights you have at cut-off.
Governance, testing and ongoing optimization
To keep Time Tracking clean over time:
Document a Time Tracking design playbook: which Time Entry Methods, Time Codes, Templates and Schedules you use and why.
Test with real-life scenarios: overtime across weeks, holiday work, project changes mid-week, and combination of Time Off plus worked hours.
Monitor reports like “Unsubmitted Timesheets”, “Time Block Corrections” and “Hours by Time Entry Code” to spot design issues early.
Treat Time Tracking as a living configuration, not a one-time setup. As the business introduces new work patterns, projects or pay rules, update configuration using the same principles rather than patching with one-off codes and templates.
A complete blueprint for clean Workday Time Tracking is ultimately about clarity: clear methods, clear codes, clear schedules and clear calculations. When workers know exactly how to enter time and payroll trusts the output, you know your configuration is doing its job.
