What exactly was ordered?
Whether 0.5 l or 0.3 l beer, which Radler variant, how many schnitzels with fries: after the festival, tally lists can no longer reconstruct this.
After the last beer
Club festival evaluation: what was ordered — and when?
After the festival, Bierblock answers the questions that otherwise leave only paper slips and memories: what was ordered, when, at which station, at which table — and by whom? Which checkouts are documented? The evaluation shows recorded events, not a counted cash balance or profit.
Work material
Debrief: from finding to the next attempt
Document an observation before you define a cause or a measure. Connect order and checkout data with feedback from bar, kitchen and service.
Example from the evaluation: during the peak on 24 July between 7 and 8 pm, 120 orders were recorded in the marquee; table 5 leads across both evenings with 44 units. These figures do not prove waiting time. Keep team observation and data source separately; evaluate the measure again at the next festival.
| Step or entry | Data source and observation | Team feedback | Possible cause (hypothesis) | Measure for the next festival | Responsible | Check at the next festival |
|---|---|---|---|---|---|---|
Scroll horizontally to see the full table.
Entries are not saved. Print the completed sheet before reloading or note the values separately.
The Problem
Why nobody knows what really happened after the festival
The evaluation answers concrete questions about the recorded flow. Six questions are at the centre — and each has its own view.
When did everything arrive at once?
Order times show which hours recorded a lot. Whether the team was waiting during the same period is not written on any slip.
Who took the money — and who only took orders?
Orders and checkouts often run through different people. Adding both together mixes two figures that must stay separate.
The Solution
Six questions, six views in the evaluation
Each view answers one question. Together they describe how the festival ran, without anyone having to sort paper slips.
What was ordered?
Quantities sold per product and variant — including sizes, variants and extras.
View drink managementWhen?
The timeline and chronological log sort orders, checkouts and cancellations by time.
At which station?
Quantities per station show how drinks and food were distributed across bar and kitchen.
In which room and at which table?
The room report breaks order quantities down by room and table.
View table managementBy which person?
The helper view counts recorded orders per person — without judging working time or performance.
View volunteer managementWhich checkouts are documented?
The per-person settlement compares collected cash, recorded revenue and orders per person.
Order value, checkout amount, cash, consumption, profit: five different figures
The evaluation documents what was recorded in the system. These five figures are often confused during the debrief — only the first two are in Bierblock.
| What the figure shows | What it does not replace | |
|---|---|---|
| Recorded order value | Sum of non-cancelled order lines at the stored prices. Free-of-charge items are excluded. | Not a payment receipt: whether and how someone paid is not part of the order. |
| Documented checkout amount | Amounts entered by the team when collecting payment, with person and time. | Not an automatically counted cash balance; handovers and shortages must be checked separately. |
| Cash in the till | The balance actually counted after the festival. | Cannot be read from Bierblock — you count the till and change yourselves. |
| Consumption | The quantity actually poured or served, including shrinkage, breakage and free drinks. | Cannot be derived from order quantities; this needs counting or a stock reconciliation. |
| Profit | Revenue minus cost of goods and expenses. | Cannot be derived from order values; this needs purchase and cost accounting. |
01
What was ordered?
The product view sums non-cancelled order lines per product and shows the stored variants: size, variant and extras. Lines with “Sold from … to …” name the period in which the product was ordered.
- Observation
- Beer leads with 1,011 units, of which 913 × 0.5 l and 98 × 0.3 l. Bratwurst (564) and lemonade (486) follow. Radler’s 402 units split across four variants; spritzer’s 414 across two sizes. The sales period runs from 24 July, 5 pm, to 25 July, 11 pm.
- Next check
- Check with purchasing whether the 913 large beers match the reorder level. Whether the small share was a deliberate guest choice only the team can say — ask the bar before planning fewer 0.3 l bottles for the next festival.
02
When were orders taken — and when was cash collected?
The chronological log lists order, checkout and cancellation events in the order they were recorded. Each entry names time, person, table or direct sale and amount; the number at the top counts all events.
- Observation
- The example has 2,520 events. On 24 July at 5 pm, order no. 844 for table 23 is recorded by Jonas for 20.00 €; in the same time window Petra documents the checkout of 20.00 €.
- Next check
- Compare dense time windows with the shift plan. Whether anyone waited during those minutes is not in the log — ask the shift and check whether order and checkout fall apart.
03
At which station was the work done?
The station view sums order lines per station and shows how many orders were completed or cancelled. An order with food and drinks appears at both stations.
- Observation
- Bar: 2,652 units and 11,234.56 € from 933 orders, 912 completed and 6 cancelled. Kitchen: 1,383 units and 12,778.26 € from 666 orders, 651 completed and 3 cancelled.
- Next check
- Check with kitchen and bar whether the higher value with fewer units matches the actual effort — for example schnitzel with sides. A conclusion about overload is only possible if the team reports waiting time.
04
In which room and at which table?
The room view sums orders per room and table. Tables without a room assignment appear under “No room”; in the example that is the direct sale.
- Observation
- For the marquee, the evaluation shows 482 units and 2,043.77 € from 159 orders, 156 completed and 1 cancelled. The peak is on 24 July between 7 and 8 pm with 120 orders. Table 5 leads the room with 44 units and 198.89 €.
- Next check
- Compare the table distribution with the service plan: who served table 5, and was the route longer? Derive a table assignment for the next festival only in conversation, not from the figures alone.
05
Which person recorded the orders?
The helper view counts recorded orders per person and shows how many were completed or cancelled. Cash is explicitly not included here; it appears in the per-person settlement.
- Observation
- Petra: 709 units and 4,224.26 €, 263 of 267 orders completed, 1 cancelled. Berni: 708 units. Markus: 687 units, recorded at the station. The names come from the example event.
- Next check
- Use the figures for the handover, not as a performance ranking: ask who worked which shift and whether orders stayed open. The collected amounts are in the per-person settlement.
06
Which checkouts are documented — and do they cover the order value?
The per-person settlement compares collected cash, recorded revenue, units sold and orders. The displayed time span is a rough estimate from the first and last recorded order or checkout. The app labels it “work time (approx.)”; it means the activity span, not actual hours worked – breaks and periods without recorded actions are not included.
- Observation
- The example ledger labelled “Kellner:in 2” collected 2,705.36 € in 212 transactions; recorded revenue is 2,802.36 € (646 units, 212 of 219 orders completed, 2 cancelled).
- Next check
- The difference between collected and recorded is not an error but a concrete question for the handover: did someone else collect, or is a transaction missing? Reconcile it with the till and receipts — Bierblock does not count cash.
Take it with you
PDF, CSV or anonymised AI prompt: take the evaluation with you
Use the “Export PDF”, “Export CSV” and “Copy anonymized for AI” buttons to start each output. Three outputs for three purposes: a report for the minutes, raw data for your own tables and an anonymised prompt for a first summary.
PDF report with section selection
The dialog lets you choose the sections: overview, sold quantities, quantities per station, per-room report, timeline, quantities per helper, settlement and event timeline. Sections without data do not appear.
Contains title, creation date and the selected tables — for printing and the minutes.
CSV raw data
One row per order line with timestamp, room, table, person who took the order, station, product, quantity, unit price, subtotal, status, cancellation details and a free-of-charge flag.
For Excel and your own analysis. The CSV contains the real names of the people who took orders and no total rows.
Anonymised AI prompt
Copies the figures as a formulated prompt to the clipboard. Person names are replaced by role pseudonyms such as “Waiter 1”; product, station and room names remain.
For pasting into a chat assistant. Check the answer against the tables before adopting a recommendation.
Sample report as PDF
Generated from test data of the example festival. The report contains all sections except the full event timeline (2,520 events); you can add that separately in the dialog.
The sample report is a test-data export, not a settlement. It shows which sections the export contains; your file contains your own data.
Benefits at a glance
How Bierblock helps you
- Follow order quantities, peak times and stations
- See collected cash and recorded revenue separately
- Take along a PDF report, CSV raw data or an AI prompt
Fictional example
An example from festival operations
Example: two festival evenings in one evaluation
The fictional “Feuerwehrfest am Dorfplatz” with two evenings, two stations and 121 tables comes to 1,599 orders, 4,035 units sold and 24,012.82 € in recorded order value. The per-person settlement shows 2,705.36 € collected for one server against 2,802.36 € recorded revenue. Such differences are the material for the debrief. The full PDF report is available as a download further down; the figures come from test data, not from a customer event.
Frequently asked questions
What organisers often ask.
Everything about setup, usage and costs.
- Do I need to set anything up for the evaluation?
- No. The evaluation is created automatically from the orders recorded during the festival — without extra entry or configuration.
- What exactly does the evaluation show?
- Order quantities and order values, documented checkout amounts as well as recorded times, stations, rooms and people. The data-basis table explains what these figures do not replace.
- Can I export the figures?
- Yes, in three ways: as a PDF report with selectable sections, as CSV with one row per order line, or as an anonymised AI prompt for a first summary. The prompt does not replace your own review of the tables.
- Why do collected cash and recorded revenue differ?
- Recorded revenue is the value of the orders taken. Collected cash is the money a person entered when taking payment. The two can differ if someone else collected, a transaction is missing or an order was cancelled. The per-person settlement shows both side by side.
- Can the team follow checkout amounts per person at a handover?
- Yes. The per-person settlement assigns collected amounts and recorded orders to each person and can support an organisational handover. It does not measure working time and does not confirm that all cash was handed over; count and reconcile money separately.
- Does the evaluation replace a settlement or accounting?
- No. Bierblock documents orders and recorded checkouts, but does not handle cash or external card payments and does not create tax receipts. Order value, checkout amount, cash, consumption and profit are different figures.
- Is the data kept after the festival?
- The event data remains available in the account according to the applicable plan and account terms. A cross-festival comparison view is not promised here; for your own debrief, use the exports.
Ready?
See how your team could take orders.
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.
Open the demo — no sign-upBuild your own test event
Start without an account. Register to save. Your own demo events allow up to 20 test orders.
See pricing