A requisition pins down the decisions a job ad usually hides:
- Role and seniority — what the work actually is, not the aspirational title.
- Openings — one hire or three, which changes the sourcing plan entirely.
- Terms — employment type, location or remote, the compensation envelope.
- The reason — growth, backfill, or a signed engagement that needs staffing.
In an IT services company the last line is the important one: hiring is usually tied to a project that starts on a date. A requisition raised against that date is a capacity decision as much as an HR one — hire too early and the person lands on the bench, too late and delivery starts short-staffed. That is why the requisition deserves an explicit approval moment: someone confirms the demand is real and funded before the pipeline spins up.
The requisition then becomes the job's source of truth — the requirements written here become the screening bar and the interview criteria, which is what keeps the funnel evaluating what was actually requested.
In Helia, the job record carries the requisition facts — openings count, department, employment type, location and remote flag, must-have and nice-to-have requirements — moves through draft → open → paused → filled or closed, and reaches the public careers page only when explicitly published; the same requirements later seed the interview scorecards.