A named expert in a proposal is a commitment someone must be able to keep

A professional biography can make a proposal persuasive. It gives the prospective client a person whose experience appears to support the work being offered. That is useful when the description matches the individual's actual role and supported participation. It becomes less reliable when the company uses a name to imply a staffing commitment that has not been discussed. The firm may possess the relevant capability in a broad sense while the particular expert is unavailable, unwilling to take the proposed assignment or unaware that their involvement has been promised. HR should help the business distinguish those claims before submission.

Our review at Velqemi concerned fifty-two colleagues named in a proposed ₹4.6 crore engineering-study engagement. Some biographies had been drawn from earlier internal material, and some availability assumptions had not been confirmed. The bid director argued that the proposal demonstrated the breadth of the firm and that final deployment could be settled later. I understood why a large named team appeared commercially useful. I also thought the client could reasonably read the names as a statement about the people who would do the work. We needed to examine that implication rather than rely on our own more flexible interpretation.

Experience does not establish availability

A person can be qualified for an assignment without being available for it. They may be committed to another engagement, have constraints on travel or prefer a different development path. Technical leaders need to determine the competence required, while commercial leaders need a deliverable staffing account. HR should not replace either judgement. Its contribution is to make sure the proposed involvement has been explained and that the people account reflects actual decisions. A stored biography is evidence of experience, subject to accuracy checks; it is not a continuing answer to every future question about deployment.

The scope of participation also matters. A short advisory contribution differs from leading an engagement, and a review role differs from full-time delivery. A proposal can become misleading through ambiguity even when the named person has agreed to some involvement. The conversation should establish what is being represented, for which opportunity and under what conditions. I do not think every commercial draft needs an elaborate employment process. I do think the company should be able to explain why the names in its final staffing promise correspond to a supported and workable plan.

There is a reasonable objection that consulting work changes quickly. A firm may not know the final award date or exact demand when preparing a bid. That uncertainty should be expressed in the proposal and managed through appropriate commercial arrangements, not silently transferred to employees or clients. Where participation is conditional, the condition needs to remain visible. Where another person may be substituted, the client should understand the relevant arrangement. HR's role is to help management describe uncertainty honestly while technical and commercial owners determine whether the resulting proposition is adequate for the opportunity.

Let unresolved participation remain unresolved

In the review, thirty-one people confirmed the defined participation, twelve declined and nine remained pending. We kept all three categories. The pending group did not become available by default, and the people who declined were not described as disengaged. A refusal could relate to the particular timing or scope rather than the person's commitment to the firm. The process repair cost ₹18 lakh. That included checking roles and revising the staffing account, work that had been omitted when the proposal was assembled from existing biographies and broad assumptions about the team's reach.

The commercial team submitted a narrower proposal around the thirty-one supported names. This made the immediate presentation less expansive. The bid director had to explain how additional requirements would be addressed rather than displaying an already complete-looking team. I considered that a real commercial tradeoff, not a trivial administrative correction. The firm might lose some persuasive force by being more precise about its present commitment. It could also avoid making a promise whose fulfilment depended on conversations that had not yet happened. We retained the tradeoff without claiming a contract outcome the review did not establish.

The ₹4.6 crore figure remained the value of a proposal. It was not fee revenue, a contract award or income lost because certain names were removed. That distinction is easy to blur when presenting a people decision to directors. A large opportunity can make a cautious staffing account look commercially damaging even when the business has not secured it. The board should understand the potential significance, but it should also know which stage the figure represents. HR should be as careful with the commercial denominator as it asks commercial colleagues to be with the people named in the bid.

We also resisted turning confirmation into a permanent permission. A colleague's agreement to one defined opportunity did not settle every later use of the same biography or every change in scope. The process needed a way to revisit material changes without making routine administration burdensome. That balance belongs in the firm's operating practice and contractual arrangements, with appropriate specialist advice. My concern was the underlying discipline: participation should remain attached to the actual proposal being made, rather than become detached from it once a convenient affirmative response has been recorded somewhere.

Carry the same care into employment promises

The distinction between a planning assumption and a commitment also appeared in a later hiring revision. Twenty-eight candidates had accepted offers when demand changed. Eighteen starts could continue; ten were affected by a proposed deferral. I initially approached the exercise too much as a headcount schedule. The accepted offers required separate examination because people may already have made decisions in reliance on them. Legal and employment specialists reviewed the terms, and HR held individual discussions. A planning system could show a revised date, but it could not decide by itself what the company should ask another person to accept.

The board approved a ₹24 lakh support envelope. Eight affected candidates accepted supported arrangements and two reached different agreed resolutions. We kept those differences visible and did not describe agreement as an absence of inconvenience. A separate ₹1.2 crore proposal about vacant posts remained outside any claim of realised savings from accepted offers. The bid-biography and hiring cases involved different relationships and different obligations. What connected them was the need to recognise when the company's account had begun to shape someone else's reasonable expectation, and to treat a proposed change with the care that expectation required.

I would bring that question to a board without trying to manage individual deployment or recruitment decisions from the boardroom. Directors can ask whether management distinguishes capability, availability, agreement and delivery in its commercial and employment reports. They can examine the cost of correcting an overstated commitment without requiring every correction to produce an immediate financial benefit. My experience is that a professional firm's credibility depends partly on these small distinctions. A name in a proposal and a date in an offer are useful only when the business understands the real person whose next decisions may depend on them.