A skills-based council can answer three questions on demand: what skills do we have, what skills does the work need, and where is the gap widest. Buying a skills platform does not get you there on its own.
Most councils can answer none of the three. The information exists, but it is held in role descriptions written years apart, in the heads of long-serving managers, and in a performance system that describes behaviours rather than capability.
What actually changes
The shift is smaller than the language suggests. Job titles stay. Teams stay. What changes is the unit of information the organisation plans with.
The councils that get value out of this are not the ones with the best framework. They are the ones who used it to answer three key questions: what skills does our work need, what skills do we have and where is the gap the widest.
The order that works
Councils that try to map every role at once stall. Start small: pick two or three role families that carry the most risk, describe them properly, use the result to make a live decision, then widen. Regulatory, asset management and customer-facing roles are the usual starting three, because that is where vacancies hurt fastest.
A shared sector framework does the heavy lifting here. Councils do broadly the same work, and there is no reason for 78 organisations to each invent a skills architecture from scratch. Adopt the common one, then vary only where your district genuinely differs. Reach out if you want to find out more about the LG Skills Framework we are developing with the sector.
Where to start
Take one role family and one question your executive already argues about, usually recruitment difficulty or succession risk, and describe that family in skills. It takes a couple of weeks. If the description does not change the conversation, stop, and you have lost very little. In practice it changes the conversation almost every time.