## Departure is easier to organise than return
Eighteen colleagues returned from two-year overseas assignments in 2023. Ten resumed the roles agreed for their return. Four accepted different roles because their original positions had ceased. Two remained in bridging work, and two left voluntarily. The assignment calendar could describe all eighteen as completed. The people account could not. These were different outcomes, with different implications for the colleagues and the enterprise. I wanted the report to preserve that difference before the successful administration of travel, dates and host placements became a claim that the whole employment commitment had been fulfilled.
Departure encourages specificity. A host team needs someone, a start date must be agreed and practical arrangements have immediate owners. The return sits farther away. It can be described through a reassuring phrase while the operating decisions that will determine it remain unsettled. That does not necessarily reflect bad intent. Organisations change, and no serious proposal can pretend to know every future circumstance. The weakness arises when uncertainty is hidden inside language that sounds more definite than the process supporting it. The colleague hears a commitment, while the organisation may have recorded little more than an expectation.
Our four changed roles made that gap concrete. Their original positions had ceased before they returned, and each accepted a different role. That outcome belonged in the account on its own terms. It was not the same as returning to the agreed position, even if a different role could be a reasonable result for a particular person. We needed to retain the change, the individual discussion and the outcome rather than remove the history once a new placement existed. Otherwise the enterprise would lose the very evidence needed to improve the next assignment proposal.
The two voluntary departures also required restraint in interpretation. A programme report can record that someone left without claiming complete knowledge of why. It should not automatically attribute the departure to a failed return arrangement, and it should not erase the departure because it complicates an otherwise positive mobility story. The relevant account is specific about what is known and cautious about what is inferred. In people work, an apparent narrative of success or failure can become more confident than the evidence permits when a colleague's personal choice is used to complete the organisation's preferred explanation.
## A bridge is useful only if its unfinished purpose stays visible
We established a ₹68 lakh bridging and transition programme over twelve months. That budget created room to address return issues; it did not establish that every rupee had been spent or every person had reached an agreed permanent position. The two colleagues still in bridging work remained unresolved in that respect. Calling their temporary allocation a placement would have made the programme easier to close administratively while changing the meaning of what had actually happened. A bridge can be useful without being the destination, and the account needs to preserve the distinction for as long as it remains true.
An interim arrangement should explain what work the colleague is doing, who supports them and what question remains open. Those are management responsibilities that require attention, not merely a line in a report. The purpose is not to make every uncertain case appear defective. It is to ensure that uncertainty has an owner and does not become invisible because payroll and reporting systems can accommodate it. A temporary arrangement can persist for reasons that deserve examination even when no single administrative action appears overdue. The person experiences the whole condition, not just the completion status of its separate tasks.
Our review connected the sending enterprise, the host team and the manager responsible for the return. Each could hold a different part of the history. The host might see an assignment completed; the sending business might see a role that changed; the colleague might see an assurance whose practical meaning had weakened. Bringing those accounts together required more than a handover form. It required agreement about who would resolve the remaining decision and how the person would be kept informed. Individual arrangements received the relevant professional review rather than being settled by a general slogan about mobility.
I do not think the answer is to promise an unchanging future job regardless of circumstance. Such language could reproduce the same weakness in a more emphatic form. A more useful assignment proposal makes the intended return explicit, identifies the process if circumstances change and gives the colleague a realistic understanding of the commitment. It should also identify the decisions that have not yet been made. The practical challenge is to be clear without pretending that uncertainty has disappeared. People can assess a bounded commitment more intelligently than a reassuring phrase whose limits emerge only when it is tested.
## The account should follow the colleague
Programme reporting often follows organisational events: approval, departure, arrival, completion and return. Those events matter, but they need to connect to the person's position after each transition. A completed host assignment can coexist with an unresolved home role. A new local placement can coexist with a material change from what was originally agreed. A voluntary departure can conclude an employment relationship without validating every assumption in the assignment design. The report should make these combinations visible, because otherwise the calendar supplies a convenient ending to a commitment whose consequences are still being worked through.
This changes the evidence I would want before approving another series of assignments. I would look for an account of what previous returnees actually experienced, including changed roles and open bridging cases, rather than a count of assignments completed. I would also want to understand the receiving enterprise's capacity to absorb the skills it has helped develop. Sending someone abroad can be an attractive opportunity while the return organisation remains unclear about where that experience belongs. The question is not whether mobility is generally desirable. It is whether this particular proposal connects the opportunity with a credible account of what follows.
The financial account should retain similar discipline. Our ₹68 lakh programme was a resource decision, not a valuation of successful returns or an automatic measure of employee benefit. A budget can support useful work while cases remain open. Spending the budget would not itself resolve those cases, just as spending less would not necessarily mean they had been handled well. The people outcome and the financial account need to be read together without one standing in for the other. That helps management explain what has been achieved, what remains uncertain and which decisions still require attention.
For a board, the useful oversight question is whether the organisation understands the promises inside its development programmes. Directors should not allocate individual return roles, but they can ask whether management's summary retains changed circumstances, unresolved cases and the responsibility for completing them. My example contains ten planned returns, four agreed alternatives, two continuing bridges and two voluntary departures. Keeping that account intact is more valuable than turning it into one percentage with an optimistic label. An assignment should be remembered through the commitment made to the colleague, not only through the dates the enterprise managed to complete.