Notes pile up at the bar.
When several people record orders separately, agree how each order reaches the responsible station.
Want to stop carrying order slips to the bar or deciphering handwriting? This guide takes you through a complete rehearsal: assortment and stations, access and devices, a mixed test order, questions and handover, and a joint decision. At the end you can say with reasons whether the change passed or not. Bierblock sends orders digitally; the devices need internet access, and you agree a fallback for longer interruptions.
For everyone who's had enough of the notepad
Each task states an expected result. Record in “Actually observed” what really happened during the rehearsal. Two rows are filled in as examples and can be overwritten. The list does not guarantee error-free operation; it makes the test traceable and the decision checkable.
Entries are not saved. Print the completed list before reloading, or record it separately. Your browser will ask before leaving the page with unsaved entries.
The Problem
A few simple checks help identify where written handovers can become ambiguous.
When several people record orders separately, agree how each order reaches the responsible station.
Abbreviations can be read differently. Agree on product names and quantities before the event.
Plan the post-event review in advance and keep order quantities distinct from payment and stock records.
The Solution
Bierblock supports orders between helpers, kitchen and bar. Responsibilities, test criteria and a fallback remain the festival team’s task.
Check product names, options and prices, and assign each item to the station that actually prepares it.
Set up helper and station access, clarify correction and cancellation roles, and test the actual devices at the venue.
Send one drink and one meal to table 41 and check whether the same order number appears at Grill and Kellnertheke.
Name contacts, rehearse the shift handover and agree the fallback for longer interruptions in writing.
Record passed, not passed or passed with conditions, and assign every open condition to a person and a date.
The team selects table 41 and adds a small beer and a Kasnudel with salad. The order shows two items for €12.00 before sending.

The kitchen ticket shows the same order number and table, but only the meal.

The bar ticket also carries order no. 1 and table 41, but only the drink.

Benefits at a glance
The image shows the mixed test order group from the print preview of the same checklist. The expected line states the test criterion; the result column records what was observed. The example uses test data.
Expected: order no. 1 at table 41 with the meal at Grill and the drink at Kellnertheke. Observed: both tickets show order no. 1 and status Open; Grill shows the Kasnudel, Kellnertheke the small beer.

The checklist ends with a joint decision: passed, not passed or passed with conditions. It does not promise error-free operation.
Frequently asked questions
Everything about setup, usage and costs.
Ready?
Open the public demo to explore order taking, the kitchen and the bar. No account is needed. To prepare your own setup, start a test event afterwards.
Start without an account. Register to save. Your own demo events allow up to 20 test orders.
See pricing