What Is eNPS? The Employee Net Promoter Score, Explained
The employee Net Promoter Score turns one question into a single number for how loyal your team is — here's how to calculate it, read it, and act on it.
Ask a room of HR leaders how their people feel about working there and you'll get a dozen answers, most of them anecdotes. The employee Net Promoter Score — eNPS for short — exists to replace those anecdotes with one number you can track over time. It's built from a single question, a little arithmetic, and nothing else.
This guide covers what eNPS is, how to calculate it, what a good score looks like, why the maths is stricter than it seems, how it differs from customer NPS, and — the part most teams skip — how to run it so the answers are actually honest.
What is eNPS?
The employee Net Promoter Score is a measure of employee loyalty and satisfaction, adapted from the customer-facing Net Promoter Score (NPS) that companies have used for two decades. Where NPS asks customers how likely they are to recommend a product, eNPS asks employees one thing:
On a scale of 0 to 10, how likely are you to recommend this company as a place to work?
That's the whole instrument. Everyone answers the same question on the same 0–10 scale, and their answers roll up into a single score somewhere between −100 and +100. Because the question and the maths are fixed, eNPS is one of the few employee-experience metrics you can compare across teams, across quarters, and — roughly — across companies.
How to calculate eNPS
The calculation sorts every response into one of three groups based on the 0–10 rating:
- Promoters (9–10) — genuinely enthusiastic. The people who'd recommend you unprompted.
- Passives (7–8) — satisfied but unattached. They won't badmouth you; they also won't screen a recruiter's call.
- Detractors (0–6) — disengaged, and the group quietly updating their CVs.
Then the formula:
eNPS = % Promoters − % Detractors
Passives count toward your total responses but drop out of the subtraction. Worked example: in a team of 50, if 25 people score 9–10 (50% promoters), 15 score 7–8 (passives), and 10 score 0–6 (20% detractors), your eNPS is 50 − 20 = +30.
The result is a whole number from −100 (everyone's a detractor) to +100 (everyone's a promoter). Note what's missing: there's no averaging. A score of 30 doesn't mean "people rated us 3 out of 10" — it means promoters outnumber detractors by 30 percentage points.
What is a good eNPS score?
There's no universal pass mark, but the commonly cited rules of thumb run roughly like this:
- Above 0 — more promoters than detractors. The floor for "healthy."
- 10 to 30 — a solid, good score for most organizations.
- 30 to 50 — strong; your people are actively engaged.
- 50+ — excellent, and rare.
- Below 0 — a warning. Your detractors outnumber your enthusiasts, and that's a fire alarm, not a rounding error.
Two cautions. First, benchmarks vary by industry, company size and region, so treat any single "good score" number with suspicion. Second — and this matters far more — a one-off reading tells you almost nothing. The movement is the signal. A +20 that was +45 two quarters ago is a very different company from a +20 that was +5. Watch the line, not the number.
Why the scoring feels harsh — and why that's the point
If you're new to NPS-style scoring, the groups feel unfair the first time you see them. A 7 or an 8 sounds like a decent answer — but it counts for nothing. A 6 sounds only slightly worse — but it counts against you.
That harshness is deliberate. People are polite. Asked to rate almost anything, most of us hand out 7s the way we say "fine, thanks" — it's the answer that ends the conversation. eNPS is built to strip that politeness out of the signal. Only genuine enthusiasm counts for you, and everything lukewarm counts as a warning, because lukewarm employees are the ones with one foot out the door.
So a score of zero doesn't mean "average." It means your enthusiasts and your flight risks are exactly balanced. Healthy teams land well above it.
eNPS vs. NPS: what's the difference?
They share the same maths and the same 0–10 scale, but the audience and the question differ:
- NPS (Net Promoter Score) asks customers how likely they are to recommend your product or service. It measures customer loyalty.
- eNPS (employee Net Promoter Score) asks employees how likely they are to recommend your company as a place to work. It measures employee loyalty and engagement.
The shared method is the point: if your leadership already tracks customer NPS, eNPS drops into the same mental model with no new vocabulary to learn.
Why eNPS matters
For one question, eNPS carries a lot:
- It's an early warning for turnover. Detractors are your flight risk, and a falling eNPS often shows up quarters before resignations do — early enough to act.
- It's fast and cheap. One question means high response rates and near-zero survey fatigue. You can run it monthly or quarterly without exhausting anyone.
- It's comparable. Fixed question, fixed maths — so it's trackable over time and roughly benchmarkable against others.
- It's a conversation starter, not a verdict. The number judges no one; it tells you where to go ask a human question.
What eNPS can't tell you
Be honest about the limits. A single number can't explain why people feel the way they do — a bare score with no comment attached is a thermometer with no diagnosis. eNPS also compresses a lot of nuance into one figure, so a healthy company-wide score can hide a team in real trouble. And like any survey, it's only as truthful as people believe it to be anonymous. Which brings us to the part most teams get wrong.
How to run an eNPS survey people actually trust
The question is free. The things that make the answer trustworthy are where the real work lives — and they're the parts a bolted-on survey tab tends to skip.
Anonymity people actually believe. An eNPS is only as honest as people believe it is anonymous. If scores can be traced back later — by an admin with database access, by a small-team filter, by process of elimination — people learn to answer 8 and move on, and your score becomes decorative. In SquadBear, answers are aggregated with no minimum group size to game around, and when a survey closes, the key linking people to their answers is destroyed — not hidden behind an access rule, destroyed. There's nothing left to export or leak.
A trend, not a trophy. A single reading tells you little; the movement tells you everything. Every survey lands on a per-team timeline, so the score becomes a line you can watch instead of a number you announce once a year.
The why, next to the number. The score tells you where you stand; it never tells you what to fix. Invite an optional comment with each rating and surface those comments alongside the results — anonymous and shuffled — so the low scores arrive with their reasons attached.
Context from the rest of the system. An eNPS dip rarely happens in a vacuum. When the survey lives next to your leave and workload data, you can see whether the quarter your score slid was also the quarter absence spiked and on-call load doubled — and answer the "why" with evidence instead of a guess.
From score to action
The failure mode of every engagement metric is the same: measure, present, file away, repeat. The number becomes a ritual and nothing changes — except that people notice nothing changes, and the next score comes back a little lower and a little less honest.
So treat the score as a trigger, not a report. When it dips, the comments tell you where to look; what you do next should have an owner and a date attached, visible to the team. Ask honestly, read the why, fix something, ask again. That loop is the entire value of eNPS — the question was never the product.
Measure your team's eNPS
The eNPS check is built into SquadBear, aggregated and anonymous by design. Ask the demo to "run an eNPS check for the engineering team and show me the trend," or start free and send your first one this week.
Earlier in this series: burnout tracking without the Big Brother — reading team health without surveilling the people in it.