managing-headcount-planning
Structures workforce planning with headcount budgeting, compensation modeling, and organizational analysis. Use when planning headcount, budgeting compensation, or modeling workforce scenarios.
Best use case
managing-headcount-planning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Structures workforce planning with headcount budgeting, compensation modeling, and organizational analysis. Use when planning headcount, budgeting compensation, or modeling workforce scenarios.
Teams using managing-headcount-planning should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/managing-headcount-planning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How managing-headcount-planning Compares
| Feature / Agent | managing-headcount-planning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Structures workforce planning with headcount budgeting, compensation modeling, and organizational analysis. Use when planning headcount, budgeting compensation, or modeling workforce scenarios.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Managing Headcount Planning Structures workforce planning with headcount budgeting, compensation modeling, and organizational analysis for FP&A, management accounting, and business intelligence teams. ## When To Use - Annual or quarterly headcount budgeting cycles - Scenario modeling for hiring plans (expansion, contraction, reorg) - Compensation benchmarking and total cost-of-employment analysis - Departmental workforce reviews or org structure assessments - Board or leadership presentations requiring workforce cost projections - M&A integration headcount planning or post-acquisition rationalization ## Inputs To Gather - **Current roster data**: Employee census with department, title, level, location, start date, and FTE status - **Compensation details**: Base salary, bonus targets, equity grants, commission structures per role - **Burden rate assumptions**: Benefits cost per employee, payroll taxes by jurisdiction [VERIFY], employer 401(k)/pension match, insurance premiums - **Hiring plan**: Open requisitions, target start dates, recruiting pipeline stage - **Attrition data**: Historical voluntary/involuntary turnover rates by department and level - **Budget constraints**: Total comp envelope, approved headcount cap, cost-center allocations - **Org chart**: Reporting structure, span-of-control metrics, leveling framework ## Workflow 1. **Build the current-state roster model** - Import employee census and map each record to cost center, department, and level - Attach fully loaded compensation: base + bonus + equity + benefits burden + payroll tax - Calculate current-state run-rate (annualized) and monthly cash outflow by department - Flag any missing data fields (e.g., no bonus target, missing location) with [VERIFY] 2. **Layer in planned changes** - Add approved new hires with assumed start dates, ramp periods, and target compensation - Model backfills for projected attrition using historical turnover rates - Apply planned promotions, merit increases, and equity refresh grants with effective dates - Account for known departures, RIFs, or contractor-to-FTE conversions 3. **Run scenario analysis** - **Base case**: Approved plan with current assumptions - **Upside case**: Accelerated hiring, lower attrition, or expanded roles - **Downside case**: Hiring freeze, elevated attrition, or budget reduction - For each scenario, produce monthly headcount and cost projections over the planning horizon (typically 4-8 quarters) - Calculate variance between scenarios to quantify decision impact 4. **Analyze organizational metrics** - Span of control by manager level (flag ratios below 3:1 or above 12:1) - Revenue per employee and cost per employee by business unit - Compensation mix analysis (base vs. variable vs. equity) against market benchmarks [VERIFY] - Location cost arbitrage opportunities (if multi-geography) 5. **Prepare the headcount plan deliverable** - Summary dashboard: total headcount, total cost, quarter-over-quarter delta - Department-level detail: HC by level, average comp, open req count, projected attrition - Scenario comparison: side-by-side cost and HC for each scenario with key assumptions noted - Sensitivity table: impact of +/- 10% attrition, +/- 5% comp inflation, or delayed start dates ## Output The deliverable is a **Headcount Plan Report** containing: - **Executive summary** with total HC, total fully loaded cost, and net change vs. prior period - **Roster-level detail** by cost center with per-employee loaded cost (anonymized if needed) - **Monthly projection table** showing HC and cost trajectory for the planning horizon - **Scenario matrix** with base/upside/downside cases and key variance drivers - **Org health metrics**: span of control, comp mix, revenue-per-head, attrition assumptions - **Open items log** listing all [VERIFY] flags, missing data, and pending leadership decisions ## Quality Checks - Confirm total loaded cost ties back to GL actuals for the most recent closed period within a 2% tolerance - Verify headcount totals reconcile to HRIS system of record — every FTE and contractor is accounted for - Ensure burden rate assumptions (benefits, taxes) reflect current plan year rates [VERIFY against benefits renewal and jurisdiction-specific payroll tax tables] - Validate attrition assumptions against trailing 12-month actuals; flag if projected rate deviates by more than 20% - Check that new hire compensation aligns with approved salary bands and leveling framework - Confirm scenario assumptions are internally consistent (e.g., a hiring freeze scenario should not include new-hire costs) - Review for double-counting: backfills should not overlap with existing employees still on roster - Ensure all currency, FTE basis (annualized vs. monthly), and date conventions are consistent throughout