Sample result
Kitchen Dashboard Builder for Restaurants
The owner asked this:«On Saturdays my pass jams, this week four dishes came back to the stove and yesterday I threw out half a pot of beans. I want to see my kitchen in numbers.»
① Block A · the kitchen dictionary and the pass by dish
| Indicator | Formula | Data source | Frequency | Owner | Numeric target |
|---|---|---|---|---|---|
| Ticket time by dish (median) | min from order ticket to pass | POS + pass clock | Daily | Head chef | Platter ≤ 14 min |
| Ticket time by dish (peak) | worst 10% of service | POS | Daily | Head chef | ≤ 22 min |
| Returns with reason | returned ÷ served | Pass log | Daily | Head chef | ≤ 1% |
| 86s and leftovers | time of the 86 · % left over | Production plan | Daily | Manager | 0 86s before 21:00 |
| Sample grammage | real weight ÷ standard recipe | Pass scale | Weekly | Head chef | ±5% |
SUPUESTO: the Platter's 14 min standard does not come from an industry reference — none exists that fits this menu. The median of this kitchen's last 4 weeks is taken and set as a provisional ceiling. If measuring at peak hour showed a real median of 18 min, the standard rises and what changes is not the target but the bottleneck that has to be opened.
The pass this week: the Platter runs at a 13 min median and a 26 min peak. Saturday's jam IS the Platter — the star dish, as usual — and the bottleneck is the pork crackling cut to order at peak hour. Measurable change proposed: cut in short batches between 12:30 and 14:00 and read the peak again the following Saturday.
② Block B · the cocina.html file, four blocks on one screen
Returns with FIXED reasons (names do not change, or the frequency does not accumulate):
| Reason | This week | 4 weeks | Trend |
|---|---|---|---|
| Doneness of the protein | 3 | 9 | ▲ most frequent — THIS one gets fixed |
| Temperature | 1 | 4 | = |
| Presentation | 0 | 2 | ▼ |
| Order-ticket error | 0 | 3 | ▼ (already cross-linked to the operations board) |
Production against plan: sancocho 86'd at 20:15 on Tuesday and beans at 38% left over on Wednesday. Thursday's plan drops the beans to half a pot and raises the sancocho meat; what is left over goes out labelled into FIFO rotation. The plan recalculates on tomorrow's expected covers, with delivery counted separately because it consumes production at other hours.
The file opens from the desktop, with no connection and no libraries; the close-of-service cells are filled in under 5 min and where data is missing the cell says PENDING with its owner.
The full example has 1 more part(s): you see them inside the library, with your account.