At a glance
A practical guide for university HR systems and talent acquisition leads on configuring Workday Recruiting for faculty and staff searches, from approval chains and requisition controls to candidate experience and job-board distribution.
The question came from a partner running a chair search in a faculty of health sciences. Their preferred candidate had signed elsewhere eleven days before the offer letter arrived. "Was it the money?" they asked. It wasn't. The requisition had sat with a budget partner for eighteen working days, then with a dean's office for another nine, and nobody had written to the candidate in between. The search committee had done everything right. The process around it hadn't.
That gap — between how a university describes its hiring and what an applicant actually lives through — is where most academic searches are lost. Workday Recruiting is a capable enterprise system, and nearly every complaint I hear about it traces back to a business process somebody configured during an implementation and nobody has opened since.
Where the weeks actually go
In Workday, a position and a requisition are separate objects, and at most institutions they are separate approvals. Norfolk State University, which moved its recruiting onto Workday, describes position creation and job requisition as two steps each requiring sign-off, with the requisition then routing through an HR partner, the manager's manager, a dean or director, a vice president, and in some cases the president and budget partners. The University of Maryland system's Workday design adds central budget review to the same chain and sends faculty requisitions through the provost's office on top of it.
None of that is unreasonable. Position control is how a university knows it can afford the hire; budget review is how a dean finds out. But each handoff is a queue, and queues are where strong candidates go quiet.
The cost is measurable. A study of faculty searches at the City University of New York found an average of 97 days between a president's approval of a search and the job appearing on the system's job portal, with the worst-performing campus stretching to 195 days. The same analysis put 386 days between approval and hire. That is most of an academic year spent waiting for internal steps to clear.
One business process can't govern three kinds of hire
American University's experience is the clearest case I've seen. Its Workday setup ran faculty, staff and student hiring through a single requisition and job application business process, with conditional logic doing the differentiation. A single hire could take up to a month. Approvals sometimes landed with the same person acting in two roles, and steps duplicated. The fix was structural rather than cosmetic: three rule-based business processes, one per hire type, with approvals consolidated and steps set to auto-complete once conditions were met. Recruitment cycle time fell by more than half.
The lesson isn't that the platform needs replacing. It's that a configuration choice made under go-live pressure quietly becomes institutional policy for a decade.
The University of Washington took the other route and was candid about the trade-off. It approved Workday Recruiting under an "Implement, Adapt and Evolve" method: launch with the essential features after roughly nine months of design and testing, then spend nine months refining against live feedback. The University of Washington's implementation announcement reads like a campus deciding to ship a smaller process and improve it rather than delay for a perfect one. Both approaches work. What fails is launching a process nobody has scoped against how departments actually hire.
What the candidate actually meets
Workday applications are requisition-specific and point-in-time. At Washington, that meant applicants could no longer correct education or work history once submitted — they had to reapply — and attachments uploaded beyond what the department asked for could not be removed on the institutional side. External applicants gained job alerts; internal applicants could save searches but were not notified about new roles. A professor who spots an error in a cover letter at eleven at night has no path to fix it inside the record of their own application.
The volume arriving at the other end isn't the problem. The University of Washington's biology department typically received between 500 and 1,000 applications for a single faculty post, according to reporting in eLife; CV screening cut that to roughly 100, and reference letters to about 40. Reviewer attention is the scarce resource, and every week a requisition sits unposted is a week the pool isn't forming.
Workday has been buying its way into parts of this. It completed the acquisition of Paradox, a conversational candidate experience agent, on 1 October 2025, and Workday's announcement frames the agent around frontline and high-volume roles, scheduling and instant responses. That's genuinely useful for the staff and student-worker requisitions running through the same tenant. It does very little for a chair search with nine shortlisted candidates and a senate committee waiting on a rubric.
Photo by Vitaly Gariev on Unsplash
The compliance trail is the product
Most of what looks like bureaucracy in an academic search is documentation that has to exist afterwards, and the system of record is where it should live. Florida Atlantic University's faculty recruitment checklist is precise about the sequence: the recruiting partner moves the finalist to "Request Hiring Review" in Workday, that review is approved, and only then may a verbal offer be made. The offer status is then recorded as accepted, declined or in negotiation, and a background check runs through the university's vendor before the appointment is finalised.
Fort Hays State University handles timing rules in the same place: a position must stay posted seven days for hourly roles and 30 days for salaried ones before screening starts, on-campus faculty interviews require approval from chair, dean and provost inside Workday, and search committee members enter their interview ratings and comments there rather than in a shared spreadsheet that nobody can retrieve two years later.
What this buys the institution is defensibility. What it costs is time, unless somebody deliberately designs the path. FAU's published department checklist for faculty recruitments is worth reading as a model of clarity — every step names who performs it and what must exist before the next one opens. The administrative staff who maintain those documents rarely get credit for how much friction they remove.
The requisition is the record. Distribution is a separate job.
Workday will host your career site, brand it, translate it and let you run several of them. What it won't do is put a lecturer post in front of a disciplinary audience that never visits an employer careers page. A mid-career physicist doesn't browse institutional job portals; they read the field's board, a listserv, a society newsletter. Employer branding earns attention on the margin, and the branding work that actually shifts applications is usually the specific, unglamorous detail — start-up funding, teaching load, visa support — rather than the homepage design.
Connecting a job board to Workday is a data contract with specific terms. Indeed's ATS sync takes an hour or two to configure and picks up only postings that are both Active and External, on requisitions that are Open or set up as Evergreen; a role advertised in two languages needs two requisitions, because the recruiting APIs can't detect which language a requisition is written in. Handshake's integration runs the other direction — the candidate applies externally and the application lands in Workday within minutes tagged with the source — and needs five to ten days including validation in a staging tenant. Applications arriving through a connected board keep their source; the ones arriving as email in a recruiter's inbox lose it before the shortlist meeting. That is why source-of-hire reporting so often tells an institution nothing it can act on.
AcademicJobs.com sits on the specialised side of that split. A requisition opened and approved in Workday can be advertised on the board by feed, through a distribution partner, or by manual post, with applicants sent to the institution's own career site to complete the application inside Workday. The requisition stays the single record; the audience widens. The Workday integration page sets out how the connection works, and the recruitment hub covers posting options for teams running several searches at once.
Same system, different rhythm
Where the delay sits depends on which country you're hiring in. In the United States it's usually approval. William & Mary's published search matrix for tenure-eligible and teaching faculty shows the shape of a well-run cycle: dean's authorisation in early August, search committee approved by 21 August, position created in Workday on 9 September, requisition and posting prepared by 17 September, application review beginning 30 to 45 days after the posting goes live, long-list interviews four weeks after that, on-campus interviews running from mid-January to late February, and a request for a verbal offer reaching Faculty Personnel Services by early March.
In Australia and New Zealand, Workday's higher education base is smaller and newer. Workday has put the regional count at 16 institutions running its software for HR and finance, among them the University of Melbourne, Macquarie and RMIT, and Workday Student only became available in the region in December 2024, with Melbourne, Macquarie and the University of Auckland forming the local advisory panel. Melbourne's ERP now runs Workday alongside UKG Pro and Cayuse. Fewer peers means fewer configurations to borrow and more teams building these workflows for the first time.
For anyone running an international campaign, that has a blunt consequence: the same requisition moves at different speeds in different places, and a timeline a search committee reads as thorough can read as silence to a candidate in another market.
An implementation checklist for HR systems and TA leads
Work through these in order. Each one assumes you can pull a report out of the tenant without raising a change request.
Photo by Hitesh Choudhary on Unsplash
- Run business process history on your last twenty faculty searches. Find the step with the longest median queue time. That single number is the most useful recruitment metric most institutions aren't reporting.
- Split the business process by hire type. Faculty, staff, student and postdoc searches have different approvers and different documentation. Conditional logic inside one process is cheaper to build and more expensive to run.
- Check where the completion step of Hire and Job Application sits. If it sits after compensation and offer approval, service steps queue behind it and the candidate waits for a letter that could have been drafted days earlier.
- Assign security roles at the supervisory organisation rather than ad hoc. Interviewers who can't see the requisition will ask for CVs by email, and the audit trail ends at that point.
- Audit the requisition template against academic reality. A degree dropdown that stops at master's level, a required "current company" field and one generic resume slot all cost you applications from exactly the people you wanted.
- Confirm which requisitions are eligible to syndicate. Active and External, Open or Evergreen. A posting that fails those conditions syncs nowhere, and nobody notices for a fortnight.
- Set a screening-start service level. Thirty to 45 days after posting is common for faculty searches; agree who reviews on day one and state the date in the advert.
- Write acknowledgement and disposition language once, centrally. Every applicant gets the same clear message at the same point, including the ones you don't advance.
- Give each open search a named owner. Not only the committee chair — a recruiter or HR partner whose actual job includes the candidate's week-to-week experience.
- Turn on source tracking before the next campaign, not after it. You can't defend a job-board spend you can't attribute to a hire.
One thing to do this month
Take the ten most recent faculty and professional searches. Run a business process history report on each, note which step held the requisition longest, and attach a name and a two-day turnaround to that step. Don't restructure the approval chain yet. Make the queue visible to the person who owns it, and tell candidates in writing when they'll next hear from you. At partner institutions where this has been done, two to three weeks typically come out of the search before anyone touches a configuration setting.
Then widen the funnel. Connect your Workday tenant to AcademicJobs.com so the requisitions you've already approved reach readers who search by discipline rather than by employer brand. A search committee can only choose from the pool it can see.
- Workday Recruiting
- Higher Education HR
- Faculty Recruitment
- Applicant Tracking Systems
- University Talent Acquisition

