peopletechguide.com

Category: Core HCM (Functional)

  • Build Workday Organization Hierarchy from Scratch

    Here’s a confession from every Workday implementation:

    • Week 1, someone asks: “How should we structure our organizations?”
    • Week 3, someone says: “Let’s just copy our current org chart.”
    • Week 8, someone realizes: “Wait, this doesn’t work the way we thought.”
    • Week 20, someone admits: “We need to redesign the entire organization structure.”

    I’ve watched this pattern repeat across dozens of Workday implementations. Teams rush to build organization hierarchies without understanding how they actually work in Workday. They treat Supervisory Orgs like departments, Cost Centers like teams, and wonder why security breaks, approvals route incorrectly, and reports pull the wrong data.

    The truth is this: your organization hierarchy is the structural foundation of your entire Workday tenant. Get it right from day one, and Workday runs smoothly. Get it wrong, and you’ll spend months fixing downstream consequences.

    This guide walks you through building Workday organization hierarchies from scratch. We’ll cover Supervisory Organizations, Cost Centers, superior org logic, manager assignments, and the design decisions that separate clean implementations from messy ones.

    Let’s build it right the first time.

    Why Organization Hierarchy Matters in Workday

    Organizations in Workday are not just labels or groupings. They are active system objects that control critical functionality across your entire tenant.

    Your organization hierarchy determines:

    Security and Data Access:

    • Which HR Partners can see which workers
    • Which Payroll Partners can process payroll for which teams
    • Which managers inherit role-based permissions
    • How domain security scopes access by organization

    Business Process Routing:

    • Where hiring approvals go
    • Who approves compensation changes
    • How time off requests route to managers
    • Which stakeholders review terminations

    Reporting and Analytics:

    • How you slice headcount by department, location, or business unit
    • How Finance reports costs by Cost Center
    • How HR tracks diversity metrics by organization
    • How leadership views organizational spans of control

    Financial Postings:

    • Where worker costs land in the General Ledger
    • How budget vs. actuals roll up by Cost Center
    • Which organizations own spend and expenses

    Get your organization hierarchy wrong, and all of these break. Security fails. Approvals route incorrectly. Reports pull bad data. Finance can’t reconcile costs.

    The time to fix organization design is before you load workers, not after.

    Understanding Workday Organization Types

    Before we build anything, let’s clarify what we’re building. Workday provides several organization types, but two are critical for most implementations:

    Supervisory Organizations

    What They Are:
    Supervisory Organizations (Sup Orgs) define your reporting structure. They group workers who report to the same manager and form a hierarchical tree that mirrors your organizational chart.

    What They Control:

    • Worker reporting relationships (who reports to whom)
    • Business process routing (hiring, promotions, terminations, comp changes)
    • Role-based security (HR Partner, Payroll Partner roles are assigned at the Supervisory Org level)
    • Approval chains (time off, expenses, requisitions route through the Supervisory Org hierarchy)
    • Manager self-service access (managers can see and manage their team)

    Key Point:
    If your Supervisory Org tree is wrong, everything downstream breaks. Approvals route to the wrong manager. Security grants access to the wrong workers. Reports show incorrect reporting lines.

    Cost Centers

    What They Are:
    Cost Centers represent financial responsibility. They are the organizational unit that owns the budget, tracks spend, and posts to the General Ledger.

    What They Control:

    • Budgeting and forecasting (Cost Centers are the primary dimension for budget allocation)
    • Spend analytics (requisitions, expenses, journal entries route to Cost Center managers)
    • General Ledger posting (worker costs post to the GL based on Cost Center assignment)
    • Financial reporting (Finance reports actuals vs. budget by Cost Center hierarchy)

    Key Point:
    Cost Centers tell Finance who owns the numbers. Supervisory Orgs show reporting lines. Cost Centers show financial lines. These are often (but not always) the same.

    The Foundation: Superior Organization Logic

    Every organization hierarchy in Workday is built using superior organization relationships. This is the single most important concept to understand before you create a single organization.

    How Superior Org Logic Works

    In Workday, organizations don’t exist in isolation. Every organization (except the top-level organization) has a superior organization above it in the hierarchy.

    Think of it like a family tree:

    • Parent Org (superior)
    • Child Org (subordinate to the parent)
    • Grandchild Org (subordinate to the child, which is subordinate to the parent)

    When you create an organization, you define its superior organization. Workday automatically builds the hierarchy tree based on these relationships.

    Example:

    textCEO Organization (top-level, no superior)
├── Sales Organization (superior: CEO Organization)
│   ├── Sales North America (superior: Sales Organization)
│   └── Sales EMEA (superior: Sales Organization)
├── Engineering Organization (superior: CEO Organization)
│   ├── Engineering Product (superior: Engineering Organization)
│   └── Engineering Platform (superior: Engineering Organization)
└── Finance Organization (superior: CEO Organization)

    Each organization points to its superior. Workday builds the tree automatically.

    Why Superior Org Logic Matters

    Superior org relationships control:

    • Hierarchy roll-ups: Reports can roll up headcount, costs, and data by superior org
    • Security inheritance: Role-based security can inherit down the org tree
    • Approval routing: Some business processes route approvals up the superior org chain
    • Reporting structures: Organizational charts and workforce planning tools use superior org logic

    If you assign the wrong superior org, the hierarchy breaks. Workers appear in the wrong branch of the tree. Reports pull incorrect data. Security grants access to the wrong teams.

    Step-by-Step: Building Your First Supervisory Organization Hierarchy

    Let’s walk through building a Supervisory Organization hierarchy from scratch. We’ll use a realistic example: a mid-sized company with 500 employees across Sales, Engineering, Finance, and HR.

    Step 1: Design the Hierarchy on Paper First

    Before you touch Workday, map out your organization structure on paper (or a spreadsheet). Answer these questions:

    What are your top-level organizations?

    • CEO
    • Sales
    • Engineering
    • Finance
    • HR
    • Operations

    What are the subordinate organizations under each?

    • Sales: Sales North America, Sales EMEA, Sales APAC
    • Engineering: Engineering Product, Engineering Platform, Engineering Data
    • Finance: Finance FP&A, Finance Accounting, Finance Tax
    • HR: HR Business Partners, HR Talent Acquisition, HR Payroll

    Who are the managers for each organization?

    • CEO Org: Jane Smith (CEO)
    • Sales Org: Tom Johnson (VP Sales)
    • Sales North America: Sarah Lee (Director Sales NA)
    • Engineering Org: Mike Chen (VP Engineering)

    How many levels deep is your hierarchy?

    • Level 1: CEO
    • Level 2: VPs (Sales, Engineering, Finance, HR)
    • Level 3: Directors (by function or region)
    • Level 4: Managers
    • Level 5: Individual Contributors (optional: some orgs put ICs in their own leaf orgs)

    Design Principles:

    • Keep hierarchies shallow (3-5 levels maximum, avoid 7+ levels)
    • Align with reporting lines (Supervisory Orgs follow who reports to whom, not budget ownership)
    • Use clear naming conventions (e.g., “Sales – North America” not “NA Sales Team”)
    • Plan for growth (leave room for future orgs without redesigning the entire tree)

    Step 2: Create the Top-Level Organization

    We’ll start by creating the CEO Organization (the top of the tree).

    Navigate to Workday:

    1. Search for Create Supervisory Organization
    2. Click the task to open it

    Fill in Organization Details:

    • Organization Name: CEO Organization
    • Organization Code: ORG-CEO (create a unique code for reference)
    • Organization Type: Supervisory
    • Superior Organization: Leave blank (this is the top-level org, it has no superior)
    • Manager: Jane Smith (search by name or Employee ID)
    • Default Cost Center: (optional, can assign a default Cost Center for workers in this org)
    • Effective Date: Your go-live date or the date the org becomes active

    Click OK to submit.

    Workday creates the organization and assigns Jane Smith as the manager.

    Key Points:

    • The top-level organization has NO superior organization
    • Every other organization in your hierarchy will have a superior
    • The manager you assign becomes the default approver for workers in this org
    • Organization Code is your external reference ID (use it for EIB loads and integrations)

    Step 3: Create Second-Level Organizations (VPs)

    Now we’ll create the VP-level organizations that report to the CEO.

    Create Sales Organization:

    1. Navigate to Create Supervisory Organization
    2. Fill in:
      • Organization Name: Sales Organization
      • Organization Code: ORG-SALES
      • Organization Type: Supervisory
      • Superior Organization: CEO Organization (search and select)
      • Manager: Tom Johnson (VP Sales)
      • Effective Date: Same as CEO org
    3. Click OK

    Repeat for other VP-level orgs:

    • Engineering Organization (superior: CEO Organization, manager: Mike Chen)
    • Finance Organization (superior: CEO Organization, manager: Lisa Brown)
    • HR Organization (superior: CEO Organization, manager: David Kim)

    Your hierarchy now looks like this:

    textCEO Organization (Jane Smith)
├── Sales Organization (Tom Johnson)
├── Engineering Organization (Mike Chen)
├── Finance Organization (Lisa Brown)
└── HR Organization (David Kim)

    Step 4: Create Third-Level Organizations (Directors)

    Now we’ll create Director-level organizations under each VP org.

    Create Sales North America:

    1. Navigate to Create Supervisory Organization
    2. Fill in:
      • Organization Name: Sales – North America
      • Organization Code: ORG-SALES-NA
      • Organization Type: Supervisory
      • Superior Organization: Sales Organization (NOT CEO Organization)
      • Manager: Sarah Lee (Director Sales NA)
      • Effective Date: Same as parent org
    3. Click OK

    Repeat for other Director orgs:

    • Sales – EMEA (superior: Sales Organization)
    • Sales – APAC (superior: Sales Organization)
    • Engineering – Product (superior: Engineering Organization)
    • Engineering – Platform (superior: Engineering Organization)
    • Finance – FP&A (superior: Finance Organization)
    • Finance – Accounting (superior: Finance Organization)

    Your hierarchy now looks like this:

    textCEO Organization (Jane Smith)
├── Sales Organization (Tom Johnson)
│   ├── Sales - North America (Sarah Lee)
│   ├── Sales - EMEA (John Davis)
│   └── Sales - APAC (Amy Wong)
├── Engineering Organization (Mike Chen)
│   ├── Engineering - Product (Alex Garcia)
│   └── Engineering - Platform (Maria Lopez)
├── Finance Organization (Lisa Brown)
│   ├── Finance - FP&A (Robert Taylor)
│   └── Finance - Accounting (Jennifer White)
└── HR Organization (David Kim)

    Step 5: Create Fourth-Level Organizations (Managers)

    Continue building down the hierarchy for Manager-level orgs.

    Example: Create Sales – NA East:

    1. Navigate to Create Supervisory Organization
    2. Fill in:
      • Organization Name: Sales – NA East
      • Organization Code: ORG-SALES-NA-EAST
      • Organization Type: Supervisory
      • Superior Organization: Sales – North America (NOT Sales Organization)
      • Manager: James Wilson (Sales Manager East)
    3. Click OK

    Continue until your full hierarchy is built.

    Step 6: Validate the Hierarchy Tree

    After creating all organizations, validate that the hierarchy is correct.

    Navigate to:

    1. Search for View Supervisory Organization
    2. Select CEO Organization
    3. Click Organization Chart or View Hierarchy

    Workday displays your full org tree visually.

    Check for:

    • All organizations appear in the correct superior/subordinate relationships
    • No orphaned orgs (orgs that don’t appear anywhere in the tree)
    • Managers are assigned correctly
    • Naming conventions are consistent

    Common Issues:

    • Org appears in the wrong branch: You assigned the wrong superior org. Edit the org and correct the superior.
    • Org doesn’t appear at all: You forgot to assign a superior (unless it’s the top-level org). Edit and add superior.
    • Circular reference error: Org A is superior to Org B, Org B is superior to Org C, Org C is superior to Org A. Fix by breaking the circular reference.

    Step-by-Step: Building Your Cost Center Hierarchy

    Cost Centers work the same way as Supervisory Organizations, but they represent financial responsibility instead of reporting lines.

    Step 1: Design the Cost Center Structure

    Work with Finance to design the Cost Center hierarchy. It should align with:

    • Your Chart of Accounts structure
    • Budget ownership and responsibility
    • How Finance wants to report actuals vs. budget

    Example Cost Center Structure:

    textCorporate Cost Center (top-level)
├── Sales Cost Center
│   ├── Sales NA Cost Center
│   ├── Sales EMEA Cost Center
│   └── Sales APAC Cost Center
├── Engineering Cost Center
│   ├── Engineering Product Cost Center
│   └── Engineering Platform Cost Center
├── Finance Cost Center
└── HR Cost Center

    Key Decision:
    Do Cost Centers mirror Supervisory Orgs exactly? Or do they differ?

    • Same structure: Easier to maintain, simpler for users to understand
    • Different structure: More flexible for Finance reporting, but adds complexity

    Step 2: Create Cost Centers

    The process is identical to creating Supervisory Organizations, but you use Create Cost Center task instead.

    Create Top-Level Cost Center:

    1. Search for Create Cost Center
    2. Fill in:
      • Cost Center Name: Corporate Cost Center
      • Cost Center Code: CC-CORP
      • Organization Type: Cost Center
      • Superior Organization: Leave blank (top-level)
      • Manager: CFO or Finance Director
      • Effective Date: Go-live date
    3. Click OK

    Create Subordinate Cost Centers:
    Repeat for each Cost Center, assigning the correct superior Cost Center.

    Step 3: Assign Cost Centers to Workers

    Once Cost Centers are created, assign them to workers.

    Option 1: Assign Default Cost Center at Supervisory Org Level

    • Navigate to Edit Supervisory Organization
    • Set Default Cost Center for the org
    • All workers in that Supervisory Org inherit the Cost Center automatically

    Option 2: Assign Cost Center Individually

    • Navigate to Change Job for a worker
    • Assign Cost Center on the Job Details page
    • This overrides the default Cost Center from Supervisory Org

    Critical Design Decisions

    Decision 1: Where Does the Manager Sit?

    This is the most common org hierarchy mistake:

    Should the manager sit INSIDE the org they manage, or in the SUPERIOR org?

    The Right Answer:
    Managers should sit in the superior organization of the org they manage, NOT inside it.

    Example:

    CORRECT:

    textSales Organization (Tom Johnson, VP Sales)
├── Sales - North America (Sarah Lee, Director Sales NA)
│   ├── James Wilson (Sales Manager, reports to Sarah)
│   ├── Emily Davis (Sales Rep, reports to James)
│   └── Mark Thompson (Sales Rep, reports to James)

    Tom Johnson sits in CEO Organization (superior to Sales Organization).
    Sarah Lee sits in Sales Organization (superior to Sales – North America).
    James Wilson sits in Sales – North America (manages reps in his own org).

    INCORRECT:

    textSales Organization (Tom Johnson sits HERE, manages Sales Org)
├── Sales - North America (Sarah Lee sits HERE, manages Sales NA)

    Why This Matters:

    • Security inheritance works correctly when managers sit in superior orgs
    • Approval routing flows up the chain properly
    • Role-based access grants managers permission to see subordinate orgs
    • Prevents weird permission overlaps and conflicts

    Decision 2: How Deep Should the Hierarchy Go?

    Recommended Depth:
    3-5 levels maximum

    Why:

    • Deep hierarchies (7+ levels) slow approvals
    • Every approval step adds delay and complexity
    • Reporting becomes harder to navigate
    • Security configuration gets messy

    If You Have More Than 5 Levels:

    • Flatten the hierarchy by combining levels
    • Use Custom Organizations for matrix relationships instead of adding Supervisory Org levels
    • Consider whether every level truly represents a distinct manager with approval authority

    Decision 3: Should Individual Contributors Have Their Own Orgs?

    Option 1: ICs Report Directly to Manager’s Org

    • Manager’s org contains both the manager and their direct reports
    • Simpler structure, fewer orgs to maintain
    • Works well for small teams (manager + 3-10 ICs)

    Option 2: ICs Have Their Own Subordinate Org

    • Manager sits in superior org, ICs sit in subordinate org
    • More granular reporting and security scoping
    • Works well for large teams (manager + 20+ ICs) or when you need to segment by sub-team

    Most Common Approach:
    Option 1 for small teams, Option 2 for large teams.

    Decision 4: Naming Conventions

    Use clear, consistent naming conventions for all organizations:

    Good Examples:

    • Sales – North America
    • Engineering – Product
    • Finance – Accounting
    • HR – Talent Acquisition

    Bad Examples:

    • NA Sales Team (inconsistent format)
    • Eng Prod (abbreviations aren’t clear)
    • Accounting Dept (mixing “Finance” and “Dept”)

    Best Practices:

    • Start with function or department name
    • Add geography, sub-function, or team type after a separator (dash or comma)
    • Avoid abbreviations unless universally understood
    • Keep names concise (under 50 characters)
    • Use title case for readability

    Assigning Workers to Organizations

    Once your org hierarchy is built, you need to assign workers to organizations.

    For New Hires

    When you hire a new worker, you assign their Supervisory Organization and Cost Center on the Hire Employee task:

    1. Navigate to Hire Employee
    2. Fill in worker details
    3. In Job Details section:
      • Supervisory Organization: Select the org the worker reports to
      • Cost Center: Select the Cost Center for financial tracking
      • Manager: Workday assigns the manager automatically based on Supervisory Org
    4. Submit and approve

    For Existing Workers

    When you need to move a worker to a new organization, use Change Job:

    1. Navigate to Change Job
    2. Select the worker
    3. In Organizations section:
      • Update Supervisory Organization (if reporting line changes)
      • Update Cost Center (if financial responsibility changes)
    4. Set Effective Date
    5. Submit for approval

    Common Mistakes and How to Avoid Them

    Mistake 1: Building Orgs Based on Locations or Departments Instead of Reporting Lines

    The Problem:
    Teams create Supervisory Orgs for “Seattle Office” or “Marketing Department” without thinking about who reports to whom.

    What Happens:
    Workers in the same office report to different managers, but they’re all in the same Supervisory Org. Approvals route incorrectly. Security breaks.

    The Fix:
    Supervisory Orgs follow reporting relationships. If workers in Seattle report to different managers, they should be in different Supervisory Orgs. Use Locations for geography and Custom Orgs for departments that cross reporting lines.

    Mistake 2: Creating Organizations After Loading Workers

    The Problem:
    Team loads 500 workers into Workday, then realizes they need to create organizations. Now they have to mass-update 500 worker records to assign orgs.

    What Happens:
    Mass updates through Change Job trigger 500 approval workflows. Data quality suffers. Rework takes weeks.

    The Fix:
    Build your organization hierarchy before you load workers. Orgs should exist in Workday before the first worker is hired or migrated.

    Mistake 3: Not Planning for Future Growth

    The Problem:
    You build a hierarchy for today’s 500 employees. Company grows to 2,000 employees. Hierarchy doesn’t scale. You need to restructure.

    What Happens:
    Mass org reassignments. Business process disruptions. Reports break. Security needs reconfiguration.

    The Fix:
    Design your hierarchy for scale. Leave room for new regions, new departments, new functions. Build flexibility into the structure from day one.

    Mistake 4: Inconsistent Superior Org Assignments

    The Problem:
    Sales – North America reports to Sales Organization. Sales – EMEA accidentally reports to CEO Organization (skipping Sales Organization).

    What Happens:
    Hierarchy tree looks broken. Roll-up reports are incorrect. Tom Johnson (VP Sales) can’t see EMEA team data because they don’t roll up to his org.

    The Fix:
    Validate superior org assignments carefully. Use View Supervisory Organization Hierarchy to visually check the tree structure before go-live.

    Workday Tasks for Organization Management

    Create Organizations:

    • Create Supervisory Organization (build Supervisory Org hierarchy)
    • Create Cost Center (build Cost Center hierarchy)
    • Create Region (build geographic groupings)
    • Create Custom Organization (build matrix or project-based orgs)

    Edit Organizations:

    • Edit Supervisory Organization (change superior, manager, or org details)
    • Edit Cost Center (change superior, manager, or cost center details)
    • Inactivate Organization (deprecate old orgs without deleting them)

    View and Validate:

    • View Supervisory Organization (see org details and hierarchy)
    • View Organization Chart (visualize reporting structure)
    • View Cost Center Hierarchy (see Cost Center roll-ups)

    Assign Organizations to Workers:

    • Hire Employee (assign orgs for new hires)
    • Change Job (update orgs for existing workers)
    • Change Organization Assignments (bulk update org assignments)

    Final Thoughts

    Building a Workday organization hierarchy from scratch isn’t complicated. It just requires thoughtful planning and disciplined execution.

    Start with these steps:

    1. Design the hierarchy on paper first (align with stakeholders)
    2. Use superior org logic correctly (every org points to its superior)
    3. Keep hierarchies shallow (3-5 levels maximum)
    4. Follow clear naming conventions (consistent, readable, scalable)
    5. Build orgs BEFORE loading workers (avoid mass updates later)
    6. Validate the hierarchy tree before go-live (check superior relationships)

    Get your organization hierarchy right from day one, and everything else in Workday works smoothly. Security flows correctly. Approvals route properly. Reports pull accurate data. Finance can reconcile costs.

    Get it wrong, and you’ll spend months untangling org assignments, fixing security, and rebuilding hierarchies.

    Start simple. Plan for scale. Document everything.

  • Understanding Workday Organization Types Right

    Every Workday implementation team faces the same question in Week 1: “How should we structure our organizations?”

    And almost every time, someone says: “They’re all basically the same, right? Just different names for groups of people.”

    Wrong.

    Choosing the wrong organization type is one of the fastest ways to create security gaps, break approval workflows, and turn reporting into a nightmare. Workday organizations are not interchangeable. Each type serves a specific functional purpose, drives distinct system behaviors, and impacts everything from business processes to financial postings.​

    If you design your organization structure incorrectly from day one, you will spend months—or years—fixing the downstream consequences.

    This guide explains exactly what each Workday organization type does, when to use it, and how to avoid the most common mistakes that break Workday designs.

    Why Organization Design Matters in Workday

    Organizations in Workday are not just labels. They are the structural foundation of your entire tenant.​

    Organizations control:

    • Security domains – Who can see and edit which worker data
    • Business process routing – Where approvals go and who signs off
    • Reporting hierarchies – How you analyze workforce data
    • Financial postings – Where costs land in the General Ledger
    • Role-based access – Which managers inherit permissions down the hierarchy​

    Get your organization design right early, and Workday runs smoothly. Get it wrong, and you will face:

    • Broken approval chains that route to the wrong manager
    • Security domains that expose sensitive data or lock out HR
    • Reports that pull incorrect headcount or cost data
    • GL postings that land in the wrong cost center or company
    • Rework that requires mass updates, org redesigns, and business process changes​

    The time to fix organization design is before go-live, not after.

    The Core Workday Organization Types

    Workday delivers several organization types out of the box. Each one has a distinct purpose, distinct configuration tasks, and distinct domain security.​

    Let’s break down the big three—and why they are not interchangeable.

    1. Supervisory Organizations: The Backbone of Your Workday Experience

    What They Are:
    Supervisory Organizations (Sup Orgs) define your reporting structure. They group workers who report to the same manager and form a hierarchical tree that mirrors your organizational chart.​

    What They Control:
    Supervisory Orgs are the most powerful organization type in Workday HCM because they drive:

    • Worker reporting relationships – Who reports to whom
    • Business process routing – Hiring, promotions, terminations, job changes, and compensation all route through the Supervisory Org hierarchy​
    • Role-based security – Roles like “HR Partner” or “Manager” are assigned at the Supervisory Org level and inherit down the tree by default​
    • Approval chains – Time off, expenses, and other transactions route to the manager of the worker’s Supervisory Org​
    • Advanced Compensation workflows – Comp planning, merit increases, and bonus allocation follow the Supervisory Org structure

    Why This Matters:
    If your Supervisory Org tree is wrong, everything downstream breaks.​

    Example: A worker sits in the wrong Supervisory Org. Their time-off request routes to a manager in another department. That manager has no context, delays approval, and the worker misses their flight.

    That is not a process problem. That is an organization design problem.

    Key Design Rules:

    • Managers should sit in the superior organization of the org they manage, not inside it​
    • Every Supervisory Org must have one assigned manager​
    • Use Supervisory Org subtypes (e.g., “Corporate,” “Field,” “Shared Services”) to segment different parts of the business without creating separate trees​
    • Default Cost Center can be assigned at the Supervisory Org level to streamline financial defaults​

    Common Mistakes:

    • Creating too many levels (7+ layers) that slow approvals and complicate security
    • Assigning managers to positions inside the org they manage, which creates inheritance conflicts
    • Using Supervisory Orgs to track project teams or matrix relationships (use Custom Orgs instead)

    2. Cost Centers: Your Financial Source of Truth

    What They Are:
    Cost Centers represent financial responsibility. They are the organizational unit that owns the budget, tracks spend, and posts to the General Ledger.​

    What They Control:

    • Budgeting and forecasting – Cost Centers are the primary dimension for budget allocation in Workday
    • Spend analytics – Purchase requisitions, expense reports, and journal entries route to Cost Center managers for financial approval​
    • General Ledger posting – Worker costs (salary, benefits, taxes) post to the GL based on the worker’s Cost Center assignment
    • Financial reporting – Finance teams report actuals vs. budget by Cost Center hierarchy

    Why This Matters:
    Cost Centers tell Finance who owns the numbers.​

    Supervisory Orgs show the reporting line. Cost Centers show the financial line.

    These are often—but not always—the same.

    Example: A worker reports to a manager in the Sales Supervisory Org but is funded by the Marketing budget. Their Supervisory Org is Sales. Their Cost Center is Marketing. Workday tracks both, and reports accordingly.

    Key Design Rules:

    • Assign one primary Cost Center per worker (Workday supports split costing, but keep it simple at first)
    • Cost Center hierarchy should mirror your chart of accounts structure
    • Cost Center managers approve financial transactions (requisitions, expenses, journals) while Supervisory Org managers approve HR transactions (time off, job changes)​
    • Use Cost Center View security to control which Finance users can see which cost data​

    Common Mistakes:

    • Conflating Supervisory Orgs and Cost Centers (“They’re the same thing, right?”)
    • Not assigning a Cost Center manager, which breaks expense and requisition approvals​
    • Creating Cost Centers at too granular a level, which clutters GL reporting

    3. Companies: Legal Entities That Drive Financial Structures

    What They Are:
    Companies represent your legal entities. In Workday, a Company is the top-level organization for Financials, Payroll, and Benefits.​

    What They Control:

    • Legal entity assignment – Every worker must be assigned to a Company
    • Payroll processing – Payroll runs by Company
    • Benefits eligibility – Benefit plans are configured by Company
    • Chart of Accounts – The General Ledger is structured by Company, and Company is the first dimension in every GL posting​
    • Tax and compliance – Legal reporting (W-2s, statutory filings, labor law compliance) is Company-specific

    Why This Matters:
    If you operate in multiple countries or have multiple legal entities (e.g., a holding company with subsidiaries), you must configure each as a separate Company in Workday.

    Key Design Rules:

    • One Company per legal entity
    • Company hierarchy can roll up to a parent for consolidated reporting
    • Do not create “fake” Companies for reporting convenience—use Custom Orgs or Regions instead
    • Ensure workers are assigned to the correct Company for tax and payroll purposes

    Common Mistakes:

    • Using “Company” as a proxy for “division” or “business unit” (use Supervisory Orgs or Custom Orgs instead)
    • Not aligning Company structure with your legal entity structure, which breaks tax and statutory compliance

    4. Regions: Geographic Groupings

    What They Are:
    Regions group workers, locations, and organizations by geography.​

    What They Control:

    • Geographic reporting – Headcount, costs, and workforce analytics by region
    • Regional compliance – Policies, business processes, and benefits that vary by geography
    • Location-based security – Regional HR partners can be granted access to workers in their assigned region
    • Regional management layers – Some organizations use Region hierarchies to create geographic leadership structures (e.g., EMEA Director, APAC VP)

    Why This Matters:
    If you operate globally, Regions help you segment workers, track regional performance, and assign region-specific HR support without creating duplicate Supervisory Org trees.​

    Example: A global company has one Supervisory Org hierarchy for reporting lines but uses Regions to group workers into North America, EMEA, APAC, and LATAM for regional HR team assignments and compliance tracking.

    Key Design Rules:

    • Use Regions for geography, not for business units or functions
    • Region assignment can inherit from Location, or be assigned manually
    • Keep Region hierarchies simple (2-3 levels maximum)
    • Use Regions in security policies to grant HR partners access to workers in their geography​

    Common Mistakes:

    • Creating Regions for non-geographic groupings (e.g., “Remote Workers” as a Region)
    • Overcomplicating Region hierarchies with too many sub-levels
    • Not using Regions at all, then manually maintaining geographic access lists

    5. Custom Organizations: Flexibility for Everything Else

    What They Are:
    Custom Organizations are user-defined organizations that capture any business dimension not covered by Supervisory Orgs, Cost Centers, Companies, or Regions.​

    What They Control:
    Custom Orgs are the Swiss Army knife of Workday organizations. Use them to track:

    • Matrix reporting relationships – A worker reports to one manager (Supervisory Org) but also works for a project manager (Custom Org: Project Team)​
    • Product lines, business units, or divisions – Groupings that cross Supervisory Org boundaries
    • Project teams – Temporary or permanent project assignments that need their own hierarchy
    • Centers of Excellence, shared services, or practice groups – Functional groupings that span multiple Supervisory Orgs
    • Gigs or flex work – Track workers assigned to short-term initiatives or temporary teams​
    • Work Councils or employee representative bodies – Labor governance structures required in certain countries​

    Why This Matters:
    Most businesses are not purely hierarchical. You have matrix relationships, cross-functional teams, project-based work, and shared resources.​

    Custom Orgs let you track all of that without polluting your Supervisory Org tree.

    Example: A product manager reports to the VP of Product (Supervisory Org) but is assigned to the “Mobile App Relaunch” project team (Custom Org). Workday tracks both relationships. The project lead can run reports on their team, but approvals and security still flow through the Supervisory Org.

    Key Design Rules:

    • Use Custom Orgs for reporting and analysis, not for routing or security (unless absolutely necessary)​
    • Create Custom Org Types (e.g., “Project Team,” “Practice Group,” “Business Unit”) to keep them organized​
    • Custom Orgs can be single-level or hierarchical—use hierarchies when you need roll-up reporting
    • Workers can belong to multiple Custom Orgs simultaneously​
    • Avoid using Custom Orgs to fix broken Supervisory Org designs—fix the Supervisory Org instead

    Common Mistakes:

    • Using Custom Orgs for approval routing (this gets complicated fast)
    • Creating too many Custom Org Types, which clutters reporting
    • Assigning workers to Custom Orgs without a clear business use case or reporting need​

    Other Organization Types You Should Know

    Work Councils

    Represent employee representative bodies, works councils, or labor governance structures required in certain countries (especially in Europe). Use Work Councils when you need to track which workers are represented by which council for compliance, reporting, or business process routing.​

    Matrix Organizations

    A legacy organization type used to track dual reporting relationships. In modern Workday implementations, Custom Organizations are preferred because they offer more flexibility and cleaner reporting.​

    Pay Groups

    Not technically an organization, but often confused with one. Pay Groups define payroll frequency (weekly, biweekly, monthly) and are assigned to workers to control payroll processing schedules.

    Project Organizations

    Used in Workday Projects (part of Financials). If you track billable projects, Project Orgs define the project hierarchy for time tracking, billing, and project reporting.

    How to Choose the Right Organization Type

    Here is the simple decision tree most Workday practitioners use:

    If you need to track…Use this organization type
    Reporting lines and manager hierarchySupervisory Organization
    Financial responsibility and budget ownershipCost Center
    Legal entities for payroll, tax, and benefitsCompany
    Geographic groupings (countries, regions)Region
    Matrix teams, projects, business units, or flex workCustom Organization
    Labor councils or employee representative bodiesWork Council

    Golden Rule:
    Use the right org for the right purpose. Do not force one organization type to do the job of another.​

    Why Most Workday Designs Fail at Organization Structure

    Here are the three most common failures I see in Workday organization design:

    1. Conflating Supervisory Orgs and Cost Centers

    Teams assume these are the same thing. They are not.​

    Supervisory Orgs define reporting relationships. Cost Centers define financial responsibility.

    Sometimes they align. Often they do not.

    Example: A sales operations analyst reports to the Head of Sales Operations (Supervisory Org) but is funded by the Marketing budget (Cost Center). If you force Supervisory Orgs and Cost Centers to be identical, you lose the ability to track this split.​

    Fix: Design Supervisory Orgs for reporting lines. Design Cost Centers for financial ownership. Let Workday track both.​

    2. Designing Organizations After Go-Live

    Organizations are not configuration. They are foundational data.​

    You cannot “add them later” without mass updates, org reassignments, and business process changes.

    Fix: Lock down organization design in Week 1 of your implementation. Test it against your business processes, security model, and reporting requirements before you load workers.​

    3. Using Custom Orgs as a Bandaid for Broken Supervisory Org Design

    If your Supervisory Org tree does not reflect reality, the answer is not to create a Custom Org to “fix” it.​

    The answer is to fix the Supervisory Org.

    Fix: Use Custom Orgs for matrix relationships, project teams, and cross-functional groupings—not as workarounds for bad Supervisory Org design.

    Workday Organization Design Best Practices

    1. Design for Scale, Not for Today

    Your organization structure will change. Plan for growth, mergers, acquisitions, and reorganizations from day one.​

    2. Keep Supervisory Org Hierarchies Shallow

    Avoid 7+ levels of management. Deep hierarchies slow approvals, complicate security, and frustrate managers.​

    3. Align Cost Centers with Your Chart of Accounts

    Finance should own Cost Center design. Cost Centers must map cleanly to your GL structure.​

    4. Use Custom Orgs Sparingly

    Every Custom Org Type you create adds complexity to reporting and maintenance. Only create them when you have a clear business use case.​

    5. Test Organization Design Against Security and Business Processes

    Before go-live, validate:

    • Does security inheritance work the way you expect?
    • Do approvals route to the right managers?
    • Can Finance run budget vs. actuals by Cost Center?
    • Can HR pull headcount reports by Supervisory Org?​

    6. Document Your Organization Strategy

    Write down the purpose of each organization type, who owns updates, and how workers get assigned. This becomes your operating manual for post-go-live org maintenance.​

    Real-World Example: Designing Organizations for a Global Company

    Let’s walk through a realistic scenario.

    Company: GlobalTech, a 5,000-employee software company with offices in the US, UK, Germany, India, and Australia.

    Business Requirements:

    • Workers report to functional managers (Engineering, Sales, Marketing, Finance)
    • Costs are tracked by department and region
    • The company has three legal entities (US Inc., UK Ltd., Australia Pty)
    • Product teams are cross-functional and span multiple departments
    • Regional HR teams need access to workers in their geography

    Organization Design:

    Org TypeDesign Decision
    CompanyThree Companies: GlobalTech US Inc., GlobalTech UK Ltd., GlobalTech AU Pty (one per legal entity)
    Supervisory OrgFunctional hierarchy: CEO → VPs (Eng, Sales, Marketing, Finance) → Directors → Managers → ICs
    Cost CenterDepartment-based Cost Centers (aligned with GL): Engineering, Sales EMEA, Sales APAC, Marketing, Finance, IT
    RegionFour Regions: Americas, EMEA, APAC, ANZ (for geographic reporting and HR access)
    Custom OrgProduct Teams (Custom Org Type) with one Custom Org per product line (Mobile, Cloud, Enterprise, Data) for cross-functional project tracking

    Why This Works:

    • Supervisory Orgs define clear reporting lines and drive approvals​
    • Cost Centers align with Finance’s budget structure​
    • Companies align with legal entities for payroll and tax
    • Regions enable geographic reporting and HR access​
    • Custom Orgs track product team assignments without disrupting the Supervisory Org tree​

    Final Thoughts: Get Organizations Right the First Time

    Organizations are the foundation of your Workday tenant.​

    Get them right, and Workday runs smoothly. Security works. Approvals route correctly. Reports pull accurate data. Finance trusts the numbers.

    Get them wrong, and you spend months fixing broken processes, reassigning workers, and redesigning hierarchies.​

    The time to design organizations is before go-live, not after.

    Use Supervisory Orgs for reporting lines and workflow routing. Use Cost Centers for financial ownership. Use Companies for legal entities. Use Regions for geography. Use Custom Orgs for everything else.​

    And never, ever assume that all organizations are “basically the same.”

    They are not.

  • Workday Position vs Job Management: When to Use Which

    Here’s the first question every Workday implementation team asks during kickoff:

    “Should we use Position Management or Job Management?”

    And here’s what usually happens next:

    Someone from Finance says: “We need Position Management for headcount budgeting and control.”

    Someone from HR says: “Position Management sounds complicated. Can we just use Job Management?”

    Someone from IT says: “What’s the difference?”

    The conversation stalls. The team defaults to Job Management because it seems simpler. Implementation moves forward.

    Six months after go-live, Finance complains: “We can’t track approved headcount. We can’t freeze positions. We can’t budget by position.”

    HR says: “We told you Job Management was easier.”

    Finance says: “Easier doesn’t mean right.”

    Now you’re stuck. Switching from Job Management to Position Management post-go-live requires a complete data migration, org redesign, and business process reconfiguration. It’s a multi-month project that could have been avoided with the right decision during implementation.

    This guide explains the difference between Position Management and Job Management, when to use each, and how to make the right choice for your organization before you go live.

    Let’s start with the fundamentals.

    What Is Job Management?

    Job Management is Workday’s default staffing model. It’s simpler, more flexible, and easier to implement. In Job Management, you hire workers directly into Job Profiles without creating predefined positions.

    How Job Management Works

    When you hire a worker using Job Management:

    1. You select a Job Profile (e.g., “Software Engineer,” “HR Business Partner,” “Sales Manager”)
    2. You assign the worker to a Supervisory Organization
    3. You assign a Location, Cost Center, and other job details
    4. The worker is hired, and their job data is tracked in Workday

    There is no position object. The worker’s job is defined by their Job Profile, organization assignments, and manager relationship.

    Example: Hiring with Job Management

    Scenario: You need to hire a new Software Engineer for the Engineering – Product team.

    Steps:

    1. Navigate to Hire Employee
    2. Enter worker details (name, email, hire date)
    3. In Job Details:
      • Job Profile: Software Engineer
      • Supervisory Organization: Engineering – Product
      • Manager: Alex Garcia (Director, Engineering Product)
      • Location: San Francisco Office
      • Cost Center: Engineering Product Cost Center
    4. Submit and approve

    The worker is now employed. Workday tracks their job data, but there is no “Position 12345” assigned to them. They simply hold the job “Software Engineer” in the “Engineering – Product” organization.

    Key Characteristics of Job Management

    Flexibility:

    • You can hire as many people as you want into the same Job Profile
    • No need to create positions in advance
    • Easy to restructure organizations without worrying about position assignments

    Simplicity:

    • Fewer Workday objects to manage (no positions)
    • Easier to implement and configure
    • Less training required for HR and hiring managers

    Limitations:

    • No headcount control: You can’t limit the number of people in a Job Profile
    • No position-level budgeting: You can’t budget for “Position 12345” with a specific salary
    • No position freeze: You can’t freeze hiring for a specific position
    • No position requisition tracking: You can’t track which positions are open vs. filled

    Who Uses Job Management:

    • Small to mid-sized companies (under 5,000 employees)
    • Companies with flexible, rapidly changing org structures
    • Startups and high-growth companies
    • Organizations without strict headcount control requirements
    • Companies that don’t need position-level budgeting

    What Is Position Management?

    Position Management is Workday’s advanced staffing model. It’s more structured, more controlled, and more complex. In Position Management, you create predefined Positions in advance, and workers are hired into those positions.

    How Position Management Works

    In Position Management, you follow this workflow:

    1. Create a Position in Workday (e.g., “Software Engineer – Position 12345”)
    2. Assign the position a Job Profile, Supervisory Organization, Location, and budgeted salary
    3. The position exists in Workday with status = Unfilled (no worker assigned yet)
    4. When you’re ready to hire, you create a Requisition linked to that position
    5. When you hire a worker, you assign them to the position
    6. The position status changes to Filled

    The position object exists independently of the worker. If the worker terminates, the position remains and can be refilled.

    Example: Hiring with Position Management

    Scenario: You need to hire a new Software Engineer for the Engineering – Product team.

    Step 1: Create the Position

    1. Navigate to Create Position
    2. Fill in position details:
      • Position ID: POS-12345 (auto-generated or manually entered)
      • Job Profile: Software Engineer
      • Supervisory Organization: Engineering – Product
      • Manager: Alex Garcia (Director, Engineering Product)
      • Location: San Francisco Office
      • Cost Center: Engineering Product Cost Center
      • Budgeted Salary: $120,000 annually
      • Effective Date: January 1, 2025
    3. Submit and approve
    4. Position is created with status = Unfilled

    Step 2: Create a Requisition

    1. Navigate to Create Requisition
    2. Link the requisition to Position POS-12345
    3. Submit for approval
    4. Requisition is posted, recruiting begins

    Step 3: Hire a Worker into the Position

    1. Navigate to Hire Employee
    2. Enter worker details (name, email, hire date)
    3. In Job Details:
      • Position: POS-12345 (select the position)
      • Workday auto-fills Job Profile, Supervisory Org, Location, Cost Center, and Budgeted Salary from the position
    4. Submit and approve

    The worker is now employed in Position POS-12345. The position status changes from Unfilled to Filled.

    Key Characteristics of Position Management

    Control:

    • Predefined positions with approved headcount
    • Each position has a budgeted salary
    • You can freeze positions to prevent hiring
    • You can track open vs. filled positions in real time

    Budgeting:

    • Finance can budget by position (not just by Job Profile or org)
    • Each position has a salary budget that can be tracked against actuals
    • Position-level cost forecasting and workforce planning

    Tracking:

    • Requisitions are linked to positions
    • You can see which positions are open, filled, or frozen
    • Historical tracking: who held each position over time

    Complexity:

    • More Workday objects to manage (positions, requisitions, position hierarchies)
    • Requires upfront planning (you must create positions before hiring)
    • More training required for HR, hiring managers, and Finance
    • Less flexibility (harder to restructure orgs when positions are involved)

    Who Uses Position Management:

    • Large enterprises (5,000+ employees)
    • Government agencies and public sector organizations
    • Highly regulated industries (healthcare, financial services)
    • Organizations with strict headcount control and budget governance
    • Companies that need position-level budgeting and forecasting

    Key Differences: Job Management vs. Position Management

    DimensionJob ManagementPosition Management
    Staffing ModelWorkers hired into Job ProfilesWorkers hired into predefined Positions
    Headcount ControlNo control (hire as many as you want)Strict control (only hire into approved positions)
    BudgetingBudget by Job Profile or OrgBudget by individual Position
    Position FreezeNot availableCan freeze positions to prevent hiring
    Requisition TrackingRequisitions not linked to positionsRequisitions linked to positions
    FlexibilityHigh (easy to restructure orgs)Lower (positions tied to orgs)
    ComplexitySimple (fewer objects to manage)Complex (positions, requisitions, hierarchies)
    Implementation TimeFaster (less configuration)Slower (requires position setup)
    Best ForSmall/mid-sized, flexible orgsLarge enterprises, regulated industries
    Workday DefaultYes (default staffing model)Optional (must be enabled and configured)

    When to Use Job Management

    Choose Job Management if:

    1. You’re a Small to Mid-Sized Organization (Under 5,000 Employees)

    Small companies value flexibility over control. You need to hire quickly, restructure frequently, and avoid bureaucratic headcount approval processes.

    Why Job Management Works:

    • No need to create positions in advance (hire as needed)
    • Easy to scale up or down rapidly
    • Minimal overhead for HR and Finance teams

    Example:
    A 500-person startup needs to hire 50 engineers over the next quarter. Instead of creating 50 positions, approving budgets for each, and tracking requisitions, they simply hire engineers into the “Software Engineer” Job Profile as candidates are found.

    2. Your Organization Restructures Frequently

    If you reorganize teams quarterly, change reporting lines often, or operate in a fast-paced, agile environment, Position Management becomes a maintenance burden.

    Why Job Management Works:

    • Workers are tied to Job Profiles and Supervisory Orgs, not positions
    • When you restructure, you just reassign workers to new orgs (no position reassignments)
    • No risk of orphaned positions or position hierarchy mismatches

    Example:
    A tech company reorganizes product teams every quarter based on roadmap priorities. Workers move between teams frequently. Job Management keeps HR administration simple without worrying about position updates.

    3. You Don’t Need Strict Headcount Control

    If Finance doesn’t require position-level budgeting, and your leadership trusts managers to hire within budget guidelines, you don’t need the overhead of Position Management.

    Why Job Management Works:

    • Budget at the Supervisory Org or Cost Center level (not position level)
    • Managers approve hires based on team need, not predefined positions
    • Simpler approval workflows (no position requisition step)

    Example:
    A consulting firm hires based on client demand. Headcount fluctuates based on project pipeline. Finance budgets by Cost Center and trusts practice leaders to hire appropriately without position-level control.

    4. You Want a Faster, Simpler Implementation

    Position Management requires significant upfront configuration, position data setup, and business process customization. If you’re on a tight implementation timeline, Job Management is faster.

    Why Job Management Works:

    • Fewer Workday objects to configure
    • No need to load historical position data
    • Simpler business process workflows (Hire, Terminate, Change Job)
    • Less training required for end users

    Example:
    A company switching from a legacy HRIS to Workday has 4 months to go live. They choose Job Management to avoid the complexity of creating and loading 3,000 positions during migration.

    When to Use Position Management

    Choose Position Management if:

    1. You Need Strict Headcount Control and Budget Governance

    Large organizations, government agencies, and highly regulated industries require tight control over headcount. Every hire must be approved, budgeted, and tracked at the position level.

    Why Position Management Works:

    • Finance approves each position with a budgeted salary before recruiting begins
    • You can’t hire unless a position exists and is unfilled
    • Position freeze prevents hiring into specific roles without additional approval

    Example:
    A state government agency has a fixed annual headcount budget approved by the legislature. Every position must be authorized, budgeted, and tracked. Position Management ensures compliance with public sector headcount rules.

    2. You Budget and Forecast at the Position Level

    If Finance builds budgets by position (not just by department or Job Profile), you need Position Management to align Workday with your budgeting process.

    Why Position Management Works:

    • Each position has a budgeted salary that flows into financial planning tools
    • Finance can compare budgeted salary (position) vs. actual salary (worker)
    • Workforce planning tools show open positions, filled positions, and budget variance

    Example:
    A Fortune 500 company builds annual budgets by position. Finance allocates $150,000 for “Senior Product Manager – Position 45678.” Workday tracks actual salary against this budgeted amount and reports variance monthly.

    3. You Need to Track Open vs. Filled Positions in Real Time

    If leadership wants real-time visibility into open headcount, requisition status, and time-to-fill metrics, Position Management provides this out of the box.

    Why Position Management Works:

    • Positions have status: Unfilled, Filled, Frozen
    • Requisitions are linked to positions (easy to track open reqs)
    • Reports show open position counts by department, location, Job Profile

    Example:
    A healthcare system with 10,000 employees needs to track critical open positions (nurses, physicians, therapists). Position Management gives HR and leadership a live dashboard of open positions, requisition status, and hiring pipeline.

    4. You Operate in a Highly Regulated Industry

    Government agencies, healthcare organizations, and financial services firms often have regulatory requirements for headcount tracking, position documentation, and audit trails.

    Why Position Management Works:

    • Full audit trail: who created the position, who approved it, who filled it, when
    • Position history shows all workers who held a position over time
    • Supports compliance reporting and external audits

    Example:
    A federal agency must document every position, justify every hire, and provide audit trails for inspector general reviews. Position Management provides the required documentation and compliance tracking.

    5. You Want to Freeze Hiring for Specific Positions

    If your organization needs the ability to temporarily freeze hiring for specific roles (due to budget cuts, hiring freezes, or organizational changes), Position Management supports this.

    Why Position Management Works:

    • You can freeze individual positions or groups of positions
    • Frozen positions can’t be filled until unfrozen
    • Provides granular control over hiring without blanket freezes

    Example:
    A company facing budget constraints freezes 50 mid-level manager positions while keeping engineering and sales positions open. Position Management allows this selective freeze without stopping all hiring.

    Hybrid Model: Can You Use Both?

    Yes. Workday allows you to use Position Management for some Job Profiles and Job Management for others.

    How the Hybrid Model Works

    You configure specific Job Profiles to require positions. Workers hired into those Job Profiles must be assigned to a position. Other Job Profiles remain position-optional.

    Example Hybrid Configuration:

    Positions Required:

    • Executive roles (VP, SVP, C-Suite)
    • Management roles (Director, Senior Manager)
    • High-cost roles (Principal Engineer, Senior Architect)

    Positions NOT Required:

    • Individual contributor roles (Software Engineer, Sales Rep, Analyst)
    • Contract workers and consultants
    • Temporary or seasonal workers

    When to Use Hybrid Model

    The hybrid model works well when:

    • You need headcount control for leadership and management roles but want flexibility for individual contributors
    • Finance wants to budget senior positions individually but budget IC roles at the org level
    • You want to phase Position Management in gradually (start with exec roles, expand over time)

    Hybrid Model Challenges

    Complexity:

    • Two staffing models to manage and maintain
    • Users need to understand which roles require positions and which don’t
    • Reporting becomes more complex (some workers have positions, some don’t)

    Recommendation:
    Only use hybrid if you have a clear business reason. Most organizations should choose one model and stick with it for simplicity.

    Implementation Considerations

    Switching from Job Management to Position Management

    The Bad News:
    Switching from Job Management to Position Management post-go-live is painful. You need to:

    1. Create positions for every current worker
    2. Assign workers to positions (mass update via Change Job)
    3. Reconfigure business processes to require positions
    4. Retrain HR, hiring managers, and recruiters
    5. Migrate requisition workflows

    This is a multi-month project with significant change management effort.

    The Good News:
    If you choose the right model during implementation, you won’t need to switch.

    Switching from Position Management to Job Management

    Even Harder.
    Workday strongly discourages switching from Position Management to Job Management because:

    • You lose all position-level budget data
    • Historical position tracking is lost
    • Requisitions become unlinked from positions
    • Finance loses position-based forecasting

    Recommendation:
    If you think you might need Position Management in the future, implement it from day one. It’s easier to start with Position Management and simplify later than to retrofit it after go-live.

    Decision Framework: Job Management vs. Position Management

    Use this decision tree to choose the right model:

    Question 1: Do you need strict headcount control?

    • Yes: Position Management
    • No: Continue to Question 2

    Question 2: Does Finance budget at the position level?

    • Yes: Position Management
    • No: Continue to Question 3

    Question 3: Do you need to track open vs. filled positions in real time?

    • Yes: Position Management
    • No: Continue to Question 4

    Question 4: Are you in a highly regulated industry (government, healthcare, financial services)?

    • Yes: Position Management
    • No: Continue to Question 5

    Question 5: Do you have more than 5,000 employees?

    • Yes: Consider Position Management (depends on control requirements)
    • No: Job Management is likely sufficient

    Question 6: Do you restructure frequently or operate in a fast-paced environment?

    • Yes: Job Management
    • No: Position Management may work

    Common Mistakes

    Mistake 1: Choosing Job Management Because “It’s Easier”

    The Problem:
    Teams default to Job Management during implementation because it’s simpler and faster. They ignore long-term requirements for headcount control and budgeting.

    What Happens:
    Finance complains post-go-live. You’re forced to retrofit Position Management 12 months later at massive cost and effort.

    The Fix:
    Involve Finance early. Understand budgeting and headcount control requirements before choosing a staffing model.

    Mistake 2: Choosing Position Management When You Don’t Need It

    The Problem:
    Teams assume “bigger companies use Position Management, so we should too.” They implement Position Management without clear business requirements.

    What Happens:
    HR drowns in position administration. Creating and maintaining positions becomes a bottleneck. Hiring slows down. Users complain about complexity.

    The Fix:
    Only implement Position Management if you have a clear business need for position-level control and budgeting.

    Mistake 3: Not Planning for Future Growth

    The Problem:
    A 1,000-person company chooses Job Management because “we don’t need position control today.” They plan to grow to 10,000 employees over 5 years.

    What Happens:
    At 5,000 employees, Finance demands position-level budgeting. Now you need to retrofit Position Management across a live tenant.

    The Fix:
    Design your staffing model for future state, not current state. If you plan to grow significantly, choose Position Management from the start.

    Workday Tasks for Position Management

    Create and Manage Positions:

    • Create Position (define new positions)
    • Edit Position (update position details)
    • Fill Position (assign worker to position)
    • End Position (inactivate position)
    • Freeze Position (prevent hiring into position)

    Position Requisitions:

    • Create Requisition (linked to position)
    • Edit Requisition (update req details)
    • Close Requisition (when position is filled)

    Position Reporting:

    • View Position (see position details and history)
    • Position Summary (track open vs. filled positions)
    • Position Budget vs. Actuals (Finance reporting)

    Position Hierarchies:

    • Create Position Hierarchy (group positions for reporting)
    • View Position Hierarchy (see position org structure)

    Final Thoughts

    Choosing between Job Management and Position Management is one of the most important decisions you’ll make during Workday implementation.

    Choose Job Management if:

    • You’re small to mid-sized (under 5,000 employees)
    • You value flexibility and speed over control
    • You don’t need position-level budgeting
    • You restructure frequently
    • You want a simpler, faster implementation

    Choose Position Management if:

    • You need strict headcount control and governance
    • Finance budgets at the position level
    • You need to track open vs. filled positions in real time
    • You’re in a highly regulated industry
    • You’re a large enterprise with complex workforce planning needs

    The Right Time to Decide:
    During implementation, not after go-live.

    Involve Finance, HR, and leadership. Understand your current requirements AND your future state. Choose the model that supports your business for the long term.

    Because switching later is expensive, disruptive, and avoidable.

  • 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.

  • Designing Your Workday HCM Foundation

    Designing Your Workday HCM Foundation

    Designing your Workday HCM foundation is one of the most important decisions you will ever make in a tenant. Once you go live with supervisory orgs, positions, job profiles and cost centers, reversing bad design is painful, political and expensive. A clean foundation, on the other hand, makes every downstream process easier: hiring, transfers, security, reporting, integrations and even future modules like Time Tracking or Learning.​

    Start with a clear operating model

    Before touching configuration, clarify how the business actually operates. In Workday terms, this means understanding who manages whom, how cost is tracked, how HR wants to report headcount and how finance wants to see labor cost. You will use those answers to decide the shape of supervisory orgs, whether you go position or job management, and which worktags (like cost centers) become mandatory.​

    Workday supervisory organizations represent management relationships and operational structure, not legal entities. Companies and entities represent legal and accounting structure, while cost centers and other worktags represent how cost is tracked and reported. Separating these concepts early prevents you from overloading supervisory orgs with finance responsibilities they were never designed to carry.​

    Designing supervisory orgs that do not collapse

    A common mistake is to copy the HR org chart directly into Workday as dozens or hundreds of tiny supervisory orgs. That usually creates reporting complexity, security noise and constant maintenance whenever someone changes manager. A better pattern is to design supervisory orgs around stable management units: departments, teams or business units that change less frequently than individual manager assignments.​

    When designing supervisory orgs, ask:

    • Can this org survive manager changes without needing to be restructured every week?
    • Does this level of granularity help reporting and security, or just create clutter?
    • Is there a clear business purpose for this org beyond “we have a manager”?

    Aim for a hierarchy that can support real-world approvals, headcount reporting and security boundaries, but is still simple enough that new HRIS analysts can navigate it confidently.​

    Positions vs jobs: choose consciously

    Workday supports position management and job management, and the choice is foundational. Position management is best when you need rigorous headcount control, budget-to-position matching and clear tracking of vacancies. Job management is lighter and works well in fluid environments where individual seats are less important than overall staffing levels.​

    For position management, design patterns include:

    • Use positions anywhere headcount is tightly controlled, such as regulated functions or centralized operations.​
    • Give positions meaningful, consistent titles that align with job profiles and not personal names.
    • Avoid creating “temporary” positions for one-off cases; these often become long-term clutter.

    For job management, ensure you still have clear job profiles with compensation grades and worktags so that reporting and security do not depend on free-text job titles.​

    Job profiles as your talent backbone

    Job profiles are the backbone of how Workday sees roles, qualifications, compensation and, in some tenants, learning and talent. Poorly designed job profiles lead to reporting chaos: dozens of variations for the same role, unclear grade mappings and confusing job histories for workers.​

    Strong job profile design usually includes:

    • A consistent naming pattern (e.g., “Analyst, HR Operations” instead of many variations).
    • Clear classification into job families and job profiles that align with how HR and talent teams think about roles.​
    • Linkage to compensation grades and grade profiles so that pay ranges are consistent across markets.​

    When job profiles are clean, you can deploy performance, learning and career frameworks more easily, because everything hangs off a small number of well-maintained roles rather than hundreds of one-off titles.​

    Cost centers and worktags: think like finance

    Cost centers and other worktags are how finance sees the world in Workday Financials, and even in HCM-only tenants they drive a lot of reporting. HR often underestimates how important it is to design cost centers that match finance’s management reporting rather than HR’s internal labels.​

    Good practices include:

    • Keep cost centers relatively stable and align them to budget owners or P&L responsibility.​
    • Avoid duplicating cost centers just to represent small team differences; use supervisory orgs, locations or custom organizations for that.​
    • Ensure default cost centers are set correctly at the position, worker or org level so payroll and financial postings are accurate without manual fixes.​

    When cost centers and worktags are clean, you can produce reliable reports like headcount by cost center, labor cost by business unit and budget versus actual staff cost with minimal reconciliation.​

    Putting it all together in real processes

    The real test of your HCM foundation is not whether it looks neat in the configuration pages, but whether everyday processes run smoothly. When HR creates a new position, it should be obvious which supervisory org to use, which job profile to select and which cost center should default. When a manager initiates a transfer, the path through supervisory orgs and cost centers should be clear, and reporting should show the move without gaps or duplicates.​

    Think through core processes end to end:

    • Hire to retire: are orgs, positions and cost centers stable across promotions, transfers and international moves?​
    • Security: can you grant HR partners and managers access based on supervisory orgs and cost centers without dozens of exceptions?​
    • Reporting: can HR and finance quickly answer questions about headcount, vacancies and cost without manual spreadsheets?​

    When these scenarios work, you know the foundation is serving the business rather than the other way around.

    Design for the next three years, not three months

    Finally, design your Workday HCM foundation with a three-year horizon. Most organizations will go through reorganizations, new business lines and possibly new geographies in that time. Build supervisory org structures, position rules, job profiles and cost center hierarchies that can absorb that change without needing a full rebuild.​

    Document your design principles and decisions, not just your configuration. Future HRIS analysts, Workday consultants and auditors should be able to understand why the tenant looks the way it does. That documentation is part of the foundation, just as much as the orgs and positions themselves.​

    A strong Workday HCM foundation does not happen by accident. It is the result of deliberate choices about how to represent your organization, control headcount, classify roles and track cost. When you get those basics right, everything from security to payroll to analytics becomes simpler, more reliable and much easier to scale.