The missing resource in a recruitment number
I once helped arrange a development calendar that required the same experienced colleagues to be in a classroom and at a customer assignment. The contradiction was not hidden. It was distributed across documents prepared by different teams, each of which appeared reasonable. When cancellations began, we described the problem as scheduling pressure. That phrase was too mild. We had promised learning without securing the time of the people capable of providing it. The participants paid for our optimism through repeated changes to their plans.
That experience is why I hesitate when an apprentice intake is presented as a single number. The number matters, but it describes only the people entering. It says little about the experienced workforce that must make their entry useful. A technical business can recruit more quickly than it can develop supervised practice. Unless the difference is recognised, a well-intentioned programme can create frustration for learners and additional pressure for the colleagues expected to teach them.
I start by asking who will provide practical support, what time is being allocated and which existing work will move. These questions belong beside the recruitment budget. An instructor may be willing to help and still have no available capacity. A supervisor may agree to release someone while assuming that an urgent assignment will take precedence. The agreement needs to describe that tension before it becomes a repeated exception. Otherwise the programme is financed partly by unacknowledged extra effort.
In our fictional 2022 programme at Lanshuan Power, twelve experienced mentors could be released. We reduced the proposed intake from 120 to seventy-two apprentices and funded the learning arrangement within RMB 4.6 million. The smaller intake did not solve the entire future staffing requirement. It made that remaining requirement visible. We could then discuss additional experienced recruitment, later cohorts and changes to the operating timetable without pretending that an announcement had already created the necessary capability.
There is a legitimate objection to this approach. If every development plan waits for spare capacity, a growing business may never train enough people. I agree that learning cannot depend on whatever time remains after all other work is allocated. The answer is to make an explicit investment decision. Release experienced colleagues, fund cover, change the schedule or accept a different pace of growth. Each option has a cost. Calling development a priority while leaving every operating commitment untouched does not remove that cost; it moves it onto individuals.
Learning has several different endings
The second difficulty concerns what the programme says it has achieved. Attendance, completion and readiness to perform specific work are different records. A people function can administer attendance and ensure that the programme requirements are documented. Technical leaders must determine the relevant competence and authorisation. I do not want an apprentice to discover that a celebratory completion event has been interpreted as permission to undertake work that has not been assessed. Equally, a completed programme should not become an empty credential because nobody arranged the next assessment.
I therefore ask for a visible transition between these stages. Who reviews the learner's progress? What happens if more time is needed? How is the employee told what remains? The answers should be understandable without requiring the apprentice to navigate the organisation's internal divisions. A learner who needs further development is not necessarily a failed hire. The company must distinguish a reasonable extension from a programme that has not provided the promised experience. Both the individual and the employer have responsibilities, and the record should allow those responsibilities to be examined.
By December 2023, sixty-three of our seventy-two apprentices had completed the programme. Five had left and four required additional development. Those outcomes deserved separate discussion. The departures could teach us something about selection or the employment offer, but they did not all have the same cause. The extensions required a plan, not a euphemism. We also discovered that two mentors needed help with feedback. Expertise in a technical role did not automatically make every colleague equally prepared to teach another person.
That last point is easy to overlook. Mentoring can be described as an honour while being treated as an invisible addition to the day. I want the role to have preparation, recognition and a way to raise difficulties. A mentor should be able to say that the assigned work does not offer the necessary learning opportunities. They should also be able to challenge an unrealistic deadline without being seen as obstructing the workforce plan. The quality of that conversation affects what the apprentice experiences more directly than the language used at the programme launch.
There are limits to central design. A framework cannot predict every site condition or replace the judgement of experienced practitioners. My purpose is not to prescribe the technical sequence of learning from human resources. It is to ensure that the organisation has made a credible arrangement for learning to happen and that the people responsible understand their roles. Where conditions change, the plan should change openly. Repeated informal improvisation is a poor substitute for acknowledging that the original allocation no longer works.
A smaller promise can carry more responsibility
For a board or executive team, the useful question is therefore broader than how many apprentices joined. I would ask how the business has funded experienced teaching capacity, what proportion of the cohort has reached each stage and what unresolved needs remain. I would also ask whether the workforce forecast assumes more readiness than the evidence supports. Those questions invite a discussion about investment and operating choices. They do not require directors to become technical assessors or to review individual learning records.
I still value a confident recruitment commitment. Young people deserve a clear invitation into worthwhile technical careers, and businesses need to develop their future workforce. Confidence becomes more credible when it includes the experienced colleagues who will carry the promise. The apprentice's first day is the beginning of an obligation for the employer. A smaller cohort, supported properly and followed honestly, can be a stronger expression of ambition than a larger number whose practical meaning is left for site teams to discover.