Headcount Plan
Plan the seats each position should have and what they should cost, then see at a glance how many are filled, how many are being recruited, and where the money differs from the budget.
Open Human Resources → Positions and choose Headcount plan from the Related menu. A plan is kept per year — this year and next are offered in the Period filter — and you can filter by department and status or search by position, grade or department. The mobile app shows the plan read-only.
Building The Plan
- Under Add a plan line, choose a position, optionally a department, the planned headcount and the budgeted cost per head per month, in your base currency.
- Edit planned numbers and costs directly in the table and choose Save plan. A line can be removed from its row.
- Positions people hold that have no plan line appear as Not in plan, so nobody falls out of the totals unseen.
Reading The Table
| Column | Meaning |
|---|---|
| Planned | The seats you plan for the position. |
| Filled | Employees in the position who are active, on probation or suspended. |
| In recruitment | Unfilled openings on draft, open and on-hold vacancies. |
| Variance | On plan, a number under, or a number over. |
| Budget / month | Planned headcount × budgeted cost per head. |
| Actual / month | Each person's monthly basic plus allowances and benefits from their active contract, in your base currency only. People without an active contract in that currency are not costed, and the page says how many. |
Requisitioning The Gap
Where a position is under plan, Requisition opens a new vacancy already filled in with the position, its department and the number of openings still needed. Finish it in Recruitment; once saved it counts as In recruitment.
Permissions
- View employees — see the plan.
- Manage headcount plan — add, change and remove plan lines.
- Manage recruitment — use the Requisition button.
Related
- Employee Management — positions, departments and contracts.
- Expiring Soon
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.