A requirement to show that staff had completed mandatory training became the starting point for something wider. It turned into an early attempt to make the skills and training of a whole NHS Trust visible.

The requirement

The immediate need was practical. A central training database of mandatory training had been identified as a requirement for CNST, the Clinical Negligence Scheme for Trusts, and the Trust needed one place to show who had been trained.

Behind that sat bigger questions. Who had been trained, and in what? Where did skills and expertise sit across the organisation? Which staff needed training or updating? How could managers see their own teams' records, and how could the training information that already existed be brought together?

Seeing beyond the presenting problem

A log would have met the requirement. The more useful question was what the organisation needed to know about itself.

As Lead Nurse Practice Education, I led the project. Georgina Dumler, Systems Support Team Leader, gave technical support, and Gavin Gault from IT developed the system. Rona Davis, a Learning Curve Advisor, took on managing the database once it was running. It was a team effort, and the technical skill in it was theirs.

We did not start from scratch. We modified a database the Corporate Nursing Team were already using and added course management functions. At launch, staff could see when courses were running, how many places were available and where they were held, and the system sat on the intranet under education and training. Managers could see what training their staff had attended and access their own records. There were functions for printing certificates and attendance lists, and for emailing groups.

The newsletter also reported what we hoped would follow. We hoped to capture training data from local departments and specialist teaching, so the Trust could demonstrate investment made trust-wide and have, in the words I used then, “a clearer corporate view on the wealth of skills and knowledge in the organisation”. We hoped it would help staff have equitable access to training and development. We planned to link it with staff rostering systems so that skills could be identified at any one time. Text message confirmations and printable training records for portfolios were also described as planned. Those were intentions, not features that I can say were delivered.

What it was, and what it was not

It was an intranet database that made course information and attendance visible. It was not today's digital workforce systems, and I would not describe it as one. It was an early, practical attempt to bring fragmented information together so that people could see it.

Records are not competence

A record that someone attended a course, or passed one, shows that training took place. It does not show that they are competent in practice. Competence is judged against an agreed standard, in the workplace, by the employer or supervisor under local policy. A good training database makes the evidence easier to find and the gaps easier to see. It does not replace that judgement. See Certificates vs Competency and Certificates, Competency and Employer Sign-off.

Why it still matters

The lesson I take from it is about infrastructure. When an organisation cannot see where its skills are, it cannot plan, assure or develop them well. Making capability visible is a leadership task as much as a technical one, and it is also a fairness task: people can only have equitable access to development that the organisation can see.

That thinking runs through my later work in clinical education, competency assurance and improvement, and into how VeinTrain supports a structured route to competence: Learn, Train, Scale. The setting is very different, but the question is the same. What does the organisation need to be able to see? You can read more about why VeinTrain exists, and find related pieces in Leadership & Transformation.

The original source

If your organisation is trying to see where its skills and training sit, and what that means for implementation and assurance, I would be glad to talk it through. Book a conversation with Sarah.

This article is a personal reflection on an earlier NHS role. It is not a statement of VeinTrain policy, and a VeinTrain certificate does not replace local policy, supervision, scope of practice or employer competency sign-off.