peopletechguide.com

Tag: workday business process

  • Tracking Changes in Workday Business Processes

    “Who Changed the Offer BP?” – A Common Workday Problem

    Almost every Workday team has experienced this moment: recruiting suddenly stops working as expected, offers get stuck, approvers change, and someone finally asks, “Who changed the Offer business process last week?” The room goes quiet, people check emails and messages, and no one has a clear answer.

    This is not just a technical problem. It is a governance and accountability problem. When business process (BP) changes are not properly tracked, communicated, and owned, HR, Talent Acquisition, and Hiring Managers lose confidence in Workday. The system appears unpredictable and “risky,” even when the root cause is simply a missing process for change control.

    Why Workday Business Process Changes Are So Sensitive

    Business processes in Workday control the steps, routing, notifications, and validations that drive core workflows: hiring, offers, onboarding, job changes, promotions, terminations, and more. A small change in a condition, approver, or step can materially impact:

    • Who needs to approve an action.
    • How long a transaction takes.
    • Which data is required or optional.
    • Which stakeholders are notified—or not notified.

    When these changes are made quickly, without documentation or testing, they often look harmless in the moment. But a week later, when a recruiter asks why offers are stuck or a manager wonders why a new approver is suddenly in the chain, the lack of visibility becomes a major issue.

    Typical Symptoms of Poor BP Change Governance

    If your Workday tenant has weak governance around business process changes, you might notice some of these symptoms:

    • Recruiting or HR users report “something changed” in approval flow, but no one knows exactly what.
    • Approvers change without clear business agreement, creating political or compliance issues.
    • Testing happens directly in production because “it’s just a small tweak.”
    • Documentation about the current BP design is outdated, or doesn’t exist at all.
    • The same issues reappear across releases because no one tracks previous decisions.

    Over time, this erodes trust. Business users start to see Workday as a black box that “randomly changes,” even if those changes were made with good intentions.

    The Foundation: Clear Ownership and Roles

    Before getting into tools and reports, it is crucial to define who actually owns each key business process. For example:

    • HR Operations might own the Hire and Termination processes.
    • Talent Acquisition might own the Offer and Recruiting processes.
    • HR and Finance together might own Job Change and Compensation changes.

    Clear ownership means:

    • No changes to a process are made without the knowledge and approval of its owner.
    • Owners participate in design, testing, and sign-off for any configuration updates.
    • There is a known “RACI” (who is Responsible, Accountable, Consulted, and Informed) for each core BP.

    When ownership is vague, changes happen informally, through ad-hoc requests and one-off messages. When ownership is explicit, it becomes easier to implement a simple but effective change control process.

    Practical Ways to Track Who Changed What and When

    Workday provides multiple tools and logs that help teams understand configuration changes, but they only work if you build them into your operating rhythm. Depending on your tenant setup and access, you may have options such as:

    • Configuration reports that show recent changes in business processes and related objects.
    • Delivered or custom audit reports that track who made specific configuration updates and when.
    • Change tickets or requests in your ITSM tool (e.g., Jira, ServiceNow) that record the “why” behind changes.

    The key is to combine system-level visibility (who changed what, technically) with process-level governance (who approved the change, and what problem it solved). Technical logs alone are not enough; they need to be tied to a clear request and approval trail.

    A Simple Change Control Flow for Workday Business Processes

    You do not need a huge bureaucracy to manage business process changes. A lightweight change control flow is enough to avoid most issues. For example:

    1. Request
      A user identifies a problem (e.g., an approver is missing, a step is unnecessary) and submits a change request with context.
    2. Review and Design
      The Workday admin and BP owner review the request, explore options, and agree on the design.
    3. Configure in Non-Production
      The change is made in a test or sandbox tenant, not directly in production.
    4. Test with Real Scenarios
      HR, Talent, or Finance users test the change using realistic scenarios and confirm the expected behavior.
    5. Approve and Document
      The owner approves the change, and a short design note is recorded (what changed, why, and any impacts).
    6. Move to Production and Communicate
      The change is migrated, and impacted users receive a short update—especially if their approvals or steps change.

    With this simple pattern, the question “Who changed the Offer BP last week?” has a clear answer: there is a ticket, an owner, and documentation.

    Communicating Business Process Changes to Stakeholders

    Even when changes are well-controlled, they can still cause confusion if users are not informed. For Workday business process changes, communication should match the impact:

    • Small, low-impact tweaks can be summarized in a monthly “Workday changes” digest.
    • Medium-impact changes, like new approvers or extra validation steps, should be highlighted in targeted emails or intranet posts.
    • High-impact changes that affect many users or critical workflows may deserve training sessions, FAQs, or quick reference guides.

    The goal is not to flood users with technical details, but to answer their key questions: What changed? Why did it change? What do I need to do differently?

    Building Trust by Making Workday Changes Visible

    Ultimately, tracking and governing business process changes is about building trust. HR, Talent, and Finance teams are more willing to rely on Workday when:

    • They know there is a stable process for changing core workflows.
    • They can see, in plain language, what has changed and why.
    • They feel involved in design decisions rather than surprised by new behavior.

    The next time someone asks, “Who changed the Offer BP last week?”, your goal is not just to have a name. Your goal is to be able to say: “Here’s the change request, here’s who approved it, here’s the test we ran, and here’s how we communicated it.”

    That is how Workday becomes simpler, more predictable, and more trusted for HR and Finance teams.

  • Workday Position Management

    “We’re implementing Workday Position Management next quarter. Any advice?”

    I get this question at least once a month from HR leaders embarking on Workday implementations.

    My honest answer? Position Management works beautifully when configured correctly. When configured poorly, it becomes the most complained-about feature in your entire Workday tenant.

    Last year, I joined a client project three months after their Workday go-live. The HR Operations team was drowning in position management tickets:

    “Why can’t I fill this position?”

    “The system says this position is filled, but the worker terminated two weeks ago.”

    “I need to create 50 new positions for our expansion, but it takes 45 minutes per position.”

    “Position data doesn’t match our headcount reports.”

    “Why do I need a position AND a job? They’re the same thing!”

    Their Position Management implementation had all the classic problems. Five thousand positions. Three thousand active workers. Dozens of unfillable positions. No clear ownership. Inconsistent data quality. And an HR team that had completely lost trust in the system.

    We spent six weeks systematically fixing the root causes. By the end, position management went from their most hated feature to a strategic workforce planning tool that executives actually used.

    This guide will show you the seven fixes that transformed their implementation and have since worked across dozens of other Workday tenants. These are not theoretical best practices from Workday Community. These are battle-tested solutions to the specific problems that make people hate Position Management.

    Why Position Management Gets So Much Hate

    Before we dive into fixes, you need to understand why Position Management creates so much frustration.

    The Fundamental Misunderstanding

    Most organizations implement Position Management because they think they need it for budgeting or headcount planning.

    They are partially right. Position Management can support those use cases. But that is not what Position Management actually does.

    Position Management is a workforce structure management tool that maintains a parallel organizational structure based on positions rather than workers.​

    When you enable Position Management in Workday, you are making a fundamental architectural decision: Your organizational structure will be built on positions first, workers second.

    Without Position Management, your organizational structure looks like this:

    • Worker → Job → Supervisory Organization → Cost Center

    With Position Management, your organizational structure looks like this:

    • Position → Worker → Job → Supervisory Organization → Cost Center

    That extra layer creates the complexity that frustrates everyone.

    The Three Core Complaints

    Every Position Management complaint falls into one of three categories:

    Complaint 1: “It’s too much work”

    Creating positions is more work than just hiring workers directly into jobs. Managing position changes is more work than managing worker job changes. Every organizational change now requires updating positions first, then workers.

    Complaint 2: “The data doesn’t match reality”

    Positions show as filled when workers have terminated. Positions show as vacant when workers are actively working. Position budgets don’t match actual headcount. Position titles don’t match what people actually do.

    Complaint 3: “Nobody understands it”

    Hiring managers do not understand the difference between a position and a job. Finance does not understand why budget is allocated to positions that have no workers. HR does not understand when to create new positions versus reusing existing vacant positions.

    All three complaints stem from the same root cause: Position Management was implemented without clear business rules and governance.

    The fixes I am about to show you establish those rules and governance.

    Fix 1: Define Clear Position Creation Rules (Or Stop Creating Positions Entirely)

    This is the most important fix. Get this wrong and everything else fails.

    The Problem

    Most organizations have no clear rules for when to create a new position versus reusing an existing vacant position.​

    The result? Managers create new positions for every hire because it is easier than searching for vacant positions to reuse. Three years later, you have 8,000 positions for 3,000 workers.

    Your position-to-worker ratio should rarely exceed 1.5:1 (1.5 positions for every 1 worker). When you hit 2:1 or 3:1, your position data has become meaningless.​

    The Fix: Establish Position Creation Governance

    Implement one of these three position creation strategies based on your organizational needs:

    Strategy 1: Strict Position Control (Best for stable, hierarchical organizations)

    New positions can only be created through:

    • Annual budgeting process (Finance approves all position budget)
    • Formal headcount planning (HR Ops creates positions in batches)
    • Executive approval for unbudgeted positions

    When to use this: Large enterprises with formal budgeting processes, government organizations, healthcare systems with strict FTE budgeting.

    Position-to-worker ratio target: 1.1:1 to 1.3:1

    Strategy 2: Manager-Initiated with Approval (Best for growing organizations)

    Managers can create positions through a business process that requires:

    • Business justification
    • Budget code assignment
    • HR Operations approval
    • Finance approval for new budget allocation

    When to use this: Mid-sized companies with active hiring, organizations in growth mode, companies with distributed HR.

    Position-to-worker ratio target: 1.3:1 to 1.5:1

    Strategy 3: Just-in-Time Position Creation (Best for dynamic organizations)

    Positions are created automatically during the hiring process:

    • Requisition approval creates the position
    • Position is filled immediately upon hire
    • Position closes automatically when worker terminates

    When to use this: High-growth startups, project-based organizations, consulting firms with rapid hiring cycles.

    Position-to-worker ratio target: 1.0:1 to 1.2:1

    Implementation Guidance

    Step 1: Audit your current state

    Calculate your current position-to-worker ratio:

    • Total positions ÷ Total active workers = Ratio

    If your ratio exceeds 2:1, you have a data quality crisis that needs immediate cleanup before implementing governance.

    Step 2: Choose your strategy

    Select the strategy that matches your culture. Do not choose Strategy 1 (Strict Position Control) if your organization values manager autonomy. Do not choose Strategy 3 (Just-in-Time) if you need position budget before hiring approval.

    Step 3: Document the rules

    Create a position management policy document that answers:

    • Who can create positions?
    • What approval is required?
    • When should positions be created (before requisition? during hiring? after offer acceptance)?
    • How are vacant positions reused?
    • When are positions closed or inactivated?

    Step 4: Train your stakeholders

    Position creation rules mean nothing if managers, recruiters, and HR do not understand them. Include position management in:

    • New manager onboarding
    • Recruiter training
    • HR operations procedures
    • Finance budgeting processes

    Step 5: Enforce through business process configuration

    Configure your Workday business processes to enforce your rules:

    • Remove position creation from manager self-service if using Strict Position Control
    • Add approval steps to position creation if using Manager-Initiated
    • Auto-create positions from requisition approval if using Just-in-Time

    Do not rely on training and documentation alone. Configure Workday to make the wrong behavior impossible.

    Expected Impact

    Clear position creation rules reduce position proliferation by 60% to 80% within the first year.​

    One client reduced their position-to-worker ratio from 2.7:1 to 1.4:1 over 18 months by implementing Manager-Initiated position creation with HR approval.

    Fix 2: Implement Position Lifecycle Automation

    Manual position lifecycle management creates the data quality problems that make everyone hate Position Management.

    The Problem

    In most implementations, positions remain in “Filled” status after workers terminate. They remain in “Vacant” status after workers are hired. They accumulate in “On Hold” or “Frozen” statuses with no clear owner responsible for cleanup.​

    Finance allocates budget to positions showing as “Vacant” that have been filled for six months. HR Operations sees positions showing as “Filled” when the incumbent terminated three months ago.

    Nobody trusts position data because position status never reflects reality.

    The Fix: Automate Position Status Updates

    Configure Workday to automatically update position status based on worker events:

    Automation 1: Position Fills on Hire

    When a worker is hired into a position:

    • Position status changes from “Vacant” to “Filled”
    • Position availability changes from “Available” to “Unavailable”
    • Position filled date updates to hire date
    • Position worker relationship is established

    Workday configuration: Enable “Update Position on Hire” in your Hire business process.

    Automation 2: Position Vacates on Termination

    When a worker terminates from a position:

    • Position status changes from “Filled” to “Vacant”
    • Position availability changes from “Unavailable” to “Available” (if the position should remain open)
    • Position vacant date updates to termination date
    • Position worker relationship is ended

    Workday configuration: Enable “Update Position on Termination” in your Terminate Employee business process.

    Automation 3: Position Status Updates on Worker Job Change

    When a worker moves to a new position:

    • Old position status changes from “Filled” to “Vacant”
    • New position status changes from “Vacant” to “Filled”
    • Old position becomes available for backfill
    • New position becomes unavailable

    Workday configuration: Enable “Update Position on Job Change” in your Job Change business process.

    Automation 4: Position Freezes on Elimination

    When a position is eliminated:

    • Position status changes to “Frozen” or “Eliminated”
    • Position availability changes to “Unavailable”
    • Position budget can be reallocated
    • Position cannot be filled without unfreezing

    Workday configuration: Create “Eliminate Position” business process with automatic status update.

    Position Availability Logic

    Position status and position availability are different fields that control different behaviors:

    Position Status (informational):

    • Vacant
    • Filled
    • Frozen
    • Eliminated

    Position Availability (controls hiring):

    • Available (can be filled through hiring)
    • Unavailable (cannot be filled)

    Your automation should update both fields appropriately.

    Example logic:

    • Filled position = Status “Filled”, Availability “Unavailable”
    • Vacant position approved for hire = Status “Vacant”, Availability “Available”
    • Vacant position on hiring freeze = Status “Vacant”, Availability “Unavailable”
    • Eliminated position = Status “Eliminated”, Availability “Unavailable”

    Expected Impact

    Lifecycle automation eliminates 90% of position status data quality issues.​

    One client had 450 positions with incorrect status before automation. Six months after implementing lifecycle automation, they had 12 positions with incorrect status (all explained by complex job sharing scenarios that required manual management).

    Fix 3: Solve the Position Title Confusion

    Position titles are one of the most frustrating aspects of Position Management for managers and workers.

    The Problem

    Workers are confused when their position title does not match their job title. Managers are confused when they see “Senior Software Engineer – Position 00347” on organizational charts instead of just “Senior Software Engineer.”

    The root cause: Workday displays position ID and position title in many places where users expect to see job title.​

    Example of the confusion:

    • Worker name: Sarah Chen
    • Job: Senior Software Engineer
    • Position: Senior Software Engineer – Position 00347

    Sarah sees “Senior Software Engineer – Position 00347” on her worker profile, organizational charts, and business cards. She reasonably asks: “Why does my title have a position number in it?”

    The Fix: Standardize Position Titling Convention

    Implement one of these three position titling strategies:

    Strategy 1: Position Title Matches Job Title (Simplest)

    Every position’s title exactly matches its job title.

    Example:

    • Job: Senior Software Engineer
    • Position Title: Senior Software Engineer
    • Position ID: P-12847 (used for internal tracking only)

    When to use this: Organizations where positions represent generic roles, not unique positions.

    Pros: Workers see familiar job titles everywhere. No confusion.

    Cons: Cannot distinguish between multiple positions with the same job title. Difficult to track specific positions for budgeting.

    Strategy 2: Position Title Includes Location or Department (Balanced)

    Position title includes job title plus identifying information.

    Example:

    • Job: Senior Software Engineer
    • Position Title: Senior Software Engineer – Product Engineering
    • Position ID: P-12847

    When to use this: Organizations that need to distinguish between positions in different locations or departments.

    Pros: Clear identification of specific positions. Still readable and makes sense to workers.

    Cons: Position titles become long. Requires consistent naming convention enforcement.

    Strategy 3: Position Title Uses Descriptive Unique Identifier (Most Control)

    Position title is completely unique and descriptive.

    Example:

    • Job: Senior Software Engineer
    • Position Title: Lead Engineer – Payment Processing Platform
    • Position ID: P-12847

    When to use this: Organizations with highly specialized positions where each position has unique responsibilities.

    Pros: Maximum clarity about what each specific position does. Useful for succession planning and workforce planning.

    Cons: Most complex to manage. Position titles may not align with external market titles. Requires significant governance.

    Display Configuration

    After choosing your titling strategy, configure what displays in common views:

    Worker Profile: Display job title, not position title.

    Organizational Charts: Display job title, not position title (unless position title is strategy 3 with descriptive information).

    Headcount Reports: Include both job title and position ID (for HR and Finance), but default display to job title.

    Position Budget Reports: Display position title and position ID (for Finance).

    Expected Impact

    Standardized position titling reduces position-related confusion tickets by 50% to 70%.​

    One client implemented Strategy 2 (job title plus department) and saw position titling questions drop from 30 tickets per month to 8 tickets per month.

    Fix 4: Build Position Forecasting and Planning Tools

    Position Management only creates value when it enables better workforce planning. Most organizations implement positions but never build planning tools.

    The Problem

    Organizations implement Position Management to support headcount planning and budget forecasting. Then they discover Workday does not automatically provide planning tools just because you enabled positions.​

    Finance wants to see position budget versus actual spend. HR wants to forecast hiring needs based on vacant positions. Executives want to see position fill rates and time-to-fill by department.

    Without these reports and dashboards, Position Management becomes a compliance requirement that creates work without providing value.

    The Fix: Create Position Planning Reports and Dashboards

    Build these five essential position management reports:

    Report 1: Position Budget vs. Actual Headcount

    Purpose: Finance needs to reconcile position budget with actual headcount and spending.

    Key fields:

    • Supervisory Organization
    • Position ID
    • Position Title
    • Position Status (Filled, Vacant, Frozen)
    • Position Budget FTE
    • Worker Name (if filled)
    • Worker Annual Salary
    • Budget Variance (Position Budget minus Actual Salary)

    Frequency: Monthly

    Primary audience: Finance, HR Operations

    Report 2: Vacant Position Analysis

    Purpose: HR needs to prioritize filling critical vacant positions and identify positions that should be eliminated.

    Key fields:

    • Position ID
    • Position Title
    • Supervisory Organization
    • Position Vacant Date
    • Days Vacant
    • Position Budget
    • Requisition Status (if open requisition exists)
    • Last Worker Name (who previously held the position)
    • Last Worker Termination Date

    Frequency: Weekly

    Primary audience: HR Operations, Hiring Managers, Recruiters

    Report 3: Position Fill Rate Dashboard

    Purpose: Executives need to monitor hiring effectiveness and workforce planning.

    Key metrics:

    • Total Positions
    • Filled Positions
    • Vacant Positions
    • Fill Rate Percentage (Filled ÷ Total)
    • Average Days to Fill
    • Fill Rate by Department
    • Fill Rate Trend over Last 12 Months

    Frequency: Monthly

    Primary audience: CHRO, CFO, Department Heads

    Report 4: Position Lifecycle Audit

    Purpose: HR Operations needs to identify data quality issues and positions stuck in wrong status.

    Key fields:

    • Position ID
    • Position Title
    • Position Status
    • Position Availability
    • Worker Name (if status is “Filled”)
    • Data Quality Flag (e.g., “Status shows Filled but no worker assigned”)

    Frequency: Weekly

    Primary audience: HR Operations, Workday Administrators

    Report 5: Position Forecasting by Department

    Purpose: Department heads need to forecast hiring needs and budget requirements.

    Key fields:

    • Supervisory Organization
    • Total Positions (current)
    • Filled Positions (current)
    • Vacant Approved Positions (ready to hire)
    • Vacant Unapproved Positions (not ready to hire)
    • Frozen/Eliminated Positions
    • Forecasted New Positions (from planning process)
    • Total Forecasted Headcount (12 months forward)

    Frequency: Quarterly

    Primary audience: Department Heads, Finance, HR Business Partners

    Dashboards and Visualizations

    Reports alone are not enough. Create executive dashboards using Workday’s discovery boards or external visualization tools:

    Executive Workforce Dashboard:

    • Fill rate trend line
    • Vacant positions by department (bar chart)
    • Average days to fill by department
    • Headcount actual vs budget (variance analysis)

    HR Operations Dashboard:

    • Positions vacant over 90 days
    • Positions with data quality issues
    • Requisitions without positions
    • Recent position changes log

    Department Manager Dashboard:

    • My team’s positions (filled and vacant)
    • My vacant positions awaiting requisition
    • My team’s budget vs actual
    • Hiring pipeline status

    Expected Impact

    Position planning tools increase Position Management value perception by 80% or more.​

    One client’s CFO went from saying “Position Management just creates extra work” to “Position Management is our single source of truth for workforce budgeting” after implementing these five reports and two executive dashboards.

    Fix 5: Integrate Position Management with Recruiting

    The disconnect between Position Management and Recruiting creates operational friction that frustrates everyone.

    The Problem

    In many implementations, Position Management and Recruiting operate as separate processes:

    • HR creates positions
    • Weeks later, someone creates a requisition
    • The requisition is not clearly linked to the position
    • The position is filled through hiring, but the requisition status does not update
    • Nobody knows which vacant positions have active recruiting efforts

    Managers ask: “Which of my vacant positions are we actively recruiting for?”

    Recruiters ask: “Which positions do I need to create requisitions for?”

    HR asks: “Why do we have 200 vacant positions but only 80 open requisitions?”

    The Fix: Tightly Integrate Position and Requisition Workflows

    Implement one of these two integration strategies:

    Integration Strategy 1: Position-First Workflow

    Positions must exist before requisitions can be created.

    Process flow:

    1. Manager or HR creates position (or reuses vacant position)
    2. Position status = “Vacant”
    3. Position availability = “Available”
    4. Manager creates requisition linked to the position
    5. Requisition approval process completes
    6. Recruiting begins
    7. Candidate hired into the position
    8. Position status automatically updates to “Filled”
    9. Requisition status automatically updates to “Filled”

    Workday configuration:

    • Make position selection required on Create Requisition business process
    • Enable automatic position update on Hire
    • Create report showing positions available but without requisitions

    When to use this: Organizations using Strict Position Control or Manager-Initiated strategies (Fix 1). Organizations with formal budgeting where positions represent budget allocation.

    Integration Strategy 2: Requisition-First Workflow

    Requisitions can be created first, and positions are created automatically.

    Process flow:

    1. Manager creates requisition with job and organization
    2. Requisition approval process completes
    3. System automatically creates position linked to requisition
    4. Position status = “Vacant”
    5. Position availability = “Available”
    6. Recruiting begins
    7. Candidate hired into the position
    8. Position status automatically updates to “Filled”
    9. Requisition status automatically updates to “Filled”

    Workday configuration:

    • Enable automatic position creation on Requisition approval
    • Configure position naming convention for auto-created positions
    • Enable automatic position update on Hire

    When to use this: Organizations using Just-in-Time position creation strategy (Fix 1). High-growth companies where hiring speed is critical.

    Position-Requisition Status Synchronization

    Regardless of which integration strategy you choose, implement status synchronization:

    When requisition is approved:

    • Linked position availability updates to “Available”

    When requisition is on hold:

    • Linked position availability updates to “Unavailable”

    When requisition is filled:

    • Linked position status updates to “Filled”
    • Linked position availability updates to “Unavailable”

    When requisition is cancelled:

    • Linked position availability updates to “Unavailable” (if position should be frozen)
    • Or remains “Available” (if position should be filled through a new requisition)

    Reporting Integration

    Create reports that show the position-requisition relationship:

    Vacant Positions Without Requisitions Report:

    Shows positions approved for hiring but no active recruiting effort. HR Operations uses this to prompt managers to create requisitions or inactivate unnecessary positions.

    Requisitions Without Positions Report:

    Shows requisitions approved but not linked to positions. Finance uses this to identify potential budget disconnects.

    Expected Impact

    Position-recruiting integration reduces time-to-fill by 20% to 30% by eliminating administrative delays.​

    One client reduced their average time-to-fill from 67 days to 48 days primarily by eliminating the lag between position approval and requisition creation through requisition-first integration.

    Fix 6: Solve the Job vs. Position Confusion

    The most common Position Management complaint is: “Why do I need a position AND a job? They seem like the same thing.”

    The Problem

    Most people do not understand the difference between a job and a position in Workday.

    The technical definitions do not help:

    Workday documentation says:

    • Job: A generic role (like “Software Engineer”)
    • Position: A specific instance of a job (like “Software Engineer position in the Product team”)

    That explanation makes sense to Workday consultants. It makes no sense to hiring managers.

    The confusion creates practical problems:

    Managers do not know whether to change the job or the position when responsibilities change.

    HR does not know whether to create a new position or change the position’s job when a role evolves.

    Finance does not understand why budget is allocated to positions but compensation is tied to jobs.

    The Fix: Create Clear Guidance on Job vs. Position

    Develop simple, practical guidance that non-HR people can understand:

    Simple Explanation:

    Job = What you do (your role, responsibilities, job level)
    Position = Where you do it (which team, which budget, which headcount slot)

    Examples that clarify:

    Scenario 1: Two people doing the same work in different locations

    Sarah and David are both Senior Software Engineers (same job) on different teams (different positions).

    • Sarah: Job = “Senior Software Engineer”, Position = “SSE – Product Team”
    • David: Job = “Senior Software Engineer”, Position = “SSE – Platform Team”

    Same job. Different positions. Different managers. Different budgets.

    Scenario 2: A promotion

    Sarah gets promoted from Senior Software Engineer to Staff Software Engineer.

    What changes?

    • Her job changes (Senior to Staff)
    • Her position might stay the same (still “SSE – Product Team” position, but now we need to rename it)
    • Or she might move to a different position (new “Staff Engineer – Product Team” position)

    Scenario 3: A transfer

    David transfers from the Platform Team to the Product Team.

    What changes?

    • His job stays the same (still Senior Software Engineer)
    • His position changes (from “SSE – Platform Team” to “SSE – Product Team”)

    Practical Decision Rules

    Give managers these decision rules:

    When to change the job:

    • Promotion or demotion (job level changes)
    • Significant responsibility change that affects market pay (accountant becomes senior accountant)
    • Role type changes (individual contributor becomes manager)

    When to change the position:

    • Worker transfers to a different team
    • Worker moves to a different location
    • Worker’s budget allocation changes to a different cost center
    • Organizational restructure moves the position to a different reporting line

    When to create a new position:

    • Headcount increase approved (new budget allocation)
    • Organizational expansion (new team, new location)
    • Backfill approval for a departed worker (if using position reuse strategy)

    When to change both job and position:

    • Promotion with transfer (worker promoted and moves to new team)
    • Role change with team change (individual contributor becomes manager in a different organization)

    Training Materials

    Create visual decision trees that managers can reference:

    Decision Tree: Do I need to change the job, position, or both?

    Start: Something about this worker’s role is changing.

    Question 1: Are their responsibilities or job level changing?

    • Yes → Job change needed
    • No → Continue to Question 2

    Question 2: Are they moving to a different team, location, or reporting line?

    • Yes → Position change needed
    • No → Continue to Question 3

    Question 3: Is their budget allocation or cost center changing?

    • Yes → Position change needed
    • No → No job or position change needed (might be compensation change, org assignment change, or other worker data change)

    Expected Impact

    Clear job versus position guidance reduces manager confusion tickets by 60% to 80%.​

    One client created a 2-page visual guide on job versus position and included it in manager onboarding. Position-related manager questions dropped from 45 tickets per quarter to 12 tickets per quarter.

    Fix 7: Implement Position Data Quality Audits

    Even with all the fixes above, position data quality degrades over time without active monitoring.

    The Problem

    Position data quality problems accumulate silently:

    • Positions showing as filled when workers terminated months ago
    • Positions showing as vacant when workers are actively working
    • Duplicate positions for the same role and team
    • Position titles that do not match job titles
    • Positions with outdated budget allocations
    • Frozen positions that should be eliminated
    • Eliminated positions that should be reopened

    Nobody notices until Finance runs a budget report that shows 200 vacant positions with budget allocation when HR knows they only have 80 approved openings.

    The Fix: Quarterly Position Data Quality Audits

    Implement a recurring quarterly audit process:

    Audit Checkpoint 1: Position Status Accuracy

    Data quality check: Position status matches actual worker assignment.

    Query logic:

    • Positions with status “Filled” but no worker assigned
    • Positions with status “Vacant” but worker is assigned
    • Positions with worker assigned but status is “Frozen” or “Eliminated”

    Resolution:

    • Update position status to match reality
    • Investigate why automation failed (Fix 2 may need adjustment)
    • Identify positions that require manual status management (job sharing, complex scenarios)

    Audit Checkpoint 2: Position-to-Worker Ratio

    Data quality check: Position-to-worker ratio remains within target range.

    Query logic:

    • Total positions ÷ Total active workers
    • Position-to-worker ratio by department
    • Departments with ratios exceeding 2:1

    Resolution:

    • Identify departments with position proliferation problems
    • Work with department heads to eliminate unnecessary positions
    • Review position creation governance (Fix 1) if ratio is increasing

    Target: Position-to-worker ratio should remain between 1.1:1 and 1.5:1 depending on your strategy from Fix 1.

    Audit Checkpoint 3: Vacant Position Aging

    Data quality check: Vacant positions are actively managed or eliminated.

    Query logic:

    • Positions vacant for more than 180 days
    • Positions vacant without open requisitions
    • Positions with status “Frozen” for more than 365 days

    Resolution:

    • Contact department heads about positions vacant over 180 days
    • Eliminate positions with no hiring plan
    • Unfreeze positions approved for hiring or permanently eliminate positions no longer needed

    Audit Checkpoint 4: Position Budget Alignment

    Data quality check: Position budget matches organizational budget allocation.

    Query logic:

    • Positions with no budget allocation
    • Positions with budget allocation but status “Eliminated”
    • Total position budget versus total organizational budget (should match)

    Resolution:

    • Update position budget to match approved headcount budget
    • Reallocate budget from eliminated positions
    • Investigate discrepancies between position budget total and organizational budget

    Audit Checkpoint 5: Position Naming Consistency

    Data quality check: Position titles follow your established convention from Fix 3.

    Query logic:

    • Positions with titles not matching job titles (if using Strategy 1 from Fix 3)
    • Positions with generic titles like “Position 1” or “New Position”
    • Positions with titles containing “copy” or “test”

    Resolution:

    • Rename positions to match your titling convention
    • Train HR Operations on proper position creation
    • Consider implementing position name validation in business process configuration

    Audit Reporting and Accountability

    Create a quarterly Position Data Quality Scorecard:

    Metrics to track:

    • Total positions
    • Position-to-worker ratio
    • Positions with status accuracy issues (count and percentage)
    • Positions vacant over 180 days (count and percentage)
    • Positions with budget alignment issues (count and percentage)
    • Position data quality score (percentage of positions with zero issues)

    Accountability:

    • Assign HR Operations ownership for overall position data quality
    • Assign department heads ownership for their department’s positions
    • Report scorecard to CHRO and CFO quarterly
    • Set improvement targets (e.g., 95% data quality score)

    Expected Impact

    Quarterly audits maintain position data quality above 95% accuracy.​

    One client started with 72% position data quality (28% of positions had at least one data issue). After four quarterly audits with clear accountability and remediation, they reached 96% position data quality.

    Implementation Roadmap: Rolling Out These 7 Fixes

    You cannot implement all seven fixes simultaneously. Here is a realistic implementation roadmap:

    Quarter 1: Foundation (Fixes 1, 2, 3)

    Month 1: Fix 1 – Position Creation Governance

    • Audit current position-to-worker ratio
    • Choose position creation strategy
    • Document position creation rules
    • Configure business process enforcement

    Month 2: Fix 2 – Position Lifecycle Automation

    • Enable automatic position updates on hire, termination, job change
    • Test automation with representative scenarios
    • Train HR Operations on new automation
    • Monitor for edge cases requiring manual intervention

    Month 3: Fix 3 – Position Title Standardization

    • Choose position titling strategy
    • Rename existing positions to match strategy (may require batch update)
    • Configure display preferences
    • Train stakeholders on new conventions

    Expected outcome: Position creation is controlled, position status reflects reality, position titles make sense to workers.

    Quarter 2: Value Creation (Fixes 4, 5)

    Month 4: Fix 4 – Position Planning Reports (Part 1)

    • Build Report 1 (Position Budget vs. Actual)
    • Build Report 2 (Vacant Position Analysis)
    • Train Finance and HR on new reports

    Month 5: Fix 4 – Position Planning Reports (Part 2)

    • Build Report 3 (Position Fill Rate Dashboard)
    • Build Report 4 (Position Lifecycle Audit)
    • Build Report 5 (Position Forecasting)
    • Create executive dashboards

    Month 6: Fix 5 – Recruiting Integration

    • Choose position-requisition integration strategy
    • Configure business processes for integration
    • Enable status synchronization
    • Build integration reports
    • Train recruiters and hiring managers

    Expected outcome: Position Management delivers tangible value through planning insights and recruiting efficiency.

    Quarter 3: Sustainability (Fixes 6, 7)

    Month 7: Fix 6 – Job vs. Position Guidance

    • Develop simple explanations and decision rules
    • Create visual decision trees
    • Build training materials
    • Deliver training to managers

    Month 8: Fix 7 – Data Quality Audits (Setup)

    • Build audit reports for all five checkpoints
    • Create Position Data Quality Scorecard
    • Assign accountability
    • Set baseline metrics and targets

    Month 9: Fix 7 – Data Quality Audits (First Execution)

    • Run first quarterly audit
    • Remediate identified issues
    • Refine audit queries based on findings
    • Establish recurring quarterly schedule

    Expected outcome: Stakeholders understand Position Management, data quality is maintained systematically.

    Ongoing: Continuous Improvement

    Quarterly activities:

    • Run position data quality audit
    • Review position-to-worker ratio trends
    • Assess position planning report usage
    • Gather stakeholder feedback
    • Refine processes based on learnings

    Annual activities:

    • Comprehensive review of position creation governance
    • Position title convention review and updates
    • Position budget alignment with annual planning
    • Position Management training refresher for all stakeholders

    Common Objections (And How to Respond)

    When you propose these fixes, you will encounter objections. Here is how to respond:

    Objection 1: “This is too much governance. We need flexibility.”

    Response: Position Management without governance creates chaos, not flexibility. You currently have 6,000 positions for 2,500 workers. That is not flexibility; that is data that nobody trusts. These fixes give you disciplined flexibility with accountability.

    Objection 2: “We don’t have time to implement all this.”

    Response: You are already spending time managing position chaos. Last quarter, your HR Operations team spent 120 hours investigating position data quality issues and answering manager questions. These fixes automate 80% of that work. You are not adding work; you are replacing chaotic reactive work with structured proactive work.

    Objection 3: “Our organization is too complex for simple rules.”

    Response: Every organization thinks they are too complex for simple rules. Then they implement simple rules and discover 90% of scenarios fit the rules perfectly. You can handle the other 10% as exceptions. Start simple. Add complexity only when genuinely needed.

    Objection 4: “Finance will never agree to change the budgeting process.”

    Response: Finance wants position data they can trust more than they want to maintain the current process. Show your CFO the current position-to-worker ratio and ask if they trust position budget numbers. They will support process changes that improve data quality.

    Objection 5: “We already tried to fix Position Management and it didn’t work.”

    Response: Most Position Management fixes fail because they address symptoms instead of root causes. These seven fixes address root causes systematically. Also, previous failures often occurred because fixes were implemented without stakeholder buy-in. This roadmap builds buy-in through phased implementation with visible results.

    Measuring Success: Key Metrics

    Track these metrics to demonstrate improvement:

    Operational Efficiency Metrics:

    • Position-related HR tickets per month (target: 75% reduction)
    • Time spent on position data quality remediation (target: 80% reduction)
    • Position creation to approval time (target: 50% reduction)

    Data Quality Metrics:

    • Position-to-worker ratio (target: 1.1:1 to 1.5:1)
    • Position data quality score (target: 95%+)
    • Positions with status accuracy issues (target: less than 5%)

    Business Value Metrics:

    • Finance confidence in position budget data (survey-based, target: 8/10 or higher)
    • Manager understanding of position concepts (survey-based, target: 7/10 or higher)
    • Position planning report usage (target: 80% of eligible users accessing monthly)

    Recruiting Efficiency Metrics:

    • Average days to fill (target: 20-30% reduction)
    • Time from position approval to requisition creation (target: less than 5 days)
    • Percentage of vacant positions with active requisitions (target: 90%+)

    Conclusion: From Most Hated to Strategic Asset

    Position Management gets a bad reputation because most organizations implement it poorly.

    They enable the feature, create positions, and expect value to appear automatically. When chaos ensues, they blame Position Management.

    But Position Management is not the problem. Lack of governance, automation, and planning tools is the problem.

    The seven fixes in this guide transform Position Management from a compliance burden into a strategic workforce planning capability:

    Fix 1 controls position proliferation through clear creation rules.

    Fix 2 ensures position data reflects reality through lifecycle automation.

    Fix 3 eliminates title confusion through standardized conventions.

    Fix 4 delivers business value through planning reports and dashboards.

    Fix 5 improves recruiting efficiency through tight integration.

    Fix 6 reduces stakeholder confusion through clear guidance.

    Fix 7 maintains data quality through systematic audits.

    Implement these fixes systematically over three quarters, and Position Management will go from your most complained-about feature to a trusted strategic asset that Finance, HR, and executives actually use.

    Tell Me Your Experience

    What is your biggest Position Management frustration? Which of these seven fixes would have the most impact in your organization?

    Have you successfully implemented Position Management? What worked for you?

    Share your experiences in the comments below. We learn best from each other’s real-world challenges.

  • Workday Business Process Configuration Guide

    Here’s what happens in every Workday implementation:

    • Week 1: “We need to configure business processes.”
    • Week 4: “Why is every hire routing to the CEO for approval?”
    • Week 8: “Why aren’t managers getting notifications?”
    • Week 12: “Can we add Finance approval for salary increases over $10K?”
    • Week 16: “We broke something. All approvals are stuck.”

    I’ve watched this pattern repeat across dozens of implementations. Teams rush to configure Business Processes without understanding how they actually work. They copy approval steps from templates, add conditions they don’t fully understand, and hope everything routes correctly.

    The result? Broken approval workflows. Notifications going to the wrong people. Critical transactions stuck in someone’s inbox for weeks. And endless troubleshooting sessions trying to figure out why a simple hire took 47 days to approve.

    The truth is this: Business Processes are the automation engine that powers Workday. Every hire, termination, compensation change, time off request, and org change flows through a Business Process. Get the configuration right, and workflows run smoothly. Get it wrong, and your entire tenant grinds to a halt.

    This guide walks you through Business Process configuration from scratch. We’ll cover approval routing, conditional logic, notifications, security policies, and the configuration decisions that separate clean implementations from chaotic ones.

    Let’s build workflows that actually work.

    What Is a Workday Business Process?

    A Business Process is Workday’s term for an automated workflow. It defines the steps, approvals, notifications, and conditions that govern how transactions move through your system.

    Every action in Workday that requires approval or multi-step execution is controlled by a Business Process:

    Common Business Processes:

    • Hire Employee (onboarding new workers)
    • Terminate Employee (offboarding)
    • Change Job (promotions, transfers, org changes, compensation updates)
    • Request Time Off (vacation, sick leave, personal days)
    • Request Compensation Change (merit increases, bonuses, allowances)
    • Change Benefits (enrollment updates)
    • Add Additional Job (assign secondary positions)
    • Change Emergency Contacts (self-service updates)
    • Submit Expense Report (expense approvals)
    • Create Requisition (hiring approvals)

    Each Business Process controls:

    • Who can initiate the transaction (Business Process Initiators)
    • What approval steps are required (Step Approvals, Manager Approvals, Role Approvals)
    • What conditions trigger different routing paths (Conditional Steps, Due Date Criteria)
    • What notifications are sent and when (Email Notifications, To-Do Notifications)
    • Who can view or cancel transactions in progress (Business Process Security Policy)

    Think of a Business Process as a flowchart that Workday executes automatically. You define the flowchart. Workday follows it.

    Anatomy of a Business Process

    Before we configure anything, let’s understand the key components of every Business Process:

    1. Business Process Type

    The Business Process Type defines what kind of transaction this workflow handles. Workday provides dozens of predefined Business Process Types:

    Common Types:

    • Hire (for hiring workers)
    • Termination (for offboarding)
    • Job Change (for job, org, or compensation changes)
    • Person Event (for personal data changes like address updates)
    • Absence (for time off requests)
    • Benefit Event (for benefits enrollment changes)

    You can’t create new Business Process Types. You configure existing ones.

    2. Business Process Steps

    A Business Process Step is an individual action or approval in the workflow. Steps execute in sequence (step 1, then step 2, then step 3).

    Common Step Types:

    • Approval (someone must approve before the transaction continues)
    • To-Do (someone must complete a task, but it’s not blocking)
    • Notification (send an email or alert to someone)
    • Condition (evaluate criteria and route accordingly)
    • Review (informational step where someone can view but not approve)

    Example Workflow for Hire Employee:

    Step 1: HR initiates hire (Initiator = HR Partner)
    Step 2: Manager approval (Approver = Hiring Manager)
    Step 3: HR approval (Approver = HR Business Partner)
    Step 4: Notification to IT for provisioning (To-Do = IT System Admin)
    Step 5: Transaction completes and worker is hired

    Each step has:

    • Step Name (e.g., “Manager Approval”)
    • Step Type (Approval, To-Do, Notification, etc.)
    • Assignees (who gets this step in their inbox)
    • Due Date (how long they have to complete it)

    3. Approval Routing

    Approval Routing determines WHO receives each approval step. Workday provides several routing options:

    Manager Approval:

    • Routes to the worker’s direct manager
    • Uses the Supervisory Organization hierarchy
    • Most common routing type for manager-level approvals

    Role Approval:

    • Routes to users assigned a specific role (e.g., HR Partner, Payroll Partner)
    • Uses Role-Based Security Groups
    • Good for functional approvals (HR, Finance, Legal)

    Organization Owner Approval:

    • Routes to the manager of a specific organization (e.g., Cost Center manager, Supervisory Org manager)
    • Good for budget approvals or org-level sign-offs

    Conditional Routing:

    • Routes to different approvers based on criteria (e.g., salary > $100K routes to VP, salary < $100K routes to Director)
    • Uses Condition Rules to evaluate logic

    Static User or Group:

    • Routes to a specific person or security group
    • Use sparingly (hard to maintain if people change roles)

    4. Conditions and Criteria

    Conditions control when steps execute or which routing path the transaction takes. You define criteria, and Workday evaluates them at runtime.

    Common Condition Types:

    Due Date Criteria:

    • Define how long someone has to complete a step
    • Example: “Manager has 3 business days to approve time off”

    Step Activation Criteria:

    • Control whether a step executes at all
    • Example: “Only route to Finance approval if salary increase > 10%”

    Routing Conditions:

    • Control which approver receives the step
    • Example: “Route to VP if total compensation > $150K, route to Director if < $150K”

    Field-Based Conditions:

    • Evaluate transaction data fields
    • Example: “If Supervisory Org = Sales, route to Sales VP for approval”

    5. Notifications

    Notifications inform users about actions they need to take or events that occurred. Workday sends notifications via:

    Email:

    • External email to user’s primary work email
    • Includes transaction details and link to Workday

    Workday Inbox:

    • In-app notification in the user’s Workday inbox
    • Shows as “Action Items” or “To-Dos”

    Push Notifications:

    • Mobile app alerts (if Workday mobile app is enabled)

    When to Send Notifications:

    • When a step is assigned to someone (Approval Assigned)
    • When a step is completed (Approval Completed)
    • When a step is overdue (Overdue Reminder)
    • When the entire transaction is complete (Process Complete)

    6. Business Process Security Policy

    The Business Process Security Policy controls:

    • Who can initiate the Business Process
    • Who can approve at each step
    • Who can view in-progress or completed transactions
    • Who can cancel or rescind transactions

    Security is configured separately from routing logic. You might route an approval to a manager, but the security policy determines whether that manager actually has permission to approve.

    Step-by-Step: Configuring Your First Business Process

    Let’s configure a real-world Business Process from scratch: Request Time Off.

    Business Requirement

    Goal: Allow employees to request time off. Managers approve. HR can view all requests. Employees get notified when requests are approved or denied.

    Approval Routing:

    • Employee initiates request
    • Manager approves or denies
    • If approved, time off is granted
    • If denied, employee is notified

    Notifications:

    • Email to manager when request is submitted
    • Email to employee when request is approved or denied

    Let’s build it.

    Step 1: Navigate to the Business Process

    Search for View Business Process in Workday

    1. In the search field, type: Request Time Off
    2. Select the Request Time Off Business Process from the results
    3. Click to open the Business Process Definition

    You’ll see the current configuration, including all steps, approvals, and conditions.

    Step 2: Create a New Business Process Definition (Optional)

    If you want to create a custom variation of the Business Process (for example, different routing for different countries or organizations), you can create a new Business Process Definition.

    Why Create Custom Definitions:

    • Different approval routing for different regions (US vs. UK vs. India)
    • Different routing for different worker types (Employees vs. Contractors)
    • Different due dates or conditions based on organization

    How to Create:

    1. From the View Business Process screen, click Related Actions
    2. Select Create Business Process
    3. Choose the Business Process Type (e.g., “Request Time Off”)
    4. Name your custom definition (e.g., “Request Time Off – US Employees”)
    5. Configure the steps (we’ll do this next)

    For this guide, we’ll edit the default Business Process Definition (applies to all workers).

    Step 3: Configure Business Process Security

    Before we configure steps, we need to define WHO can initiate and approve this Business Process.

    1. From the View Business Process screen, scroll to Security Policy Configuration
    2. Click Edit

    Configure Initiators (Who Can Submit Time Off Requests):

    • Initiate: Employee as Self (workers can request their own time off)
    • Optionally add: Manager (managers can submit time off on behalf of their team)
    • Optionally add: HR Partner (HR can submit time off for workers)

    Configure Approvers (Who Can Approve Steps):

    • We’ll configure this per step in the next section

    Configure Viewers (Who Can View Requests):

    • View: Employee as Self (workers can see their own requests)
    • View: Manager (managers can see their team’s requests)
    • View: HR Partner (HR can see all requests)

    Configure Rescind/Cancel:

    • Rescind: Employee as Self (workers can cancel their own requests before approval)
    • Cancel: Manager, HR Partner (managers and HR can cancel requests)
    1. Click OK to save security configuration

    Step 4: Add Approval Steps

    Now we’ll configure the approval workflow.

    1. From the View Business Process screen, scroll to Process Steps
    2. Click Edit Process (or Configure if you’re creating a new definition)

    Current Steps (Default Configuration):

    • You’ll see existing steps (if any). We’ll modify them to match our requirements.

    Add Step 1: Manager Approval

    1. Click Add Step (or edit existing manager approval step)
    2. Configure step details:
      • Step Name: Manager Approval
      • Step Type: Approval
      • Assignee Type: Manager
      • Routing: Supervisory Organization Manager (routes to worker’s direct manager)
      • Due Date: 3 business days (manager has 3 days to approve)
      • Allow Delegation: Yes (manager can delegate to another manager if out of office)
      • Required: Yes (transaction cannot complete without this approval)
    3. Activation Criteria (when does this step execute):
      • Leave blank (step always executes for all time off requests)
      • OR add criteria: “Only execute if Time Off > 3 days” (auto-approve short requests)
    4. Click OK to save the step

    Add Step 2: Notification to Employee (Approval Complete)

    1. Click Add Step
    2. Configure step details:
      • Step Name: Notify Employee of Approval
      • Step Type: Notification
      • Assignee Type: Initiator (send notification to the employee who submitted the request)
      • Notification Method: Email
      • Email Template: Use Workday default template or create custom template
    3. Activation Criteria:
      • Trigger: When Manager Approval step is Approved
    4. Click OK

    Add Step 3: Notification to Employee (Denial)

    1. Click Add Step
    2. Configure step details:
      • Step Name: Notify Employee of Denial
      • Step Type: Notification
      • Assignee Type: Initiator
      • Notification Method: Email
    3. Activation Criteria:
      • Trigger: When Manager Approval step is Denied
    4. Click OK

    Your workflow now looks like this:

    textStep 1: Manager Approval (Approver = Manager, Due Date = 3 days)
Step 2a: Notify Employee (if approved)
Step 2b: Notify Employee (if denied)
    1. Click Done to save the Business Process configuration

    Step 5: Configure Notifications

    Now let’s configure email notifications for each step.

    1. From the View Business Process screen, scroll to Notifications
    2. Click Edit Notifications

    Configure Manager Notification (When Request is Submitted):

    • Event: Step Assigned (Manager Approval step)
    • Recipient: Manager (step assignee)
    • Email Subject: “Time Off Request from [Worker Name]”
    • Email Body: Include worker name, time off dates, time off type, balance available
    • Include Link: Yes (link to approve/deny in Workday)

    Configure Employee Notification (When Approved):

    • Event: Step Completed (Manager Approval = Approved)
    • Recipient: Initiator (employee)
    • Email Subject: “Your Time Off Request Was Approved”
    • Email Body: Include approved dates, remaining balance

    Configure Employee Notification (When Denied):

    • Event: Step Completed (Manager Approval = Denied)
    • Recipient: Initiator (employee)
    • Email Subject: “Your Time Off Request Was Denied”
    • Email Body: Include reason for denial, instructions to contact manager
    1. Click OK to save notification configuration

    Step 6: Test the Business Process

    Before activating in production, test the workflow in your Implementation Tenant or Sandbox.

    Test Scenario:

    1. Log in as an employee
    2. Navigate to Request Time Off
    3. Select time off type (Vacation)
    4. Select dates (next week, 3 days)
    5. Submit request

    Expected Results:

    • Request routes to your manager’s inbox
    • Manager receives email notification
    • Manager can approve or deny from email link or Workday inbox
    • If approved, employee receives approval email
    • If denied, employee receives denial email
    • Time off balance updates automatically (if approved)

    Check:

    • Did the approval route to the correct manager?
    • Did email notifications send correctly?
    • Did the due date calculate correctly (3 business days)?
    • Can the employee view the request status?
    • Can HR view the request?

    If everything works, you’re ready to activate in production.

    Step 7: Activate Pending Changes

    After configuring the Business Process, you must activate your changes.

    1. Search for Activate Pending Security Policy Changes
    2. Review pending changes (your Business Process configuration updates)
    3. Click OK to activate

    Changes take effect immediately. All new time off requests will follow your configured workflow.

    Advanced Configuration: Conditional Approval Routing

    Let’s add complexity. Suppose you have this requirement:

    Business Rule:
    “If an employee requests more than 10 consecutive days off, route to both Manager AND HR for approval. If less than 10 days, route to Manager only.”

    Here’s how to configure conditional routing:

    Step 1: Edit the Business Process

    1. Navigate to View Business Process > Request Time Off
    2. Click Edit Process

    Step 2: Add Condition Rule

    1. Click Add Step (before Manager Approval step)
    2. Select Step Type: Condition
    3. Condition Name: Check Time Off Duration
    4. Criteria: Evaluate Number of Days Requested

    Configure condition logic:

    IF Number of Days Requested > 10:

    • Route to Path A (Manager + HR Approval)

    ELSE (Number of Days ≤ 10):

    • Route to Path B (Manager Approval Only)

    Step 3: Configure Path A (Long Time Off)

    Add Step: Manager Approval

    • Step Name: Manager Approval (Long Time Off)
    • Assignee: Manager
    • Due Date: 3 business days
    • Activation Criteria: Condition = “Number of Days > 10”

    Add Step: HR Approval

    • Step Name: HR Approval (Long Time Off)
    • Assignee: HR Partner (role-based routing)
    • Due Date: 3 business days
    • Activation Criteria: Condition = “Number of Days > 10” AND Manager Approval = Approved

    Step 4: Configure Path B (Short Time Off)

    Add Step: Manager Approval

    • Step Name: Manager Approval (Short Time Off)
    • Assignee: Manager
    • Due Date: 3 business days
    • Activation Criteria: Condition = “Number of Days ≤ 10”

    Step 5: Save and Test

    Test Long Time Off Request (15 days):

    • Routes to Manager
    • If Manager approves, routes to HR
    • If HR approves, request is granted

    Test Short Time Off Request (3 days):

    • Routes to Manager only
    • If Manager approves, request is granted (no HR step)

    Advanced Configuration: Role-Based Approval Routing

    Let’s configure another scenario:

    Business Rule:
    “For compensation changes, route to Manager first. If salary increase > 10%, route to Finance for budget approval. If salary increase > 20%, route to VP for executive approval.”

    Here’s how to configure multi-level conditional routing:

    Step 1: Edit Request Compensation Change Business Process

    1. Navigate to View Business Process > Request Compensation Change
    2. Click Edit Process

    Step 2: Add Approval Steps with Conditions

    Step 1: Manager Approval

    • Assignee: Manager
    • Activation Criteria: Always (all comp changes require manager approval)

    Step 2: Finance Approval (If Increase > 10%)

    • Assignee: Finance Partner (role-based security group)
    • Activation Criteria:
      • Manager Approval = Approved AND
      • Percentage Salary Increase > 10%

    Step 3: VP Approval (If Increase > 20%)

    • Assignee: Organization Owner (Cost Center manager at VP level)
    • Activation Criteria:
      • Manager Approval = Approved AND
      • Finance Approval = Approved AND
      • Percentage Salary Increase > 20%

    Step 3: Test Scenarios

    Scenario 1: 5% Salary Increase

    • Routes to Manager only
    • If Manager approves, comp change completes

    Scenario 2: 15% Salary Increase

    • Routes to Manager
    • Routes to Finance
    • If both approve, comp change completes

    Scenario 3: 25% Salary Increase

    • Routes to Manager
    • Routes to Finance
    • Routes to VP
    • If all approve, comp change completes

    Business Process Best Practices

    1. Keep Approval Chains Short (3 Steps Maximum)

    The Problem:
    Teams add too many approval steps. Every transaction requires 5-7 approvals, taking weeks to complete.

    The Fix:
    Limit approval steps to 3 maximum. Use conditional routing to add approvals only when necessary (high-value transactions, exceptions).

    Example:
    Instead of: Manager → Director → VP → Finance → HR → CEO
    Use: Manager → Finance (if > $10K) → VP (if > $50K)

    2. Set Realistic Due Dates

    The Problem:
    Due dates are too short (1 day) or too long (30 days). Approvers ignore short deadlines. Long deadlines cause transactions to sit in inboxes forever.

    The Fix:
    Use 3-5 business days for most approvals. Use 1-2 days for urgent transactions. Use escalation if approvals go overdue.

    3. Enable Delegation for Manager Approvals

    The Problem:
    Manager goes on vacation. All approvals sit in their inbox for 2 weeks. Team can’t take time off or complete transactions.

    The Fix:
    Enable Allow Delegation on manager approval steps. Managers can delegate to another manager if they’re out of office.

    4. Use Role-Based Routing (Not Static Users)

    The Problem:
    Business Process routes approvals to “John Smith” (specific user). John leaves the company. Approvals break.

    The Fix:
    Route to roles (HR Partner, Finance Partner) or organization owners (Cost Center Manager), not static users.

    5. Send Email Notifications for Action Items

    The Problem:
    Approvals sit in Workday inbox. Users don’t check Workday daily. Approvals go unnoticed.

    The Fix:
    Enable email notifications for all approval steps. Include a direct link to approve/deny in the email.

    6. Test in Sandbox Before Activating in Production

    The Problem:
    You edit a Business Process in production. Routing breaks. All hires, terminations, or comp changes get stuck.

    The Fix:
    Always test Business Process changes in Sandbox or Implementation Tenant first. Validate routing, notifications, and security before promoting to production.

    7. Document Your Business Process Configuration

    The Problem:
    No one knows why approvals route the way they do. When someone asks “Why does this route to Finance?”, no one has an answer.

    The Fix:
    Create a Business Process Documentation spreadsheet:

    • Business Process Name
    • Approval Steps and Order
    • Routing Logic (who approves at each step)
    • Conditions and Criteria
    • Due Dates
    • Notification Recipients
    • Business Owner (who approved this configuration)

    Common Mistakes and How to Avoid Them

    Mistake 1: Not Activating Pending Security Policy Changes

    The Problem:
    You configure a Business Process. You test it. Nothing happens. Approvals don’t route correctly.

    What You Forgot:
    You didn’t activate pending changes. Business Process configuration changes don’t take effect until you run Activate Pending Security Policy Changes.

    The Fix:
    After any Business Process configuration change, navigate to Activate Pending Security Policy Changes and activate.

    Mistake 2: Circular Routing Logic

    The Problem:
    You configure approval routing with circular logic: Step A routes to Step B, Step B routes to Step C, Step C routes back to Step A.

    What Happens:
    Transactions get stuck in an infinite loop. Approvals never complete.

    The Fix:
    Draw out your approval workflow on paper before configuring. Validate that each step has a clear path to completion (no circular references).

    Mistake 3: Forgetting to Grant Security Group Permissions

    The Problem:
    You configure a step to route to “HR Partner” role. No one in the HR Partner security group can approve because they don’t have Business Process Security Policy permissions.

    What Happens:
    Approvals route to HR inbox, but HR can’t approve. Transactions get stuck.

    The Fix:
    Always check Business Process Security Policy configuration. Grant the security group permission to Approve at the appropriate step.

    Mistake 4: Over-Relying on Static User Routing

    The Problem:
    You route approvals to specific users by name. Users change roles, leave the company, or go on extended leave. Approvals break.

    The Fix:
    Use role-based routing (HR Partner, Finance Partner) or organization owner routing (Cost Center Manager, Supervisory Org Manager). These update automatically when role assignments change.

    Mistake 5: Not Testing Edge Cases

    The Problem:
    You test the “happy path” (manager approves, transaction completes). You don’t test denials, cancellations, or conditional routing edge cases.

    What Happens:
    Production issues surface when edge cases occur (manager denies, worker cancels, conditional routing fails).

    The Fix:
    Test ALL scenarios:

    • Approval
    • Denial
    • Cancellation
    • Delegation
    • Overdue (what happens if no one approves within due date?)
    • Conditional routing (both paths: condition true, condition false)

    Workday Tasks for Business Process Configuration

    View and Edit Business Processes:

    • View Business Process (see current configuration)
    • Edit Business Process (modify steps, routing, conditions)
    • Create Business Process (create custom definition for specific orgs or regions)

    Business Process Security:

    • Edit Business Process Security Policy (configure who can initiate, approve, view, cancel)
    • Activate Pending Security Policy Changes (activate configuration changes)

    Testing and Validation:

    • Initiate Business Process (test by submitting a transaction)
    • View Event (see transaction history and routing log)
    • View Inbox (check if approvals route correctly)

    Reporting:

    • Business Process History (audit trail of all transactions)
    • Outstanding Business Processes (see stuck or overdue approvals)

    Final Thoughts

    Business Process configuration is where Workday’s automation power lives. Get it right, and transactions flow smoothly through approvals, notifications fire correctly, and your tenant runs like clockwork.

    Get it wrong, and every hire takes 47 days, approvals route to the wrong people, and your HR team spends hours troubleshooting stuck workflows.

    The keys to success:

    • Understand the anatomy of a Business Process (steps, routing, conditions, notifications, security)
    • Keep approval chains short (3 steps maximum)
    • Use role-based routing instead of static users
    • Test thoroughly in sandbox before activating in production
    • Document your configuration for future maintenance

    Start simple. Build one Business Process correctly. Test it. Document it. Then move to the next one.

    Your future self (and your Workday admin team) will thank you.