Planning headcount with requisitions
Last updated: July 29, 2026
Requisitions add a headcount-approval step before a job can open. Turning them on is a setup decision worth making early, because it changes how roles start and how offers close.
This article explains what requisitions do, how they connect to jobs and offers, and helps you decide whether to turn them on.
Who can do this: Super Admin, Admin (the Manage requisitions permission is on by default for both)
Where to find it: Settings → Jobs & Requisitions → Requisitions (confirm exact label in-product)
What a requisition is
A requisition is one unit of approved headcount — a signed-off "yes, you may hire for this role" that exists before the job is created. It usually carries the role, department, office, work type, salary, and the recruiter and hiring manager attached to it.
It helps to separate three things that are easy to blur together:
Thing | What it represents |
|---|---|
Requisition | Approved headcount — the permission and budget to hire for a role. |
Job | The advertised role and its candidate pipeline. |
Offer | The proposal made to one specific candidate. |
A requisition is the approval to hire. A job is how you hire. An offer is who you hire.
How requisitions connect to jobs and offers
When requisitions are on, a role flows like this:
Hiring Managers raises a requisition for the role.
It goes through approval (if you set up an approval workflow).
Once approved, you open a job against it.
You interview and send an offer.
When the candidate accepts or is hired, the requisition is consumed — that seat is now filled.
If a requisition is approved for more than one hire, Kula tracks the remaining hires on the job, so you can see how many seats are still open against the approved headcount. Approvals for requisitions, jobs, and offers are unified, so they live in one place for your approvers.
This is the real link to offers: the requisition is what an accepted offer "spends." Without requisitions, an offer just marks a candidate hired. With requisitions on, an accepted offer also closes out a unit of approved headcount — which is what lets you track approved-vs-filled and stop over-hiring.
Should you turn them on?
Requisitions add governance, and governance is useful to some teams and overhead to others. Decide by how your hiring is approved today.
Turn requisitions on if… | You may not need them if… |
|---|---|
Headcount must be signed off (by finance or leadership) before recruiting starts. | Whoever owns hiring can just decide to hire and open a job. |
You track approved headcount against filled to protect a budget or plan. | You don't separate "approved headcount" from "the job posting." |
You use formal requisition IDs / numbers in your process. | You have no requisition numbering and don't need one. |
You hire several people against one approved role and need to track remaining seats. | You open one job per hire and count is never in question. |
You want requisition-level reporting — opened, filled, time-to-fill by department or type. | Job and offer reporting already tells you what you need. |
You're an enterprise or regulated team that needs an audit trail on who approved a role. | You're a small team where sign-off is a conversation, not a workflow. |
In between? You don't have to go all in. You can turn requisitions on but not mandate them on every job — use them for the roles that need sign-off and open the rest as plain jobs. Start light and tighten later.
What turning them on changes
A Requisitions area appears under Jobs & Requisitions.
You can optionally mandate a requisition when a job is created — or leave it optional.
You configure requisition fields (role, department, office, work type, salary, dates, plus custom fields) and, if you want sign-off, a requisition approval workflow. Approval rules can differ by department, office, work type, or requisition type.
The Manage requisitions permission stays with Admins and Super Admins by default.
You can turn requisitions on or off at the account level if you change your mind.
Good to know
You can enable requisitions without mandating them. Requiring one on every job is a separate toggle — turning the feature on doesn't force it everywhere.
A requisition is consumed automatically on offer acceptance or hire, so approved-vs-filled stays accurate without manual clean-up.
Confidential requisitions are visible only to permitted users, so a sensitive role can be kept off most people's view.
Requisitions, jobs, and offers share one approval system, so you're not setting up approvals three separate ways.
Need help? If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.