How to set staffing requirements for a work schedule

A useful staffing requirement answers four questions: what work needs coverage, when it needs coverage, how many people are required, and what makes a person qualified to count. Keep those facts separate from the names of employees. Requirements describe the need; the schedule assigns people to meet it.

Use the same time interval for the requirement and the coverage check. If demand changes every 15 minutes, a daily or shift-wide average will hide the exact periods that need action.

Start at the level where the staffing decision has meaning. Use a role when the main question is who must be present. Add an activity when the role covers different work during the day. Add a workstream when one activity has separate queues, languages, locations, customers, or demand sources.

Do not enter the same requirement at every level. Let the work below roll up into the parent where possible. Add a parent-level value only when the complete role or activity needs more coverage than its children explain.

Enter the number of people needed for each period where the requirement stays constant. A support queue can need two people from 08:30 to 09:00, seven from 09:00 to 10:00, and twelve during the midday peak. The time blocks should follow real operating changes, not arbitrary calendar boundaries.

Headcount and qualified coverage are different facts. Add a skill only when a person must hold it to perform the work. Include a minimum level when proficiency matters, such as French at B2, a current clinical qualification, or authorization for a machine or system.

A skill filters who can satisfy a requirement. It does not add more people by itself. If ten agents are required and three of those ten must speak French, model the French need as qualified coverage inside the same operating demand, not as thirteen people.

Use manual requirements for fixed posts, opening hours, known routines, regulatory cover, and planned work that a manager can state directly. Copy a proven day or pattern when the same need repeats, then adjust the exceptions.

Use forecast requirements when demand changes from historical volume, queue arrivals, orders, tickets, visits, or another demand signal. Keep the forecast assumptions visible and apply manual adjustments only when a known event is not already represented in the data.

Compare the schedule with the requirement at the same interval and scope. Required is the target. Scheduled is the qualified capacity assigned to that work. Net is scheduled minus required. A negative result is short, zero is covered, and a positive result is over.

Keep shortages and surplus periods separate. Three extra people at 15:00 do not repair a three-person shortage at 11:00. Daily FTE-hour totals are useful summaries, but the interval view tells the planner when to act.

Review changes before they become the live staffing plan. Keep comments and history with the requirement so another planner can understand why a value changed. Copy a day when the operating pattern repeats, but keep forecast-driven work connected to its source instead of copying stale output.

After the day ends, compare required, scheduled, and actual results. Update the requirement when the operating need was wrong. Update the schedule process when the requirement was right but the team did not meet it.