The unbilled judgement still belongs in the career

In 2018 I endorsed an appraisal framework with a strong emphasis on client-billable assignment time. It offered a clear measure that managers could explain and compare. Latha challenged the treatment of employees who had been instructed to carry out internal technical review. Their contribution supported the enterprise, but the framework could make that time look like an absence from valuable work. I had accepted the visibility of an invoice as too close a substitute for the value of an assigned responsibility.

We reopened twenty-eight affected employee records. The review examined the work actually commissioned, the evidence of contribution and the original assessment. Six ratings changed and twenty-two were confirmed. Those outcomes mattered: the correction was not a blanket increase for everyone who had recorded unbilled time. It was an individual response to a framework that had not represented the work adequately. The resulting pay correction totalled ₹18 lakh for this review, with the appropriate employment and payroll assessment behind the payments.

Commercial managers worried that reducing the dominance of billable time would make assessment subjective and weaken attention to customer delivery. I agreed that the company still needed to understand where its revenue came from. I did not agree that the answer was to leave instructed internal work outside the account of contribution. We made those responsibilities visible in subsequent assessment discussions, asking managers to explain both the purpose of the work and the evidence used to evaluate it. Technical competence and professional approval stayed with qualified colleagues.

The change cost money and management time. It also removed the convenience of treating a single utilisation measure as a complete explanation of performance. We did not claim that the correction improved the quality of any survey or established that every employee regarded the outcome as fair. The narrower result was a reviewed set of ratings and a paid correction, with my responsibility for the earlier framework explicit.

I would now ask a different question before endorsing a measure: what work does the organisation require that this measure cannot see? The answer may not justify a pay change, but it should be available before an employee is judged. A professional employer cannot rely on judgement that its own career system makes difficult to recognise.

An acquisition in 2022 brought forty-two employees into the enterprise. The integration team wanted a common joining date in the new records, which would simplify administration. The immediate people question concerned the company's voluntary long-service recognition programme. Colleagues asked whether work completed with the predecessor business would count. A new system entry could be accurate as an acquisition date and still be an inadequate account of the service the programme intended to recognise.

Finance preferred a single rule beginning with the transfer into Zaqvermi. It offered a clear cost boundary and avoided relying on inconsistent old records. Employees argued that this would make years of contribution disappear from a benefit explicitly concerned with service. I recommended a defined predecessor-service review, with the purpose and evidence requirements explained. This programme decision did not reset or replace statutory or contractual rights; those questions were referred to the appropriate employment and transaction specialists for their own assessment.

Thirty-three service records were confirmed for the voluntary programme. Nine remained unresolved because further evidence was needed. The company allocated ₹27 lakh for the additional recognition cost. That was an allocation, not a report that every rupee had already been paid or that the nine open cases had been refused. We retained a response owner for each unfinished record and avoided asking colleagues to reconstruct unnecessary personal history unrelated to the service question.

The acquisition team gave up the simplicity of one date for every purpose. The people team accepted more administration, and finance had to explain an additional cost rather than assume that integration itself settled eligibility. We also resisted declaring the entire people transition complete on the basis of this one programme. Recognition, pay, contractual conditions and other obligations could require different evidence and decisions.

The result was a clearer response to a specific promise. Thirty-three colleagues had predecessor service recognised; nine still needed an answer. The case did not prove universal satisfaction or establish a legal conclusion about the acquisition. It showed that administrative consistency is useful only when the chosen fact fits the purpose. An employer can standardise its records without pretending that a colleague's earlier working life began when the new system first opened their file.

In 2023 nineteen experienced professionals considered their next role within the survey enterprise. The conventional advancement discussion often led towards managing people, even where the contribution valued by colleagues was deeper technical judgement. Some wanted management responsibility. Others wanted a more demanding technical role without making team supervision the main account of progress. I proposed a principal technical route with defined responsibilities, alongside the existing management route, rather than a new title offered as consolation for not becoming a manager.

Latha led the professional discussion about the authority and competence each technical role would require. HR worked on responsibilities, remuneration and the decision process around it. We did not treat a title or attendance at training as technical authorisation. Eight professionals chose the principal technical positions, seven chose the people-management route and four remained undecided at the review date. The categories describe choices in this group, not a judgement that one kind of career is superior.

The eight principal positions added ₹56 lakh annual role expense. That total was not a uniform payment per person and did not promise the same progression to every employee. Finance challenged the cost of creating senior positions without increasing management capacity. Farhan also asked how the company would meet future leadership needs if experienced colleagues chose another route. Those were real consequences. We retained the management pipeline requirement while accepting that some valuable professionals would contribute differently.

The approved structure therefore bought a more explicit choice at a known recurring cost. It did not establish a retention improvement, a technical-quality result or the eventual performance of every appointee. The four undecided colleagues stayed in the account without being described as resistant to development. A career conversation can require time, particularly when the organisation is asking someone to choose a different kind of responsibility rather than simply accept the next title.

I learned to make the employment proposition concrete before celebrating the existence of two routes. What work changes? Who can assess it? What remuneration and capacity does the business support? The answer must be sufficient for the employee and the enterprise. A technical employer should not require a person to acquire direct reports merely to demonstrate that their judgement has become more valuable.

During 2024 we reviewed eleven client requests to remove named employees from assignments. An urgent commercial response could make reassignment appear the easiest solution. Yet a customer request might concern a working problem, a disagreement about a technical finding or personal pressure unrelated to a fair assessment. I wanted the enterprise to understand the request before allowing it to become an employee's performance record.

The review identified substantive working or assignment issues in six cases, unsubstantiated personal pressure in three and two matters still unresolved. Those categories did not determine disciplinary guilt or certify technical conclusions. The six required proper follow-up through the appropriate owners; the three did not mean that every aspect of the employee's work was beyond criticism. Latha retained professional assessment responsibilities, while employment questions followed the relevant process and advice. Individual details were not circulated as a management scorecard.

Commercial colleagues worried about delay and the prospect of damaging a client relationship. I accepted that the company could lose an opportunity if its response was unhelpful. I did not accept that commercial urgency should automatically become evidence against a colleague. We spent ₹16 lakh on review and administration, gave the requests an accountable response route and kept the two unfinished cases visible. The case does not claim that every employee stayed on the original assignment or that a particular client was lost; those outcomes are not established by the review categories.

The immediate trade-off was a slower and more demanding staffing response. Managers had to explain why a request needed examination rather than present a personnel move as an uncomplicated service gesture. Employees also needed to understand that being heard did not promise a preferred outcome. The objective was a fair basis for the decision, with the customer's substantive concern preserved where evidence supported it.

The experience sharpened a boundary in my role. HR can protect the quality of the employment process without declaring a structure sound, a survey correct or a customer wrong. A technical employer needs a way to hear criticism and resist unsupported pressure at the same time. If it treats every client preference as a verdict, it risks asking professionals for judgement while privately making that judgement conditional on whether the customer welcomes it.

In 2025 thirty-six employees requested permission to use examples of their professional contribution in career portfolios. Some wanted to describe the problem they had examined, others their part in a team assignment. A blanket refusal would protect the company from review work but leave colleagues unable to explain experience that mattered to their careers. Unrestricted approval could expose client information or attribute a team result to one person. I proposed a defined permission process with those two risks stated together.

The review approved fourteen sanitised case accounts. Eight requests needed authorship clarification, six awaited client permission and eight were declined for confidentiality reasons. These categories account for all thirty-six requests. The pending groups were not authorised to publish while waiting, and the approved accounts did not certify technical competence or turn a project contribution into sole ownership of its findings. Appropriate professional and contractual owners assessed the material before permission was given.

Some managers preferred a general prohibition because each request consumed time and could create difficult conversations about credit. Employees wanted a route that did not depend entirely on a manager's personal willingness to help. The company spent ₹12 lakh on review and administration. It accepted the work of providing reasons and recognising that a contribution may deserve an account even when the employee is thinking about a future career beyond the present assignment.

The result was permission for fourteen bounded accounts, not proof that they were published, secured promotion or improved retention. Eight refusals remained refusals; the process did not promise that every experience could be shared publicly. We also retained the difference between permission to describe work and a right to reproduce client documents. A useful professional narrative could sometimes explain a judgement without exposing the records or identifying the commission.

For me, this was an employment decision about visibility. The organisation benefits from technical experience and should be able to explain how a colleague can represent their contribution responsibly. That does not erase confidentiality or authorship obligations. It requires a process that examines them, gives an answer and keeps unfinished requests from disappearing behind a general statement that professional development is encouraged.