A blank space on a schedule looks like it charges nothing. If no decision is made, no budget, no staffing and no system order gets set. So the blank reads like a saving. In practice it is closer to the opposite.
Major Asian countries are moving toward fixing when, and for which companies first, climate-related disclosure becomes mandatory. Korea has put off finalizing its roadmap. And in the same week, California's disclosure rules went before a court weighing whether they are unconstitutional. With the three facts piling up at once, the argument for "let's watch a little longer" gained force.
The moment confusion over the rules is turned into a reason to wait, the preparation costs Korean companies must eventually pay do not disappear; they are pushed back and grow bigger.
The strongest counterargument is sunk cost. If standards are shifting internationally and a company rushes to build a system, the money spent is thrown away when the conclusion changes. For those holding the regulatory compliance budget, that is a trade-off worth weighing.
But the issues now in dispute and the nature of what companies have to prepare sit on different layers. What is at stake in the litigation and the policy debate is closer to how much disclosure can be compelled, and of what. Setting the boundary for counting emissions, and making those figures withstand verification the way accounting records do, is not discarded under any conclusion. What gets sunk is the format of the report, and the data remains.
More important is that some items can only be bought with time. Emissions data reaching down to suppliers, internal control procedures, and the continuity of records needed for verification cannot be compressed into a few months by raising the budget. Start after the effective date is fixed, and what must be secured is a figure for a period already past, while what is in hand is only future time. Responding then is always more expensive.
Delay is a possible choice. For that choice to be justified, conditions are needed. How wide a gap to set between the effective date and the period actually required for preparation, and how that gap changes with company size, have to be presented together. Postponing without that design does not become a grace period; it only shifts the burden.
What to check from here is not whether a roadmap is announced. It is whether the announcement states both the effective date and the preparation period, and whether the distance between the two is manageable for a company that has never built supply chain data from scratch. The blank will be filled someday. The question is how much time companies will have left on the day it is filled.
