Your Benefits Site Should Be a Public Benefits Portal, Not a Login Screen

A broker I know had a client losing candidates to a competitor, it was in the competitive AI space. The pay was close and the plan was comparable; what set the competitor apart was a benefits page anyone could read before applying. The client's benefits sat behind a login only current employees could reach. The broker's client didn't lose on the offer. It lost on the login screen. People want more transparency these days.

That's the pattern at scale too. Go to one.walmart.com right now, with no employee ID and no credentials, and you can read the actual medical plan costs, the prescription drug tiers, the tuition benefit, and the parental leave policy. The largest employers in the country have quietly stopped treating benefits information like something to protect. Most everyone else still gates it behind a login, out of habit rather than reason.

Stay on that Walmart page for a few minutes and the pattern gets clearer. It isn't a stripped-down summary written for outsiders. It's the same information an enrolled employee would use to pick a plan. It's published in the open instead, on the assumption that a candidate deserves to see it before they apply. None of this requires a login on that site:

• Plan costs per pay period, for every medical option offered
• Prescription drug tiers and retail versus mail order pricing
• Tuition assistance and eligibility rules
• Parental leave policy, written in plain language

None of that is confidential in the way a Social Security number or a claims history is confidential. It's a description of what the job pays in total, and hiding it protects nothing. It just costs employers candidates, and it costs HR teams the credit for a plan they spent a year negotiating.

The habit nobody chose

Nobody sat down and decided benefits information should require a login. Benefits portals grew out of enrollment systems, and enrollment systems need authentication because they touch personal data tied to one specific person, things like elections and dependents, sometimes health information too. That login wall belongs there.

The problem is that the informational layer got dragged behind the same wall. What the PPO costs. What the deductible is. Whether the plan covers fertility treatment. None of that is personal. It's identical for every employee enrolled in that plan. But the system that hosts it also handles enrollment, so the whole thing sits behind a login, and nobody revisits the decision once it's made. A plan summary written for open enrollment ends up living behind the same wall meant for someone's Social Security number, and two very different audiences, a current employee finishing enrollment and a candidate deciding whether to apply, get treated as if they need the same barrier.

This shows up constantly in the small, repeated questions HR teams field. An office manager fields a version of it every time a new hire asks what the plan actually costs before day one, and has to say some version of "you'll see it once you're set up in the system." That answer is fine for a new hire. It's a dealbreaker for a candidate still weighing two offers.

I know from personal experience that I've been lucky enough to have multiple offers before deciding which offer to accept. Most of the times, the pay has been similar and I am judging things from the intangibles, like culture, the hiring manager and their benefits. Most of the times, I feel as a candidate like I get squirrelly answers from HR when I ask about the benefits. The times I haven't are the times I feel more confident in the companies. Imagine, benefits are the 3rd largest cost to a company but they still don't have the bandwidth to be transparent. If you are going to spend the money, flaunt it!

Why a Public Benefits Portal Works Better Than a Login Screen

Walmart isn't unusual among large employers here. Many of the biggest companies in the country run a public benefits portal because, at that scale, benefits are recruiting marketing, not internal documentation. When you're competing against a handful of other massive employers for warehouse staff and entry-level corporate hires, the benefits package is part of the pitch. A candidate should be able to read it before they apply, not after they accept.

This is the part people get wrong: they assume openness makes benefits look worse, because now employees can compare and complain. In practice, the opposite tends to hold. A vague or hidden benefits package invites more suspicion, not less. Employees fill in the blanks with worst-case assumptions when information is scarce, the same way they forget what's actually in their package once open enrollment ends and nobody talks about it again. Hiding the plan doesn't protect it from scrutiny. It just delays the scrutiny until an employee is already enrolled and already frustrated.

There's also a quieter cost that rarely gets named. When benefits information is gated, HR ends up as the only channel for questions that a public page could have answered on its own. Every candidate question, every new hire question, every "wait, does this cover my kid" question routes through one inbox instead of a page anyone could read. A handful of recurring benefits questions get asked over and over precisely because the answer lives somewhere nobody outside the company can reach.

The broker's client eventually built a public summary page. It lived apart from the enrollment system and existed for one purpose: recruiting. The demand for it hadn't come from a compliance requirement. It came from a hiring manager tired of losing candidates to a competitor with a visible benefits page.

Where gating still makes sense

There are real reasons to keep some things behind a login, and the case for openness doesn't hold up if it pretends otherwise.

Self-funded employers sometimes have competitive reasons to keep specific plan design out of a rival's hands, especially in a tight labor market where a competitor could underbid a benefit almost line by line. Some union-negotiated plans carry contractual restrictions on public disclosure, which is a different problem entirely from squeamishness about openness. Beyond those cases, anything tied to one employee's elections, claims, health status, or medical history has to stay behind authentication regardless of company size. No public benefits portal should ever expose that kind of data.

I'd draw the line at the plan level. Publish what every employee on a given plan pays and gets. Keep anything tied to a name, a Social Security number, a claim number, or a specific diagnosis locked down exactly the way it is now. That distinction does most of the work. It separates information that's identical for a hundred employees from information that belongs to one, and only the second kind has any business behind a login.

Most employers gating their benefits information today aren't doing it for one of these narrow reasons. They're doing it because the system they bought defaults to a login screen and nobody asked whether it should. The vendor didn't build it maliciously. It's simply easier to lock everything down by default than to sort plan-level content from person-level content, so most systems don't bother sorting it at all.

Making the switch

Publishing everything Walmart publishes isn't necessary to get most of the benefit of a public benefits portal. Start with the pieces of the program that carry no personal data and genuinely help someone decide whether to work there: plan options, approximate costs, headline perks like parental leave, and tuition help.

A short public page covering that ground answers most of what a candidate wants to know before they ever submit an application, and it reaches them earlier than the enrollment communication timeline most companies build was ever designed to. It gives recruiters something concrete to point to instead of a promise to explain the details later, once the offer is already signed.

It also changes the tone of the conversation once someone is hired. Instead of discovering the plan for the first time during a rushed enrollment window, a new employee arrives already knowing roughly what they're getting, because they read it before they accepted the offer. The plan stops being a surprise revealed after the fact and starts being one of the reasons they said yes.

That's the actual choice most employers are making, whether they know it or not. Every benefits program already has an informational layer that carries no personal risk and a transactional layer that carries all of it. The login wall was built for the second one. Somewhere along the way, most companies let one wall cover both layers. Nobody ever asked whether the plan they're proud of should be this hard to see.