
In brief: A caterer without temporary workers is a caterer who turns down events. Managing temporary workers is the operational core of the business: building a reliable pool, tracking availability, mobilising quickly, handling last-minute replacements, automating Dimona (Belgian employee registration system) declarations. This guide covers the full temporary worker management cycle, from building the pool to post-event billing, and shows how Shyfter industrialises this process.
A caterer operates with a small permanent team: a chef, one or two permanent cooks, a logistics manager, a sales person. Everything else relies on temporary workers. A 200-guest wedding may require 25 to 30 people on site. A corporate cocktail needs 8. A corporate brunch, 5.
The ratio of permanent to temporary staff is often 1 to 5, or even 1 to 10 in peak season. This dependence on temporary workers is not a choice: it is the very structure of the business. Activity is event-based, needs fluctuate from week to week, and maintaining 30 permanent employees when there are only 2 events per week in January is not viable.
Basic rule: your pool must be 3 to 4 times larger than your maximum need. If your busiest weekend of the year mobilises 60 temporary workers, aim for a pool of 180 to 240 people. Why such a ratio? Because temporary workers are not exclusive. They work for multiple caterers. They have classes, exams, another job. On the day, you will never get a 100% response rate.
For each temporary worker in your pool, centralise essential information:
Done manually by phone and WhatsApp, this process easily takes half a day per event. With 4 events per weekend, you spend half your week calling temporary workers instead of preparing events.
Shyfter automates sending mission proposals. You define the positions to fill, the system identifies available and qualified temporary workers, and each person receives a push notification with the mission details. The temporary worker accepts or declines with a tap.
Last-minute cancellations are part of daily catering life. The cancellation rate in the 48 hours before an event is around 5–10%. For a 30-person event, that means 1 to 3 cancellations on average.
When a temporary worker cancels their mission in Shyfter, the system automatically triggers an alert, identifies available and qualified temporary workers not yet mobilised for that slot, and sends them an urgent replacement proposal. You save hours of phone calls.
Each temporary worker engaged for an event must be subject to a Dimona declaration before the start of the service. For an active caterer, the volume is considerable: 4 events per weekend x 20 temporary workers average = 80 declarations per week. In peak season, this figure can double.
With Shyfter, the Dimona workflow is integrated into the mobilisation process: the temporary worker confirms, the system verifies their administrative data is complete, the Dimona declaration is generated automatically and sent to the NSSO. Any modification triggers automatic update of the corresponding declaration.
Temporary workers are not full-time employees. Their availability changes from week to week. Set up a regular collection system: monthly availability per temporary worker, weekly updates, anticipated unavailabilities (holidays, exams, personal commitments).
Shyfter lets temporary workers update their availability from the mobile app at any time. Track the response rate of each temporary worker. A temporary worker who never responds to mission proposals clogs your pool without contributing to it.
After each event, briefly evaluate the temporary workers who participated. A simple rating (1 to 5) on a few criteria: punctuality, service quality, attitude, cleanliness, versatility. These evaluations feed the profile of each temporary worker and guide future assignments.
Aim for a pool 3 to 4 times your maximum simultaneous need. If your busiest weekend of the year requires 60 temporary workers, build a pool of 180 to 240 people. In practice, only 25–30% of your pool will be available for any given slot.
Confirm missions at least 2 weeks in advance. Send reminders 48h and 24h before the event. Always plan 10–15% more staff. Identify standby temporary workers ready to step in at J-1. Pay better for late-confirmed missions. And above all, retain your best temporary workers by treating them well: fast payment, priority missions, decent working conditions.
A Dimona declaration is required for each distinct service. If a temporary worker works for you on a Saturday and a Sunday for two different events, those are two separate declarations. The volume of declarations is therefore directly proportional to the number of temporary workers multiplied by the number of events.