A proposed internal transfer can look unusually attractive in an expansion spreadsheet. The person is already employed, knows the company and may need less introduction than an external hire. The new operation gains experience without an immediate increase in group headcount. That account is incomplete if it says little about the work the person currently performs. The colleague is not spare capacity merely because the payroll cost already exists. Their departure changes another operating plan, sometimes in ways that are difficult to replace quickly.
In a pharmaceutical business, the experience behind a position matters as much as the label. Two employees with the same title may have different familiarity with a process, different supervisory experience and different authorisations. I do not make those technical assessments as a CHRO. I do need the staffing plan to acknowledge them. If the people report treats all filled positions as interchangeable, it can make a weak operating assumption appear administratively complete. The resulting problem will later be described as a recruitment delay even when its origin was a poor definition of the requirement.
Count what leaves the sending operation
Our fictional 2023 line expansion at Anvethra began with a proposal to transfer twenty-four experienced colleagues from an established unit. It was understandable why the new unit wanted them. They knew the organisation and brought practical experience that a newly assembled team would lack. The existing unit’s leaders objected because the group included people important to supervision and technical continuity. Their objection was initially heard as resistance to supporting growth. That interpretation made it harder to examine the underlying dependency.
I asked the teams to describe the work each proposed transfer would leave behind. The discussion moved from a list of names to an account of responsibilities, available cover and the time needed to develop alternatives. Some transfers were manageable within the proposed sequence. Others would have created a gap that could not be resolved simply by approving a vacancy. The sending managers had to provide evidence rather than a general claim that nobody could be released. The receiving managers had to explain why each capability was needed at that stage.
Employees also needed to be part of the plan. An internal move can change location, travel, working patterns and the person’s expectations about their career. Familiarity with the company does not make these consequences trivial. My team discussed the practical terms with the individuals and identified issues requiring a management decision. A plan based on presumed willingness can fail late, after the operating timetable has already been built around it. It is better to discover a constraint while there is still room to consider an alternative.
The revised arrangement used twelve transfers and twelve external hires. We funded staged overlap and preparation at ₹2.4 Cr, and moved the planned line start by six weeks. Those numbers are invented for this demonstration, but the choice they illustrate is specific. Management accepted more cost and a later start to avoid stripping experience from the existing operation. The alternative was not costless. It merely left more of the likely cost outside the expansion proposal, to be absorbed later by the sending unit.
Separate a filled role from authorised work
A recruitment milestone answers an employment question: has the person accepted, joined and entered the agreed role? It does not answer every technical question about the work they may perform. In our review, operations and quality leaders retained responsibility for the relevant assessment and authorisation. The people function tracked joining and preparation without turning those milestones into a claim that the line was ready. This separation can feel inconvenient when a project review wants one simple percentage. It is nevertheless necessary if the percentage is otherwise combining different kinds of evidence.
The same distinction applies to internal colleagues. Experience at an existing unit can be valuable without being identical to readiness for every task in the new setting. Technical leaders must define the preparation needed and the conditions under which work can begin. My role is to make the time and employment arrangements available, and to escalate a plan that assumes those conditions can be met without support. I should not make the project appear healthier by changing the label attached to an incomplete technical process.
There is a practical communication issue here. A board or investment committee may see staffing as one line in a much larger project report. The report should therefore explain the difference concisely. It can show appointments completed, preparation under way and technical decisions still outstanding, with the responsible functions named. That is more useful than a single green indicator that hides a material dependency. The aim is not to burden directors with every operational detail, but to ensure that a material assumption is visible at the level where the investment is being judged.
This also prevents an unfair attribution of responsibility. A recruiter cannot resolve a technical authorisation gap merely by filling another vacancy. A quality leader should not have to defend an uncompleted assessment against a claim that staffing is already finished. Each function needs an accurate account of what it has committed to deliver. Where the plan crosses those responsibilities, management must coordinate the decisions rather than ask one team to absorb the uncertainty created by another.
Put the staffing decision into the investment conversation
The six-week change in our plan was harder to discuss because the original timetable had already circulated widely. Once a date appears repeatedly in presentations, questioning it can sound like a failure of execution rather than a correction of an assumption. I would bring the workforce dependencies into the investment discussion earlier next time. The proposal should describe the experience required, the likely sources and the effect on existing operations before the timetable acquires that authority.
Finance should also see the difference between a steady-state cost and a transition cost. The final organisation may have a sensible employment envelope while the route to it requires overlap, travel, preparation or temporary cover. Hiding those costs does not remove them. It makes the project harder to manage honestly and can create pressure to shorten activities that were never properly funded. A credible plan should explain why the transition expenditure is needed and when it will end, rather than rely on a vague allowance for contingencies.
None of this means that an internal transfer is a poor choice. It may be the best way to carry practical knowledge into an expansion and create a valuable career opportunity. The point is to evaluate it as an operating decision with consequences on both sides. In our case, the twelve transfers and twelve hires were completed under the revised plan. That is the employment result I can describe. It does not establish a product-quality or commercial outcome, and I would not claim one from a staffing report.
An expansion becomes more credible when management can explain where its experience will come from and what the company gives up to provide it. The people function contributes by making those dependencies discussable, funding the practical arrangements and keeping different forms of readiness distinct. A person already on the payroll can be an excellent choice for a new unit. Their existing work still needs an answer.