Casual Workers and Students in Hospitality

The role of casual workers and students in hospitality

A hotel cannot operate on permanent staff alone. Weekend banquets need 10 to 15 extra servers. Peak season doubles housekeeping requirements. A 200-participant conference mobilises reinforcements on every floor. This flexibility rests on two statuses specific to the hospitality sector: the casual worker and the student jobber.

In Belgium, an average-sized hotel (50–100 rooms) permanently employs 5 to 15 casual workers and students alongside its permanent team. In peak season or during events, this figure can double. Managing these flexible workers without administrative errors is a daily challenge.

Casual worker status in hospitality

Definition and legal framework

The casual worker in hospitality is a status specific to the sector, defined by the CP 302 hospitality collective agreement. A casual worker is engaged for a one-off assignment, for a maximum of 2 consecutive days with the same employer. Beyond 2 days, the worker must be engaged under a standard employment contract (fixed-term or permanent). The total number of casual worker days is capped per year and per worker. Consult your payroll provider for the current limits.

Dimona declarations for casual workers

Each time a casual worker is put to work, a prior Dimona employment declaration must be filed with social security. The declaration must be made before the shift starts, mentioning the date, planned hours and the worker's identity.

In hospitality, the volume of declarations is high: a Saturday evening banquet with 12 casual workers means 12 individual declarations. A peak-season weekend with casual workers in housekeeping, the kitchen and the dining room can mean 20 to 30 declarations. Shyfter automates these declarations directly from the schedule.

Risks associated with casual worker status

Casual worker status is frequently checked by the social inspectorate. The most common infringements:

• Casual workers not declared in Dimona (undeclared work)
• Exceeding 2 consecutive days (reclassification as an employment contract)
• Exceeding the annual cap on casual worker days
• Permanent casual workers who work every week (circumventing permanent contracts)

Sanctions range from administrative fines to contract reclassification with retroactive payment of social contributions at the standard rate.

Student jobber status

The 475-hour reduced-contribution limit

In Belgium, a student jobber benefits from a reduced social contribution rate (approximately 8% instead of 25–30%) for the first 475 hours worked in the calendar year. This reduced rate applies across all employers combined: if the student has already worked 200 hours elsewhere, only 275 reduced-contribution hours remain with you.

Tracking these hours is the employer's responsibility. Exceeding 475 hours shifts contributions to the standard rate for all hours beyond that limit, adding 15 to 20% per hour for the employer. On a student who exceeds by 100 hours, the financial impact runs to hundreds of euros.

The student contract

The student employment contract must be established in writing before the start of employment. It states the duration, working hours, pay and working conditions. The contract is subject to the same CP 302 wage scales as other workers.

Student Dimona

As with casual workers, each time a student is put to work, they must be declared via Dimona. The student Dimona declaration specifically mentions student status, which allows social security to track the 475-hour counter. A standard Dimona without mentioning student status does not trigger reduced contributions.

Where to use casual workers and students in a hotel

Restaurant service and banquets

This is the most common position for casual workers in hospitality. Banquets (weddings, conferences, galas) require significant one-off reinforcements. Casual workers handle tray service, table service, clearing and bar. Students are also used for these events, often at weekends.

Housekeeping

In peak season, housekeeping needs reinforcements. Students are engaged for support tasks: preparing trolleys, cleaning common areas, assisting with turndown service. Housekeeping casual workers must be trained to the establishment's standards before being sent to rooms.

Kitchen

Kitchen casual workers cover dishwashing, preparation and dressing support during events. Students from hospitality schools are particularly sought for these positions, as they have basic kitchen training.

Reception and front desk

Casual workers at the front desk are rarer, as the position requires knowledge of the PMS and hotel procedures. However, students can be employed as reception reinforcements during events (cloakroom, directing guests, badge management).

Recruiting and managing a casual worker pool

Building the pool

Do not recruit casual workers at the last minute. Build a structured pool before the season: identify profiles (hospitality students, former employees, professional casual workers); collect administrative information (national ID, contact details, status, usual availability); classify by skill (service, kitchen, housekeeping, multi-skilled); and train new casual workers in your establishment's standards.

Sizing the pool

Your pool must be 2 to 3 times larger than your maximum simultaneous needs. If your biggest event needs 15 casual workers, your pool must contain 30 to 45 people. This oversizing compensates for unavailability: a casual worker who works one weekend in two, a student in exams, a profile who does not respond.

Managing availability

The main challenge with casual workers and students: their availability changes every week. Students follow the rhythm of courses and exams. Casual workers often have multiple employers. A digital availability-collection system is essential. Shyfter allows each casual worker and student to declare their availability via the mobile app. When you need reinforcements, you immediately see who is available and assign them with a few clicks.

Critical periods

Exam periods (January and June)

During exam periods, your students disappear from the schedule. This is predictable (exam dates are known from the start of term) but often poorly anticipated. Prepare for this absence at least one month in advance: increase hours for non-student casual workers; call in additional ad hoc casual workers; ask permanent employees to cover shifts normally handled by students.

Summer peak season

Summer is paradoxical: it is the period of highest occupancy and the one when students are most available (school holidays). It is the ideal time to maximise student hours. However, watch the 475-hour counter: a student working full time in July and August consumes 300 to 350 hours in two months, leaving almost nothing for the rest of the year.

Year-end holidays

Christmas and New Year combine high occupancy with festive events. Casual workers and students are in high demand. Supplements (public holidays, nights) accumulate. The schedule for this period must be finalised at least 3 weeks in advance.

Mistakes to avoid

The permanent casual worker

A casual worker who has worked every weekend for 6 months is no longer a casual worker: they are a disguised employee. The social inspectorate can reclassify this relationship as an employment contract, with retroactive payment of social contributions plus fines. Limit recourse to the same casual workers and diversify your pool.

Missing a Dimona

Every undeclared start of work is an infringement. In the event of an inspection, fines are proportional to the number of infringements. Automation via Shyfter is the best remedy.

Undetected 475-hour excess

Without real-time tracking, exceeding 475 hours is often discovered after the fact, during the annual close by the payroll provider. At that point, the employer receives a contribution regularisation that can reach several hundred euros per student. Proactive hour tracking is the only effective prevention.

Lack of training

Sending an untrained casual worker to serve a wedding banquet risks the service. Plan a minimum 30-minute briefing before each assignment: service standards reminder, floor plan explanation, position allocation. For new casual workers, a half-day of initial training is recommended.

Digitalising the management of casual workers and students

Shyfter centralises the management of flexible workers: pool database with skills, availability and history; availability collection via mobile app; assignment to shifts in a few clicks; automatic Dimona declarations at each assignment; real-time 475-hour counter for each student; digital time-tracking by department; and export to the payroll provider distinguishing statuses (casual worker, student, fixed-term).

Request a demo

FAQ

Can a casual worker work more than 2 consecutive days in a hotel?

No. Casual worker status in hospitality is limited to a maximum of 2 consecutive days with the same employer. Beyond that, the worker must be engaged under a standard employment contract. For a 3-day event, you must either rotate casual workers (one group for days 1–2, another for day 3) or engage them under a fixed-term contract. Non-compliance exposes you to contract reclassification and sanctions.

How do you know how many hours a student has already worked for other employers?

The student can check their remaining hour balance on the Student@Work website (social security). Request an attestation of their balance before engaging them. Note: the Student@Work counter is not always updated in real time (a few days' delay). Build in a safety margin. Shyfter tracks hours worked with you in real time, but hours with other employers must be declared by the student.

What sanctions does a hotel risk for not declaring casual workers via Dimona?

Missing a Dimona declaration is considered undeclared work. Sanctions range from administrative fines (80 to 800 euros per infringement, per worker) to criminal prosecution in serious or repeated cases. In an inspection, each undeclared casual worker constitutes a separate infringement. For an event with 10 undeclared casual workers, fines can reach several thousand euros. Automating declarations is the safest way to avoid these risks.