download dots

👥 Work Out How Many People You Need

Build the calculator you keep rebuilding in a spreadsheet, then put it on a link anyone can use. These prompts turn a formula into a working app: clean inputs, a result people trust, a saved record of every calculation, and an assistant that explains what the number means. Useful on your own desk, and useful in public as the page that brings people to you.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Work Out How Many People You Need

Copy

I roster by habit and we are either overstaffed or drowning. Build me a staffing calculator. Let me enter expected demand by period, such as customers, orders, calls or jobs per hour, and the average service time each one takes. Keep target service levels and the maximum acceptable wait as editable settings. Work out the number of people required in each period, then add cover for breaks, and an absence allowance percentage. Show the requirement against my planned roster so gaps and overstaffing are both visible, and highlight the peak periods rather than the average. Let me record what actually happened so my service times can be corrected from real data. Add an AI agent that reviews the last month and tells me plainly which periods I am consistently short in and what that is costing in service. Automate a scheduled weekly comparison of planned against required staffing before the rota is published. Two logins: a manager who builds rotas, and an owner who sets service levels.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Work Out How Many People You Need

Turn demand and service time into a staffing requirement per period, with break and absence cover and peak analysis.

// the spark catches · intelligence awakens · the answer unfolds

Rosters are usually built from habit. This works out the number from demand and service time, then shows what happens when someone is off.

What's Included

  • Demand by period rather than one average for the whole day.
  • Service time per unit of work which is what actually sets the number.
  • Cover for absence and breaks included rather than discovered.
  • An assistant that finds the periods you are consistently short.

How To Use

  1. Model demand by hour or by period. A daily average hides every problem.
  2. Include breaks and absence cover. The theoretical number never works.
  3. Check the peak, not the mean. The peak is what customers experience.
  4. Compare planned against actual and correct your service times.

Turn the number into a rota with time tracking prompts, and cost it with the employee cost calculator.

Related from the blog