Love, Policy, and Productivity: Should Companies Rethink Their Approach to Employee Dating?

Love, Policy, and Productivity: Should Companies Rethink Their Approach to Employee Dating?

Between the third Zoom call and a common deadline, two coworkers may have a crush on each other. It happens constantly. And no amount of HR policy language has ever really changed that.

So the question isn't whether workplace relationships happen. It's what to actually do about them. Because right now, most organizations are handling it badly. Some with blanket bans that backfire. Some with vague "use your judgment" language that protects nobody. And some with nothing written down at all, which is arguably the worst option.

Interestingly, even a well-run best dating service like SoulMatcher tends to operate with more transparent rules around consent and communication than the average corporate handbook. Make of that what you will.

One in Three People. That's the Baseline

The Kickresume ran a pretty extensive survey on this. The result: 33% of employees had been in a romantic relationship with a coworker at some point. Among workers under 35, it jumped to nearly 40%. And 31% of those relationships ended in marriage.

So this isn't purely a liability story. It's also, weirdly, a love story. A significant one.

But then there's the part that is a liability story: 25% of reported workplace romances involved someone in a management position over the other person. That's where it gets genuinely complicated. Not two peers who sit in adjacent cubicles and eventually get dinner – that's one conversation. A supervisor and a direct report is a completely different one, and conflating the two is where most policies go wrong before they even get started.

The Ban Does Not Work

Companies that have tried full prohibition generally end up with one outcome: the relationships still happen, they just go underground. Employees subject to strict no-dating rules were more likely to hide their relationships from management, not less.

And hidden relationships, when they go bad, are a structural nightmare. No disclosure trail. No accommodation made for reporting lines. No clear procedure for what happens next. The ban created the exact opacity it was supposed to prevent. Neat, in a tragic sort of way.

The Disclosure Model

The more functional approach, which companies like Google have used in various forms for years, is essentially: tell someone, and we'll adjust accordingly. You're in a relationship with a colleague? Fine. Tell HR. If one of you manages the other, one of you moves to a different reporting structure. Done.

It's not romantic. But it's honest, and it holds up when things don't go well between the people involved.

The elements that actually matter in a policy worth having:

  • A disclosure process that doesn't punish people for being honest;
  • Automatic restructuring of direct reporting relationships – no exceptions, no "we'll see how it goes";
  • A written procedure for post-breakup situations where one party feels uncomfortable or harassed;
  • Manager training on handling disclosures without gossip, assumptions, or quiet retaliation;
  • Some form of review cycle, since workplace culture in 2026 is different from what it was in 2018.

The Productivity Argument Is a Red Herring

One more thing. The assumption baked into a lot of anti-dating policies is that romance between colleagues hurts performance – for the team, the individuals, and the broader culture.

However, major researches found essentially no consistent link between workplace relationships and team-level productivity outcomes. What did affect performance was how management responded to disclosure. Handled with discretion and structure – neutral outcome. Handled with gossip, awkwardness, or punishment – real damage.

The relationship wasn't the variable. The company's reaction was. Which, if you think about it, puts the responsibility exactly where it belongs.