In this article
Every HR article on this site assumes you're scheduling shifts or managing tasks. This one is about something no rota can plan for: two people on your floor or in your kitchen falling for each other.
Hospitality has the highest rate of coworker dating of any industry ever measured — not because restaurant staff are different, but because a restaurant is the textbook setting for it: long shared shifts, an intense, adrenaline-heavy service, a small team that eats, smokes and closes together, and a workforce that skews young and single.
Pretending it won't happen at your restaurant is the one option this article is going to talk you out of.
This piece puts the three real policy choices side by side, with what each one actually costs — not a checklist to work through, but three different ways of handling the same reality.
Why Your Restaurant, Specifically
Workplace-romance research consistently ranks hospitality highest: roughly half of hospitality workers report having dated a colleague at some point, versus roughly a third to two-fifths of the workforce generally.
That is not a red flag to manage away. About 30% of workplace relationships become long-term relationships, and separately, around 3 in 10 people who ever dated a coworker went on to marry that person.
The number that actually decides what your restaurant needs to DO about it: roughly 4 in 5 workplace relationships are between peers with no reporting-line conflict at all — same level, different section. It's the remaining 1 in 5, where one person schedules, evaluates or can effectively end the other's job, that every policy below is really about.
Two figures from the same body of workplace-romance research, side by side.
This is the argument for a policy that only touches the 1-in-5 case — not one that tries to prevent something that isn't actually the problem 4 in 5 of the time.
What "No Policy" Costs You
No written policy is the default for most independent restaurants — cheapest to "write" because there's nothing to write.
What it fails at: the moment a relationship between a shift lead and someone on the section they run ends badly, mid-service or mid-season, there is no framework for reassigning either person without it reading as a demotion, a punishment, or favoritism.
The real cost usually isn't the couple — it's everyone downstream of them: the two people whose shift swap suddenly doesn't happen fairly, the new hire who isn't sure which of the two to report a problem to.
Three Policies, Ranked by Risk
None of the three is a checklist to work through in order — they're three different ways of handling the same reality, and which one fits your restaurant depends on how your team is actually built.
Silence — No Written Policy
Nothing on paper, nothing said unless something goes wrong. That's exactly the cost described above: no framework the moment a relationship with a reporting-line conflict ends badly.
There's one place this genuinely still works: a very small team — a handful of people — with no real reporting-line structure at all. There's structurally nothing yet for a policy to protect against.
Disclosure-Based — the Model Most Restaurants Land On
Staff who start a relationship let a manager or owner know privately, within a short, low-pressure window — restaurant HR guidance commonly suggests something like two weeks — specifically so that if there IS a reporting-line conflict, one of the two can quietly move to a different shift lead or section. Not fired, not separated from the business, just no longer directly supervising or being supervised by their own partner.
Confidentiality and an explicit no-retaliation line are what make staff actually use it instead of hiding it. This is the shape most restaurants that write anything down actually converge on.
A Hard Line on Reporting-Line Relationships Only
The strictest version a restaurant can realistically enforce: peer relationships — two servers, two line cooks — are left alone entirely. Banning them invites a real argument about controlling employees' private lives outside work, and in most EU countries that argument does not hold up.
But a relationship where one person sets the other's schedule, writes their review, or decides their pay is banned outright, with an automatic, non-optional reassignment the moment it's disclosed. This is the version for a manager who wants zero ambiguity about what to actually do when it happens.
Who can date whom without creating a supervision problem — and who can't.
Safe — peers, no schedule or pay authority
- Two servers, different sections
- Two line cooks on the same station
- Bartender and host
Risk — one sets the other's schedule, pay or review
- Head chef and the commis they supervise
- Floor manager and the server whose shifts they build
- Owner and any direct report
The right-hand list is exactly what every policy above is actually about — never the left-hand one.
The One Relationship No Version of This Can Allow
The owner or top manager — the person with no one above them to reassign the relationship away FROM — dating a direct report. There is no "move one of them to a different supervisor" option when the person in the relationship IS the top of the reporting line.
So it has to be a flat no, or the owner personally becomes the single point of failure in every favoritism, schedule-fairness or harassment conversation the rest of the team has about them from then on. The same underlying logic — a hard line exactly where one person controls another's pay, schedule, or job — is what draws the line in the site's own restaurant CCTV and GDPR policy, applied to a completely different situation.
Which Policy Fits Your Restaurant?
Four short questions about your team return a recommended policy tier, the reason for it, and a sentence you could put straight into your staff handbook.
Nothing you type below leaves your browser.
Which Policy Fits You?
Four questions, one recommendation.
Recommended policy:
—
—
—
This always applies regardless of the tier above: a relationship between the owner or top manager and a direct report has no "reassign to a different supervisor" option and stays its own, strict rule.
Everything above runs in your own browser; nothing is sent anywhere or saved.
What to Check Tonight
Check your own schedule tonight for a single reporting-line pair that could realistically become a couple — a shift lead and someone on their own section, a chef and their commis. If none exists, "Silence" may genuinely be fine for now — revisit once the team grows past a handful of people.
If one exists, write the two sentences the disclosure tier needs and move on. That pair, if it ever happens, is exactly the roughly-1-in-5 case that costs you something if there's nothing written down.