Job Requisition

Job Requisition is the execution document for an approved headcount plan.

A job requisition is the internal approval document that authorizes HR to begin recruiting for an open position. It captures the business case, headcount budget, required skills, and reporting structure before a job posting goes live. In enterprise HRIS platforms like Workday and SAP HCM, the requisition is the system record that triggers the hiring workflow. Also called: hire request, position request.

Job requisition vs. job description vs. job posting

These three documents serve different audiences at different stages of the hiring process. Conflating them creates compliance gaps and candidate experience problems.

The req gates the process. No approved req means no job description drafted, no posting published, no ATS record opened. Enterprise orgs using Workday configure req approval chains as conditional workflows: a backfill at the same pay band may require two approvals in 48 hours, while a net-new headcount above director level triggers a five-approver chain including the CFO.

What goes in a job requisition

A well-structured req contains six categories of information:

1. Role details

Job title, department, reporting line, location (remote/hybrid/onsite), employment type (FTE, contractor, part-time), anticipated start date.

2. Business justification

Is this a backfill (departure or leave) or net-new headcount? For net-new, the hiring manager must state the business case: revenue impact, project dependency, or compliance requirement. Finance teams use this to validate against the approved headcount plan.

3. Compensation and budget

Target salary band, bonus eligibility, total comp range. Many enterprise orgs require the finance BP to counter-sign this section, especially when the role falls outside the pre-approved annual headcount budget.

4. Required skills and qualifications

Minimum qualifications must be job-related and defensible under EEOC Uniform Guidelines on Employee Selection Procedures. Listing credentials that are not operationally necessary (e.g., requiring a degree for a role where skills testing demonstrates competency) exposes the organization to adverse impact claims. Skills-based hiring programs, like those documented by SHRM, use the req stage to enforce job-relatedness before the posting goes live.

5. Headcount and position control data

Position control number (PCN), cost center, budget code, FTE count impact. In Workday, this links the req to the position management module. SAP HCM uses personnel requests tied to organizational units. Getting this right at the req stage prevents downstream payroll and reporting errors.

6. Approval signatures

Role-based access control (RBAC) determines who can initiate, edit, approve, or reject a req. A hiring manager can create and edit. A department head approves business justification. HR approves compliance and job-relatedness. Finance approves budget. An executive approves net-new headcount above a threshold. Only users with the correct Workday security roles can advance the req to each stage.

How to write a job requisition

Step 1: Confirm the workforce plan alignment

Check the approved headcount plan before initiating. If the role is not in the plan, the req will require an off-cycle exception, which adds approval layers and time. Partner with workforce planning stakeholders early.

Step 2: Draft the business justification

State the business impact in numbers where possible. “This role will own three enterprise accounts currently without a dedicated CSM, representing $2.4M ARR at risk” is approvals-ready. “We need more headcount” is not.

Step 3: Validate compensation against the band

Pull the approved salary band for the level and location from your HRIS. Flag any exceptions before submission. Off-band requests routed without pre-approval from the compensation team are the most common cause of req rejection at large organizations.

Step 4: Define minimum qualifications with job-relatedness in mind

List only what is operationally required. For each qualification, be ready to explain the business necessity if audited. If you use structured assessments as a qualifying step, document that the assessment is validated and job-relevant per EEOC Principles for the Validation and Use of Personnel Selection Procedures.

Step 5: Set up the RBAC and notification chain in your ATS or HRIS

In Workday, assign the req to the correct supervisory org and position. In Greenhouse or Lever, configure approval stages before publishing. Ensure the hiring manager has access only to their req and cannot view or modify other open requisitions. This is both a data hygiene issue and a legal one.

Step 6: Submit and track SLA compliance

Enterprise talent acquisition teams should enforce approval SLAs: 48 hours for backfills, five business days for net-new. LinkedIn Talent Solutions data shows that req-to-offer cycles lengthen by an average of 11 days when req approvals slip past the five-day mark, compounding time-to-fill across the pipeline.

Enterprise considerations: Workday, SAP HCM, and headcount controls

At organizations running Workday HCM, the job requisition is not a standalone form. It is a business process object that triggers a configurable approval chain. Key configuration points:

• Position management vs. headcount management: Organizations using position management require a funded, approved position to exist before a req can be created. Headcount management is more flexible but less controlled.
• Headcount freeze controls: Finance can activate a global freeze that blocks new req submission or routes all reqs to an executive committee regardless of type. HR ops teams should verify freeze status before submitting off-cycle reqs.
• ATS integration: Workday pushes approved reqs directly to recruiting modules (or via API to Greenhouse/Lever). Field mapping errors at this stage, particularly for job family, pay rate type, or worker type, cause downstream issues in offer management and onboarding.
• Audit trail: Every status change, approval action, and field edit on a Workday req is logged with user ID and timestamp. This log is what HR Legal pulls in an EEOC investigation or SOC2 audit. Treating the req as a living document rather than a one-time form is the correct posture.

For organizations managing bulk hiring across seasonal or project-based cycles, talent acquisition teams benefit from templated req libraries with pre-approved job families, reducing drafting time per req from hours to minutes.

Why job requisitions matter for compliance and audit trails

Three compliance use cases make the req non-negotiable at enterprise scale:

EEOC and adverse impact monitoring

The req defines the minimum qualifications used to screen candidates. If those qualifications produce adverse impact on a protected class, the req is the first document EEOC investigators examine. Requirements must be job-related and consistent with business necessity under the Uniform Guidelines.

SOC2 and access control

Organizations seeking SOC2 Type II certification must demonstrate that access to personnel decisions is controlled and logged. RBAC on requisitions, enforced at the HRIS level, satisfies the logical access control criteria under the Common Criteria.

GDPR and data minimization

Reqs that capture more candidate data than operationally necessary, or that store applicant information beyond retention policy, create GDPR exposure. The req template is the right place to enforce data minimization: collect only what the role requires, specify retention period, and link to the applicant tracking system privacy configuration.

Enterprise teams use Testlify to assess candidates against the skills defined in the job requisition before the interview, giving hiring managers objective data on every shortlist : start your free trial.

Frequently asked questions