Roster and Resource Pool

A resource pool (also called a roster) is the firm’s complete catalog of billable resources available for project assignment, including full-time employees, part-time staff, and approved subcontractors and contractors, each with a defined role, skill set, and availability profile. It is the supply side of resource planning and capacity planning.

What a resource pool contains

Each record in the resource pool describes one assignable resource:

• Name and role title
• Seniority level (analyst, consultant, manager, principal, partner)
• Skills and certifications (technology stacks, industry expertise, methodologies)
• Cost rate (internal) and bill rate (external)
• Current availability and confirmed allocations
• Location and timezone, for client and project matching

Why structure matters

An unstructured roster is a contacts list. A structured resource pool is a matchable database. The difference is visible when a delivery manager needs to find an available senior cloud architect in a specific timezone within 48 hours. A structured pool returns a filtered shortlist. A contacts list requires phone calls and guesswork.

The pool versus the project team

The resource pool is the firm’s complete supply of available people. A project team is the subset of the pool allocated to a specific engagement. Members of the pool move in and out of project teams as engagements start and end. Resources not currently assigned to a project are on the bench.

Subcontractors in the pool

Many firms maintain a pre-approved subcontractor bench alongside their employee roster. Including subcontractors in the pool with their own availability and rates makes capacity planning more accurate and shortens the time to fill a resource gap when demand spikes. Excluding them creates a blind spot in staffing and allocation decisions.

Keeping the pool current

Resource pools degrade quickly without active maintenance. People change roles, acquire new certifications, and leave the firm. Rates change. Allocations update weekly. A resource pool is only useful if the data in it reflects reality, which requires a clear owner and a regular update cadence. The resource manager typically owns this process. Stale data produces inaccurate utilization rate calculations and leads to double-booking, which creates delivery risk downstream.