Mid-Year HR Review: Headcount, Performance, Pay

June is an awkward month for HR. The first half of the year is finished enough to judge, but the second half is still open enough to change. Most teams let the moment pass and rediscover in December that headcount drifted, half the performance conversations never happened, and salary decisions were made one exception at a time. A structured mid-year checkpoint fixes that, and it does not need to take a month.

Start with a headcount you can verify

Every mid-year review begins with a number that sounds simple and rarely is: how many people work here right now? Ask three departments and you will often get three answers. Finance counts the names on the last payroll run, department heads count the people they see every day, and recruitment counts the roles they were told to fill. The gaps between those figures are where budget quietly leaks.

The fix is to reconcile everything against one system of record rather than a spreadsheet that was last correct in March. ERPat's Human Resource module keeps employee profiles, schedules, attendance, leaves and holidays in the same place, so the roster you review is the same roster that attendance and leave are already measured against. That removes the most common argument in a mid-year review, which is whose list is right.

Work through the list deliberately. Confirm that separated employees are actually marked as separated, that everyone hired in the first half has a complete profile and an assigned schedule, and that roles you are still carrying in the budget are roles you still intend to fill.

Trace the movements behind the number

A headcount total hides as much as it reveals. Two departments can end June with identical numbers while one of them has quietly replaced half its team. What you want at mid-year is the movement history, not just the current org chart.

ERPat's Movements module keeps an audit trail of employee movements, so transfers, promotions and role changes are recorded as events rather than reconstructed from memory. Read that trail by department. A team that keeps exporting people to other parts of the business is telling you something about its manager, its workload or its pay band, and it is easier to act on that in June than after a resignation letter arrives.

The same module handles internal hiring through a self-service internal job portal governed by a configurable mobility policy. Mid-year is a sensible time to check whether that policy is doing what you intended — whether internal candidates are genuinely being considered before roles go external, and whether the tenure and approval rules you set in January still match how the business actually moves people.

Score performance while the evidence is fresh

Annual-only reviews have a well-known flaw: by the time managers sit down to write them, they are mostly remembering the last few weeks. A mid-year checkpoint captures the first half while the records, the projects and the reasons are all still recoverable.

ERPat's KPI Matrix builds performance scorecards that weight metrics by role, which matters more than it sounds. A collections officer, a support representative and a warehouse supervisor should not be measured against the same set of numbers, and giving each role its own weighting is what keeps a scorecard from becoming a popularity contest with a spreadsheet attached.

Scores then roll up into a team matrix, and that view is where the useful conversations start. One person below target is a coaching problem. An entire team below target is usually a process problem, a resourcing problem or a target that was set badly in January — and if you catch it in June, you still have two quarters to do something about it.

Connect performance to pay before budgets close

Pay decisions made in isolation are the ones that get relitigated. Someone gets an increase because they asked at the right moment, and by the following year nobody can explain the pattern to the people who did not ask. Tying compensation to the same scorecards everyone was measured on is what makes the outcome defensible.

The KPI Matrix turns scores into salary recommendations, so the conversation starts from a consistent basis rather than from whoever argued most persuasively. Treat the output as a proposal that a human being reviews, weighs against the budget and adjusts with context the system does not have — market conditions, retention risk, a role that changed mid-year.

Sweep the compliance basics while the year is still correctable

The second half of the year is a poor time to discover a records problem. Errors found in June can be spread across the remaining pay periods and corrected calmly. The same errors found in November collide with year-end reporting and 13th-month pay, when there is no slack left in anyone's schedule.

Keep this part unglamorous and complete. Confirm that every active employee has full and accurate government identifiers on file for SSS, PhilHealth and Pag-IBIG, that everyone hired in the first half is properly enrolled, and that separations were processed rather than simply removed from a list. Check that withholding details and tax status on record still match each employee's actual circumstances, since a change reported verbally in February helps nobody if it never reached the file.

Then look at the DOLE-facing records the Human Resource module already holds — schedules, attendance, leave balances and holiday handling. Those are the records you will be asked to produce, and mid-year is when correcting them is still cheap.

Turn the findings into an H2 plan

A review that ends in observations is a review that gets repeated next year with the same observations. Close the checkpoint by writing down decisions: which vacant roles you will fill and which you will hold, which performance conversations must happen this month, which pay adjustments are approved and when they take effect, and which policies need changing before the next hiring cycle.

Give every item an owner and a date. Then set the next checkpoint now, while the reasoning is still fresh, rather than waiting for December to force one.

A checkpoint worth keeping

Mid-year reviews earn their place by being ordinary. Verify the headcount, read the movements, score the first half honestly, settle pay on a consistent basis, and clean the compliance records while there is still time. Done once, it feels like extra work in a busy month. Done every June, it is the difference between planning the second half of the year and reacting to it.