When a dashboard number is an override, not a calculation
Every application we have reviewed allows some form of override. Markets gap, vendors miss a price, a corporate action is late. A person pins a value so that the committee pack can be issued. That is ordinary operations. The control question is whether anyone can later see that the tile was not calculated in the ordinary way.
A good override has four traits. It has an author. It has a reason. It has a second reviewer if the figure will be published. It has an expiry or a review date. Missing any one of those traits turns a practical workaround into an invisible policy.
We have seen overrides that outlived the event that justified them. A suspended stock was pinned in 2023 and still pinned in 2026 because nobody owned the expiry. The dashboard was consistent. The file was not.
Suppressing a line is a stronger act than pinning a price. Removing a position or a fee from a view because it “distorts the story” is a reporting choice. It should be described in the pack, not only in an application log that the committee never reads.
If you operate a dashboard application today, ask for a list of live overrides before the next reporting date. If the application cannot produce that list, that fact belongs in your next internal audit plan — and it is one of the first things we test when we are engaged.