A manager says "we need another person" in a meeting. Three weeks later, nobody remembers the grade, the start date or who signed it off. A requisition puts the ask in writing first. I use one link per request and keep every row.
Before the form is open
I decide who may send a request and what "approved budget" means in my company. I also write down the pay grid, so managers pick a range and do not guess.
While it is open
Managers send one request per role. The form asks for the title, the reason, how many people, the contract type, the start date, the skills and the business case, with one box for approved budget.
A manager's AI can handle this. It might ask "What is the job title?" Then "Is this a new role or a replacement?" Then "When should they start?" It shows the answers and sends them only after a yes. See agent-fillable forms.
After it closes
I download the CSV, one row per role. Rows without the budget box ticked go to finance first. The rest go to whoever writes the job post.
When an offer is ready, a job offer response form collects the candidate's answer. Hiring for a kitchen or a floor team? A restaurant job application collects the candidates. More tools are in HR and recruiting forms.
Questions
Can one request cover several identical roles?
Yes. The number of people takes more than one, so five identical roles can be one row. Use separate requests when roles differ in grade, place or skills.
Does this replace my applicant tracking system?
No. It collects the internal ask. Once a request is approved, you open the role in whatever tool you use to post jobs and track candidates.
How do I know a request has budget?
Filter the CSV on `budget_confirmed`. The manager sets that tick box. I still check it with finance before posting, because the form cannot verify it.