Reality check Workday Position Management series
Playbook / 04 · For the Head of TA

You did not need a guide to tell you
the system is broken.

You have been telling people the system is broken for two years. The point of this playbook is to give you the architectural language and the dollar figures to make the case to the people above you.

Failure 01 The hiring plan that rots before you can recruit against it.
Failure 02 The req the hiring manager will not open.
Failure 03 The three sources of truth nobody trusts.
For Heads of TA & TA Ops Fast-growing tech, 500–10,000 employees
Format 4 sections · 1 calculator ~12-minute read, talking-points ready
Companion docs CFO · CHRO · HRIS Forward the one that matches the room
Edition May 2026 Reality Check series, No. 04
In this series
00Landing argument 01The field guide 02Operator voice report 03CHRO strategy brief 03CFO cost memo 04TA playbook
Playbook · One paragraph
The hiring plan is wrong by April. The hiring manager will not open the req. The numbers Finance, HR, and TA bring to the headcount meeting do not match. These are not your team's failures. They are the architecture failing your team — and this playbook gives you the numbers to say so out loud.
Your company size
Every TA-side cost number in this playbook re-stamps to your 1,000–2,500 employee band.
Setup
For the TA Leader reading this

You already know. This playbook gives you the words.

This playbook is for Heads of TA, VPs of TA Operations, and TA Operations leaders at fast-growing technology companies with 500 to 10,000 employees that run Workday HCM, growing headcount by more than 20% per year, using Greenhouse, Ashby, or SmartRecruiters as the ATS.

Three things you know to be true that nobody else seems to see clearly: the hiring plan you are working from is wrong (30 to 50 percent of it changes between January and April). Your recruiters spend hours every week on data hygiene that does not move candidates forward. Time-to-fill numbers are unreliable because the underlying req data drifts.

These are not your team's failures. The architecture is failing your team. The rest of this playbook makes that argument with numbers — and gives you four persona-specific assets to forward, so the room is ready before you ever walk into it.

01
Section 01 · Three failure points that hit TA hardest

Each scene is from a real customer environment.

Click any of the three failures to see the scene, what it costs TA specifically, and the line your recruiters use to talk about it. Read them in order the first time.

Failure 01 · The scene

Fourteen roles changed by February.

Second week of February

It is the second week of February. Your team got the annual hiring plan in December. Sixty roles for Q1 in engineering. By the second week of February, you know fourteen of them have changed.

Three got re-leveled. Five had their locations expanded from one geo to "remote North America." Two got pulled forward because a customer signed. Four got pushed back because product priorities shifted. None of these changes have been formally updated in Workday positions. Some are in your tracker. Some are in Slack threads. Some are in the heads of the HRBPs who handled them.

By Q2, half of every Q1 plan is wrong in some way. By Q3, the plan is essentially a different plan than what was approved.

What it costs TA
Your team recruits against a plan that is wrong by 30–50%.

Candidates get sourced for roles that no longer exist. Interview loops get scheduled for levels that have been re-scoped. Offer comp ranges get debated because the plan and the comp committee minutes disagree. Every one of these introduces delay and friction your recruiters did not create.

$2.0M – $6.0M / yr Forecast variance attributable to stale plan · TA share at your tier
From the recruiter desk
"I can't recruit my way out of an architecture problem — but I can name it."

When the plan you are working from is wrong, the recruiter team owns the delivery problem that comes with it. You cannot recruit your way out of an architecture problem. But you can name it, source it, and make the case.

Failure 02 · The scene

2:11 p.m. on a Thursday.

Thursday · 2:11 p.m.

Maya, the head of Product Engineering, opens her laptop in the kitchen between back-to-back interviews. Her VP of Engineering pinged her Tuesday: we need to backfill Aaron's role, up-level to Staff. Maya does not open Workday. She opens Slack.

Your HRIS counterpart opens Workday at 2:14 p.m. They get to field eight of fourteen and realize they do not have the JD, the comp justification, or the official sign-off on the up-level. They ping Maya. She does not respond for forty-five minutes. They move on. The rec is not actually opened until the following Monday. Your recruiter does not start sourcing until the Monday after that.

Workday's Create Job Requisition flow is 12 to 18 required fields across 4 to 7 tabs. Hiring managers will not complete it. The hiring manager who runs their life in Slack and Linear is not being lazy. They are responding rationally to a workflow that does not match the way they work.

What it costs TA
Median time-to-rec at companies routing through Workday: 9–14 business days.

At companies running a decision layer in front of Workday: 1–3 business days. Across 400 reqs/year, that is 4 to 8 weeks of cumulative recruiting time lost per role — and roughly $12,000 of deferred engineering productivity for every two weeks of delay.

$1.0M – $2.5M / yr Deferred productivity from slow time-to-rec · TA share at your tier
From the recruiter desk
"The two-week delay is form friction, not effort."

Every Workday customer above 500 employees has trained their managers. The training does not stick. The form is the problem. Replace it with a Slack-grade request flow and the two-week delay collapses to two days.

Failure 03 · The scene

The Monday morning headcount meeting.

Friday before the board meeting

The CEO's chief of staff pings you, FP&A, and HR ops: need consolidated headcount numbers by EOD Monday. You meet Monday at 9. FP&A has a number from Adaptive. HR ops has a number from Workday. You have a number from your hiring tracker. The four numbers are within a few percent but they are not equal. The meeting takes ninety minutes.

At a 1,500-person company, total reconciliation labor across HR, TA, and FP&A averages 60 to 80 hours per month. The TA share is typically 20 to 30 hours of that.

Beyond the labor cost, this dynamic destroys TA credibility. When the numbers do not match, the executive team starts trusting whichever source agrees with their priors. The function with the cleanest data wins the argument.

What it costs TA
20–30 hours/month of reconciliation that does not move a candidate.

That is one recruiter-week per quarter lost to spreadsheet labor. It is also the slow erosion of executive trust in TA's data — and once that goes, you stop being included in the conversations that decide what gets hired.

$20K – $40K / yr TA-share reconciliation labor at your tier
From the recruiter desk
"The function that owns the data owns the strategic conversation."

When the executive team stops trusting your headcount data, they stop including you in headcount conversations. The function that owns the data owns the strategic conversation. Make sure that function is yours.

"These three failure points are not separate. They compound. The plan rots, so the req routes through a clunky workflow, so the numbers drift, so the meeting happens. Fix the layer underneath and all three stop."

— From the playbook
02
Section 02 · The dollar magnitude

What this costs your function, specifically.

The full architecture cost stack is in the companion CFO memo. Here we isolate the TA-side share: the lines that land on your team's budget, your team's calendar, and your team's credibility.

For a typical 1,500-person fast-growing tech company, the full-stack cost of running Workday Position Management without a decision layer in front of it is $5.1M to $13.2M per year. The TA-specific share breaks out as follows. Numbers re-stamp to your tier above.

Line · 01

Reconciliation labor on TA's desk

$20K – $40K / yr

20–30 hours/month of recruiter and TA-ops time spent reconciling the tracker, Workday, and the ATS — labor that does not move a candidate forward.

Line · 02

Recruiter time lost to data hygiene

$50K – $100K / yr

Every recruiter on your team loses 2 to 4 hours per week to cleaning up req fields, chasing approvals, and updating the tracker because the ATS pull is unreliable.

Line · 03 · The largest

Delayed productivity from slow time-to-rec

$1.0M – $2.5M / yr

Every two weeks of delay on an engineering hire is approximately $12,000 of deferred productivity. Across 400 reqs/year with a 5–8 business day delay, that is the productivity not delivered.

Line · 04

Forecast variance attributable to stale plan

$2.0M – $6.0M / yr

The TA-allocable share of the operating-expense miss that lands on the CFO's desk as "the hiring plan changed." It comes home to TA as next year's revised plan.

The full-stack cost · all-in by company size
Company size
Annual cost · low
Annual cost · high
500 – 1,000 employees
$2.3M
$4.7M
1,000 – 2,500 employees
$5.1M
$13.2M
2,500 – 5,000 employees
$13.4M
$26.7M
5,000 – 10,000 employees
$22.6M
$42.4M
Stress-test the largest line

How much recruiting time does your team get back?

Move the sliders to your reality: total open reqs per year, the days you lose between decision-to-hire and open-req today, and your average loaded cost per hire. The output is the productivity recoverable by collapsing that delay to a decision-layer baseline (1–3 days).

400
Total recruiting volume across all teams.
11 days
Workday-routed median: 9–14. Decision-layer baseline: 1–3.
$160K
Salary + benefits + employer taxes. Tech average is $140–$180K.
Annual productivity recoverable
$1.6M
That is the engineering, sales, and ops output your company is currently forfeiting because reqs sit closed on a hiring manager's desk for two extra weeks.
Today · Workday-routed
11 days
delay per req · median
Decision-layer baseline
2 days
delay per req · TeamOhana customers
03
Section 03 · The architecture fix

A decision layer in front of Workday.

Workday remains the system of record. The ATS remains the recruiting system. The plan remains in FP&A. A layer gets added in front. Nothing gets replaced. Implementation runs six to eight weeks with no consulting firm.

Recruiting system
ATS
Greenhouse · Ashby · SmartRecruiters
The new layer
Decision layer
TeamOhana
Authorization state across systems
System of record
Workday HCM
Position Management — unchanged
Plan of record
FP&A tool
Adaptive · Pigment · Anaplan

One decision layer. Every system stays. Workday remains the system of record. The ATS remains the recruiting system. The FP&A tool remains the forecasting system. Nothing gets replaced.

What changes for TA, specifically
01 · Single source of truth

The plan you maintain in spreadsheets becomes the plan everyone uses.

When a hiring manager asks where their req is, they look in the front door and see it. When FP&A asks about projected headcount, they look at the same number. The reconciliation meetings go away.

02 · Ready-to-hire gate

You control the moment an approved position becomes an open req.

Keep approved positions in the plan without flooding the ATS. Your recruiter capacity becomes something you can manage against your incoming flow.

03 · Calibrated target dates

Target dates from your team's actual time-to-fill, not a guess.

The dates hiring managers chose at random in January get replaced by AI-recommended target dates based on historical time-to-fill for similar roles. Finance stops using "plan plus three months" as a default.

04 · Managers actually engage

A Slack-grade request flow replaces the 12-to-18-field Workday form.

The hiring manager opens a request from Slack. They complete it in three minutes. The request routes for approval. The recruiter starts work. The two-week delay from form friction goes away.

05 · Clean handoffs

Backfills, transfers, position changes — all one workflow.

The HRBP and the TA Operations team work from the same data with different views. Cross-team handoffs stop being a translation problem.

06 · Strategic seat at the table

You stop being asked about the form. You start being asked about the sequence.

Conversations move from "did you fill out the form correctly" to "let's talk about how to sequence your hiring against your roadmap." That is the conversation TA has wanted to have for years.

04
Section 04 · Making the case internally

By the time you have the conversation, everyone has already read their document.

The point of four persona-specific assets is that each stakeholder reads the document written for them. Forward the document. Then have the conversation. The framings below land consistently.

With the
CFO
$
Lead with

Forecast variance. The $5M to $13M annual cost for a 1,500-person company is the headline. Ask them to validate the math against your own numbers.

With the
CHRO
HR
Lead with

HRBP capacity. Your HRBPs spend 30–50% of their time on reconciliation. The strategic partnership they were hired to deliver requires that time back.

With the
HRIS Lead
W
Lead with

Integration repair work and the strategic systems work they are not building. They will recognize themselves immediately. Likely your strongest internal ally.

With your
CEO
★
Lead with

The architectural argument. Workday is the right system of record. It is the wrong system of work. Foundational for the strategic HR conversation.

"By the time you have the conversation, everyone in the room has already engaged with the argument from their own seat. The room is already half-converted before you start speaking."

— From the playbook
→
What to do next

Three concrete actions, in order of commitment.

Action 01

Forward the relevant persona documents

The CFO memo, the CHRO strategy brief, and the HRIS field guide are designed to land with their respective readers. Having all three read their own document before you discuss the topic internally collapses the timeline from awareness to decision dramatically.

See the four framings
Action 02

Run the diagnostic

A 30-minute self-assessment your HRIS lead can complete that tells you exactly which of the five underlying failure modes is producing the most pain at your company. We share it without requiring a sales conversation.

Run the 5-minute health check
Action 03

Book a 30-minute architecture review

A live conversation about your specific Workday tenant, ATS, and FP&A stack. Bring your HRIS counterpart. No RFP. No procurement. Thirty minutes and the right people in the room.

Request the review
From the editor

You know what your team looks like next Monday morning.

You can run it again — the fourteen-roles-have-changed meeting, the 2:11-p.m.-Thursday Slack thread, the ninety-minute reconciliation — or you can change the architecture underneath it. This playbook exists because the people one floor up need the language and the numbers to back you when you make that case. Now they have both.

If the document resonated, the next move is to forward the three persona-specific documents to the three people who will be in the room, and then spend thirty minutes with us walking through what a decision layer looks like in your specific stack. We come prepared.

Tushar Makhija
Tushar Makhija CEO, TeamOhana