Headcount planning tool
Every job starts with an approval
Headcount planning in Skailer: managers request a position, approvers sign off by policy, and the approved request pre-fills a new job.
Roles get approved in chats nobody can find
A lead asks for a hire in Slack, finance wants the salary range by email, and the job opens at another level. Nobody knows which seats are still open.
Request a position with everything approvers need
A manager clicks Request new position and fills in one form. The job profile sets role and level from Career architecture; division, department and location come from your structure. Add the date, salary range and files.
Route each request to the approvers your policy names
Position requests have their own category in Approval policies, the editor you already use for time off and offers. Name approvers by rule, from direct manager to department manager, and run steps in sequence or in parallel.
Turn an approved request into a job without retyping
Once a request is approved, Create job and link opens a new job pre-filled with title, description, department, job profile, location and salary range. Link to existing job moves the request to Hiring, then to Hired.
Approve roles on the structure you already run
Requests use your job profiles, departments, locations and approval policies. The hiring plan decides which roles get opened; the ATS fills them.
How does headcount planning work in Skailer?
Headcount planning in Skailer runs through the hiring plan, the approval step of Recruiting. Managers submit position requests with a job profile, department, location, hiring date and salary range. Approvers named by your policy decide. An approved request pre-fills a new job or links to an open one and runs to Hired. The hiring plan decides which roles get opened; the ATS fills them. It does not forecast headcount or model scenarios.
What the model shows for a 500-person company
HIRING REQUESTS
JOB APPROVAL
JOB CREATION
Where approved headcount lives in each kind of tool
Teams usually approve new roles in one of 3 places: spreadsheets and email, workforce planning tools, or a hiring plan inside the HR platform.
| Capability | Spreadsheets & email | Workforce planning tools | Skailer |
|---|---|---|---|
| Request format | Free text in a thread | Varies by vendor | One form with profile, date and range |
| Who approves | Whoever is copied | The plan's reviewer chain | Approvers resolved from the org chart |
| Approval rules | Agreed per thread | Set up for planning | Same policies as time off and offers |
| Opening the job | Retyped by the recruiter | Usually handed to another tool | A job pre-filled from the request |
| Tracking to hire | Manual | Varies by vendor | Statuses run to Hired |
| Best fit | A few hires a year | Finance-led planning cycles | Mid-size teams, hiring and HR in one |
How the hiring plan works in Skailer
Hiring plan in Skailer: common questions
Is the Skailer hiring plan a headcount planning tool?
Yes, for the approval side of headcount planning. Managers request each position with a job profile, department, date and salary range, approvers decide by policy, and an approved request pre-fills a new job. Forecasts and scenarios are not included.
Who approves a position request?
Does approving a request open the job automatically?
Is the hiring plan a workforce planning tool?
Can the AI assistant approve position requests?
What does Skailer hiring plan software track after approval?
Know which approved roles are still open
Book a 30-minute demo: we set up a Position request policy on your structure and run one request.