Action Register Procedure
[Entity] — three fields, or it is a note
The commentary resets every month. The register does not.
| Field | What goes in it |
|---|---|
| Line or metric | One line on the departmental P and L, or one flash metric. Not a theme |
| Committed effect | A monthly dollar amount, with a direction. Not a percentage |
| Month due | One calendar month. Not a quarter |
The distinction this makes, on one real item
| Note | We need to tighten up on delivery |
| Action | Duluth delivery cost down 14,000 a month from April, by routing every drop into one daily run |
The second one can be wrong, which is what makes it worth writing down. Notes are often true and belong in the commentary. They never get a status column, because there is nothing to score.
Tolerance, fixed when the action opens
| lands at | = | committed amount less 10 percent, floor 1,000 |
A threshold that can be revised once the result is known is not a threshold. If the commitment turns out to be unreachable, that is what versioning is for: v2 carries the smaller number and v1 stays readable.
Four verdicts, computed off the ledger
| Open | Inside the month it was due |
| Landed | The named line moved far enough, by the month named |
| Missed | It did not. Stays in the register with a cause, and ages |
| Superseded | Replaced or withdrawn with a reason. Never deleted |
Nobody is asked whether their action worked. The register reads the line.