Use when the user asks whether staffing covers demand across the business, names a hiring target, or hands over workload and team numbers: company-wide headcount planning with scenarios, not support shift scheduling.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when the user asks whether staffing covers demand, names a hiring target, or hands over workload and team numbers. This is the business-wide plan — demand per function, required heads, the hiring plan, and the scenarios. Interval-level contact forecasting, shift schedules, and intra-day moves for a support desk belong to the workforce planning skill, not here.
Past demand by function and period, current heads and roles, shrinkage drivers (time off, training, attrition), open requisitions, and the forecast horizon.
No demand history means a judgment forecast marked INFERENCE with the data need named. No shrinkage figure means you plan at 20% and say so.
Forecast from history, never from headcount totals alone. Name the trend, the seasonality, and the known events — launches, renewals, holidays. Include pipeline-weighted demand, tentative work, and time off. State the horizon and the miss band plainly.
The 12-to-16-week horizon is what drives the hire, contract, or reskill call.
Required heads = base workload heads / (1 - shrinkage/100), where shrinkage covers time off, training, and attrition.
Show the math in one block so the capacity owner can check it. Call out the convention when overtime or contractors fill the gap instead of heads.
Heads on hand, open requisitions with start dates, and the shortfall per function and month. Name coverage gaps, never hide them.
Base and high demand. Each carries hiring targets, start-by dates, cost per hire beyond salary (benefits, onboarding time, tools, and time to full productivity), and what breaks if hires slip a month.
Before opening any role externally, check whether an existing team member can step in. Hold a per-function skills inventory beside the plan: current skills against required, the top two gaps, and whether each gap closes by hire, train, or contractor. Name every single-point-of-failure role.
Forecast against actual demand, hires landed against plan, utilization, and the one planning fix for next month. Log the forecast and the hires made.
Never present a guessed headcount as modeled. Never move requisition dates or headcount budgets without the capacity owner's yes.
Save the capacity plan under capacity, dated, with its scenarios.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.