Loading...
hr

Recruiting Intake and Requisition Kickoff Form

Use this Recruiting Intake and Requisition Kickoff Form to define the role, hiring criteria, compensation range, interview plan, and approval path before sourcing starts. It helps recruiters and hiring managers align early and avoid rework later.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Technology · Healthcare · Manufacturing · Professional Services · Retail

Overview

This Recruiting Intake and Requisition Kickoff Form is the starting point for a new hire request. It captures the requisition overview, role scope, candidate profile, compensation and level, interview plan, and decision makers so everyone agrees on the job before sourcing begins.

Use it when a hiring manager wants to open a role, when a backfill needs to be documented, or when recruiting needs a clean brief before posting and outreach. The form is designed to reduce vague requests like “need a strong generalist” by forcing specific fields for responsibilities, success metrics, must-have criteria, and interview stages. It also creates a clear approval path, which helps prevent delays once candidates are in process.

Do not use it as a long policy document or a free-form brainstorming sheet. If the role is already fully defined elsewhere, keep the intake short and only collect the fields needed to launch the requisition. Avoid over-collecting personal data or asking for details that are not needed to evaluate the role, especially in notes fields. The best version of this template is concise, specific, and easy to route, so it supports faster hiring without losing control of scope, level, or pay alignment.

Standards & compliance context

  • Keep the form aligned with data minimization by collecting only the role, process, and approval details needed to launch the requisition.
  • Avoid asking for protected personal data in candidate criteria or notes unless it is legally required and handled through the correct HR process.
  • If the form is used in a public-facing or shared workflow, make required fields and validation clear to support accessibility and reduce submission errors.
  • Use a documented approval trail for compensation and level decisions so the requisition record is easy to audit later.
  • If the template is adapted for accommodation-related hiring notes, keep those prompts separate and limited to what is needed for the hiring process.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Requisition Overview

This section sets the basic identity of the hire so the request can be routed, tracked, and approved without ambiguity.

  • Requisition title (required)

    Use the working title for the role as discussed in kickoff.

  • Request type (required)
  • Department (required)
  • Hiring manager (required)

    Enter the name of the manager responsible for the role.

  • Target start date

Role Scope

This section defines what the person will actually do and how success will be measured, which keeps sourcing aligned with the real need.

  • Role summary (required)

    Briefly describe the purpose of the role and the main outcomes expected.

  • Key responsibilities (required)

    List the core responsibilities the candidate will own.

  • Success metrics

    Describe how success will be measured in the first 6-12 months.

  • Team or function

Candidate Profile

This section separates essential qualifications from preferences so screening stays focused and defensible.

  • Must-have criteria (required)

    Select the non-negotiable qualifications or experience required for the role.

  • Nice-to-have criteria

    Select preferred qualifications that would strengthen a candidate profile.

  • Must-have details (required)

    Add specifics for each must-have criterion, including any minimum thresholds.

  • Nice-to-have details

    Explain which preferred qualifications matter most and why.

Compensation and Level

This section confirms the job level and pay range early, which prevents misalignment after candidates are already in process.

  • Job level (required)
  • Compensation range minimum (required)

    Enter the minimum base salary or hourly rate for this requisition.

  • Compensation range maximum (required)

    Enter the maximum base salary or hourly rate for this requisition.

  • Compensation type (required)
  • Bonus or equity notes

    Include any bonus, commission, or equity details relevant to the offer.

Interview Plan

This section documents the hiring steps up front so interviewers know the sequence, assessment method, and candidate experience expectations.

  • Interview stages (required)

    Add each interview stage in the order it will occur.

  • Assessment method
  • Candidate experience notes

    Add any guidance to keep the process consistent, accessible, and efficient.

Decision Makers and Approvals

This section identifies who can approve the requisition and who owns the interview process, which reduces delays and duplicate feedback.

  • Decision makers (required)

    List the people who will make or influence the final hiring decision.

  • Interview panel owner

    Name the person responsible for coordinating the interview panel.

  • Is approval required before posting? (required)
  • Approval notes

    Document any approval steps, constraints, or exceptions.

How to use this template

  1. Start by entering the requisition overview fields, including the role title, request type, department, hiring manager, and target start date.
  2. Define the role scope by writing a plain-language role summary, the key responsibilities, the success metrics, and the team or function the hire will support.
  3. List the must-have and nice-to-have candidate criteria separately, and use the notes fields to explain any tradeoffs or non-negotiable requirements.
  4. Set the compensation and level details by selecting the job level, entering the pay range, choosing the compensation type, and adding any bonus or equity notes.
  5. Map the interview plan with the stages, assessment method, and candidate experience notes so the panel knows what happens after the requisition is approved.
  6. Name the decision makers, assign the interview panel owner, confirm whether approval is required, and record any approval notes before routing the form.

Best practices

  • Write the role summary as an outcome statement, not a list of vague duties, so the recruiter can quickly understand what success looks like.
  • Keep must-have criteria limited to the few qualifications that are truly necessary, and move everything else into nice-to-have criteria.
  • Use numeric or range fields for compensation instead of free text so the pay band is easy to review and compare.
  • Choose interview stages that match the role level and function, and remove steps that do not change the hiring decision.
  • Add candidate experience notes for scheduling, assessment timing, and feedback turnaround so the process stays consistent across interviewers.
  • Name one interview panel owner who is responsible for coordination, feedback collection, and follow-up actions.
  • Use conditional logic to reveal extra fields only when they are relevant, which keeps the intake shorter and easier to complete.
  • Review the form for approval readiness before submission so missing decision makers or unclear compensation do not stall the requisition.

What this template typically catches

Issues teams running this template most often surface in practice:

The role summary is too vague to guide sourcing or screening.
Must-have criteria are overloaded with preferences that should be nice-to-have.
The compensation range is missing, outdated, or inconsistent with the job level.
Interview stages are listed without a clear owner or feedback process.
Decision makers are not named, which causes approval delays.
The target start date is unrealistic for the hiring market or internal review timeline.
Candidate experience notes are absent, so interviewers improvise different processes.

Common use cases

Tech Hiring Manager Opening a Software Engineer Requisition
A hiring manager and recruiter use the form to define the stack, level, interview loop, and compensation band before posting the role. This keeps the search focused on the actual skills needed for the team.
Healthcare Operations Backfill Requisition
An operations leader documents the responsibilities, shift expectations, and approval path for a backfill role. The intake helps confirm the replacement scope before the job is routed for review.
Manufacturing Supervisor Role Alignment
A plant manager and HR partner use the template to align on team coverage, success metrics, and interview stages for a frontline leadership hire. It reduces confusion about level and decision authority.
Professional Services Client-Facing Hire
A practice lead captures the candidate profile, assessment method, and panel owner for a consultant or account role. The form helps standardize the process across multiple stakeholders.

Frequently asked questions

What is this recruiting intake form used for?

This template is used to kick off a new requisition with a clear, shared brief before sourcing begins. It captures the role scope, candidate profile, compensation range, interview plan, and decision makers so recruiters do not have to chase details later. It is especially useful when multiple stakeholders need to agree on what is being hired and how the process will run.

When should we use this form in the hiring process?

Use it as soon as a hiring need is identified and before the job is posted or candidates are contacted. That timing helps catch mismatches in level, scope, or pay range early, when they are easiest to fix. It also creates a clean approval trail before the requisition moves into active recruiting.

Who should complete the intake and requisition kickoff form?

The hiring manager usually fills in the role details, and the recruiter or talent partner helps refine the criteria, compensation, and interview plan. HR or compensation partners may need to review level and pay range, and the interview panel owner should confirm the process. The best results come when one person owns completion and others review the final version.

What fields should be required versus optional?

Core fields like requisition title, department, hiring manager, role summary, must-have criteria, compensation range, and decision makers should usually be required. Notes fields can stay optional when they are only needed for context or nuance. Keeping optional fields truly optional supports data minimization and makes the form faster to complete.

How does this template help with compensation and level alignment?

The compensation and level section forces an early check that the job level, pay range, and any bonus or equity notes match the role scope. That reduces back-and-forth after sourcing starts and helps prevent candidate drop-off caused by unclear or inconsistent pay expectations. It also gives approvers a single place to review the proposed package.

Can we customize the interview stages for different roles?

Yes. The interview plan section is meant to be adapted by role family, seniority, or function, so a technical role can include an assessment while a people-facing role may use a presentation or case discussion. Conditional logic can keep the form shorter by showing extra fields only when a specific assessment method is selected.

How does this compare with using email or a shared doc for intake?

Email and shared docs often leave gaps, duplicate comments, and no clear approval trail. This form standardizes the fields that matter, makes required items visible, and creates a consistent record of the requisition kickoff. It is easier to review, easier to route, and less likely to miss a critical detail.

What integrations are useful with this template?

This form works well when connected to an ATS, HRIS, or approval workflow so the approved requisition can move directly into recruiting. It can also feed calendar or task tools for interview scheduling and panel coordination. If your process includes compensation review, routing the form to the right approver keeps the handoff clean.

What are the most common mistakes when using this form?

Common mistakes include vague role summaries, too many must-have criteria, an unrealistic compensation range, and interview stages that do not match the role. Another frequent issue is leaving decision makers undefined, which slows approvals and creates confusion during candidate feedback. The form works best when it is specific enough to guide action, not just capture intent.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
  • A shift handoff is the structured transition between the outgoing and incoming crew at the change of a shift. It covers what was done, what wasn't done, what...
Related guides

Ready to use this template?

Get started with MangoApps and use Recruiting Intake and Requisition Kickoff Form with your team — pricing built for small business.

Get Started