A request for more people is the beginning of a workforce discussion. A useful plan explains what those people will do, which skills the work requires and how their contribution will be supported. Without that detail, a team can add capacity while leaving its most difficult bottleneck unresolved.
Start by describing the work in terms a manager and a prospective colleague can both understand. Include the expected outcomes, recurring tasks, decisions, tools and working conditions. This creates a practical foundation for choosing a staffing approach and assessing whether it remains suitable as demand changes.
Key points
- Separate the amount of work from the skills and coverage it requires.
- Define useful outcomes and decision boundaries before finalizing a role.
- Include onboarding, supervision and review in the capacity plan.
Describe demand before choosing a solution
List the activities creating pressure on the team. Distinguish recurring work from a temporary backlog, seasonal demand or a discrete project. Note whether the pressure appears throughout the week or in particular windows. A role designed for steady demand may be a poor match for work that arrives in short, unpredictable bursts.
Use the evidence already available in the operation: queue volumes, project milestones, coverage gaps and the time experienced colleagues spend on exceptions. Treat estimates as estimates. If the team does not have reliable measurements, observe a representative sample of work and record the assumptions behind the plan rather than presenting a precise but unsupported forecast.
Separate skills, judgment and availability
Capacity describes how much work a team can take on. Capability describes whether it can perform that work to the required standard. Coverage describes when the people need to be available. Consider all three explicitly. More available hours will not solve a task that requires experience nobody on the shift has.
Build the skills brief around actual decisions. Which tasks follow a documented process? Which need specialist knowledge? Which require approval from a manager or another function? This helps distinguish essential qualifications from preferences and gives interviewers a more relevant basis for discussion.
Include communication requirements and working hours in the brief. A colleague who depends on another team's decisions needs enough overlap to obtain them. Where overlap is limited, define what can progress independently and what must wait for a handoff.
Write a brief people can use
A clear role brief connects responsibilities to observable outcomes. Instead of asking someone to support operations generally, explain the queue or process they will own, the information they will maintain and the decisions they can make. State how quality will be reviewed and where difficult cases should go.
Be equally clear about what the role does not control. A support colleague may communicate a delivery update while another team manages the shipment. Setting that boundary helps the manager assess performance fairly and gives the new colleague a practical route for obtaining answers.
- Purpose: what work needs to be completed?
- Requirements: which skills and working hours are essential?
- Authority: what can the role decide or approve?
- Support: who provides context, training and escalation?
Match the staffing approach to the need
Compare the duration and predictability of the work with the available staffing options. A short project, a specialist assignment and an ongoing operating role have different requirements. Discuss continuity, availability, supervision and knowledge transfer alongside the immediate need for capacity.
Document the assumptions that would cause the plan to change. The end of a project, a sustained change in volume or a new service requirement may call for a different arrangement. Contractual terms, employment obligations and local requirements need appropriate review; a workforce plan should identify these decisions without trying to settle them through a generic template.
Budget attention for onboarding
New capacity depends on access, context and feedback. Plan who will explain the process, arrange approved access, review early work and answer questions. Include this time in the existing team's workload. An onboarding plan that assumes unlimited supervision can create pressure precisely where the team already has too little capacity.
Start with a bounded set of tasks and clear examples of acceptable work. Provide a current process guide and a named contact for exceptions. Expand responsibility as the colleague demonstrates understanding. Keep access proportional to the role and remove temporary access when the assignment or responsibility changes.
Review whether the original problem improved
After the role is operating, return to the problem that prompted it. Review quality, unresolved work, coverage and the team's ability to handle exceptions. A completed hiring process is not the same as a resolved operating constraint. Ask the colleague doing the work which instructions are unclear and where they still wait for information.
Keep the review specific. If the constraint is missing information, improve the handoff. If it is a skills gap, adjust training or the brief. If demand has changed, revisit coverage. The workforce plan should remain a living explanation of the work, the people needed to perform it and the support that makes their contribution effective.
Explore how Empire connects people, technology and operating support.
Our approach