Workforce Budgeting

The Budget Lines screen is the module's home. New budget line opens a dialog where you name the position, place it in a department, enter the budgeted headcount and the current headcount, tag the line with a period — a year such as 2026, or whatever period label your planning cycle uses — and set its status to open or closed. The position is the only field the form insists on, so a quick sketch of next year's plan can be captured first and filled in later.

Saved lines appear in a table with columns for position, department, budgeted, current, period and status, listed newest first. Status renders as a coloured badge, and any field left blank shows a quiet dash rather than a hole, so a half-complete plan still reads cleanly.

Because budgeted and current headcount sit in adjacent columns on every row, the register doubles as a gap report. Scanning the table tells you which positions are fully staffed, which are under plan and which lines have quietly gone over — no export, pivot table or formula required.

The current figure is a recorded number, which keeps the register honest about what it is: a statement of your plan and your position against it, maintained by the people who own it. When a hire lands or someone leaves, open the line's Edit dialog, adjust the number and save — the edit form opens pre-filled from the current row, so an update is a one-field change, not a re-entry.

When a gap needs filling, the Requisitions screen records the ask. A requisition names the position and department, states the headcount requested, and carries a status of pending, approved, fulfilled or rejected — so the register tells you not just what was requested but where each request stands.

Requisitions live on their own rail item beside Budget Lines, in the same table-and-dialog pattern: add through New requisition, edit in place, delete with confirmation. Approved and fulfilled render as green badges and pending as a highlighted one, so the state of the hiring queue is readable at a glance.

The Settings screen holds the module's configuration in two tabs. General Setting captures your budgeting policy as three choices: the Budget Period — Annual, Half-Yearly or Quarterly — whether requisitions require approval, and whether over-budget requisitions should be blocked. Each is a dropdown saved with one click, with the stored values reloaded whenever the screen opens.

The Cost Centers tab maintains a named list of cost centres: type a name, add it to the table, remove entries you no longer need. Settings are persisted to your organisation's shared configuration store, the same mechanism the other workspace modules use, so they survive across sessions and apply organisation-wide.

Workforce Budgeting is a tenant-scope module: it is offered to organisation roles — owner, admin, HR — and never to platform administrators browsing across tenants. On top of that coarse tier sits the Role Templates matrix, where the EmployeeBudgeting module carries nine individual form keys, including Budgeting, Planning, Budget Approvals, Budget Duration, Open Position, Position Title and Employee Budget Settings.

Untick every key in the module for a role template and that role loses the module entirely — the navigation entry disappears and the route guard bounces direct links, because both read the same rule from the same source. Conversely, an employee granted one of the module's HR-side forms gains its route, so a planning responsibility can be delegated without handing over an admin role.