In this article
Since 2022, every EU member state has enforced the same floor for how predictable a rota has to be — and hospitality is exactly the sector that trips over it most, with "we'll text you" as its default scheduling method.
It happens in almost every kitchen sooner or later: a team member gets a message Tuesday evening for a Wednesday-morning shift, and replies that they're not coming in "because that's not allowed." The owner is baffled — there's no clause in the contract about how many days' notice a shift needs. Usually the owner is right that no such clause exists. And the team member is right too, because the clause never had to be in the contract — it's already in the law.
Directive (EU) 2019/1152 on Transparent and Predictable Working Conditions has been transposed into national law in all 27 member states since August 2022. It regulates exactly the pattern hospitality runs on most: staff whose hours vary week to week, who get called in whenever it's busy, and who are expected to be flexible without anyone ever writing down what that flexibility is actually allowed to cost them in warning.
This article isn't about the national details — exactly how many hours' notice your country requires, or what compensation applies to a late-cancelled shift, differs by member state and belongs in your own staff handbook. It's about the seven numbers the directive itself fixes, identically across all 27 countries: the deadline for a written contract, the cap on a probationary period, the two conditions that both have to hold before a shift can be required, and the right a worker has when they don't.
Along the way sit two graphics and an interactive tool — the "Compliance Clock" — that turns your own start date, contract date and shift notice into exactly where your rota stands against each of those seven numbers.
Why this lands on hospitality specifically
No sector normalises "we'll see who's free" quite like hospitality. A good team runs on flexibility, and that flexibility is often rewarded quietly — the person who always steps in looks good. That's exactly what makes the sector vulnerable to the pattern this directive was written to limit: a worker who never knows which days they're working until it's almost too late to plan around it.
It isn't an edge case. Any venue that runs on variable staffing — a weekend-only server, an extra cook for a twenty-cover booking, a terrace worker called in whenever the sun comes out — is running exactly the kind of "unpredictable work pattern" this directive governs. And most owners have never heard of the directive, let alone the seven numbers inside it.
That's also why this isn't a "big companies with an HR department" story, the way the pay-transparency directive often gets dismissed. The numbers below apply from the very first person you hire — including the student who only works Saturdays and the on-call cook you've been texting for three years.
7 numbers behind the rota your staff are owed
Every one of these seven numbers is written into the directive itself, identically across all 27 member states — unlike the exact notice period or compensation rule, which each country set for itself and which this article deliberately doesn't try to reduce to one EU-wide figure.
1. 7 days — the deadline for the core of the contract
The moment someone starts working, a clock starts ticking: within 7 calendar days of the first working day, they're entitled to the core of their employment terms in writing — who the employer is, the job title, where and when they'll work, and the pay. That isn't a best-practice suggestion; it's the hard deadline in Article 4 of the directive, and it reads identically in all 27 member states.
In practice, this is exactly where a small venue slips: someone starts on trial, the "paperwork" is going to happen "sometime this week," and three weeks later nothing has ever been written down. Nobody meant to skip a step — there was just a busy week in between.
Every deadline counts from the start date — here 2026-01-12 — no matter when you actually get around to it.
In this example the contract only arrived after 14 days — 7 days past the 7-day deadline. The red flag marks that moment; the purple flag marks the check date.
2. 1 month — the deadline for the complete written statement
Beyond that 7-day core, there's a second, wider deadline: the complete written statement of employment terms — probation, notice rules, holiday entitlement, the reference hours from step 4 below — has to land within 1 month of the start date. Article 5 draws that line deliberately: the core has to arrive fast, the rest can take a little longer, but not indefinitely.
Run it against the example this article works from: a new hire starts on 2026-01-12, and the written contract only arrives on day fourteen — 7 days past the 7-day deadline for the core terms. That's exactly the scenario the timeline below plots, alongside the 1-month and 6-month markers that come with it.
3. 6 months — the default cap on a probationary period
A probationary period isn't allowed to run indefinitely as a way of keeping someone in limbo. Article 8 sets a default cap of 6 months, unless the nature of the role or the worker's own interest justifies something longer — an exception, not the norm.
For hospitality this rarely bites: most kitchen and floor roles show what they are within a few weeks. But it's worth knowing for the one case where a probation quietly drifts into an indefinite "let's see" — which isn't a legal category.
4. 2 conditions — when a shift can actually be required
This is the core of the directive for anyone with an unpredictable work pattern — hours or days that vary week to week, exactly what an on-call or flexi worker in hospitality experiences. Article 10 says an employer can only require that person to work when both of these hold: the work falls within reference hours and days fixed in writing in advance, AND the worker is given reasonable advance notice of the assignment.
The word "both" is doing the work here. A reference framework with no notice isn't enough. Notice with no pre-defined reference framework isn't enough either. They aren't two alternative routes to the same right — they're two locks that both have to open.
See it worked through in the example below: reference hours and days were never put in writing, and notice for the shift arrived only 11h before it started. Even if 11h could count as "reasonable" on its own, the scenario already fails on the first condition — there was never a reference framework for the shift to fall inside of.
A shift can only be required when BOTH of the conditions below hold — not just one.
5. 0 — the consequences allowed for a valid refusal
What happens when either condition above doesn't hold? Article 10(3) is explicit: the worker may refuse the work, and it must carry zero adverse consequences. No lighter rota the following week, no comment in a review, no quiet drift toward the least popular shifts.
That number — zero — is exactly why the opening scene of this article checks out. The cook who refuses a shift "because it's not allowed" doesn't just have the right to refuse; he has the right for that refusal to cost him nothing in the weeks that follow. Articles 15 and 16 add a further layer on top: protection against dismissal or retaliation for anyone exercising these rights.
6. 6 months, then 1 — the right to request a more predictable pattern
After 6 months with the same employer, a worker gains a new right: they can ask for a more predictable or secure work pattern — fixed hours instead of an on-call basis, for example. Article 12 requires the employer to reply in writing and with reasons, within 1 month for a small business (under 250 staff), or within 3 months for a repeated, similar request.
This is the number most owners never see coming, because it only becomes relevant months after the hire date — exactly the point at which nobody's thinking about the onboarding file any more. A staff member who asks for fixed hours after six months isn't asking for a favour; they're exercising a legal right, on a clock that starts the moment the request lands.
7. Building a rota that survives all seven numbers
The simplest fix isn't legal, it's operational: write down the reference hours and days for every on-call or flexi worker before the first rota goes out — not afterwards, "just to have it on paper." That single document already solves the first condition from step 4.
Then build a fixed notice period into your own planning, well above your country's legal minimum, which this article deliberately doesn't reduce to one EU-wide figure — so you're never planning right up against the line. A team that knows the rota goes up by Monday for the following week never has to refuse or hesitate on instinct alone.
And put three dates in your own calendar, not just the contract: day 7 for the core terms, day 30 for the full statement, and month 6 for when the right to request a steadier pattern starts running. Three quiet deadlines that never send an invoice when you miss them — until someone asks.
Calculate your own Compliance Clock
The seven numbers above apply to any employment relationship, not just the example. Enter the real start date, the day the contract actually arrived, a check date of your choosing, and the notice and start time of one specific shift — the tool works out immediately where your rota stands against every deadline.
Only tick "reference hours/days fixed in writing in advance" if that's genuinely true. That one checkbox is the entire difference between "this shift can be required" and "this shift can be refused with no consequences."
Compliance Clock
Enter the start date, the contract date and one specific shift, and see immediately where your rota stands against every deadline.
—
This is not legal advice. The exact notice period and any compensation for a late-cancelled shift differ by member state; check your own staff handbook or payroll adviser.
Use this not just on the hires you're confident about, but on the on-call and flexi workers nobody ever wrote a reference framework down for. That's exactly where the risk sits, because the rota itself looks perfectly normal — the only thing missing is the document that would legally cover it.
Remember the core of step 4: both conditions have to hold, not one. A shift that's announced on time but has no written reference framework fails just as much as one with a reference framework announced far too late.
Checklist: 3 moments to set the clock
Three checks, each tied to a concrete point in the employment relationship — not to a vague "we'll sort it out."
On the first working day
- Calendar day 7 for the core terms — job title, place of work, hours, pay — not "sometime this week."
- Calendar day 30 for the complete written statement, including the reference hours and days from step 4.
- Put every on-call or flexi worker's reference framework in writing before the first rota with their name on it goes out.
On every rota you publish
- Check that every shift falls inside the written reference framework — an exception to that is exactly the scenario from step 4.
- Run a fixed notice period in your own planning, comfortably above your country's legal minimum.
- Treat a refusal over short notice as a missed deadline of your own, not as a team member being difficult.
From month 6 onward
- Track which staff are approaching six months' tenure — that's where the right to request a steadier pattern begins.
- Reply in writing, with reasons, within 1 month of such a request — or 3 months for a repeated one.
- Document why a request was granted or declined — a verbal "we'll see" doesn't satisfy Article 12.
Seven numbers, zero excuses
Of every EU rule that applies to a hospitality venue, this might be the least visible one: no inspector shows up specifically asking about reference hours, and the rota in the app looks completely normal on its own. All it takes to see the problem is asking the question directly: is this written down anywhere, and was notice given on time?
That also makes it one of the cheapest things to fix structurally. It needs no extra staff and no software subscription — just three dates in a calendar and one document per on-call worker that should have existed before the first rota ever went out.
And in the end it isn't a trade-off against a flexible team — if anything, the opposite. A team that knows exactly which framework it's called in under, and how much notice to expect, plans its own life around that framework — and ends up just a little more available exactly when it matters most.