Start with a catalog, not a text box
If skills are typed as free text, you end up with five spellings of the same competence and no way to ask 'who can do this job?'. A catalog fixes that: a fixed list of skill codes and labels that reflects the work your business actually sells.
Keep it small and real. Ten skills that map to your service types are worth more than sixty aspirational ones nobody maintains.
Record proficiency and dates, not just a tick
- Proficiency: can they perform it alone, or only supervised?
- Date obtained: useful for renewal planning and for proving history.
- Expiry date: the field that turns a record into an early warning.
- Notes: the context a future dispatcher will need and never ask for.
Connect skills to the work
The point of the catalog is the link to service types. When a service type declares the skills it requires, the question 'who can be sent?' becomes a computed answer rather than a memory test performed at 6am by whoever is dispatching.
This is also where preferred skills matter. Required skills gate the assignment; preferred skills rank the shortlist. Confusing the two either blocks work unnecessarily or sends the wrong person confidently.
What tracking can and cannot do
A tracking system can hold a credential, remind you before it lapses, and stop you from confidently assigning someone whose credential has already expired. That is genuinely valuable and it prevents real incidents.
It cannot confirm the credential is authentic, renew it for you, or make your business compliant with any particular labour or licensing regime. Those remain human responsibilities, and any vendor implying otherwise is selling you a false floor.