TeamOhana Reality Check Series
FILE · 2026.05 · HRIS
Reality Check · No. 01 Field Guide for HRIS leaders running Workday

The Workday Admin's field guide.

A practical assessment of Workday Position Management at scale — written for the people who keep it running.

Audience HRIS leads, Workday admins 500–10,000 employee tech co.
Read time 15 to 18 minutes Forward upward in pieces.
Contents Diagnosis, cost, architecture One section per question.
Author Tushar Makhija CEO, TeamOhana

Editor's letter · For the HRIS lead reading this

You are not failing. The architecture is failing.

If you are the HRIS lead, HR systems manager, or Workday admin at a fast-growing tech company with 500 to 10,000 employees, this guide is for you specifically.

We wrote it because we have sat in too many calls with too many people in your role who all said some version of the same thing: I have followed every Workday best practice, and the data is still wrong, and I am still the person reconciling it on a Saturday.

This guide names what is happening, why it happens, what it costs, and what to do about it. You can read it in fifteen minutes. You can forward sections up. Two pages in, you will know whether the rest is worth your time.

It is not an argument against Workday. Workday is the right system of record. Position Management, on paper, is the right architecture. The argument is narrower: the system of record cannot also be the system of work. The gap between them is now where every fast-growing company's hiring chaos lives. There is something specific you can do about it.

TM
Tushar Makhija CEO, TeamOhana

What this guide gives you

Three things,
in order of use.

Diagnosis on page two. Dollar magnitude two pages later — defensible enough to forward to your CFO. The architectural alternative after that, with implementation timeline.

01

A clean diagnosis

Five specific failure modes of Workday Position Management at scale — in the language you actually use to describe them. You will recognize all five.

02

The cost, in dollars

A defensible cost stack you can put in front of your CFO. Approximately $5M to $13M per year for a typical 1,500-person fast-growing tech company. Bands for other sizes inside.

03

The architectural alternative

A front door layer that sits in front of Workday Position Management. Six to eight weeks to implement. Two to four hours of your time. Reversible. Not a replacement for Workday.

Section 01

01

This is your
Monday morning.

If you've worked an HRIS desk at a fast-growing company for more than six months, the picture below is your week.

Where the work actually lives today.

Current state · observed
LIVE WORK Hiring managers
Slack DMs Calendars Linear / Jira Email thumbs-up
PLANS Talent acquisition
TA tracker (Google Sheets) Recruiter dashboards Notion pages
FORECAST Finance & FP&A
Adaptive Insights Headcount roll-up (sheets) Anaplan
APPROVAL HRBPs
Email approvals Slack 👍 Comp committee minutes
RECONCILE You, every Monday
Workday Position Management ATS (Greenhouse / Ashby) Studio integration · fails ~4×/qtr

Hiring managers live in Slack. TA tracks the plan in a spreadsheet. Finance forecasts off a third source. HRBPs approve via email with thumbs-up emojis. Every Monday, your team reconciles. Workday and the ATS sit at the bottom, fed manually, with a sync that fails roughly four times a quarter.

Section 02

02

The five
failure modes.

Workday Position Management does not fail in one large, obvious way. It fails in five specific small ways, each survivable in isolation, that compound when they run together.

01
Failure mode 01

The hiring manager workflow nobody completes.

Workday's requisition form was designed for a different kind of work. Your hiring managers respond rationally to a workflow that does not match the way they work.

The scene · 2:11 p.m., a Thursday in February

Maya, head of Product Engineering at a 1,500-person infrastructure company, opens her laptop in the kitchen between back-to-back interviews. Her VP pinged her Tuesday: we need to backfill Aaron's role, up-level to Staff.

Maya does not open Workday. She opens Slack. @Christine can you start a rec for Aaron's backfill, up-level to Staff, San Francisco or remote, I'll send you the JD by EOD. She closes the laptop. She walks back into her interview.

You see this Slack message at 2:14 p.m. You open Workday. You open Create Job Requisition. You fill in fourteen required fields. You do not have the JD. You do not have the comp justification. You ping Maya. She does not respond for forty-five minutes. Two weeks pass before a candidate is in pipeline.

Why this happens

A typical Create Job Requisition flow has between 12 and 18 required fields across 4 to 7 tabs. The form does not save progress in a way the hiring manager trusts. If they are interrupted, which they will be, they have to either delegate the saved form or restart.

This is not a training issue. Every Workday customer with more than 500 employees has run "Workday for Managers" enablement. It does not stick. 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 you — HRIS labor consumed by translation

Company size
HRIS FTE on translation
Annual cost (fully loaded)
500 to 1,000 employees
0.2 to 0.4
$28K – $58K
1,000 to 2,500 employees
0.4 to 0.8
$58K – $115K
2,500 to 5,000 employees
0.8 to 1.6
$115K – $230K
5,000 to 10,000 employees
1.6 to 3.0
$230K – $430K

Median time from "decision to hire" to "open rec in the ATS" at companies routing through Workday is 9 to 14 business days. At companies running a front door in front of Workday, the same time is 1 to 3 business days. The third cost is what you are not doing — every hour of translation is an hour not spent on the strategic systems work you were hired to do.

From the field

"The business hate Workday and tend not to update it. Therefore you don't have a source of truth. You end up with multiple truths."

— Global Head of Recruitment Operations, 8,000-person dual-listed fintech

02
Failure mode 02

The plan that rots before the year starts.

Annual plans are 30 to 50 percent wrong by April. The position objects in Workday do not catch up, because the workflow to update them is the same workflow nobody completes.

The scene · second week of February

The company completed annual planning in December. The board approved 612 net new positions for the year, leveled and located. By the second week of February, 47 of those 612 positions are already wrong.

Three have been re-leveled because comp benchmarks shifted. Eleven have been relocated. Eight have been re-scoped from IC to manager. Twelve deprioritized. Thirteen added for a customer that signed in January. None of these 47 changes have been reflected in Workday positions.

Why this happens

Workday Position Management assumes a low rate of change. When the actual rate of change is continuous, the form-and-approval workflow cannot keep up, and the spreadsheets emerge to fill the gap. Every company we have worked with has at least three spreadsheets running in parallel: planning owned by FP&A, hiring tracker owned by TA, leadership cut owned by the CHRO's chief of staff. Each is updated faster than Workday. Each diverges.

From the field

"35 open jobs. Every single one with a start date in the past. Finance has no idea when these will actually be hired."

— VP of Talent Acquisition, 8,000-person publicly traded fintech

03
Failure mode 03

The integration that does not go both ways.

Workday pushes the rec to the ATS. The ATS sends back the hire. But changes the recruiter makes in the middle do not flow back.

The scene · a hire sync that fails on a Friday

A recruiter at a 900-person SaaS company has been working a Senior Engineering Manager role for six weeks. The role originally posted at L5 in Seattle. The hiring manager came back two weeks ago and asked to expand to L5 or L6 in any North American location. The recruiter updated the job posting in Greenhouse. Did not update the corresponding position in Workday.

A candidate accepts an offer on a Thursday at 4:30 p.m. for an L6 role in Toronto. Greenhouse fires the hire-creation event to Workday on Friday morning. The event fails because the position in Workday is still configured as an L5 in Seattle. The recruiter does not see the failure until Monday. The candidate's start date slips by a week.

What it costs you

Per Kinnect, an independent Workday consultancy: typical Workday Studio integration costs $30,000 to $50,000 in initial implementation, plus $5,000 to $10,000 annually in maintenance per ATS connection. At companies in the 1,000–2,500 employee range, the median was 4–7 broken hire syncs per quarter. Each consumes 2–4 hours of your team's labor. 32 to 112 hours per year on integration repair alone.

From the field

"A good quarter of our P-tech tickets are because the hire sync failed. We have other things to do."

— Data and Technology Specialist, 8,000-person fintech

04
Failure mode 04

The three sources of truth nobody trusts.

HR has Workday. TA has the tracker. FP&A has Adaptive. The three numbers never match. Reconciliation eats 60 to 80 hours a month at a typical mid-stage company.

The scene · the Friday before the board meeting

You, FP&A, and HR ops meet Monday at 9. FP&A has 1,387 current, 1,425 projected. HR ops has 1,392 from Workday. You have 1,389 current, 1,431 projected from your tracker. The four numbers are within 1.5 percent but they are not equal. The meeting takes ninety minutes.

Reconciliation labor — HR + TA + FP&A · fully loaded $90–$130 / hr

Company size
Hours / month
Annual cost
500 to 1,000 employees
25 to 45
$30K – $65K
1,000 to 2,500 employees
50 to 90
$60K – $140K
2,500 to 5,000 employees
90 to 180
$110K – $280K
5,000 to 10,000 employees
180 to 400
$215K – $625K

From the field

"100 different recruiters, 100 different spreadsheets, 100 different sources of truth."

— Global Head of Recruitment Operations, 8,000-person fintech

05
Failure mode 05

The audit trail that does not audit.

SOX requires you to prove who approved what, when. Slack threads and thumbs-up emojis do not count. For public companies, this is a control weakness. For companies preparing for IPO, it compounds.

The scene · the auditor asks where the approval lives

Second week of an internal audit cycle at a recently public software company. The auditor asks you for documentation of how a specific role's level was changed in Q2 of last year. The role moved from L5 to L6 between April 15 and May 3.

Workday shows the position at L6, effective May 3, approved by the VP of Engineering. The auditor asks for supporting documentation. The original request from the VP is in Slack. The CHRO's approval is a thumbs-up emoji. The CFO was tagged but did not respond. The audit finding is a control weakness with a recommendation to formalize the approval process.

What it costs you

Consultant-led remediation of a material weakness is $50,000 to $200,000 per finding. The personal cost is harder to quantify. You are the person who has to explain to the audit committee why the documentation is incomplete. The audit response process consumes your time for weeks. It is one of the highest-stress experiences of an HRIS lead's career.

From the field

"We're listing in the US this year. Clean data on one source of truth is no longer important. It's regulatory."

— Head of Recruitment Operations, dual-listed fintech preparing for US IPO

The pattern across all five

Better Workday hygiene does not fix this.

You have already tried better Workday hygiene. So has every customer we have worked with. The hygiene initiatives run six to twelve months and fade.

The structural problem is that the system was designed for a slower world, and you do not live in the slower world. The fix is not better discipline. The fix is an architectural change.

A note before you forward The next section is what your CFO needs to see. If you only forward one part of this guide upward, forward that one.

Section 03

03

The four cost lines,
banded by size.

The five failure modes have a price. The cost stack has four lines that apply at every company size. The dollar magnitude scales with headcount and hiring volume. Find your band.

For a typical 1,500-person company

$5.1M to $13.2M

Annual operating impact distributed across integration cost, reconciliation labor, forecast variance, and strategic opportunity cost.

Cost line breakdown — typical 1,500-person company

Integration cost per Kinnect data
$50K – $90KImplementation + maintenance
Reconciliation labor HR + TA + FP&A
$60K – $140K50–90 hrs/month
Forecast variance 15% one-sided miss
$4.8M – $12.0MLargest single line
Strategic opportunity cost HRIS time consumed
$180K – $325KLower bound only
Total annual operating impact $5.1M – $13.2M

All-in annual cost · banded by company size

Company size
Annual cost (low)
Annual cost (high)
500 to 1,000 employees
$2.3M
$4.7M
1,000 to 2,500 employees
$5.1M
$13.2M
2,500 to 5,000 employees
$13.4M
$26.7M
5,000 to 10,000 employees
$22.6M
$42.4M

The most important thing about this number is not its precision. It is its existence. Most companies have never tried to compute it.

Section 04

04

The architectural
alternative.

A decision layer sits in front of Workday Position Management. Not a replacement. A layer where the actual work of headcount planning happens.

Workday remains the system of record. The ATS remains the recruiting system. The FP&A tool remains the forecasting system. Nothing gets replaced. A layer gets added.

The front door — visualized.

One decision layer · every system stays.

Users

Hiring managers · TA · HRBPs · FP&A

Slack-native intake Web Mobile-friendly

Decision layer · The front door

One persistent ID across every system

Request Approval Position Requisition Offer Hire

Systems of record

Workday · ATS · FP&A

Workday Position Mgmt Greenhouse / Ashby Adaptive / Anaplan

Hiring managers, TA, HRBPs, and FP&A all transact in the decision layer. Every object carries a single persistent identifier across every system. Reconciliation is automatic because the identifier is consistent everywhere.

The cardinal architectural property · Six objects, one identifier

Each object has a durable ID.
Each crosses two or three systems during its lifetime.

01 Request HM opens from Slack or web. Profile, level, location, target start, justification.
Front door
02 Approval Routes through your policy. Approver, timestamp, comments — logged.
Front door
03 Position Approved position with a durable ID. Written to Workday via API.
Front doorWorkday
04 Requisition Opens in the ATS when TA is ready. Inherits metadata. Recruiter changes flow back.
Front doorATS
05 Offer On accept, offer details flow ATS → front door → Workday.
ATSFront doorWorkday
06 Hire Candidate becomes an employee in Workday. Matched to the original position.
Workday

Implementation reality

This is not another
Workday implementation.

Six to eight weeks. Two to four hours of your time. API-based. Reversible. No firm. No Studio dev.

Time to live

6–8weeks

Contract to production.

Your team's effort

2–4hours

HRIS admin time, weeks 1–2.

Consultant hours

Zero

No firm. No Studio dev.

Reversibility

Full

Every position stays in Workday.

Implementation timeline

Week 1–2

Connection

API connection to Workday and your ATS. Read-only at this stage. You verify the data matches what you expect.

Week 2–3

Workflow

Position management pattern configured: create positions at approval or at hire. Most customers start with hire and migrate.

Week 3–4

Approval policy

Configured against your actual rules. Different routing for new hires vs. backfills vs. level changes. Access follows Workday hierarchy.

Week 5–6

Go live

HRBPs, TA Ops, FP&A go live first. 90 minutes of training. Hiring managers in waves over the next 30 to 60 days.

What stops

You stop being the human API.

  • Translating Slack messages into Workday forms
  • Reconciling position data across four spreadsheets
  • Chasing target start dates hiring managers chose at random
  • Integration repair tickets that eat two days per quarter
  • Defending the system of record from being abandoned
  • Opening 47 tabs for the auditor

What starts

The work you were hired to do.

  • Skills inference project
  • Internal mobility infrastructure
  • Career framework rollout
  • AI-readiness audit
  • Workforce intelligence reporting your CEO will consume
  • Strategic partnership with the business

You stay at the company longer. We do not say this lightly. We have watched HRIS leads quit over the dynamic this guide describes. The architecture this guide describes makes the role sustainable.

What to do next

Three concrete actions.

In order of commitment. Pick where you want to start.

01

Self-diagnose first.

A diagnostic worksheet (Appendix A) takes 30 minutes and tells you exactly which of the five failure modes is producing the most cost. If you can answer all 12 questions cleanly, your environment is in better shape than 80 percent of mid-stage Workday customers.

Open the worksheet
02

Forward the cost section to your CFO.

The banded cost stack is the section your CFO needs to see. The numbers are defensible and sourced. If your CFO asks for the methodology, Appendix B has it.

Read the methodology
03

Book a 30-minute architecture review.

A live conversation with a TeamOhana solutions architect about your specific Workday tenant, ATS, and FP&A stack. We do not ask for an RFP. We do not require procurement to begin. We require 30 minutes.

Book a 30-min review

You know what your week looks like next Monday morning. You can run it again — or you can change the architecture underneath it.

Appendix A

The diagnostic worksheet.

Twelve questions. The ones you cannot answer cleanly are the ones the front door architecture would resolve.

Workday Position Management hygiene

  1. How many positions are in your Workday tenant today?
  2. How many were last updated more than 90 days ago?
  3. How many have a target start date in the past?
  4. What percentage match the corresponding requisition in your ATS exactly?

Hiring manager workflow

  1. What percentage of job requisitions are initiated by the hiring manager directly in Workday?
  2. What is your median time from "decision to hire" to "open requisition in ATS"?
  3. How many hours per week does your HRIS team spend translating Slack messages into Workday?

Integration and reconciliation

  1. How many failed hire syncs has your team experienced in the last 90 days?
  2. What was the initial implementation cost of your Workday Studio integration?
  3. Who owns the integration? What happens if they leave?
  4. How many distinct spreadsheets are in active use to track headcount?
  5. How many hours per month do HR, TA, and FP&A collectively spend reconciling?

10–12 clean

Better shape than 80% of mid-stage Workday customers.

6–9 clean

At the median. The cost of the gap is real but not yet acute.

0–5 clean

The trigger event has probably already happened.

Appendix B

Cost methodology.

For the CFO who wants to see the math.

ICP assumption
All figures are calibrated to fast-growing technology companies between 500 and 10,000 employees, growing headcount by more than 20% per year, using Greenhouse, Ashby, or SmartRecruiters as the ATS. Companies outside this profile face the same architectural problems with smaller dollar magnitudes.
Integration cost
Sourced from publicly published Workday Studio pricing data by Kinnect (kinnectx.com), an independent Workday consultancy. $30,000 to $50,000 upfront, $5,000 to $10,000 annual maintenance per ATS connection. Multi-system buildouts at $150,000 to $300,000 over two years based on aggregated TeamOhana customer data.
Reconciliation labor
Hours per month measured across the TeamOhana customer base. Fully loaded labor cost of $90 to $130 per hour: HR and TA generalists at the lower end, FP&A senior labor at the higher end. Bands scale linearly with company size.
Forecast variance
Measured forecast accuracy improvement from 75–85% (pre-TeamOhana baseline, n=14) to 92–97% (post-TeamOhana, two quarters post-implementation, same cohort). Dollar magnitude assumes one-sided variance at 15% against the company's net new hires for the year. Bands assume average annual headcount growth between 20% at the floor and 25% at the ceiling.
Strategic opportunity cost
Lower-bound estimate: 50% of HRIS team time consumed by operational tending, at fully loaded $120,000 to $180,000 per team member. Upper bound, which is several multiples higher, includes the strategic value of work not being built.
Customer attribution
Available on request and under appropriate NDA. We have ten or more design partner customers in the 500 to 5,000-employee fast-growing tech segment with documented before-and-after data on each of the four cost lines.

Next step

Change the architecture, not the hygiene.

Bring your specific Workday tenant, ATS, and FP&A stack. We will walk you through what a front door would look like for your environment — concretely, in thirty minutes.

Book a 30-min architecture review See the rest of the Reality Check series