Monthly Headcount Report Template: Reconcile Movements, Vacancies, and Budget
Use a six-tab monthly headcount report to reconcile employee movements, count approved vacancies, and explain staffing and cost variances. Follow the worked example and spreadsheet formulas.

What should a monthly headcount report include?
A monthly headcount report needs opening and closing employee counts, hires, departures, internal transfers, approved positions, vacancies, and workforce costs against budget. Reconcile employee movements first. Then explain what the staffing changes mean for hiring, coverage, and spending instead of leaving readers to interpret the totals themselves.
Use the workbook below to close the month, not to forecast hiring. The worked example covers September 2026, with costs in USD. Every employee count, date, identifier, and currency amount in the example is illustrative.
| Report field | September result | Control or comparison |
|---|---|---|
| Opening headcount | 100 | Agrees to August closing snapshot |
| Hires | 8 | Employment starts during September |
| Departures | 5 | Employment exits effective during September |
| Internal transfers | 3 | Zero company-wide net change |
| Closing headcount | 103 | 100 + 8 - 5 |
| Approved positions / vacancies | 110 / 7 | 110 authorized seats minus 103 occupied |
| Monthly workforce cost | $660,000 | $680,000 budget; $20,000 below budget |
How should you structure the workbook and define its fields?
Build six linked tabs: Assumptions, Employees, Movements, Positions, Costs, and Summary. Use stable employee, position, and requisition identifiers to match records. Names are not reliable keys. Store dated transactions separately from current employee records, and set the reporting cutoff before anyone starts calculating totals.
Create the tabs with these exact names and use the required fields below as column headers. Add local fields only when someone will maintain them. An extra column without an owner becomes another source of conflicting answers.
| Tab | One row per | Required fields |
|---|---|---|
| Assumptions | Reporting period | ReportDate, PriorReportDate, Currency, InclusionRule, ExitDateRule, Version |
| Employees | Employee | EmployeeID, PositionID, Department, CostCenter, Location, Category, StartDate, ExitEffectiveDate |
| Movements | Effective-dated event | MovementID, EmployeeID, EventType, EffectiveDate, FromDepartment, ToDepartment |
| Positions | Authorized seat | PositionID, RequisitionID, ApprovalStatus, RoleType, HiringStatus, TargetStartDate, BudgetOwner, OccupantID |
| Costs | Cost center and month | Period, CostCenter, BudgetHeadcount, ActualCost, BudgetCost, ForecastCost |
| Summary | Department and month | OpeningHC, Hires, Departures, TransfersIn, TransfersOut, ClosingHC, ApprovedPositions, Vacancies, Commentary |
Define the keys before entering data
- EmployeeID identifies a person; PositionID identifies an authorized seat. Neither should change because someone's name or job title changes.
- Department identifies the organizational team. CostCenter identifies where finance records expense. Location identifies the reporting site. Keep these fields separate.
- Category records the employment grouping used by your inclusion policy, such as permanent, fixed-term, or contractor. Use the same categories throughout the workbook.
- StartDate is the first employed day. ExitEffectiveDate is the first day no longer employed, not the final working day. That distinction controls the closing count.
- RequisitionID links a recruiting request to a position. ApprovalStatus records whether the seat is authorized; HiringStatus records how recruiting is progressing.
- RoleType separates replacement from net-new hiring. BudgetOwner names the person accountable for funding; TargetStartDate records when the team needs the capacity.
Which reporting rules keep the totals consistent?
Agree on the reporting date, employee inclusion policy, and effective-date rule before counting people. Write down how contractors, part-time employees, leave, and transfers are treated. Keep employee headcount separate from other capacity measures. For costs, compare the month's expense with that same month's budget, not an annual salary total.
- Cutoff: use August 31 for opening and September 30 for closing. Include an employee when StartDate is on or before the snapshot date and ExitEffectiveDate is blank or later.
- Population: this example counts each employee once, including part-time employees and employees on leave. Contractors are excluded and reported separately.
- Dates: if the final employed day is September 30, the exit takes effect October 1. Keep that employee in September closing headcount.
- Costs: compare September expense with September budget. Store annual salary, monthly expense, and forecast in distinct fields. Document accruals and allocations so finance can reproduce the comparison.
Leave capacity calculations outside this employee roll-forward. Use a separate headcount versus FTE reconciliation when HR and finance need to compare people with full-time equivalent capacity.
How do opening and closing headcount reconcile?
Start with opening headcount, add hires and transfers in, then subtract departures and transfers out. Internal transfers change department totals but cancel at company level. Check the calculated closing balance against an independently counted employee snapshot. A formula that balances internally is not enough; it must match the people actually included at month-end.
Closing = Opening + Hires - Departures + Transfers in - Transfers out. Apply the same equation to each department and the company total.
| Department | Opening | Hires | Departures | Net transfers | Closing |
|---|---|---|---|---|---|
| Operations | 60 | 5 | 3 | +1 | 63 |
| Commercial | 40 | 3 | 2 | -1 | 40 |
| Company | 100 | 8 | 5 | 0 | 103 |
Operations receives two transfers and sends one; Commercial receives one and sends two. Enter each of the three events once in Movements, with its source and destination. Derive incoming and outgoing department counts from those records rather than maintaining separate transfer lists.
Calculate the balance, then check it independently
If the table starts in column A, enter =B2+C2-D2+E2 in F2 and copy downward. Calculate the company closing total with =SUM(F2:F3). The formula total and the independent employee snapshot count must both equal 103.
Never edit opening balances just to make the report balance. Check missing events, duplicate employee records, backdated exits, and transfers incorrectly entered as hires. A departmental move is not company growth.
How should approved vacancies be reported?
Maintain an approved-position register apart from employee records. Each authorized seat needs an occupant or vacancy, a replacement or net-new classification, hiring status, target start date, and budget owner. Only unoccupied, approved seats count as vacancies. Exclude filled positions and seats whose authorization has been withdrawn.
Use Open, In Progress, Filled, and On Hold as this workbook's hiring statuses. An On Hold seat remains a vacancy while its authorization is valid. A manager's plan to hire does not belong in the approved total until the role is authorized.
| Position ID | Department | Role type | Hiring status | Target start | Budget owner |
|---|---|---|---|---|---|
| OPS-064 | Operations | Replacement | In Progress | 2026-10-12 | Operations director |
| OPS-065 | Operations | Net-new | On Hold | 2026-09-14 | Operations director |
| COM-041 | Commercial | Replacement | Open | 2026-10-19 | Commercial director |
| COM-040 | Commercial | Replacement | Filled | 2026-09-21 | Commercial director |
The complete example contains 68 approved Operations seats and 42 Commercial seats. Their employee counts are 63 and 40, leaving five and two vacancies respectively. This calculation assumes one employee per occupied seat, no overfilled positions, and matching reporting populations.
Leave overdue target dates visible. Put the revised date and operational consequence in commentary instead of silently replacing the original commitment. Carry the same position identifiers into showing vacant positions in an org chart so the staffing discussion and workbook refer to the same seats.
How do headcount and cost variances differ?
Calculate each variance as actual minus budget, but interpret headcount and costs separately. Negative headcount variance means fewer employees than planned. Negative cost variance means spending below budget. Neither tells you whether the operation has enough coverage. Label the financial direction, then explain the staffing consequence.
| Measure | Actual | Budget | Actual minus budget | Interpretation |
|---|---|---|---|---|
| Closing headcount | 103 | 110 | -7 | Seven below budget |
| Operations cost | $420,000 | $440,000 | -$20,000 | Favorable financially |
| Commercial cost | $240,000 | $240,000 | $0 | On budget |
| Total workforce cost | $660,000 | $680,000 | -$20,000 | Favorable financially |
Budgeted closing headcount equals approved positions in this example only. Keep separate fields for both: a seat's authorization and its funded start date need not match. Preserve the approved budget when expectations change. Show the newer forecast alongside it rather than erasing the original comparison.
Explain the cost base, not just the salary
Aleph's “Headcount planning templates and tips for 2026” describes cost as salary × (1 + benefits rate + tax rate) + bonus + overhead and other costs. Enter rates as decimals and put every component on the same period basis. When payroll supplies actual employer costs, do not add estimated benefits and tax percentages again.
Group explanations into timing, compensation, workforce mix, or approved-position changes. Delayed expense is not automatically a recurring saving. Seven vacancies alone do not explain the $20,000 underspend; reconcile midmonth starts, pay levels, accruals, and temporary coverage before attributing the difference to hiring delays.
Below budget is a financial direction, not proof that staffing is right.
How do HR and finance close the report each month?
Refresh the records, validate identifiers and dates, reconcile employee movements, review approved vacancies, and compare expense with budget. Give the sign-offs clear owners: HR confirms people and positions; finance confirms costs and funding. Publish the dated report only when both have resolved exceptions or documented what remains open.
- Refresh sources. Save dated employee, recruiting, position-approval, and finance records. Keep the previous approved close intact as the opening reference.
- Validate keys and dates. Flag duplicate employee IDs, missing position IDs, impossible date sequences, and multiple occupants assigned to the same seat.
- Reconcile movements. Match opening headcount to the prior close, check both sides of transfers, and investigate every difference against the closing employee snapshot.
- Review vacancies. Check authorization, hiring status, target dates, and budget ownership. Assign action on delayed hires through the agreed recruiting process.
- Compare costs. Reconcile expense with finance, calculate actual-minus-budget variances, and separate timing differences from recurring changes.
- Approve and publish. HR signs off on people; finance signs off on costs. Issue corrections in a new version. Never silently change the published file.
Assign responsibility for delayed roles through the recruiting SLA, your agreement on recruiting responsibilities and response times. Write executive commentary in a fixed order: result, cause, consequence, action, owner, next review.
Keep the signed monthly pack separate from operational dashboards and KPI reporting. Live views support daily decisions. The dated report preserves the month-end position that HR and finance agreed to, even as staffing changes afterward.
How Cogniver helps connect headcount to hiring and approvals
Cogniver gives HR and operations one organizational structure to work from. Every other module reads the same drag-and-drop org chart, and incoming hires appear as reserved seats before their first day. During staffing reviews, teams can distinguish current employees from incoming placements instead of treating both as today's headcount.
The recruiting suite takes hiring from job post through signed offer and day-one onboarding in one portal. Click-to-sign offers produce a signed PDF and reserve a placement seat on the chart. Where an assigned signatory is required, that person reviews the recruitment history and signs the exact offer text before it reaches the candidate.
Admin and HR dashboards bring live headcount, the recruiting funnel, out-today, and pending approvals into one view. Each workflow also has an isolated AI agent that answers questions, routes requests, and chases approvers. Report owners get current staffing context while the agents handle approval follow-ups that would otherwise sit with HR and operations.
Frequently asked questions
How many employees do we need in each department?
Start with approved positions and compare them with occupied seats. Operations has 63 employees against 68 approved positions in the example. Whether 68 is still the right target requires a separate review of workload, service commitments, and planned changes. The report exposes the gap; it does not settle the staffing decision.
When should we hire them?
Give each approved vacancy a target start date tied to the operational need, then check recruiting progress against it at month-end. Keep overdue dates visible. Record revised timing, interim coverage, and the accountable owner rather than moving the original target without explanation.
How much will they cost, and how are we funding them?
Record each approved seat's budget owner and cost center. Estimate salary, benefits, employer taxes, bonus, and applicable overhead on a consistent basis. Identify the approved funding source, and keep monthly expense comparisons separate from annual compensation amounts.
Do we have the budget?
Check position authorization and funding for the intended start date. An empty approved seat does not establish affordability. Finance should compare expected cost with the approved budget and show forecast changes separately. Revised expectations must not erase the original budget comparison.


