Staffing Plan Template: Headcount by Quarter + Example
9 min read ยท 2026-11-15
A staffing plan template lists the roles your team needs over the next 12 months. For each role it gives the department, contract type, headcount, skills, start date, budget and approval status. Fill it in this order: business goals, current team, gap, cost, then a hiring calendar by quarter that leadership can approve.
A blank sheet with column names is only the start. This guide gives you the full plan as a roadmap. You build and approve it in 4 weeks, then review it every quarter. It includes a filled staffing plan example for a 12 person team adding 4 people over 4 quarters, a worked countdown for timing each hire, and a one page order for presenting it to your director or finance team.
The roadmap at a glance
Goal: Get a 12 month staffing plan approved, with headcount by quarter, full cost per role and clear owners. Duration: 4 weeks to build and approve, then a review every quarter for 12 months.
Align with the business plan (Week 1)
Tie every future role to a goal leadership has already agreed on.
- Collect next year's targets: revenue, product launches, projects, new markets, service levels.
- Ask each department head what work will grow, shrink or start.
- Note fixed dates such as launches, contract starts or peak seasons.
- Write one sentence per goal on the work it creates.
Milestone: A list of goals, each linked to the work it adds, signed off by your manager.
Map the current team (Week 1 to 2)
Know exactly what capacity you have before asking for more.
- List every person by role, department, contract type and main skills.
- Flag known departures, parental leave, retirements and contract end dates.
- Note who is already overloaded and on which work.
- Record open roles that are approved but not filled yet.
Milestone: A current headcount list that HR and every department head agree with.
Run the gap analysis (Week 2)
Compare the work you need with the people you have, role by role.
- For each goal, estimate the people and skills needed to deliver it.
- Subtract current capacity to find the gap in headcount and skills.
- For each gap, choose an answer: hire, promote, train, reassign or contract.
- Rank gaps by impact on the goals if they stay open.
Milestone: A ranked gap list with one chosen answer per gap.
Cost each role (Week 3)
Turn every planned hire into a full cost, not only a salary.
- Get the salary band for each role from HR or finance.
- Add benefits, recruiting cost, equipment and software, and training.
- Spread each cost over the months the person will actually be on payroll.
- Add the totals per quarter and for the full year.
Milestone: A cost line per role and a yearly total that finance has checked.
Build the hiring calendar by quarter (Week 3)
Place each hire so the person is productive when the work starts.
- Start from the date the work begins, then count back.
- Subtract ramp up time, notice period and recruiting time.
- Set the date the job opening must be posted.
- Spread openings so no recruiter or hiring manager gets overloaded.
Milestone: A quarter by quarter calendar with a posting date and a start date for every role.
Present and get approval (Week 4)
Get a clear yes, no or change on each role.
- Write the one page summary described below.
- Review the cost with finance before the leadership meeting.
- Present, record the decision for each role and update the status.
- Share the approved plan with recruiters and hiring managers.
Milestone: Every role marked approved, deferred or rejected, with the name of the person who decided.
Review every quarter (Months 1 to 12)
Keep the plan accurate as the business changes.
- Compare hires made with hires planned.
- Re-check goals, departures and budget.
- Move, add or cancel roles, and log why.
- Report changes to leadership in the same one page format.
Milestone: A dated version of the plan after each quarterly review.
Staffing plan vs hiring plan vs recruitment plan
People often mix up these terms, and it causes confusion in meetings. A staffing plan covers your whole workforce over a period: who you have, who you need, and how you close the gap. Hiring is only one answer. Promotion, training, reassignment and contractors count too.
A hiring plan template is the part of the staffing plan that covers new people only: which roles open, when, and at what cost. A recruitment plan goes one level lower. It covers how you find and select those people: sourcing channels, job ads, interview steps. A staffing matrix is a different tool. It is a grid of people against skills or shifts, used to check day to day coverage, not to plan headcount for the year.
- Staffing plan: whole team, 12 months, all ways to close gaps.
- Hiring plan: new roles only, dates and budget.
- Recruitment plan: how each opening gets filled.
- Staffing matrix: who covers which skill or shift right now.
What to include in a staffing plan template
A staffing plan template forecasts and organizes the people a team needs over a set period. A basic version records the position, the department or team, the contract type, the number of people, the skills required, the start and end dates, the budget and the status of each role. The fields below cover the same ground. They add what leadership asks about first: the business reason for the role, the quarter it lands in, the posting date and the person who owns it.
Keep one row per role, not one row per person. If you need three support agents, write one row with a headcount of 3 and a start date for each.
- Role title and level
- Department or team
- Contract type: full-time, part-time, contractor or freelance
- Headcount for this role
- Key skills required
- Business reason: the goal this role serves
- Target start date and quarter
- End date, for fixed-term and contract roles
- Posting date: the start date minus recruiting time and notice period
- Full cost for the year
- Status: proposed, approved, open, filled or deferred
- Owner: the hiring manager
Staffing plan example: 12 person team, 4 hires over 4 quarters
Here is a filled example for a product and engineering team of 12 at a software company. Next year's goals are a mobile app launch in Q3 and a move to larger customers who need faster support. One engineer is known to be leaving in Q2.
Headcount by quarter: 13 at the end of Q1, 14 in Q2 after one departure and two arrivals (one of them a contractor), 14 in Q3, and 15 in Q4. The plan adds 4 people and loses 1, so the team ends the year 3 people larger, with one of them on a fixed term.
Notice what the example does not do: it does not hire everyone in Q1. Each start date follows the work the role serves.
- Row 1. Senior backend engineer, Engineering, full-time, headcount 1. Skills: APIs, databases. Reason: replace the Q2 departure before the handover ends. Start: Q1. Posting: early Q1. Status: approved.
- Row 2. Mobile engineer, Engineering, full-time, headcount 1. Skills: iOS and Android. Reason: Q3 app launch. Start: Q2, so the person has a full quarter before launch. Posting: late Q1. Status: proposed.
- Row 3. Product designer, Product, contractor for 6 months, headcount 1. Skills: mobile design. Reason: design peak for the app launch. Start: Q2. End: 6 months later. Status: proposed, with a review at month 5 on whether to make the role permanent.
- Row 4. Technical support specialist, Customer Support, full-time, headcount 1. Skills: product knowledge, written support. Reason: larger customers after launch. Start: Q4. Posting: Q3. Status: proposed.
How to cost a role
A salary alone underestimates every hire. Ask finance for your company's own benefits and employer tax figure, and apply it to each role. Then add the other costs that land in year one.
- Base salary for the months on payroll, not the full year
- Benefits and employer taxes
- Recruiting cost: agency fees, job boards, interview time
- Equipment and software licences
- Training and onboarding time
How to time each hire
Timing matters as much as cost. Work back from the day you need the person fully productive. Use your own recruiting data for each step. The countdown below uses example durations, not a standard.
Change any duration and the posting date moves with it. A senior role with a longer notice period pushes the posting into late Q4 of the year before. That is why a plan that sets start dates on the day the work begins always runs late.
- Target: fully productive on day one of Q3, which is week 27 of the year.
- Ramp up, example 8 weeks: the person starts in week 19, early Q2.
- Notice period, example 4 weeks: the offer is accepted around week 15.
- Recruiting from posting to accepted offer, example 9 weeks: the opening goes live around week 6.
- Result: with these assumptions, the opening is posted in the first half of Q1, about 21 weeks before the work starts.
Examples by context
The same template works for very different teams. What changes is the reason behind each row and how much of the gap you close with contractors.
Other moments call for a staffing plan too: fast growth, a reorganization, a large new project, a key person moving into a new role, succession for critical positions, and the yearly budget cycle.
- Startup: few rows, each tied to a funding milestone or a revenue target. Contractors cover specialist work until the need is permanent.
- Product or IT team: roles tied to launches, migrations and on-call coverage. Departures and handover time drive the calendar.
- Agency: headcount follows signed and likely client work. Freelancers absorb peaks, and permanent hires follow repeat clients.
- Seasonal business: part-time and fixed-term rows with start dates before the peak, training time, and planned end dates.
How to present the plan on one page
Leadership and finance rarely read a full spreadsheet. Give them one page, in the order below, and attach the detailed sheet.
Build a budget review step in before any job is advertised, so finance has already seen the cost before the meeting decides. A second check after interviews, on the selected candidate and the final offer, keeps the actual hires in line with the approved plan.
- Need: the two or three goals that create the work.
- Gap: the capacity missing today, by team.
- Calendar: headcount at the end of each quarter, with start dates.
- Cost: total for the year and by quarter, from the role cost lines.
- Risks: what slips if a role is not approved or arrives late.
- Decision requested: the exact list of roles to approve now, and those to review later.
Common mistakes to avoid
- Listing roles with no business reason, so leadership cuts them first. Link every row to a named goal.
- Budgeting salary only, which makes the plan look cheaper than it is. Add benefits, recruiting, equipment and training.
- Setting start dates on the day the work begins. Count back ramp up, notice and recruiting time.
- Forgetting known departures and leave. Add them as negative headcount in the right quarter.
- Opening every role in Q1 and overloading the hiring managers. Spread postings across the year.
- Treating the plan as final after approval. Review it every quarter and keep dated versions.
Frequently asked questions
What is the difference between a staffing plan and a hiring plan?
A staffing plan covers the whole team and every way to close a gap, including training, promotion, reassignment and contractors. A hiring plan covers only the new roles you will recruit, with their dates and budget. Most companies build the hiring plan as one section of the staffing plan.
How often should a staffing plan be updated?
Review it every quarter, and straight away after a major change such as a lost client, a new funding round or an unplanned departure. Keep each version with its date and the reason for each change, so leadership can see how the plan moved.
Should I hire full-time or use freelancers?
Choose full-time when the work is ongoing and central to your goals. Use contractors or freelancers for peaks, short projects or skills you need for a few months. A fixed-term contractor with a review date, as in the example above, lets you test the need before you commit.
How far ahead should a staffing plan go?
Twelve months is the usual horizon, split by quarter, because it matches most budget cycles. Teams with long hiring times or large projects often add a lighter view of the following year to flag roles that need early approval.