At a glance
University Workday setups don't lose candidates at the screening stage. They lose them in approval chains, requisition configuration and job board connections that nobody has revisited since go-live.
Ask a university recruiter what's wrong with their Workday setup and you rarely hear about the software. You hear about the requisition that sat with a budget officer for eleven days. The search committee that wanted to interview before the dean had signed off. The offer letter that went out three weeks after the finalist had already taken a job somewhere else.
The system did what it was told. Someone configured it that way during the implementation, and nobody has opened the business process since.
Hold two numbers side by side. The University of Akron, after going live with the full Workday platform, reported that 64% of positions were being filled in under 30 days, with onboarding completed inside the system in two days. CUPA-HR's Faculty in Higher Education Survey puts the median tenure-track search in the United States at nine to twelve months from requisition to acceptance. Both are true in the same sector, in the same software category. The software isn't the variable. The workflow wrapped around it is.
The Software Isn't the Slow Part
A faculty search in Workday isn't one business process. It's a chain of them: the requisition, the job posting, the application review, the interview scheduling, the offer, the hire. Each one carries its own approval steps, its own business process security policy and its own completion step. When people say Workday is slow, what they usually mean is that one link in that chain has a step nobody owns.
The most common version of that problem: the completion step sits at the very end, after compensation approval, after the offer letter, after the service step that creates the Workday account. Workday's own administrative guidance recommends the opposite arrangement. Approval and review steps belong before the completion step, and the completion step is often best set at a consolidated approval, the point where a manager signs off on job details and pay in a single task. Service steps like Create Workday Account are meant to sit after it, so back-office automation can run without holding up the hire.
That's a configuration choice with a cost you can measure in lost finalists. Every step you place after completion is a step where your preferred candidate is still waiting on you and a competing institution isn't.
The Approval Chain Is Doing More Damage Than the Screening Questions
Workday gives you two step types most universities underuse. The consolidated approval bundles several preceding actions into a single inbox item, so a hiring manager reviews job details, organisation assignments and compensation on one screen instead of clearing three separate tasks. The consolidated approval chain does the same and then routes that one item up the management hierarchy until it reaches the top or hits an exit condition.
The purpose isn't to thin out oversight. It's to stop oversight fragmenting into five notifications that the same person has to clear in sequence over five days. Workday's guidance also flags a specific trap: a standard approval step can be skipped automatically when the approver is the person who initiated the transaction. A consolidated step works around that, which matters in small departments where the chair is also the hiring manager.
Condition rules handle the rest. A second-level approval that only fires above a salary threshold, or a provost-level review that only triggers for tenured appointments, keeps the chain short for routine roles and long for the ones that genuinely need scrutiny. Without those rules, every search inherits the maximum number of approvals.
Timing is what makes this urgent. In the Computing Research Association's survey of faculty search practice, 43% of departments started their searches in December and 48% ended them in May. Two-thirds gave candidates two to four weeks to decide on an offer. Those are the constraints your chain operates inside. Add a week for a dean's sign-off, another for compensation review, and three days for a contracts office that doesn't work Fridays, and you've spent the candidate's decision window before the candidate has seen the salary.
Australian duration data is blunter still. In a submission to a parliamentary committee, UNSW reported that academic roles are typically advertised for four to eight weeks, sometimes twelve, and that for the 102 academic recruitment processes in a single year that ran past the four-month labour market testing limit, average time from advertising to offer acceptance was 28 weeks. Academic notice periods can run to twelve months. A search that starts late can't be rescued by moving faster at the end.
Why an Academic Requisition Isn't a Staff Requisition
Staff hiring has a hiring manager, a recruiter and a budget. Faculty hiring has a search committee, a chair, a dean, a provost's office, an equal opportunity officer and sometimes a board. It also has a data model that most corporate Workday deployments never touch.
Workday models academic appointments separately from jobs. An academic appointment records an appointee's relationship to an academic unit, over a period, on a particular academic track. Academic units are their own organisation type with hierarchies used for roll-up reporting. Adjunct and sessional teaching is usually paid through period activity pay rather than a standard salary. Treat a lecturer the way you treat an accounts payable clerk and the approvals will route to the wrong people, while the reporting won't reconcile at year end.
This is no longer an edge case, because the customer base got large. Workday reported in October 2025 that Workday Student has more than 140 customers representing over 190 institutions, with go-lives during the year at the University of Melbourne, the University of Auckland and the University of Hull, and new higher education customers including Bow Valley College in Canada and the University of York in England. Workday's announcement also lists new United States customers Loyola University Chicago, Macalester College and Swarthmore College, alongside go-lives at William & Mary and the University of Wisconsin System.
Every one of those institutions is now making the same set of decisions about how a faculty line gets approved, posted and filled. Most are making them alone, in a tenant, without a benchmark.
Compliance Lives in the Requisition, Not the Report
For US federal contractors, which includes most research universities, the applicant tracking system is the compliance record. The Office of Federal Contract Compliance Programs defines an Internet applicant through four conditions: the person submitted an expression of interest electronically, the institution considered them for a particular position, the submission showed they met the basic qualifications, and they didn't withdraw. The OFCCP's recordkeeping guidance is explicit that records must be available to the agency in a readable format no matter who maintained them, a third-party vendor included.
Four configuration consequences follow. Basic qualifications have to be written into the posting, objectively and without comparison, which is why open-rank advertisements cause trouble unless each rank's qualifications are spelled out. Every applicant who meets them needs a disposition code recorded in the system rather than in a spreadsheet the committee keeps on a shared drive. Self-identification data has to be separated from what the search committee can see. And records are held for two years from the date of the personnel action, or one year for contractors below the size threshold.
The University of Pittsburgh's changes after an OFCCP audit are a fair template. The institution began posting every faculty position, including part-time and visiting roles, stopped running open-rank advertisements without rank-specific qualifications, dispositioned all faculty applicants inside its tracking system, and required concluded searches to be closed in the system rather than left flagged as open.
Litigation risk has shifted too. In May 2025 a federal judge in California conditionally certified a nationwide age discrimination collective against Workday itself rather than against the employers using it, over allegations that its AI recommendation tools screened out applicants over 40. Workday has said its AI recruiting tools don't make hiring decisions and are designed with human oversight at their core; the company also represented in filings that 1.1 billion applications were rejected using its tools during the relevant period. Proskauer's analysis of the certification ruling is sober reading for anyone editing screening questions this year.
You don't need to resolve that case to take the practical lesson. If a questionnaire in your tenant can reject an applicant without a human opening the file, somebody should be able to say who approved each question and when it was last reviewed.
What Breaks When You Connect a Job Board
Every job board connection is a data contract, and most break on field mapping rather than on anything exotic. The published installation guides are useful precisely because they show where.
Indeed's ATS Sync for Workday is roughly one to two hours of configuration, with three required steps and three optional ones. It only picks up job postings that are both Active and External, and requisitions that are Open or set up as Evergreen. If a location is inactive in Workday, the posting won't sync. Want a role advertised in two languages? You need two requisitions, because the recruiting APIs can't detect which language a requisition is written in. The Indeed installation guide spells all of that out, including a limitation on reordering answers in branching questionnaires once they're attached to a requisition.
Handshake's integration runs the other direction. The candidate applies externally, the application lands in Workday within minutes tagged with Handshake as the source, and status changes sync hourly. Setup and validation take five to ten days and happen in a staging tenant first, per Handshake's documentation.
| Connection | Setup effort | How applications arrive | Known constraint |
|---|---|---|---|
| Indeed ATS Sync | About one to two hours, three required steps | Synced from the Workday job posting | Posting must be Active and External; each language needs its own requisition |
| Handshake | Five to ten days including staging validation | Candidate applies externally; application appears in Workday within minutes | Job must be Live in Workday; statuses sync hourly |
The pattern worth noticing is attribution. Applications arriving through a connected board land in Workday with the source intact, which is the only reason source-of-hire reporting works at all. Applications arriving through a board nobody connected arrive as email in someone's inbox, and the attribution is gone before the shortlist meeting.
Your Workday Career Site Is Not a Faculty Recruitment Strategy
Workday lets an institution run between 1 and 100 active external career sites, branded with hex colour codes, with separate language options, social login and per-site tracking pixels. It's a competent corporate careers presence. It is not where a mid-career physicist looks for a job.
There's a security detail worth knowing. Workday's configuration guidance warns that embed mode lets a third party host your career site inside another page without the user's consent, which exposes candidates to phishing and social engineering, and that enabling it removes the follow icons, the privacy policy link and the prospect self-introduction link from the embedded view. If nobody on your team can say whether embed mode is switched on, that's a question for this month rather than next year.
What reaches academics is distribution. Putting the same requisition in front of a disciplinary audience, through a feed partner or a manual post, is what turns a Workday requisition into a shortlist. AcademicJobs.com is now integrated with Workday, so a requisition opened and approved in Workday can be advertised through the board by feed or by manual post, with applicants sent back to the institution's own career site to complete the application inside Workday. The requisition stays the single record. The audience gets wider.
What the Candidate Sees Is a Form
The candidate experience is the part nobody configures, because nobody owns it. A professor applying for a chair role meets an account creation wall, a parser that mangles a forty-page CV, a field asking for a current company and a degree dropdown that doesn't include their discipline. Quick apply and resume parsing help. LinkedIn and SEEK profile import cut the typing in some markets. Workday's acquisition of Paradox in October 2025 added a candidate experience agent that engages, screens and schedules interviews, which addresses scheduling back-and-forth rather than the form itself.
Read productivity claims with the source in mind. Workday says its AI recruiting tools cut recruiter screening time by 57%, shorten hiring manager review by 35% and fill 70% of requisitions from existing talent pools. Those figures come from Workday, published around a June 2025 announcement of its position in Gartner's first Magic Quadrant for talent acquisition suites. Treat them as directional, not audited. The institution-level evidence is thinner but more persuasive: Akron's leave approvals moving from three weeks to under a day is the sort of change that shows up months later in a search timeline.
What to Fix This Term
Four things, in order of return on effort.
- Open the Hire and Job Application business processes and find the completion step. If it sits after compensation and offer approval, move it back and let the service steps run behind it.
- Run a business process history report across the last twenty faculty searches and identify the step with the longest average dwell time. That's the one to consolidate or wrap in a condition rule.
- Export every screening question that can reject an applicant without human review, and confirm each one maps to a basic qualification printed in the advertisement.
- List every board you are connected to, with the date it was last validated. Anything absent from that list is a search you cannot attribute.
None of this needs a new licence or a project team. It needs somebody with access to the tenant and the authority to change a step, and those are usually two different people who have never been in the same meeting.
Photo by Hitesh Choudhary on Unsplash
- academic-jobs
- faculty-hiring
- workday
- hr-technology
- applicant-tracking-systems

