Workforce Planning · Headcount Planning
Headcount Planning
What is workforce planning?
- Derive roles and timing from the business plan
- Cross-check with two or more estimation methods
- Total labor cost and attrition must be factored in for the budget to hold
Once workforce planning is in place, the first thing to change is how hiring requests arrive. Requests that team leads used to file in a rush after someone left now come off the headcount list that executives approved at the start of the year, in sequence. HR no longer has to re-argue 'why do we need this position?' each time and can open postings on the approved timeline. The trade-off is a more intense discussion at the start of the year, because which positions to give up has to be decided right there.
Splitting the estimate into separate components makes the discussion much cleaner. Replacement hires that fill vacancies and net additions from business growth are very different things. You can forecast replacement hiring as long as the attrition rate is right, but net additions shift whenever the business plan does. If you put the two on one line, the whole line gets cut in the budget review. Lead times vary by role too. Office roles take 45-60 days from posting to start date, while experienced developers and team leads often take more than 90, so a senior hire needed in April has to start the search by January at the latest. Labor cost also comes out wrong if you simply multiply headcount by salary. Add the employer share of Korea’s four social insurances, severance provisions, and employee benefits, and the actual cost is 1.2-1.3 times the contract salary.
The most common mistake in practice is treating a headcount freeze as cost savings. When permanent positions are blocked, business units turn to outsourcing, freelancers, and agency staff, and that spending is booked to service fees, not labor cost. Headcount is down but total cost is up, and it only shows in the books six months later. Using a single company-wide attrition rate is another common error. If customer support and field roles exceed 20% while management is around 5%, applying a flat 10% average leaves the field chronically short-staffed while headquarters has open slots it never fills. An attrition rate that isn’t split by job family is closer to number-juggling than planning. This is also why the refresh cycle matters more than precision. If you don’t revisit the plan every quarter, the one made at the start of the year is obsolete by March.
Kyungtae KimHR expert · Organizational culture and HR strategy consultant
Hwi KimCEO of HRDIST & talent development systems consultantOnce the concept of human resource planning was established, it became the practice of linking organizational strategy to workforce supply and demand. More recently, combined with people analytics, it has grown into attrition forecasting and scenario-based workforce planning.
Consider a hypothetical case. Company A builds logistics SaaS and has 180 employees and KRW 32 billion (≈ US$23,941,300) in annual revenue. Of last year’s 31 hiring requests, 22 were urgent ones marked 'needed within this month', and open developer roles stayed vacant for an average of 4.2 months. This year, in September, it drafted next year’s workforce plan first.
- The HR head first shared next year’s KRW 42 billion (≈ US$31,423,000) revenue target and the expected number of new shipper accounts with all 7 division heads, then asked them to 'write down the added work as headcount.' The first round came back at 47 people.
- The Operations division’s request for 12 people was recalculated at 320 cases per person per month and dropped to 7. The division head also admitted, 'I wrote it based on peak season.'
- Attrition was applied separately by job family. Applying the past three years’ rates of 9% for development and 24% for customer operations produced 19 replacement hires and 16 net additions, which showed up as two distinct categories.
- When the CFO converted total cost to 1.28 times contracted annual salary, the 35-person plan exceeded the budget by more than KRW 300 million (≈ US$224,500). Four net-new positions were pushed to the second half, and two were redirected to an automation project.
- Working back from a 90-day lead time, the team opened postings for 3 senior developers in the second week of January. The HR head put it bluntly: 'Starting in March is already too late.'
- That year, urgent hiring requests fell from 22 to 6, and the vacancy period for developer roles dropped from an average of 4.2 months to 1.8 months. Spending against the labor cost budget also came in at 99%, down from 103%.