Meal vouchers for crew, staff and artists – a setup that counts
Catering for crew is one of the biggest hidden costs of an event. The voucher system decides whether you pay for the meals you planned or the meals that were printed.
Decide the unit
Is a voucher “one meal” or “lunch on Tuesday”? Tie vouchers to a day. A meal voucher valid all weekend gets saved, traded and stacked; one valid today gets used today or not at all.
Hand out to leaders, not to everyone
A crew manager can’t send 200 individual vouchers before breakfast. Give each team leader their team’s meals for the day, and let them pass meals on to their people. You keep control of the total; leaders handle the names.
Keep food and drink apart
If artists get both drinks and meals, make sure each outlet only redeems its own kind. Otherwise unused meals turn into drinks after midnight.
Copies and screenshots
Printed vouchers get photocopied. A digital voucher with a server-side balance can be copied too – but every copy draws on the same count, so it can’t multiply meals.
Staff meals in restaurants
The same setup works for staff meals: a link per staff member per day, scanned by the kitchen. It replaces the notebook by the pass and shows what staff meals actually cost per week.
How it works with RONDZA
In RONDZA you create food (or drinks) on a link for a chosen day, give it to a team leader, and they pass meals on. The kitchen login scans food, the bar login scans drinks. See created, used and left per day – free during early access.