Table of Contents

Definition

The principle that the live read of the operation takes sequence priority over the report — read first, report second — because the read is the only management instrument available in real time. The report confirms what the read already found or surfaces what the read missed. An operator who manages from the report without the read is managing a representation of the operation, not the operation itself. The read is real-time and relational; the report is lagging and transactional. Both are required, but the sequence is not optional — inverting it produces an operator who knows what happened last period and cannot see what is happening right now.

Explanation

This is the operating version of the upstream/downstream frame applied to management instruments specifically. The report isn’t wrong, it’s just late by definition — by the time food cost shows on paper, the shifts that produced it are already over. The read is the only tool that exists in the moment the operation is actually happening, which is exactly why it has to come first in the operator’s sequence of attention.

An operator who leads with the report has quietly outsourced his primary judgment to a lagging instrument. He’ll catch problems a period late, always confirming damage instead of preventing it. [Primary Read] doesn’t say ignore the report — it says the report’s job is to confirm or correct what the live read already told you, never to be the first thing you look at to find out how the operation is doing.