---
name: job-requisition
description: Initiate, route, and approve job requisitions. Use when a hiring manager or stakeholder needs to open a new headcount, request budget approval for a role, or kick off the hiring lifecycle. Handles justification writing, headcount validation, budget cross-checking, multi-level approval routing (manager → HR → finance → department head), and auto-triggering downstream workflows like job description generation. Triggers on phrases like "open a requisition", "need to hire", "request headcount", "approval for new role", "fill a position".
---

# Job Requisition & Approval

Automate job requisition creation, validation, and multi-level approval routing.

## Workflow

1. Collect role details from the hiring manager: title, team, level, location, urgency, budget band, must-start date.
2. Validate against current headcount plan — check if the role is pre-approved, needs replacement (backfill), or is net-new headcount.
3. Cross-reference budget: verify the department has remaining allocation for this level and location. If over-budget, flag and suggest alternatives (lower level, deferred start, cost-center transfer).
4. Draft the requisition with auto-populated fields: market-rate compensation range (pulled from comp band data), role justification template, business impact statement.
5. Route to approval chain based on requisition type:
   - **Backfill**: Manager → HR → Finance sign-off
   - **Net-new (< $100K TC)**: Manager → HR → Finance → VP
   - **Net-new (≥ $100K TC)**: Manager → HR → Finance → VP → CFO → CEO
   - **Contract/Temp**: Manager → HR only
6. Track approval status; send reminder nudges at 48h and 72h if stalled.
7. Upon final approval, trigger downstream workflows: job description generation, ATS posting, recruiter assignment.
8. If rejected, capture rejection reason and route back to hiring manager with revision guidance.

## Requisition Data Schema

Collect these fields before routing:

| Field | Required | Notes |
|-------|----------|-------|
| Role Title | Yes | Use standard title taxonomy |
| Department / Team | Yes | Map to org chart |
| Level / Grade | Yes | E.g., L3, Senior, Band 5 |
| Employment Type | Yes | Full-time, Contract, Intern, Part-time |
| Location | Yes | City, state, remote policy |
| Headcount Type | Yes | New, Backfill, Redeployment |
| Budget Code | Yes | Cost center or project code |
| Justification | Yes | Min 3 sentences: business need, impact, timing |
| Must-Start By | No | Drives urgency flag |
| Replacing Employee | No | Name/ID if backfill |

## Approval Routing Matrix

```
                    Budget OK?
                   /          \
                 Yes           No
                 /               \
          Headcount New?      Suggest:
           /          \        - Deferral
         Yes          No       - Level downgrade
        / | \         |        - Transfer from other dept
       VP CFO CEO    Finance   - Contract instead
       |   |   |     review
      HR Fin MGR  ←  reject/revise
```

## Urgency Flags

- **Critical** (must-start within 30 days): Skip sequential routing, send parallel approvals, 24h reminders
- **Standard** (31–90 days): Sequential routing, 48h reminders
- **Pipeline** (90+ days): Queue and batch with next approval cycle

## Rejection Handling

Common rejection reasons and automated responses:

| Reason | Action |
|--------|--------|
| Over budget | Suggest lower grade, contract, or deferred start date |
| Duplicate role | Flag existing similar open requisition |
| Headcount frozen | Place in hold queue with auto-unfreeze on policy change |
| Insufficient justification | Return to manager with specific gaps highlighted |
| Compliance block | Route to legal/HRBP for resolution |

## Output

Generate an approval-ready requisition package:

```
REQUISITION #REQ-2025-0432
Status: Pending VP Approval
Role: Senior Product Manager
Team: Platform Products
Level: L6 | Type: Full-time | Location: Remote (US)
Budget: $165K–$195K base | Cost Center: PROD-2025-Q2
Justification: [auto-drafted based on inputs]
Submitted: 2025-01-15 | Est. Approval: 2025-01-19
```

## Integration Points

- HRIS (Workday, BambooHR, Gusto) for headcount data
- Budget/Finance systems (NetSuite, QuickBooks) for allocation checks
- ATS (Greenhouse, Lever, Ashby) for downstream posting
- E-signature (DocuSign) for approval capture
- Email/Slack for approval notifications and reminders

## Edge Cases

- **Emergency hires** (executive request): Override normal routing, post-approve with 30-day compliance window
- **Multi-role requisitions** (bulk hiring): Batch with single approval, individual tracking per role
- **Requisition renewals** (role stayed open >90 days): Auto-prompt hiring manager to re-justify or close