Nine of twelve projects had been accepted. A portfolio paper described that position as 75% completion, and the percentage looked easy to understand. The nine accepted assignments represented ₹18 crore of ₹60 crore combined contract value. The other three represented ₹42 crore and were still awaiting acceptance. Within those pending projects, ₹7 crore of invoices could not yet be released under their terms. The count was accurate. The conclusion the headline invited was much less secure.
I did not regard the problem as dishonest arithmetic. The programme lead had chosen a familiar way to summarise a mixed portfolio, and executives wanted a concise account. The difficulty was that the word completion moved from the state of individual assignments to a broad impression of the enterprise's remaining exposure. A small number of larger projects could carry much more value than the accepted majority. The report needed to make that distribution visible without inventing another percentage to conceal a different ambiguity.
Name the population before using the percentage
A project count answers a particular question: how many assignments occupy a defined state? It does not automatically answer how much work is finished, how much contract value has been accepted, what can be invoiced or what revenue may be recognised. Those measures can be related, but the relationship requires evidence. Treating them as interchangeable lets a reader draw conclusions the underlying count was never designed to establish.
In this case accepted also needed a clear meaning. The three pending assignments were not empty folders in which no work had occurred. They had unresolved acceptance conditions. Their full contract values did not describe the remaining production effort, and their pending status did not establish that all related amounts were overdue or impaired. We needed an operating account that explained the state rather than invite the audience to supply its own assumptions about what that state meant.
The programme lead wanted to retain the 75% headline because it made progress visible and gave the meeting a clear starting point. I understood the attraction. A report can become so detailed that it loses the decisions management needs to make. Finance colleagues, however, pointed to the larger value within the remaining three and the invoicing conditions that still mattered. Simplicity was useful only if the simplified account preserved the distinction on which the next decision depended.
We therefore retained the count but removed its claim to describe overall completion. The report showed nine accepted and three awaiting acceptance, with ₹18 crore and ₹42 crore associated with those respective groups. It explained the outstanding conditions and the ₹7 crore of invoices not yet releasable. The figures belonged together, but they were not collapsed into one performance score. Their purpose was to help leadership understand where the operating and commercial questions were concentrated.
Do not repair one misleading ratio with another
It would have been easy to divide ₹18 crore by ₹60 crore and describe the portfolio as 30% complete instead. That would have sounded more financially rigorous while introducing a different unsupported claim. Contract value was not a validated weighting of effort. The pending projects could have substantial production work behind them, and accepted projects could differ in margin, timing and obligations. A value ratio could describe the distribution of contract value by acceptance state, but not every dimension of progress.
The distinction matters because corrective reporting can acquire authority simply by looking more sophisticated than the earlier measure. A weighted calculation is not necessarily a better answer if its weights do not represent the question. Before replacing a familiar percentage, I want to know what the proposed measure means and which decision it is intended to support. Otherwise the organisation may spend considerable effort defending a new ratio whose apparent precision is another form of uncertainty.
The ₹7 crore invoicing condition also required restraint. Those invoices were not yet releasable under the relevant terms. That fact did not make the amount a bad debt, a realised loss or a promise of immediate cash once an operating task was finished. Client and finance owners retained the contractual and accounting interpretation. Operations needed to show the conditions and their status so the responsible people could assess the consequence without relying on a headline that had already implied most exposure was settled.
We did not claim that changing the paper produced a new acceptance or cash receipt. A clearer report can improve the discussion, but the work and decisions it reveals still need to happen. I wanted the account to preserve that gap. Otherwise the reporting correction itself becomes another success metric that distracts from the unfinished matters it was supposed to expose. Better visibility is a useful outcome with a limited claim, not a substitute for delivery.
Use the report to locate the next decision
The revised discussion could ask what each pending assignment needed for acceptance, who held the relevant decision and whether the operating plan supported it. That was more useful than arguing whether 75% felt sufficiently positive or negative. Different projects might require a client review, a correction or a scope decision. The report needed enough context to distinguish those paths without turning an executive meeting into a detailed production review of every item.
A concise account can still do that. The main paper can show the states, associated values and principal unresolved conditions, with supporting detail available to the people who need it. Concision should come from selecting information relevant to the decision, not from forcing unlike facts into a single ratio. The aim is a reader who understands the portfolio's shape and knows which questions deserve attention next.
For a board, the case raises an assurance question. When management reports completion, what exactly has been completed and how does that relate to the enterprise's obligations? Directors need not prescribe every operating measure to ask whether the reported population and the commercial exposure align. They can also ask whether changes in definition are explained over time, so an apparent improvement does not simply reflect a new way of counting the same unresolved work.
There is also a people consequence. If teams are rewarded for the number of accepted assignments alone, they may rationally favour smaller items that improve the count while larger obligations remain unresolved. This case does not establish that such behaviour occurred. It shows why leaders should examine the incentives a measure could create before treating it as a neutral description. A useful operating measure should help the enterprise make choices, not quietly make the choices on its behalf.
I continue to use counts. They are often the clearest way to describe a workload or state. I also use financial amounts when their meaning is established by the relevant owners. The lesson is to keep each measure attached to the question it answers. Nine accepted projects were real progress. They did not settle three quarters of every question facing the portfolio, and the leadership account became more useful when it stopped asking that one fact to do so much.