OPERATING NOTE — 001

Over weekend service, a small variance appears in the pours on higher-content cocktails. The drink still arrives. The guest may still enjoy it. The drift looks like a craft issue, or at most a margin issue, and it gets filed as either. The problem runs further down than that.

When a bartender drifts from spec, the POS still records a clean sale. Correct item, correct price. The system has no idea the pour was 20% heavier than intended. The variance never surfaces anywhere. Every liquor cost report run, every pricing decision made, every menu adjustment considered — all of it sits downstream of pours the system never actually measured. The drink is not the only thing being lost. The data was corrupted before it ever reached the screen.

The technology to close this gap exists. Smart pour spouts record every pour to the hundredth of an ounce and reconcile against the POS in real time. Most operators who use them have framed the tool wrong — as theft deterrence. The frame is data infrastructure, not loss prevention. Theft is a small subset of the problem; quiet drift is the rest of it.

Experienced bartenders already encode this discipline: at the start of a shift, pouring water into a jigger while counting, locking the rhythm before service begins. The practice is not only about the drink. It is about the integrity of every number that follows.

In hospitality, the problem is rarely one dramatic mistake. It is a small inconsistency, repeated often enough to corrupt everything built on top of it.