Capacity Planning: Skills and credentials
Objective. Validate the skills and credential definitions used by the plan - check coverage and currency - and escalate model changes rather than re-engineering them.
Skills and credentials define what people are qualified to do, so the plan can size the right skills in the right intervals rather than a headcount lump. This is a configuration screen a CSM validates for coverage and currency.
See it in the demo
What this screen answers
A CSM opens this to answer 'does the plan know who can do what?' A capacity plan is only meaningful as skills-in-intervals; that depends on the skill and credential model being right. This screen holds those definitions, so skill-based coverage can be trusted.
The task (validate, do not re-engineer)
Scope to the customer and confirm the skills and credentials represented match how the customer actually segments work, and that credential currency (expiry, certification) is accounted for. Check coverage and obvious gaps. This is validation and escalation, not model design - structural changes go to the specialist. Describe it as 'the skills and credentials configured for this scope'.
How to read it
A skill defined here is a capability label, not a count of available skilled people, and a credential can lapse. The misread is assuming a skill exists in the model means enough people hold it, or that credentials are current. Read this for whether the model matches the customer's reality - the availability of skilled people is read in workforce/availability, and an expired credential removes someone from capacity.
Honest limits
This screen does not prove enough skilled, currently-credentialed people exist - only that the definitions do. It is admin configuration; do not re-engineer it live. Confirm with product how credential expiry feeds availability, and escalate changes to the skill model to the implementation specialist.
Interpretation check
A skill defined here is a capability label, not a count of qualified people - and credentials expire; validate coverage and currency, and escalate model changes rather than re-engineering.
In the field
An RCM operation where certain work needs a certification or payer-specific credential: if currency is not tracked, the plan can show skill coverage that an expired credential has quietly removed.
Practical task
Review skills and credentials for one scope and write one line on whether the model matches the customer's work segmentation, plus a note on how credential expiry is handled - escalating any structural change.
Self-check
The model lists a skill, so is the plan covered for it?
No. A definition is not a count of available, currently-credentialed people. Coverage by skill is read in workforce/availability; an expired credential removes someone from capacity.
What is the CSM validating on this screen?
That skills and credentials match how the customer segments work, and that currency/expiry is handled - coverage and correctness, not designing the model.
Why do credentials matter to a capacity requirement?
A lapsed credential removes a person from effective skilled capacity even though they are still on headcount, so credential currency changes real skill coverage.
Verified vs demo. Screen is live in the demo at /#/skills; exact controls and figures are SME-validation-pending.