Put the conversation next to the number
A reviewer opens the month’s figures, gets to a line that has moved a long way since last month, and asks about it. Not in the sheet. In a chat channel, or in a reply to the email the sheet was attached to, quoting the entity and the measure and hoping the person on the other end is looking at the same row.
The answer comes back an hour later, by which time the reviewer is somewhere else in the file. Whoever submitted the number changes it. Nothing anywhere records that the change happened because of that exchange. Six months later, during an audit or a handover or an argument, somebody finds the figure and wants to know why it is what it is, and the reason exists only in a channel that has since been archived.
The question belongs on the cell
The grid above is a review sheet, and some of its cells have a small marker in the corner. Those are conversations. Click one, or press Alt and M on a cell, and the thread opens beside the number it is about: who asked, what they asked, what came back, and when.
One of the threads on this grid is already resolved, and its cell is marked differently from the two that are still open, so a reviewer can see at a glance which questions are settled and which are waiting on somebody. That distinction is the one that matters when the pack has to go out on Thursday. Asking whether anything is still outstanding is a hard question when the queries live in a chat channel and a glance down a column when they live on the cells.
Add a reply of your own. Nothing you type here leaves your browser, because the grid on this page is talking to a store that lives in the tab and forgets everything on reload.
The change in behaviour this produces is small and immediate. People stop quoting rows at each other. Nobody writes “the Halden Foods recognised revenue line” into a message, gets a reply about the wrong month, and spends several messages establishing which cell they are both looking at. The thread is on the cell, so the context is not something anybody has to reconstruct.
Six months later is the real audience
The person this feature is really for has not opened the file yet.
They are the auditor, or the new analyst, or the same reviewer in a different quarter, and their question is always why. Why was this restated. Why did this provision move. Why does this one line have a different treatment from the rest. Today that answer is in somebody’s inbox, and if that somebody has left, it is nowhere.
A thread on the cell survives the meeting, the quarter and the leaver. It sorts with the row, because it is attached to the record rather than to a position in the file, so the conversation is still on the right figure after somebody sorts by movement or groups by entity. Comments outlive the values they annotate, which is exactly why they cannot be tied to where a row happened to be sitting when the remark was made.
Your comments live in your systems
The grid draws the markers, the counts, the threads and the resolve control, and reads and writes through a store you supply, so comments sit under your retention rules, your access rules and your backups.
Comments are your data. They belong wherever the rest of your records live, and a grid that quietly kept a copy of a conversation about a restatement somewhere else would be a problem rather than a convenience.
You wire it to your own store, which is the reason this can be honest about what it is. Nothing is uploaded anywhere by us, because there is nowhere for it to go.
For the person reviewing the numbers, none of that is visible. There is a marker on the cell, there is a thread behind it, and the question is finally in the same place as the answer.