Headcount vs. Budget Tracker: Stop Quietly Drifting Over Plan

The problem this kills

Every org sets an approved headcount budget — so many roles, at so much cost, per department, for the year. And then reality happens. A manager opens a backfill. A net-new req sneaks in "just this once." A planned hire slips a quarter, or two hires land in the same month. By the time finance reconciles it, three departments are quietly over plan and nobody saw it coming, because the truth lives in a fragile spreadsheet that one HR analyst rebuilds by hand every period.

That spreadsheet is where headcount discipline goes to die. The plan tab and the roster tab drift apart. Open reqs get double-counted because the same role shows up in the ATS and in a manager's email. Backfills get treated as net-new. Contractor costs are in one month and out the next. Partial-year hires are costed as if they started in January. And the one control that actually matters — someone signing off before a department goes over its approved plan — happens in a hallway conversation that leaves no record.

Headcount is usually the single biggest line in the budget. Deciding whether to add to it deserves to be a real, governed application — not a workbook held together with hope.

What you'll build

A simple internal web app for HR ops, finance partners, and department leaders. You import your approved headcount/budget plan by department, your current roster (filled positions and their cost), and your open reqs and planned hires. The tool reconciles everything to a consistent point in time and computes, per department: filled headcount and cost, open reqs, planned hires, projected total spend, and the variance against the approved plan.

Any hiring action that would push a department over its approved headcount or budget gets flagged and routed for approval — finance or HR reviews it, approves or denies with a reason, and only an approved action can proceed. The plan-vs-actual reconciliation is reviewed each period, so you always know where every department stands. The whole thing handles the real-world mess: backfills vs. net-new, partial-year proration of cost, and your contractor inclusion rules.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how your departments and cost centers are named, how your plan and roster exports are actually shaped, whether you track headcount, fully-loaded cost, or both, how you treat backfills and contractors, your fiscal calendar and proration rules, and the exact rule that decides when something is "over plan." It reflects a short tailored spec back to you and gets your thumbs-up before it builds anything, so the tracker matches how your org budgets — not a generic template.

From there it walks the agent through the data model, the three imports with duplicate guards, the per-department reconciliation engine, the over-plan detection, the finance/HR approval gate, the period reconciliation review, and the headcount-vs-budget CSV export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path that uses Google Sheet / CSV imports from your HRIS and ATS and produces a clean CSV export — so you can build and run the whole thing this weekend regardless of what HR system you're on.

The governance it includes (this is the point)

Headcount is a controlled spend, so the controls aren't optional. The plan builds in login so only your HR and finance team can use it, row-level security so you only ever see your own organization's headcount data, a complete audit trail of who requested, approved, or denied each over-plan action and when, a hard human-approval gate so no over-plan hire is treated as approved until finance or HR signs off with a reason, and duplicate guards keyed on department + position/req ID so the same role can't be counted twice across the roster and the ATS.

Who it's for

HR operations, finance business partners, and department leaders who reconcile headcount and budget every period and are tired of trusting a brittle spreadsheet to catch over-plan drift. If you can describe how your departments are named, how you cost a hire, and who has to approve an over-plan req, you can build this.

You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have your first department-by-department variance on screen before the weekend's out.