AgencyOps
Resource planning guide for agencies - capacity, allocation, and forecasts
Resource planning for agencies is how you match people, skills, and calendar capacity to committed delivery, pipeline probability, and leave without relying on heroic PM memory. Done well, it connects sales promises, project milestones, and bench risk in one forward view so founders see overload before deadlines slip and margin erodes.
What agency resource planning is (and is not)
It is forward-looking staffing and skills matching tied to delivery dates, not a retrospective-only timesheet report. It is not a generic HR headcount exercise unless you deliberately fold hiring and contractor ramps into the same model your PMs use weekly.
Strong plans answer three questions simultaneously: Who is overloaded? Which milestones lack a named owner on the calendar? Where will we be short a craft before procurement can onboard a contractor?
Strategic vs. tactical horizons (run both)
Tactical (4–8 weeks)
Focus on named allocations, dependency chains, client meetings, and QA windows. This is where you catch double bookings, unrealistic parallel work, and vacation collisions that break sprint promises.
Strategic (quarterly)
Model hiring, contractor pools, training investments, and major account ramps. Tie pipeline stages to probability-weighted demand so sales does not hand delivery a cliff of assumed wins on the same Monday.
Data inputs that make resource plans defensible
| Input | Why it matters | Common failure |
|---|---|---|
| Project schedule & milestones | Drives when specific roles must be free, not just monthly FTE math | Plans that ignore dependencies and QA buffers |
| Approved time off & holidays | Shrinks real capacity before you promise dates | Surprise PTO discovered after client commitments |
| Weighted pipeline | Signals soft demand before SOW signature | Treating every late-stage deal as 100% booked |
| Billable targets by role | Balances revenue pressure with sustainable load | Uniform utilization quotas that ignore craft reality |
| Contractor & partner lead times | Prevents fake staffing on paper | Assuming vendors can start next-day indefinitely |
Conflict resolution: priority rules leadership must publish
When two projects claim the same senior designer the same week, ad hoc politics decide or the louder client wins. Replace that with a short priority stack: contractual delivery dates, penalty clauses, revenue at risk, strategic accounts, then discretionary internal work. Document it where PMs can cite it in five seconds.
- Escalate cross-project conflicts in a single forum with finance and delivery leads present.
- Prefer shifting internal pet projects before slipping fee-earning milestones.
- Log decisions so retrospectives show patterns (chronic under-staffing on a craft, not one-off heroics).
Skills-based planning vs. role titles (use both)
Job titles hide reality: two “Senior PMs” may differ on technical fluency or regulated-industry experience. Maintain a lightweight skills matrix aligned to how you sell work (brand systems, paid media ops, enterprise integrations). Planning by skill reduces the bait-and-switch where sales promises a profile you do not actually staff.
Cadence that keeps the plan honest
- Weekly tactical sync (30–45 minutes): confirm next two sprint staffing, flag slip risks, update contractor needs.
- Bi-weekly sales–delivery bridge: re-weight pipeline, kill zombie opportunities that steal planning air.
- Monthly executive scan: bench cost, overtime trend, hiring triggers, and training backlog vs. demand.
Common resource planning mistakes agencies make
- Planning in FTE buckets instead of calendar-constrained weeks.
- Hiding bench in generic internal codes instead of confronting sales pacing.
- Ignoring partial allocations across four simultaneous small accounts.
- No single source of truth Excel, PSA, and Notion disagree every Monday.
- Soft-booking pipeline at 100% for every verbal yes, then blaming delivery.
FAQ: resource planning for agencies and consultancies
- What is the difference between resource planning and project scheduling?
- Scheduling sequences tasks and dependencies in time; resource planning ensures the right humans (and contractors) exist on those dates with enough slack for quality and review cycles not just lines on a Gantt chart.
- Which tool should own the staffing truth?
- The system PMs and finance both open weekly. If only ops maintains a shadow spreadsheet, your plan is already stale. Prefer an agency operations workspace where projects, leave, and capacity views share the same client and engagement records.
- How do you plan for uncertain pipeline?
- Use stage-weighted hours and date ranges, reserve a small flex pool for late-breaking wins, and agree when soft bookings convert to hard commitments. Kill or downgrade deals that stall past defined gates so they stop consuming phantom capacity.
- How granular should allocations be?
- Week-level for most creative and consulting teams; day-level during crunch windows or regulated go-lives. Avoid fake hour-precision that your culture will not maintain.
- Who owns the resource plan?
- A delivery operations lead or PMO facilitator usually runs the process; practice leads own craft supply; executives own priority rules and hiring triggers. Sales owns forecast hygiene.