)
)
Skills based resource planning: summary & key takeaways
The definition: Skills based resource planning staffs work by proven skill level and real availability, then picks between qualified people on cost.
Must-haves first: Treat two or three minimum skill levels as a pass/fail filter before you compare anyone.
Cost rate decides: The lowest-cost qualified person protects the margin the work was priced at, worth $4,200 in our example.
Fresh data: Update ratings when real events happen, and keep at least 80% of profiles current.
Skills based resource planning staffs each project by proven capability as well as free hours. Finding someone who can do the job is the easy part; choosing between two qualified people is harder, and that choice sets what delivery costs.
At Teamwork.com, I lead an in-house team with complementary skills, plus partners where they fit, and who does what decides our speed and cost. This guide gives you a four-level proficiency scale, a three-step staffing rule, a worked example and triggers that keep the data fresh.
Why "who's free" is the wrong first question
Booking whoever has free hours is the fastest way to staff a project and the easiest way to get its cost wrong. If the first person the planner finds with time is your most senior, a mid-level task carries a senior cost. If they're too junior, rework doubles the hours, and either way margin moves before anyone logs an hour.
Good resource planning weighs availability against demand, and organizing resources with roles gets you closer. Still, a role describes a job, while skills describe what someone can deliver this month. Each approach misses something that costs you.
Approach
Skills close the fit gap, and the decision rule later in this guide closes the cost gap they leave open.
Build a skills inventory you can actually search
Closing that fit gap starts with skills data clean enough to filter on. If you're the person every project lead asks "who's good with data migrations?", that inventory lives in your head. Writing it down takes the weight off you, and the answer still exists while you're on vacation.
Keep the skill list short and separate from roles
Start with 20 to 40 skills that actually decide who gets staffed. Fewer, and every search returns everyone; more, and nobody keeps the ratings current.
Keep four things apart: roles, skills, tools and certifications. A role is the job someone holds, a skill is what they can do, and a certification is what an outside body has verified. Mix them, and a search for "Figma" returns "senior designer" and "AWS certified" too.
Give the list one owner, usually whoever runs resourcing, so "data migration" and "data migrations" never split your results. If you'd rather not start from a blank sheet, adapt a matrix from the Teamwork.com templates library. Then run your draft past three project leads and cut any skill none of them has ever staffed against.
Define what each proficiency level means
A rating only means something if two managers would give the same person the same number. Tie each level to one staffing question: can this person take the work on without a senior checking every step? Four levels also remove the comfortable middle score a five-point scale invites.
Level
Validate self-ratings against evidence
Self-ratings make a fine starting point and a poor final answer, because some people score generously and others modestly. Have everyone self-assess, then have their manager calibrate each rating against recent project history. Add one evidence rule: any rating of 3 or 4 needs a named project from the last 12 months where the person did that work. No example, and the rating sits at 2 until one turns up.
The staffing decision rule: filter, then compare
With ratings you can trust, every staffing request becomes one quick decision: which of the people who qualify should do this work? The rule runs in three steps, and the last one, comparing cost, is where most of the project's margin gets decided.
Step 1: Turn the request into must-haves and nice-to-haves
A must-have is a minimum level in a specific skill, such as level 3 in data migration, and everything else is a nice-to-have. Cap must-haves at two or three, because each extra one pushes you toward your most expensive people.
A good request fits on one line. Take a 120-hour data migration over six weeks: must-haves are data migration and SQL at level 3. Nice-to-haves are past work with this client and level 2 in the client's CRM.
Step 2: Filter out anyone who fails a must-have or lacks the hours
Next, remove anyone who misses a must-have, then anyone with less than 80% of the required hours free across the project window. For the 120-hour migration, that means at least 96 free hours over the six weeks. If nobody clears the bar, split the role between two qualified people instead of overbooking one.
Step 3: Compare the qualified people on fit, cost and growth
Among the people left, default to the lowest-cost person who meets every must-have. Nice-to-haves only break ties between people on similar cost rates.
Two exceptions earn a step up. Go to a level 4 only for a named risk a level 3 can't absorb, such as a new client or non-standard scope. Add one stretch assignment per project at most, someone a level below the must-have, and only with a level 3 or 4 reviewer on it.
Worked example: staffing a 120-hour data migration. Say the work is priced at a blended $150 an hour, so the fixed fee is $18,000. Candidate A is level 4 with a cost rate of $95 an hour, and Candidate B is level 3 at $60. Both clear the must-haves and have the hours, and all figures are illustrative.
| Candidate | Proficiency level | Cost rate ($ per hour) | Hours to deliver | Delivery cost ($) | Fixed fee ($) | Project margin ($) | Project margin (%) |
|---|---|---|---|---|---|---|---|
| A | 4 | 95 | 120 | 11,400 | 18,000 | 6,600 | 36.7 |
| B | 3 | 60 | 120 | 7,200 | 18,000 | 10,800 | 60.0 |
| B, needing 15% more hours | 3 | 60 | 138 | 8,280 | 18,000 | 9,720 | 54.0 |
Project margin is the fee left after delivery cost, as a share of the fee. Because the fee stays fixed whoever does the work, it's the number to compare:
Picking A costs $4,200 of margin on one project, for depth the request never asked for. Even if B needs 15% more hours, 138 in all, the margin is $9,720, or 54%, still well ahead of A. B would need 190 hours, about 58% more than planned, before A became the cheaper choice.
There's a capacity reason to hold back, too. My own team's plan keeps some room free for strategic work and the unexpected. Your scarcest specialist needs that room most: book your one level-4 person solid on level 3 work, and nobody's free when the risky project lands.
Keep the skills data current without a quarterly chase
The staffing rule is only as good as the ratings behind it, and ratings start to age the day a project ends. Tie updates to events that already happen in your week, rather than to calendar reminders:
Project close: the project lead confirms which skills each person used, and at what level.
Certification earned: the person adds it the week it lands, with the certificate as evidence.
First live use: a new skill goes in at level 1 or 2 the first time someone uses it on a project.
Review conversation: the manager checks each rating against the evidence rule.
Then track one number: the share of profiles updated in the last six months. Aim for 80% or more, and treat ratings on stale profiles as unverified when you run the filter.
SPI Research's 2026 Impact of AI on Professional Services report rates AI help with resource management 3.15 out of 5, and demand planning 1.98. Both sit near the bottom of its table because they rely on clean delivery and financial data. For you, automated matching inherits whatever state your skills data is in.
My team hands repetitive research, analysis and development work to AI, but judging whether the output is right stays with us. Treat a staffing shortlist the same way: someone reads it and pushes back before anyone gets booked. This walkthrough of the AI Smart Scheduler shows how a shortlist gets built from skills and availability.
When the rule says nobody fits: hire, train or partner
Once your data is current, the filter will sometimes return nobody, and that empty shortlist is useful. It names the exact skill and level you're short of, which beats a vague "we need more people".
When my team runs short on a skill, I look for a bottleneck before I look for a hire. Check your own: if level 3 people spend hours on level 2 work, you have a routing problem. A new hire would simply inherit it.
If the gap is real, how often it recurs and how soon you need it filled decide the response. To size a recurring gap in hours first, use the capacity-by-skill math in this guide to workforce capacity planning.
This approach also has a floor. Teams under about 25 people, or with largely interchangeable skills, rarely need a formal skills matrix. A role list and the planner's knowledge will do the job until staffing calls start going wrong.
How Teamwork.com runs skills based resource planning
Teamwork.com is the agentic PSA (professional services automation platform) that runs every step of the staffing rule on one plan. A PSA connects projects, resources and financials, so skills, availability and rates sit side by side when you choose someone. Its resource management tools cover the filter, the hours check and the shortlist.
Find everyone who clears the bar in one filter. Step 2 stalls when skills live in a spreadsheet nobody checks against the schedule. Skills records what each person can do beyond their Role, with one skill per level (Figma 1, Figma 2) since levels aren't built in. Filter the Planning tab by Role then Skill, including the Workload Planner, and you have a qualified list with workloads in view.
Plan the role before you pick the person. Naming someone too early locks in the wrong cost or ties up a person another project needs. In the Resource Scheduler, Placeholders hold the hours against a role, so demand is on the plan before anyone's name is. Once the filter and the 80% hours check are done, you transfer the work to the person you chose, with real availability behind the decision.
Get a shortlist without the calendar chase. Comparing qualified people slows to a crawl when you check every calendar by hand. The AI Smart Scheduler weighs availability, skills and timelines, suggests top candidates and prevents double bookings, and nothing transfers until a person confirms. With cost rates and billable rates by project, role and client set up too, the Step 3 numbers are ready.
Digital agency Invanity moved its planning into Teamwork.com, cutting project planning time by 50% and weekly workload management by 80%. With the filter, hours check and shortlist on one plan, the lowest-cost qualified person becomes the easy pick, and projects keep their priced margin.
)
)
)
)
)
)