Field note · July 18, 2026
Annotating cohort reports so operators can act
A table without the week a price changed, a store closed, or a reminder stopped is a table that invites argument. Annotation is part of the report, not decoration.
Operators do not act on a grid. They act on a sentence that sits next to a week: the reminder stopped, the price rose, the second location opened late. Cohort reporting that leaves those sentences to hallway memory will be re-litigated every quarter.
An annotation should be dated, sourced, and boring. 'Price change on 12 May, confirmed by the rate card Mara sent' is usable. 'We improved the experience' is not an annotation; it is a hope.
Put the notes in the same pack as the table, in the same order as the columns. A separate appendix is where annotations go to be ignored. Bundlelogicbase briefings keep a lane under the periods so a working session can point at a cell and a sentence together.
When two people disagree about an event, record both claims and the unresolved status. The table should not pick a winner in the absence of a file. Retention work is already full of invented causes.
The last page of a briefing is a short list of actions that the table can actually support. If an action needs a number the extract cannot produce, it stays off the list. That restraint is the difference between a report people file and a report people bring to the next staffing meeting.