Managing Casual Workers in Events

Why casual worker management is the differentiating factor in events

A caterer managing 5 permanent staff but mobilising 80 to 200 casual workers per month is not managing personnel. They are managing an ecosystem of freelancers, student workers and agency workers whose availability changes every week. The quality of that ecosystem directly determines the company's capacity to accept and deliver assignments.

The challenge is not finding casual workers. Candidates are plentiful, especially among student workers. The challenge is knowing, at any time, who is available, who is competent for which role, who is reliable and whose Dimona declarations are already in order. Without this visibility, every event starts with a cascade of phone calls.

Companies that invest in a structured pool management tool save time, reduce cancellations and improve service quality. It is a direct competitive advantage.

Building a solid casual worker pool

Defining the required profiles

Before recruiting, map the skills you regularly need. In events, the standard profiles are:

• Service and catering: waiters, bartenders, commis, head waiters
• Reception: hostesses, stewards, cloakroom
• Technical: sound technicians, lighting technicians, riggers, installers
• Logistics: runners, handlers, drivers
• Security: certified officers, first-aiders
• Coordination: production managers, team leaders, supervisors

Each casual worker in your pool must be associated with one or more of these skills. A waiter who can also tend bar is more valuable than a waiter only.

Sizing the pool

The basic rule: your pool must be 2 to 3 times larger than your maximum simultaneous needs. If your largest event mobilises 100 casual workers, your pool must contain 200 to 300. This oversizing compensates for unavailability, cancellations and event overlaps.

For festival season (June–August), increase this ratio. All your casual workers are being solicited by other employers at the same time. Start recruiting reinforcements as early as March–April for the most in-demand profiles.

Recruiting continuously

Recruiting casual workers is not a one-off activity. It is an ongoing process. Your pool naturally degrades: students finish their degrees, casual workers find permanent jobs, others move away. Plan a constant inflow to compensate for departures.

The most effective channels in events:

• Word of mouth between casual workers (your primary recruitment channel)
• Hotel and hospitality schools and universities (partnerships for internships and student jobs)
• Sector Facebook and WhatsApp groups
• Ads on student job platforms
• Spontaneous applications via your website

Tracking availability in real time

The problem of stale data

A casual worker pool whose availability data is three months old is useless. Students change their schedules every semester. Casual workers hold multiple jobs. A casual worker "available every weekend" in September may not be in December.

Without regular updates, you spend more time checking availability by phone than scheduling the event. This is the classic trap of the Excel spreadsheet with an "availability" column that is never updated.

The dynamic availability system

With Shyfter, each casual worker accesses the mobile app and indicates their availability for the coming weeks. When an event is coming up, you see in one click who is available for the relevant date and time slot. You filter by skill, geographical area and reliability history.

This system eliminates cascade calling. Instead of calling 30 people to find 15 available, you target directly those who have confirmed their availability.

Prompting availability updates

Even with a tool, some casual workers forget to update their availability. Set up an automatic reminder: every Sunday evening, a notification asks casual workers to confirm their availability for the coming two weeks. Those who do not respond after two reminders are marked as "unconfirmed" and are not prioritised.

Mobilising quickly: from schedule to assignment

The mobilisation workflow

A client confirms an event. Here is the efficient mobilisation process:

1. Define needs: number of people per role, per phase (setup, event, breakdown), per time slot
2. Filter the pool: confirmed availability for the date, required skill, geographical proximity to the venue
3. Send proposals: push notification with details (date, venue, schedule, role, pay)
4. Collect confirmations: first come, first served, or manual selection
5. Generate documents: Dimona declarations, contracts if required
6. Confirm the schedule: final notification with all practical information

This process, which takes 4 to 6 hours by phone and email, is reduced to 30–45 minutes with a suitable tool.

The rapid confirmation system

Confirmation speed is critical. A casual worker receiving a proposal must be able to confirm or decline in one tap on their phone. No email to open, no number to call back, no form to fill in. The simpler the process, the higher and faster the confirmation rate.

Managing refusals and non-responses

Always plan a waiting list. When you send proposals to 25 casual workers for 20 roles, the extra 5 are your safety net. If a casual worker declines or does not respond within 24 hours, the role is automatically offered to the next on the list.

Dimona declarations: the bottleneck

The volume of declarations in events

In events, each assignment by a casual worker requires a Dimona declaration. A caterer organising 4 events per weekend with 30 casual workers each generates 120 declarations per week. During festival season, this figure can double or triple.

Managing this volume manually is a major risk: omissions, date errors, late declarations. Every missed declaration exposes the company to NSSO penalties.

Automating via Shyfter

With Shyfter, the Dimona declaration is generated automatically as soon as the schedule is confirmed. For each casual worker confirmed on an event, the system creates the declaration with the correct dates, hours and data. You confirm in bulk, and it is done.

In the event of a last-minute modification (replacement, cancellation), the declaration is automatically updated. No risk of forgetting to update a Dimona after a schedule change.

Last-minute replacements

The classic scenario

Friday evening, 10pm. A casual worker sends you a text: "Sorry, I can't make it tomorrow." The event starts at 8am. You have 10 hours to find a replacement with the right skills, available on a Saturday at 8am, and file the Dimona declaration.

This scenario happens regularly. The drop-out rate in events ranges from 5 to 15% depending on the season and event type. For a 100-person event, expect 5 to 15 no-shows.

The systemic solution

The solution is not to select better casual workers (even the best ones cancel sometimes). The solution is a system that enables fast replacement:

• Reserve list: for each event, identify 10 to 15% of casual workers "on stand-by" who can be activated quickly
• Targeted notification: in the event of a cancellation, send a proposal to available casual workers with the right profile, sorted by geographical proximity
• Instant confirmation: the first to confirm gets the assignment
• Automatic Dimona: the declaration is generated upon confirmation, even at 11pm the night before

Tracking reliability

Not all casual workers are equal in terms of reliability. Some confirm and show up consistently. Others cancel one time in three. Implement a reliability score based on history: number of accepted assignments, number of cancellations, punctuality at clock-in.

This score allows you to prioritise reliable casual workers when assembling teams. It is not discrimination; it is operational management. A casual worker who cancels 3 assignments out of 10 costs you more than a slightly less skilled one who is always present.

Managing student workers in the pool

The 475-hour counter

Student workers are a valuable resource in events: available at weekends and in summer, motivated, and benefiting from reduced social contributions for the first 475 hours. But tracking these hours is your responsibility as employer.

A student worker often works for multiple employers. You cannot control the hours they work elsewhere. Regularly request a certificate of the remaining balance via Student@Work, and integrate this data into your management tool.

The exam period

In January and June, your student workers disappear. This is predictable and non-negotiable. Prepare for these periods by increasing the share of non-student casual workers in your pool. For festival season (June–August), the flow reverses: student workers are massively available, but the risk of exceeding 475 hours increases.

Multi-employer management

A casual worker who works for you probably also works for 2 or 3 other caterers or agencies. That is the reality of the sector. This creates scheduling conflicts: the casual worker who confirms Saturday may receive a better offer in the meantime.

To minimise this risk:

• Confirm assignments as early as possible
• Communicate full assignment details (venue, schedule, role, uniform) at the time of confirmation
• Maintain a quality relationship with your casual workers (fast payment, proper conditions, clear communication)
• Prioritise loyal casual workers when allocating the best assignments

Centralising pool management in a single tool

The limits of the artisan approach

Many event companies still manage their pool with a mix of Excel files, WhatsApp groups and personal address books. This works as long as volumes stay low. Beyond 50 casual workers and 5 events per month, the gaps appear: scattered information, duplicates, missed Dimona declarations, inability to know who is available without making 20 calls.

What Shyfter changes for casual worker management

An event scheduling tool centralises everything in a single platform:

• Casual worker database with skills, certifications and contact details
• Availability updated in real time via the mobile app
• Shift proposals and confirmation in one tap
• Reliability score based on history
• Automatic Dimona declarations
• Geolocated mobile time tracking at each event site
• Complete history per casual worker: assignments, hours, reliability, validated skills

The result: less time on the phone, more time in the field. And complete traceability in the event of an inspection.

Request a demo

FAQ

What size casual worker pool should you aim for in events?

Aim for a pool 2 to 3 times larger than your maximum simultaneous needs. If your busiest weekend requires 100 casual workers, build a pool of 200 to 300 people. This ratio accounts for unavailability (on average 40 to 50% of the pool is unavailable on any given date), cancellations (5 to 15%) and event overlaps. During festival season, increase this ratio further as your casual workers are being solicited by other employers.

How do you reduce casual worker drop-out rates?

Three main levers. First, confirm assignments as early as possible with full details (venue, schedule, uniform, role). A well-informed casual worker cancels less than one left in the dark. Second, pay quickly and correctly. Casual workers who wait three weeks for payment choose another employer. Third, use a reliability score to prioritise the most consistent casual workers in assignment allocation. Casual workers quickly understand that reliability gives access to the best assignments.

Should casual workers and permanent staff be managed in the same tool?

Yes, this is strongly recommended. Your permanent production manager and your 50 Saturday casual workers are working at the same event. Managing them in two separate tools creates blind spots: who is assigned where, how many people in total, what is the total staff cost for this event. Shyfter manages both in a single platform, with different statuses (permanent, casual, student, agency) and rules adapted to each contract type.