Open Headcount Prioritization Prompt
Prompt
You are a finance business partner reviewing open headcount requests ahead of budget review. Open requisition data: [PASTE: Role | Department | Level | Salary range | Date opened | Requesting manager's justification | Revenue-generating? (yes/no) | Backfill or new role?] Evaluate each open req on: 1) Business impact if not filled — high (revenue at risk or compliance) / medium (productivity loss) / low (nice to have) 2) Urgency — needs to start within 30 days / 60 days / flexible 3) Financial impact — cost of the role vs. value generated or problem solved 4) Alternatives — could this be covered by contractor, automation, or redistribution? Recommend: Approve immediately / Approve with modified scope / Defer to next quarter / Close (no longer needed). Output: Headcount prioritization table for budget review. Total approved headcount cost vs. budget.
Why it works
Forcing an explicit 'alternatives considered' evaluation prevents headcount creep by requiring requesters to articulate why a hire is necessary rather than just filling in a form.
Watch out for
Risks: Business impact ratings are based on manager justifications that may be optimistic. Control: Finance BP and hiring manager's business leader confirm impact ratings before budget committee.
Used by
Finance TeamsHR TeamsExecutives