From sustainability reporting to management

A target describes a destination. Management needs an account of the changes that will produce it. Identify the activities that must improve, the assets that need investment and the results that depend on suppliers, infrastructure or technologies outside the company’s immediate control. The distinction between what management can deliver directly and what remains contingent should be explicit.

Consider an illustrative manufacturer seeking to reduce energy use in a heat-intensive process. The plan might combine operating improvements, equipment replacement and changes to production scheduling. These actions differ in cost, timing and certainty. Staff can change some practices quickly. A replacement project may require engineering, procurement, a shutdown and commissioning before it affects performance.

The plan should connect those dependencies to the business calendar. A missed engineering decision could push installation beyond a scheduled shutdown and delay benefits for another operating cycle. Reporting the project as ‘in progress’ would hide the significance of that delay. The useful milestone is the decision that preserves the next feasible delivery date.

Finance should be able to reconcile the proposed actions with the capital and operating budgets. Where an initiative has no approved funding, its contribution should be shown as conditional. Where technical feasibility remains unresolved, the plan should include the work needed to establish it. A gap can be managed once leadership has agreed that it exists.

Responsibility is often assigned more readily than authority. A sustainability lead may compile performance, coordinate reporting and challenge weak evidence while having little control over production, purchasing or capital expenditure. Making that person solely accountable for the outcome leaves the decisions that shape it elsewhere.

The executive who controls the relevant activity should own delivery. The data owner should maintain the evidence, and the sustainability function should test whether the measures and actions remain consistent with the commitment. These responsibilities can sit with different people, provided the hand-offs and escalation route are clear.

Some decisions cross organisational boundaries. Procurement may need a higher-cost specification that operations considers unnecessary. A site may need investment whose benefit falls outside its annual performance targets. Leadership must resolve these conflicts. The project owner cannot be expected to negotiate indefinitely without authority.

A practical test is to ask what the accountable executive can actually change this month. If the answer is limited to requesting cooperation and updating a dashboard, the assignment is incomplete. Specify the decisions within the executive’s remit and the forum that will resolve those beyond it.

A reported measure can improve for reasons that deserve very different management responses. Energy use may fall because a process became more efficient, output declined, a facility was sold or a source of consumption disappeared from the reporting boundary. The headline movement alone cannot distinguish these explanations.

Management should preserve a clear account of the measure: what it includes, how it is calculated, the period covered and the treatment of estimates or missing information. When the definition changes, explain the effect on comparability. Replacing an inconvenient baseline without a transparent reason makes it difficult to judge either progress or the remaining task.

Absolute and intensity measures can also tell different stories. A factory can use less energy per unit while using more energy overall as production grows. Leadership needs to know which outcome the commitment addresses. If the target concerns total consumption, improved efficiency may contribute without being sufficient evidence of delivery.

Data quality should be visible alongside performance. Identify estimates, the assumptions behind them and the checks performed. Keep missing observations visible. Uncertainty does not always prevent action. It should determine what can reasonably be concluded and what additional evidence is needed before a larger commitment is made.

Management already has many targets and meetings. An additional sustainability reporting layer can consume time without changing the business. Place the relevant decisions in the forums that already control resources and performance.

Equipment decisions belong in capital reviews. Supplier requirements belong in procurement decisions. Workforce measures belong in the management of staffing, work design and supervision. A separate forum is useful when the issue genuinely crosses those boundaries or requires authority that the existing process lacks.

Within those forums, the sustainability consequence should be explicit. A cheaper input may increase waste. An accelerated production schedule may make a planned efficiency project impossible. A longer asset life may conserve capital while delaying an intended improvement. The task is to understand the full choice, including effects that individual budgets may omit.

There will be cases where the proposed action is unaffordable, technically premature or less effective than an alternative. A credible system allows leadership to say so. It also requires an account of what happens next: redesign the action, change the sequence, secure resources or reconsider the commitment. Repeating the target while withholding the means to achieve it transfers the problem to a later reporting cycle.

A missed milestone should prompt diagnosis before another recovery plan is approved. Establish whether the original assumption was wrong, a decision was delayed, the intervention worked less well than expected or the apparent shortfall is a measurement problem. The remedy depends on the cause.

In the illustrative heat-process project, a delayed installation and an underperforming installed asset require different responses. The first may need a new shutdown decision. The second may require technical changes or a reassessment of expected benefits. Combining them in a single red status indicator obscures the action leadership must take.

Keep a concise record of the decision, its owner and the evidence expected at the next review. Repeated delays then become visible as a pattern that may require a change in authority, resources or ambition. Public reporting can draw on that record to explain progress and limitations with greater precision. The report can then describe a functioning process without requiring the explanation to be assembled afresh at publication time.

In India, the Business Responsibility and Sustainability Report (BRSR) and BRSR Core make this distinction practical. SEBI’s framework specifies disclosures, measurement approaches and, where applicable, assessment or assurance. It also requires disclosure of changes to the base methodology and relevant estimates.¹ A polished narrative cannot resolve a missing meter reading or an undefined reporting boundary.

For management, a useful response is to assign each reported measure a data owner, a source record, a calculation basis and a review trail. This is Vogabe’s operating recommendation. It allows the reporting team to explain how a number was assembled and the executive team to decide what the number requires them to do.

The company’s own reporting and value-chain reporting should not be conflated. SEBI’s framework makes the latter voluntary for the specified category; it is not a blanket obligation on every supplier.¹ Establish the applicable scope before commissioning collection or verification.