Recruitment operations
Design and run the operational infrastructure behind recruiting — requisition workflows, ATS configuration, SLAs, process governance, and reporting — so recruiters can focus on candidates instead of process friction.
Supported tasks
- Designing requisition creation and approval workflows
- Configuring ATS pipeline stages, statuses, and automation rules
- Setting recruiting SLAs (time-to-screen, time-to-schedule, time-to-offer)
- Auditing the recruiting process end-to-end to find bottlenecks
- Standardizing interview scheduling and coordination workflows
- Building recruiting operations dashboards and reporting cadence
- Managing recruiting vendor and tool integrations (ATS, scheduling, assessment)
- Designing capacity planning models for recruiter workload
- Creating recruiting process documentation and playbooks for new recruiters
- Governing data quality and hygiene within the ATS
- Coordinating recruiting operations across multiple business units or regions
- Running root-cause analysis on missed hiring targets or process failures
Key prompts
Workflow design
- "Design a requisition approval workflow with clear stages from headcount request to job posting approval."
- "Configure recommended ATS pipeline stages for [role type], including automation triggers between stages."
- "Standardize our interview scheduling process to reduce coordination time between recruiter, panel, and candidate."
- "Design an intake process for hiring managers that captures role requirements clearly enough to avoid rework mid-search."
SLAs and process health
- "Define recruiting SLAs for time-to-screen, time-to-schedule, and time-to-offer appropriate for [role type/volume]."
- "Audit this recruiting process end-to-end and identify the top three bottlenecks slowing time-to-hire."
- "Run a root-cause analysis on why we're missing hiring targets for [team/quarter]."
- "What escalation process should trigger when a requisition breaches its time-to-fill SLA?"
Reporting and governance
- "Design a recruiting operations dashboard showing pipeline health, SLA adherence, and recruiter capacity."
- "What ATS data hygiene rules should we enforce to keep reporting accurate (mandatory fields, disposition reasons, stage definitions)?"
- "Build a capacity planning model estimating how many open reqs one recruiter can effectively manage at a time."
- "Design a weekly recruiting operations review agenda that surfaces problems early rather than at quarter-end."
Documentation and scale
- "Write a recruiting process playbook for onboarding a new recruiter, covering requisition-to-offer workflow."
- "How should recruiting operations be structured and governed across multiple business units or regions?"
- "What should be standardized globally versus left to regional recruiting teams to adapt locally?"
- "Draft a change management plan for rolling out a new ATS workflow to a recruiting team used to the old process."
Tips
- Fix process bottlenecks before adding headcount — a broken workflow makes every additional recruiter less effective, not more.
- Set SLAs that are realistic for role type and volume; unrealistic SLAs erode trust and get silently ignored.
- Treat ATS data hygiene as a prerequisite for reporting — dashboards built on inconsistent stage definitions produce misleading numbers.
- Involve recruiters in workflow design, not just leadership — the people using the process daily spot friction leadership can't see.
- Review recruiting operations dashboards on a fixed cadence and act on the data, not just publish it.