A forecast and an offer do different things
A customer opportunity can change without anyone having acted irresponsibly. Procurement takes longer, a programme is resequenced or the customer revises its priorities. A technology-services company needs room to respond to that uncertainty. An employment offer, however, does something different from an internal forecast. It invites a person to make decisions about income, notice, location and professional relationships. My view is that management should understand this difference before approving hiring, rather than discovering it only when a customer date moves and the candidate asks what will happen next.
The company may see a planned cohort as capacity associated with a possible mobilisation. The candidate sees a proposed job with a joining date and a set of expectations. Neither perspective is inherently unreasonable. The problem begins when the organisation makes the second proposition while managing only the first risk. A recruitment process can be administratively complete and still lack a considered answer to a simple question: what are we prepared to do if the work starts later than our current forecast?
I am not arguing that every hiring decision should wait for perfect certainty. That would be impractical in many services businesses and could itself create delivery risk. I am arguing that uncertainty should be assigned to a decision-maker and considered before personal commitments are requested. The choice may be to hire ahead, to limit the cohort, to describe a genuinely conditional proposition accurately or to defer action. Appropriate legal and employment advice matters in the circumstances. The people leader's contribution is to ensure that the business understands the human and financial consequences of the route it chooses.
In the fictional 2024 Samvetrik Digital case, ninety-six people had accepted offers when the expected customer start moved. Some had already resigned. Retaining their joining dates required ₹2.7 Cr for interim employment and preparation. That was a material cost, and we did not describe it as free learning capacity. The decision was based on the commitments already made and the available alternatives. It should not be turned into a universal policy claim that any company can absorb any delay, regardless of its circumstances.
The contingency belongs in the approval discussion
Before an offer is authorised, I want the commercial assumption described in language the approving leaders can examine. Is the work contracted? Which date remains uncertain? What has to happen before mobilisation? A probability label may help a portfolio forecast, but it is not a sufficient explanation of an individual commitment. Two opportunities with the same estimated likelihood can create very different consequences if one requires immediate resignation and relocation while the other allows a longer preparation period. The people decision needs that context.
The next question is what the company can fund if the assumption changes. That discussion should include more than the direct employment cost. There may be supervision, preparation, equipment and a manager's time in supporting people who join before their intended work is available. There may also be alternative assignments with genuine value. The answer should not depend on inventing internal tasks after the delay occurs merely to improve the utilisation report. If management chooses to carry capacity, it should be willing to describe the choice as such.
The approval process should also consider what has been communicated. Recruiters and hiring managers need a consistent explanation of the role, likely work and joining arrangements. A candidate should not hear certainty from one conversation and conditions from another. When circumstances change, the company needs a clear owner for the next communication. Silence while managers negotiate internally can be consequential for a person serving notice elsewhere. Timely contact does not ensure an easy resolution, but it gives the candidate a more accurate basis for their own decisions.
In our case, we retained the agreed dates and organised relevant preparation and interim work. Delivery leaders remained accountable for the quality and purpose of those assignments. People partners explained the changed timetable and discussed individual circumstances. We did not ask colleagues to pretend that the original engagement was certain to restart on a particular date. Nor did we assume that accepting a different assignment was a trivial administrative substitution. The nature of the work, location and development implications needed to be discussed honestly.
Seventy-four colleagues entered the intended engagement within twelve weeks, while twenty-two agreed other assignments. Those outcomes resolved the original cohort in the account we reviewed. They do not prove that the initial forecast had been sound, or that every aspect of the experience was satisfactory for every individual. A responsible review should preserve those limits. It should also ask whether the alternative assignments were appropriate, rather than treating any allocation as evidence that the company had fulfilled the professional proposition originally made.
Keeping the account honest afterwards
Once people are working, the organisation may be tempted to close the story as a successful mobilisation. I prefer to keep the interim cost and the changed assumptions visible. Otherwise the account team learns that hiring ahead carries little apparent downside, while the expense is absorbed somewhere less visible. That can encourage the same decision again without a proper discussion of whether the earlier outcome depended on favourable circumstances. A people leader should help the company remember the actual choice it made, including the cost of protecting commitments.
There is a similar risk in presenting the episode as a cultural triumph. Keeping a promise can be the right thing to do without requiring a campaign about the company's generosity. Candidates had acted on what they were told. The more useful organisational lesson concerns how the promise was approved, how uncertainty was communicated and whether the contingency was considered early enough. An impressive story about the recovery can distract from a preventable weakness in the decision that created the problem.
I would review the experience with commercial, finance, delivery and recruitment colleagues together. Each sees a different part of the sequence. The commercial team understands the customer change; recruiters know what candidates were told; delivery managers understand the interim work; finance can explain the cost and its treatment. The purpose is not to identify a single function to blame. It is to establish which assumptions need a different approval, which conversations need greater precision and which decisions should be escalated before the company asks another cohort to make personal commitments.
The principle I would carry into a board discussion is straightforward: management should know when a forecast becomes a promise to somebody outside the planning meeting. That moment deserves attention because the consequences no longer sit entirely inside the company's reporting system. A candidate may already have resigned, arranged a move or declined another opportunity. The business can still face uncertainty, but it should not act as though that uncertainty has no owner simply because the customer has changed its mind.