Most project staffing failures don't happen in a hiring meeting. They happen the week before, in a Slack thread where someone asks "who's free?" and three people guess. By the time the resource manager catches up, the wrong person is already booked.
This guide walks through the project staffing process step by step, compares the four common staffing models, gives you a 9-field staffing plan template you can copy into a sheet right now, and shows how to run staffing intake as a form so nothing falls through the thread again.
Quick answer
Project staffing is the work of deciding which people, with which skills, for which hours, will deliver a specific project.
Run it as a 7-step process (capacity intake, scope-to-skill mapping, forecasting, role assignment, kickoff, mid-project rebalance, post-project review), pick a model (in-house, outsourced, hybrid, or staff augmentation), document everyone in a 9-field staffing plan, and route every request through a form instead of a Slack thread.
The project staffing process: 7 steps
Run this in order. Skipping a step does not save time; it moves the cost to the back of the project.
-
Capacity intake
Before scoping anyone in, document who is already booked and at what percentage. Pull current allocations from your PM tool or use a staffing request form to collect availability from team leads in one pass.
-
Scope-to-skill mapping
Break the project into work packages. For each package, list the skill required, the seniority needed, and the estimated hours. Skill, not job title. "React with hooks experience" beats "frontend engineer."
-
Resource forecasting
Add up hours per skill per week across the project length. This is the demand curve. Compare it against the supply curve from step 1. The gaps are what you actually need to staff.
-
Role assignment
Match named people to work packages, starting with the highest-risk skill first. Document allocation as a percentage (50%, 75%, 100%), not as a binary "assigned."
-
Kickoff and onboarding
Share the staffing plan with the team in week one. Every person should see their role, allocation, start, end, and dependencies. Most onboarding failures are documentation failures, not introduction failures.
-
Mid-project rebalance
Re-check actual vs planned allocation at 30% and 70% of the timeline. If utilization is over 90% on any individual, rebalance before they burn out. If it's under 50%, free that person for the next intake.
-
Post-project review
Within two weeks of project close, log what actually happened: estimated hours vs actual, skill gaps you hit, who delivered above plan. This data is the input to your next forecast.
Project staffing plan template: 9 fields
Copy these nine columns into a sheet, or use the project intake form template to collect them as structured submissions instead of free-text rows.
| Field | What goes in it | Example |
|---|---|---|
| Role | Function on the project | Backend engineer |
| Department or team | Where they sit org-wise | Platform |
| Type | Full-time, part-time, contract | Contract |
| Headcount | Number of people in this role | 2 |
| Skills required | Specific, not generic | Node.js, PostgreSQL, AWS Lambda |
| Start date | When allocation begins | 2026-07-01 |
| End date | When allocation ends | 2026-10-15 |
| Allocation | Percentage of working hours | 75% |
| Status | Filled, open, at risk | Open |
- Allocation is a percentage, not a yes/no. "75%" tells the next PM what's left.
- Status updates weekly, not at milestones. By milestone, the slip is already real.
- Skills column lists the tool or technique, not the seniority label. "React Server Components" not "senior frontend."
Project staffing models compared
Two filters decide between them: how core the work is to your IP, and how stable the demand is. Core plus stable picks in-house. Non-core plus spiky picks staff augmentation. Most companies end up hybrid.
| Model | Best for | Cost band | Ramp time | Control | Exit cost |
|---|---|---|---|---|---|
| In-house | Core IP work, recurring projects | Highest fixed | Slow (hire cycle) | Highest | Severance |
| Outsourced | Defined scope, non-core work | Medium fixed | Medium | Lowest | Contract end |
| Hybrid | Mixed core and commodity work | Medium variable | Fast for variable | Medium | Low for contractors |
| Staff augmentation | Skill gaps, surge capacity | Highest variable | Fastest | Medium-high | Lowest |
Capture project staffing requests on a form that routes itself
Conditional logic for role and seniority, notifications to the right hiring manager, a clean audit trail per submission.
Start free on FormesterFree forever plan•No credit card•Setup in 2 minutes
Start with a staffing form, not a meeting
Three free templates that turn project staffing intake into a clean queue. Clone any of them and ship in 10 minutes.
Project intake form
Collect new project requests with scope, timeline, and skill needs in one structured submission.
Open template FormesterProject resource engagement form
Request specific people or skills mid-project, with conditional fields based on urgency.
Open template FormesterEmployee availability form
Pulse current availability from your team in one pass at the start of each planning cycle.
Open template
