Shift desk / Bandista
The work before service
July close / pre-service board
A calmer board for
real service data.
Recipes, prep, batch planning, and PMIX demand now sit together in one source-aware desk. The unknowns stay marked until a manager or a measurement closes them.
Uploaded source sheets stay preserved. Manager review and measured-yield gates remain visible before release.
Today's control list
Open loops
Source ledger
What came through
Batch quantities come from the uploaded recipe and measured prep yields. Pickup additions remain separate so the team knows what belongs in the batch and what is added per drink.
Library / active & review
Recipes with a paper trail.
Batch, service-build, and PMIX demand coverage are visible on every record. Manager decisions can be recorded here.
Service / uploaded pickup chart
Cocktail cards for the floor.
Each card uses the pickup-chart wording inside the app: the source build, service method, presentation details, and the operational batch split. The original scan stays available when someone needs to verify the source.
Production / house-made
Prep is a chain, not a line item.
All 28 supplied prep records are present with ingredients, yields, and source-grounded method notes.
Restored records
Known prep library
Yield standard
Measure the thing you will actually pour.
Source yields are retained where supplied. Production yield still needs a measured result at working temperature, without added air.
Production / batch planner
Build the prep packet before service.
Choose a recipe. The uploaded batch base and service build appear automatically; enter usable batching carried over from the previous prep so the planner only asks for what is still needed.
New production record
Batch inputs
Verification guard
Two signatures before release.
Compare actual output with planned output and explain variance.
Direct ingredients and nested house-prep quantities are checked recursively.
Keep the packet together with the measured result and any variance note.
Production packet / local pilot
Batch packet
Add each recipe needed for the prep run, then open the packet as one print-ready document.
Forecast / source intake
Turn a PMIX into prep decisions.
Upload a PMIX screenshot or report for the manager to review. The source image stays attached to the import, and only confirmed rows should drive weekly batch planning.
Source report / current pilot data
Bandista demand rows
Average weekly usage is calculated from the source period. Use “Plan weekly batch” to carry the rounded starting target into production.
Planner rules
Demand first. Yield second.
Keep the source file attached to every import.
Use quantity sold as demand, not as a batch volume.
Confirm screenshot rows before they affect planning.
Push linked prep requirements through every nested recipe.
Use the weekly average as the starting portion count, then adjust for events and reservations.
Control room / feedback
Keep the uncomfortable evidence.
Pilot issues are part of the product. Each one gets a severity, a reproduction path, and a next owner.
Local issue log
Open review queue
Gate / readiness
What must be true before go-live.
This is the handoff between a source-connected prototype and a shared operational system.
Rebuild readiness
Source-connected pilotThe real data layer is present locally. Cloud ownership, manager decisions, and live validation remain open.
Activation gate
Required inputs
Department model
One app, multiple outlet assignments.
A team member can be assigned to more than one outlet. Supabase Row Level Security still limits each person to the departments assigned to them.
Source intake / manager review
Upload the sheets the app should work from.
The local pilot stages the filename and review status. The live Supabase version preserves the original file and extracts reviewable rows before anything changes in production.