[TomMarius]

Reaction to your edit with a cyclist, I have no idea how that relates to this case. That's an accident, something that no one knew will happen, and everyone understands that. On the other hand it doesn't seem nice to purposefully not tell someone information that might be extremely important to them and might even mean if they do or do not lose their business.

[PeterisP]

The position here is that it's not information that might be extremely important to them. Legally (and ethically!) this information literally can not, must not influence any of their decisions regarding that employee in any way whatsoever. What is the employer going to do if they tell them if they can't use that information or act on it? They might do something, but they should not; they likely want to do something, but they should be prevented from doing so.

In essence, the applicant has a right to demand treatment as if the employer didn't know that information. By not telling them, they're exercising that right, taking precautions so that it wouldn't be violated in a way that's illegal but hard to prove.

[TomMarius]

What? That an employee will be away for several years is not an important information? Since when?

The employee has right to be treated as if the information was unknown, I never said the opposite and never wanted to even imply that (and I'm pretty sure that I did not). That doesn't mean that the employer shouldn't have an opportunity to plan accordingly (e.g. start looking for a temporary replacement, stop accepting new projects and so on).

[PeterisP]

Okay, yes, there are some reasonable and legal actions that can be taken with that information, so it is valuable, I was apparently exaggerating.

However, giving that information right before a decision point (i.e. when changing jobs, getting a promotion, etc) is just inviting it to be misused, it's a risk they shouldn't be required or always expected to take.

For some context, some time ago I was involved in handling quite a few maternity/replacement situations. Our local laws are quite generous with maternity leave, so for existing employees we (in that company) had often started planning replacements as early as 6 months before start of their leave. However, this is a bit tricky - if there was some promotion issue in the middle of that period (3 months after I'd known but 3 months before she'd leave), I could try acting as if that information was unknown, but it's difficult, I can't magically unlearn things, I couldn't be sure myself if I wasn't biased one way or another (unless we had extremely dry formal procedure based on some arbitrary "objective" metrics that mismeasure as much as they measure), and I definitely couldn't prove that I wasn't influenced if that was contested. So in such an situation I might have even preferred not to know, despite the extra hassle it would cause.

It's probably a question of trust. If an employee is working in a trustworthy environment, they'd likely volunteer that information (which I've seen happen) and the employer would benefit from having created such an environment. But if employees feel a lack of trust, they would likely want to protect themselves and keep it a secret (which I've also seen happen), and IMHO they have (or should have) a right to do so if they really feel the need. The employer's reputation and trustworthiness is their own fault or achievement based on their previous actions, so in some sense they deserve what they get, whether it's trust or lack of it.

[carlob]

Pregnancies are not all exactly planned…

[zaarn]

And pregnancies don't happen out of the blue either.

[TomMarius]

Maternal leaves are, though.