One booked event creates the production list and the shift plan at the same time. Quantities, shifts, tracked hours and labour cost all follow the same guest count instead of living in a scheduling app, an inventory tool and a spreadsheet.
7-day free trial · no credit card · live in minutes
AI generatedThree steps, one data base: what the event says drives both kitchen and staff.
Guest count, menu and date are entered once, on the event. Univents derives the production quantities and the staffing demand per job from them.
One entry instead of three tools.
The production list goes to the kitchen monitor, the staffing demand into the shift plan. Both sides work from the same numbers, even when the guest count still changes.
Kitchen and staff stay in sync.
The team clocks in and out in the staff portal. Approved hours feed the payroll export and show the labour cost of that event at the same time.
Labour cost sits on the event itself.
Production demand and staffing demand come from the same number.
As soon as an event is confirmed, Univents derives both: the quantities for kitchen and purchasing, and the staffing demand per job, from set-up through kitchen and service to tear-down. If the guest count changes, both sides follow.
That removes the usual break between scheduling app and inventory software, where every change has to be entered twice and one of the two lists eventually goes stale.
AI generatedProduction list and kitchen monitor come straight from the booking.
Every production item appears on the kitchen monitor with quantity, lead time and allergens. The team moves it from open through in progress to done, visible to everyone on site.
For purchasing and prep, the same basis prints as a production list per event or aggregated across several days.
AI generatedShifts belong to the event, not to a separate weekly roster.
Shifts are planned per job, with times, meeting point and required qualification. The team sees its assignments in the staff portal, reports availability and requests time off right there.
Temporary staff and freelancers do not need a company account for this: they reach their shifts through a personal link, including push notifications when something changes.
AI generatedTracked hours get approved, exported and turned into cost.
The team records working hours in the portal, management approves them. From there come the payroll export for your accountant and the labour cost per event, with no spreadsheet in between.
So next to the revenue of an event you also see the staffing effort, based on the hours actually worked rather than the ones originally planned.
AI generatedMost operations combine two systems: a scheduling app for staff and inventory software for the kitchen. Univents covers both in one product because both sides come from the same event. Guest count and menu produce the production quantities, the jobs produce the staffing demand. When the booking changes, kitchen and shift plan change together.
For rostering itself, it is. What it lacks is the link to the event: a scheduling tool does not know how many portions are produced, which items are on the quote and what gets invoiced in the end. That is exactly where double maintenance starts. In Univents, shift, production item and document all hang on the same event.
The production list is derived from the booked items and the guest count. It can be viewed and printed per event or aggregated across several days, and it appears as items with a status on the kitchen monitor. If the guest count is corrected, quantities are recalculated.
Yes. Besides the regular login there is a personal link through which temporary staff reach their shifts, hours, documents and messages without creating an account. On a phone the portal can be installed like an app and sends push notifications when a shift changes.
Staff clock in and out in the portal or add hours later. Management approves the entries. Approved hours feed the payroll export for your accountant and the labour cost of the event. If hours are billable to a client, they can be adopted as line items on a document.
Yes. Staff report availability and request time off in the portal, management approves or declines. Both feed into shift planning, so nobody is scheduled for a day they are not available.
Yes. Labour cost per event comes from the tracked hours and the stored rates and sits in the event's finance area next to revenue and cost of goods. Because the figure is based on actual hours, it does not drift from reality when a shift ran longer than planned.
For caterers, event venues and event catering from a one-person operation up to around 200 staff. What matters is less the size than the setup: as soon as the same event involves both production and staffing, a shared data base saves more time than two specialised tools.
Try Univents for free and see how simple event management can be.
We use cookies for statistics and — with your consent — for marketing (Google, Meta, LinkedIn) to improve our advertising. Details: Cookie Policy