Production plan – plan the week and run daily production on the tablet
After reading this article you can use the production plan in Inventory: see what is needed for which delivery date, let Univents plan the week, create orders with a workstation and people, spot deviations and track the time per recipe step in daily production on the tablet.
The production plan shows you what your kitchen has to have ready by which delivery date and turns that into a weekly plan: which recipe is produced on which day, at which workstation and by whom. It reads the delivery dates from your events' delivery notes, breaks recipes down to their sub-recipes and combines the same product into one order as long as the shelf life allows. In the Daily production view the team sees the day's orders on a tablet, with the recipe scaled to the order quantity, and records per recipe step who worked on it and for how long.
What the production plan is for
An example: you need 10 l of tomato sauce for Wednesday and another 10 l for Thursday. The sauce needs 2 days of preparation and keeps for 3 days. The kitchen monitor shows the two quantities separately, each against its own date. The production plan sees that sauce made on Monday is still good on Thursday and suggests a single order: Monday, 20 l.
The plan separates two things:
- Demand is what is needed: product, quantity and delivery date. It comes from bookings and delivery notes and is read only.
- Orders are what you schedule: product, quantity, day, optional time, workstation and people. One order can serve several delivery dates, including just part of a quantity.
You find the production plan under Inventory on the Production plan tab (between Production List and Kitchen). At the top you switch between the Planning view (the week) and the Daily production view (one day).
Requirements
- Activation. The production plan is part of the Production module, together with the kitchen monitor and the recipe prep steps. The module is available from the Core plan; we unlock it on request, on the Production plan tab with Request the Production module. The request goes straight from the app to us, no email program opens. It cannot be booked on your own, but from the Core plan you can try it free for 7 days: on the Production plan tab with Try the Production module free for 7 days. During the test the whole module is open (kitchen monitor, prep steps, production plan); afterwards everything is locked again and you request the module. The Production module can be tried free for 7 days, then on request. If you already use the kitchen monitor, you request the production plan the same way. Without activation, the tab only shows the Request the Production module button.
- Access. The tab is visible to anyone who may access the kitchen monitor and can view Inventory. To plan, the role needs permission to edit Inventory. Read-only roles see the plan but cannot change anything.
- Recipes with the checkbox. Demand only arises for recipes that have Use for kitchen production ticked in the Production section of the product editor. This also applies to sub-recipes: the tomato sauce in the lasagne needs its own checkbox, otherwise only the lasagne appears.
- Shelf life and prep time. Under Timing & shelf life on the recipe you enter Shelf life (days) and Prep time (hours). Without a prep time the production day is the delivery day; without a shelf life the plan combines nothing.
- One delivery note per delivery day. The plan takes the delivery date from the service period of the delivery notes. For multi-day events, create one delivery note per day with that day's items, ideally with a time (see Delivery note per day). Items that are on no delivery note are due at the start of the event.
- Kitchen access for people. You can only assign contacts with kitchen access to orders. You turn kitchen access on in the person's staff record with Portal: kitchen planning. The same switch also unlocks kitchen planning for that person in the Employee Portal.
- Workstations are optional. Without workstations, all orders sit in one shared row.
Creating workstations
Workstations are the rows of the plan, for example “Stove 1”, “Cold kitchen” or “Pastry”.
- Open Inventory → Production plan → Planning and click Workstations.
- Click Add workstation and enter a name.
- Optionally choose, under Default for production categories, the production categories this workstation is responsible for. You can pick the main categories from the Kitchen Categories tab; a product in a subcategory belongs to the workstation of its main category.
- Save the workstation.
Plan the week then creates new orders directly at the matching workstation. If a category is set on two workstations, the one higher up in the list wins; the dialog points this out.
A workstation you don't need right now can be set to inactive. It stays on its existing orders but no longer receives new orders from the proposal. Delete asks for confirmation first; orders of that workstation then appear under No workstation.
Planning: demand and orders of the week
The Planning view always shows one calendar week. Use the arrows to change the week; This week jumps back.
Left: Not yet scheduled. This is the open demand, grouped by product: quantity, delivery date (such as “Wed 11:30” or “Thu (no time)”), event and delivery note. Whatever is scheduled disappears from the list; a partial quantity leaves the rest behind.
Right: the week grid. The columns are the seven days, the rows are the workstations plus No workstation. Each card is an order with product, quantity, status (planned, in progress, done, cancelled), the people's initials, the delivery dates it serves, its origin (automatic or manual) and, once work has started, the actual time.
How demand arises:
- Delivery notes count as draft, finalised and signed. Replaced and deleted delivery notes do not count.
- The quantity comes from the booking. If an item is on several delivery notes, the plan splits the booked quantity across those delivery notes.
- Delivery note without a time: the product has to be ready at the start of the delivery day.
- Sub-recipes have their own demand. They are due when the dish they are part of is produced. Example: the lasagne is delivered on Wednesday and needs 24 hours of preparation, so it is made on Tuesday. The tomato sauce for this lasagne therefore has to be ready on Tuesday, not only on Wednesday. If the same sauce goes into several dishes, you see a separate demand per dish.
- Origin. Under each demand you see what it is needed for, for example “for Pasta Pomodoro · delivery Wed”. For a sub-recipe these are the dishes it goes into.
- Shelf life. If the recipe has a shelf life, the demand and the order show how long the product lasts: usable up to and including Thu.
Notes on an item:
- no delivery note: the item is on no delivery note and is due at the start of the event.
- more on delivery notes than booked: the item is on several delivery notes with more quantity in total than booked. The plan assigns the booked quantity to the earliest delivery dates in order. You schedule such items manually only (note manual only). To fix it, enter only that day's quantity on each delivery note and choose Change in this delivery note only.
- different unit: the item uses a different unit than the product. The plan does not convert units; you schedule these manually only as well.
- Kitchen monitor: 300 of 1,800 done: some of this event's quantity has already been marked done on the kitchen monitor. The note is for orientation only.
Unconfirmed events and bookings in draft are hidden. With Show unconfirmed they appear in grey; they are never scheduled automatically. Demand whose delivery date has passed is collapsed under Past, not scheduled. For a delivery note without a time, this only applies once the delivery day is over.
If the production day of a demand falls in another week, it appears in its own group Plan in week 47 (with the matching week number). Plan the week schedules it there, not in the week you are looking at.
If the list is empty, the plan tells you why: either there is no demand for the week (with a note on where demand comes from), or everything is scheduled, or the only open items come from unconfirmed events and bookings in draft (Show unconfirmed displays them).
The view does not refresh by itself. If someone else changed something, click Refresh.
Plan the week
Plan the week calculates a proposal for the week on screen. The rule:
- The prep time sets the latest production day: delivery date minus prep time. 24, 48 or 72 hours count as whole days, other values as hours.
- The shelf life sets the earliest production day. What you produce on Monday with a shelf life of 3 days can be used up to and including Thursday.
- The order goes on the latest day, but never earlier than the shelf life allows.
- A later delivery date joins the same order as long as the product keeps from the order day until that date.
The tomato sauce example: it has to be ready on Wednesday at 11:30 (10 l) and on Thursday without a time (10 l), prep time 48 hours, shelf life 3 days.
- For Wednesday the sauce has to be started on Monday at the latest (Wednesday minus 2 days).
- Produced on Monday it keeps up to and including Thursday (Monday plus 3 days). So it also covers Thursday.
- Result: one order on Monday for 20 l, serving Wednesday and Thursday.
With a shelf life of only 1 day you get two orders: Tuesday 10 l for Wednesday and Wednesday 10 l for Thursday. Both carry the note Prep time longer than shelf life, because the shelf life wins here. Without a shelf life the plan combines nothing (Monday 10 l and Tuesday 10 l). If the calculated day is already in the past, the proposal schedules the order for today and marks it as due today, tight.
How to apply the proposal:
- Choose the week and click Plan the week.
- Check the rows: new, changed, removed and free from manual order. Deselect any rows you don't want. A line at the top of the dialog summarises the proposal, for example “2 new orders · 1 changed · 1 dropped”. Every removed row states the reason: Already covered by another order, New production day falls outside this week or Demand no longer exists.
- Click Apply. If you close the dialog without applying, nothing changes.
What the proposal never touches: orders you created or changed by hand (Set manually), orders in progress, done and cancelled orders, and orders with recorded time. If a manual order still has free quantity, the proposal counts it first, for example “free from manual order Mon: 15 l”, and only plans the rest. The manual order keeps its quantity and gets the delivery dates assigned.
The proposal only plans orders whose day falls in the selected week; later delivery dates are handled with their own week. If someone else has changed the plan in the meantime, Apply reports “The plan has changed in the meantime — reload” and creates nothing twice. If the demand could not be loaded completely, Plan the week is locked until you reload.
Creating and changing an order manually
- In Not yet scheduled, click Schedule on an item.
- The dialog already contains the product and the open quantity. Choose the day, optionally a time, the workstation and the people. Only contacts with kitchen access can be selected.
- Under Deliveries served you see which delivery dates the order produces for and can adjust the partial quantity per date.
- Click Save order.
Days that don't fit are locked and state the reason: before the earliest day (the shelf life doesn't last until the delivery), after the delivery date, or in the past. If you schedule less than the demand, the rest stays under Not yet scheduled. If the order quantity is higher than the assigned deliveries, the dialog points this out.
To change an order, click its card in the grid; the same dialog opens. As soon as you change the day, time, quantity, workstation or deliveries, the order is Set manually and Plan the week leaves it alone. If you untick that box, the proposal may recalculate the order again.
Orders are not deleted but cancelled: Cancel order asks for confirmation, frees the assigned deliveries again and stops any running steps. A cancelled order disappears from the plan and the daily production and cannot be reopened. If someone has changed the order in the meantime, the dialog tells you; reload and save again.
Deviations after scheduling
If a booking or a delivery date changes after scheduling, the plan does not recalculate anything. It shows the deviation on the order:
- Demand now 21 l, scheduled 20 l: more was booked, for example lasagne for 44 instead of 40 guests. The missing litre appears again under Not yet scheduled.
- over-scheduled +10: more is scheduled for this delivery date than is needed, for example because two orders serve the same date.
- Delivery moved: now Fri 11:30: the delivery note has a new date. If the order day no longer fits, the note is shown in red.
- Day no longer fits (red): the order day is before the earliest day (too early, earliest …, with the shelf life) or after the delivery (after delivery, latest …).
- Demand no longer exists: the item was deleted, or the delivery note was replaced or deleted.
You adjust the order yourself: open the card, change the quantity or day, save.
Daily production on the tablet: start, who is working, stop
The Daily production view is built for the tablet at the station: large buttons, one day, orders grouped by workstation. Every role with access to the production plan may view it; starting, stopping and Order done need the same permissions as planning.
- Switch to Daily production at the top. Use the arrows to change the day; at the top you filter by workstation or person.
- Each card shows product, quantity, time, people, status and delivery dates. Tap it to open the recipe: the ingredients scaled to the order quantity (such as Ingredients for 20 l) and the recipe's steps. If the recipe has no steps, there is one step Preparation.
- Tap Start on a step. Univents asks Who is working on this step? and shows the assigned people. If nobody is assigned, all contacts with kitchen access can be chosen, and the selected person is assigned to the order.
- The time is running. With the first start the order is in progress.
- Tap Stop when the step is finished. The actual time then shows on the step and on the card in the planning view.
- When all steps are finished, tap Order done. This only works when no step is running. If that was a mistake, reopen the order with Reopen.
Several people can work on the same step at the same time, each with their own time. The same person cannot start the same step twice; Univents then reports “This step is already running.” If you start before the order's earliest production day, the note Too early appears with the day from which it fits; nothing is stopped because of it.
Stopped times can no longer be changed or deleted. Besides the person doing the work, Univents also stores who was logged in on the tablet. If a step is later deleted or renamed in the recipe, the recorded times keep the old text. Step times do not count as working time in staff time tracking.
Daily production does not refresh by itself either: what was started on another device shows up after Refresh. How to create steps in a recipe is described under Recipe steps.
Difference from the production list and the kitchen monitor
- Production list: a list or printout per event or across several events. It says what has to be produced and packed, but not on which day and by whom.
- Kitchen monitor: the daily board with the status open, in progress and done per item, live on all devices. It shows an item on the day of the event and, if a shelf life is set, on the days before.
- Production plan: plans when, where and by whom something is produced, combines delivery dates across days and events and records the time per recipe step.
All three read the same bookings but work independently of each other. Order done in the production plan reports nothing to the kitchen monitor and releases nothing on the packing list. Kitchen items can only be packed once the kitchen monitor shows them as done, so whoever packs keeps marking them done there.
The two also calculate shelf life slightly differently: the production plan counts whole calendar days, the kitchen monitor locks an item to the hour. The “too early” note can therefore differ by a few hours.
Limits of this version
- No Employee Portal: the production plan exists only in the back office. So a Univents user whose role may edit Inventory is logged in on the tablet.
- No link to the kitchen monitor and the packing list (see above).
- Deviations are only shown, not applied automatically.
- No live refresh; use Refresh instead.
- Units are not converted.
- Sub-recipes follow the demand of the dish, not its scheduled order. If you schedule the lasagne one day earlier by hand, the sauce stays due on the calculated day.
- Step times stay separate from staff working time.
Production plan in the AI chat
The AI assistant knows the production plan. It answers questions such as “What does the hot kitchen have to produce next week?” and creates or changes individual orders, for example “Schedule 20 l of tomato sauce on Monday at Stove 1”. The same rules apply as in the dialog: if the day is before the earliest production day, after the delivery date or in the past, the assistant says so instead of creating the order. Plan the week is only available in the production plan itself.
Frequently asked questions
Why is a product missing from the production plan? Check in order: is the product a recipe with Use for kitchen production ticked? Is the event confirmed (otherwise only with Show unconfirmed)? Is it cancelled? Has the delivery date already passed (then it is under Past, not scheduled)?
Why is a product due at the start of the event instead of on the delivery day? The item is on no delivery note, or the delivery note has no service period. Create one delivery note with a date per delivery day.
Why does “Plan the week” not schedule an item? It carries one of the notes more on delivery notes than booked or different unit, belongs to an unconfirmed event, or its order day falls in another week. You schedule the first two manually.
Why is the tomato sauce due earlier than the lasagne? A sub-recipe has to be ready when the dish it is part of is produced. With 24 hours of prep time for the lasagne, the sauce is due one day before the lasagne's delivery date.
Is the recorded time paid as working time? No. The times per recipe step serve as a record of who produced what and when. You keep recording staff working time in time tracking.