Headcount that reconciles
without anyone intervening.
Position management problems are rarely a position management problem. Headcount that will not reconcile is usually a design and ownership problem wearing a configuration costume.
HR
Creates the positions, in Workday.
Finance
Plans against them, in the planning system.
Recruiting
Hires against them, in the ATS.
The reconciliation is a symptom. The position model is the problem.
None of the following is a position management problem by itself. Together they are the signature of a position model that was configured before it was designed.
Cleaning the data works until the next reorg, because the thing generating bad data was never changed.
- HR, Finance, and Recruiting each report a different headcount
- Requisitions stall because the position is missing, wrong, or unapproved
- Someone maintains a spreadsheet to track what Workday should already know
- Position data has to be reconciled by hand before anyone trusts a report
- Nobody can say who owns creating, closing, or approving a position
- Reorganizations leave orphaned positions and broken reporting lines
Where it traces back to
Configuration
Position management was switched on without deciding what a position means here, so the rules that should prevent bad data were never written.
Ownership
Three teams touch a position and none of them owns it. Every edge case becomes a meeting, and every meeting sets a precedent nobody records.
Process
Promotions, transfers, and reorgs each need a defined path through the position model. Where one is missing, people invent a workaround and it becomes the standard.
Integration
The ATS was integrated to the position model rather than to the headcount plan, so recruiting and finance drift apart the moment anything changes.
Four of the six domains where Workday debt accumulates: Configuration · Data · Process · Integration · Governance · Ownership.
Three functions are steering the same car from three different maps.
Each has valid priorities. None of them shares a system with the others. That is the whole problem, and no amount of configuration fixes it on its own.
The organizational architect
HR
Owns the system where positions are created, and translates business need into headcount requirement.
Lives in Workday
The fiscal navigator
Finance
Runs the scenarios that decide what the company can afford, and depends entirely on Workday data being current.
Lives in the planning system
The talent acquisition engine
Recruiting
Executes against the plan, and needs to know which positions are approved, what the real budget is, and what timeline is realistic.
Lives in the ATS
Position management is the technical implementation inside Workday. Headcount management is the wider process it has to serve, approvals, budgeting, and recruiting across all three. Designing the first without the second is what produces the numbers that will not reconcile.
Six components, because position management is never only a configuration problem.
Scope is built around what your environment actually needs. These are the components it gets built from.
A 90-day stabilization touches position management but does not go this deep. If headcount is the thing that is actually broken, this is the engagement rather than a workstream inside a larger one.
Strategy
What position management is for in your business, and what it has to control before anything gets configured.
Alignment
Roles and responsibilities across HR, Finance and Recruiting, written down. The three teams define the same words differently, so the first job is surfacing where, and settling it before anything gets configured.
Configuration
The position model, guardrails, and validation rules that make the agreed design enforceable in the tenant.
Business process
Approval paths for creation, change, and closure, including the edge cases that currently become meetings.
Integration
The ATS and downstream systems wired to the headcount plan, not just to the position record.
Change management
The people who operate it understand why the decisions were made, so the design survives the next reorg.
Where we go deep
- Position vs job management design
- Approval and governance workflows
- Headcount and budget reconciliation
- ATS and downstream integrations
Make the right thing the easy thing.
Position management carries complex logic: job profiles drive compensation ranges, cost centers determine approval chains, locations influence tax. One wrong selection sends a request down the wrong path or creates errors three systems downstream.
Simplify what a manager has to touch
Request forms carrying only the fields a manager genuinely needs. Every extra field is a chance to send the request somewhere it should not go.
Validate before it becomes data
Conditional logic and validation rules that prevent the error rather than catching it in a reconciliation three weeks later.
Define ownership at each stage
Who can modify which attributes, and when. Positions get adjusted repeatedly between approval and hire, level, location, budget, and undefined ownership is why that becomes drift.
Harden the integrations
The ATS and downstream systems wired to the headcount plan, with reconciliation cycles that surface a break in days rather than at quarter end.
The alternative is what we usually find: a full-time position janitor whose entire job is cleaning up data the system should never have accepted, and an endless “your numbers do not match my numbers” argument nobody can win.
Guardrails are the part clients ask about most, because getting them wrong is what made the last model unusable. Happy to walk through how we design them.
Book a strategy callThis is for you if
- You are on position management and hitting the problems it is known for
- HR, Finance, and Recruiting each hold a different headcount number
- You want headcount to be a control, not a monthly reconciliation exercise
- You are building toward strategic workforce planning and need the foundation right first
This is not for you if
- You run job management rather than position management
- You want a data cleanup without changing what produced the bad data
- You are looking for someone to administer tickets rather than redesign the model
If three teams in your business would give three different headcount numbers today, that is worth half an hour rather than another reconciliation cycle.
You will be talking to Seena, not a sales rep.
Diagnose, stabilize, and hand it back.
The same three steps regardless of the service. The last one is the point: control stays with your team.
01Diagnose
Identify the recurring failure patterns and the priority root causes underneath them.
02Stabilize
Contain immediate risk and repair the agreed priority foundations.
03Transfer control
Establish governance, document the operating model, and equip the internal team.
It usually starts narrower than it ends.
A global technology company brought us in through the HRIS team to build position management as the foundation for strategic workforce planning. That is where these engagements normally begin, one team, one foundation, one clear problem.
The work ran across all three sides of the tripod: stakeholder interviews through HR, Finance, and Recruiting; recommendations for aligning inside each function and then across them; and specific direction on configuration, integrations, process, and who owns what. It grew into an end-to-end headcount management strategy, and a seat at the steering committee helping internal leadership make the calls.
Client name withheld. Most of our position management work is under agreements that do not allow attribution.
Who oversees the work
Seena Mojahedi
CEO and Founder
Former client-side Workday leader. Vets every consultant on the bench personally. Solution focused, outcome oriented, and set on raising the quality of the Workday ecosystem itself.
Belinda Smit
SVP, Services Delivery
Runs delivery for Kandor Solutions and built the frameworks behind our position management and M&A work. An engagement lead, and oversees the managed-services pods.
intellectsEvery consultant vetted personally by Seena Mojahedi, minimum 5 years in the Workday ecosystem and typically 5-7.
Free Framework
Position Management Framework
A planning workbook for defining who owns what, what a position means in your business, and when one gets created or closed, before anyone touches configuration. Four to six working sessions, and you keep the output.
Everything below is free, and none of it needs your email.
Four articles covering the same ground this page summarizes, the framework, the failure patterns, and the integration decisions underneath them.
The four practices that make position management hold
- Define the framework before you configure anything
- Establish ownership across the whole hiring process
- Build guardrails into the system, not into people’s memory
- Train the teams who operate it, not just the ones who own it
The five mistakes we find most often
- An unclear definition of what position management is for
- Treating it as an ATS integration rather than headcount planning
- No single owner, so every edge case becomes a meeting
- Data mismanaged across the hire-to-retire path
- Self-service switched on before the guardrails existed
Where Workday and your ATS come apart
- The three-way intersection problem between HR, Finance and Recruiting
- Which data elements actually have to agree
- Keeping Workday as the source of truth without slowing recruiting
Comparing the integration options
- What Workday Studio really costs to build and maintain
- Where a packaged connector stops short
- How to choose against your own constraints rather than a vendor’s
Common questions about Workday position management
- What is the difference between position management and job management in Workday?
- Position management requires a position to be created, defined, and approved before anyone can be hired into it, which gives granular control over headcount, budget, and approvals. Job management lets you hire within a supervisory organization without a predefined position, trading control for flexibility.
- Our headcount will not reconcile. Is that a position management problem?
- Usually not on its own. Headcount that will not reconcile normally traces back to configuration, ownership, or governance decisions made during implementation. Position management is where the symptom shows up, so that is where we start looking, but the fix is often somewhere else.
- Do we have to re-implement Workday to fix this?
- Almost never. Most position management problems are design and governance problems expressed in configuration, and they are repairable inside the tenant you already have. Re-implementation is a last resort, not a starting assumption.
- Can you work on position management while our support partner stays in place?
- Yes. This is design and governance work rather than ticket work, so it runs alongside an existing AMS or internal support function rather than replacing it.
- Does this cover the recruiting side as well?
- Yes. The requisition-to-hire path crosses Workday and your ATS, so the integration and the approval model on both sides are in scope. Treating them separately is what causes the manual reconciliation in the first place.
- What happens after the work is done?
- Control transfers to your team. That means a documented operating model, the governance and approval rules written down, and the people who run it trained on why the decisions were made, not just on which buttons to press.
- How long does a Workday position management engagement take?
- It depends on how much of the model has to change rather than on headcount. Aligning three functions and redesigning the structure underneath them is usually a matter of months, not weeks. Where the design is sound and only governance is missing, it is considerably shorter. We scope it after the diagnosis, not before.
- Who from our team needs to be involved?
- Someone with authority from each of HR, Finance and Recruiting, because the disagreement between those three is usually the actual problem. Plus whoever owns the Workday configuration. If only HR is in the room, the number will reconcile until Finance sees it.
- We use Greenhouse for recruiting. Does that change the approach?
- It changes the integration work, not the design work. The position model still has to be decided first. What Greenhouse changes is where requisitions originate and what has to flow back, which is a common source of the mismatch between what Recruiting has open and what Finance has budgeted.
- How much does Workday position management consulting cost?
- It scales with how much of the model is being redesigned and how many functions have to be aligned, so a number quoted before that is understood is a guess. The comparison worth making is against what the manual reconciliation is already costing you every month.
- Is position management the same as headcount planning?
- No, and conflating them is part of why they disagree. Position management is the structure inside Workday that says what a position is, when one exists and who owns it. Headcount planning is the forecast. Planning against a structure nobody agrees on produces a forecast nobody trusts.
Start with the framework.
Define who owns what, and what a position means in your business, before anyone touches configuration again. It is the step most teams skip, and the one that decides whether the cleanup holds.
Get the Position Management FrameworkFree. No sales call required.