Employee retention
The way employee retention is calculated changed between these two points, so they are not comparable and no movement is shown.
Comparisons resume once a full period has been recorded the new way. The number itself is unaffected.
Where it stands
Monthly, up to the last 12 months
Employee retention reads 88% against floor 75%, which is inside its band. It moves after the damage either way, so read it as the quarterly scoreboard and watch workload and the team survey in between.
- Window
- Stated as of Aug 23, 2026. The period the reading covers is set by its source and is not stated on this tile.
- How it is counted
- Of the people who were on the team a year ago, the share still here today, based on hire and departure dates on file.
- Source
- Employment history, as of Aug 23, 2026
- Drivers
- Reasoned from this metric's own definition and sources. The driver breakdown is not composed for this tile yet, and the section below says what it would take.
What this is
Share of last year's team still here today. Of the people who were on the team a year ago, the share still here today, based on hire and departure dates on file.
Why it is on your dashboard
The team is the most expensive investment the agency makes, and every departure walks out with client context and takes months of ramp to replace. The working floor is 75% of last year's team still here. Read the direction with team sentiment rather than alone: in a slow hiring market people stay for reasons that have nothing to do with wanting to. It sits on this board against floor 75%.
Why it is where it is
This accounts for the people who left, out of the 8 who were here at the start, one person in all.
Left on Oct 31, 2025. Account Management, account_executive.
How this was measured: This person was employed here at the start of the period and their employment record carries a leaving date inside it. Counted once, from the employment history rather than from who is on the roster today.
Each person is counted once, against the team they were recorded in. Somebody hired and gone inside the same period is not here, because the share measures who stayed out of who was already here. By team, the heaviest loss was Account Management, which lost 1 of 3. Three from a team of four and three from a team of forty are the same number and different businesses, which is why the team size is beside it. Departures are counted against the people who were already here at the start of the period. Somebody hired and gone inside the same year is not in this cohort, which is what the share measures and not a judgment about the hire. No pay information travels with this list.
What we checked, in order
Not answered here.
There is no ruled order of checks for Employee retention yet. Three of these ordered diagnostics exist and they attach to the profit share, an account under the floor, and absorbed work. This metric is not one of them.
An ordered set of checks is worth more than a list of things to look at, because the order is what stops the most expensive move being tried first. Writing one for this metric is a decision about how it should be diagnosed rather than a gap in the data.
Root cause
Like the client version, this reports on decisions already taken, and it reports them late. What sits behind it is rarely one thing anybody could have pointed at on the day: workload that stayed high past the point it was supposed to be temporary, a stretch of work nobody found interesting, or a manager. The pattern in WHO left is what separates those, and it is usually obvious the moment the departures are named: one team, one role level, one manager. On this workspace the departures were Maren Voss, and by team the heaviest loss was Account Management, which lost 1 of 3. The team survey is not on this board, so the comparison this calls for cannot be made here. Read this next to the team survey when there is one, because a share that holds up while the survey does not is the pattern worth catching. People who feel stuck and people who feel secure produce the same reading here, and only one of them is good news.
What to do now
Not answered here.
The share is above its floor on this read, so there is no loss here to respond to.
This number moves after the fact in both directions, so a good reading is not an all clear. The live signals are workload balance and the team survey, and both are available between readings.
What stops it coming back
Watch the live signals between readings and treat this as the scoreboard. Workload balance and the team survey both move well before anybody resigns.
The structural problem with people metrics is the lag. By the time the scoreboard moves the ramp cost is already committed, and a replacement takes months to reach the output of the person who left. The signals that lead it show up weekly, and the one that matters most in a services firm is how the work is spread, because the people who go first are usually the ones carrying the most and complaining the least. Acting on those is the change. This tile only tells you afterwards whether it worked.
This closes no measured driver above, and does not claim to.
What happens if this is ignored
Every departure walks out with client context that was never written down and takes months of ramp to replace, and the cost lands in two places that do not look connected to it. Income per person falls, because headcount refills long before output does. And client relationships thin, because the person who knew the account is gone and the handover was a document. The compounding version is the one to watch: whoever covers for a departure is the most likely next one, so a single loss on a stretched team is rarely a single loss.
Is this target still telling you anything
Not answered here.
The window spans a measurement change, so its periods are not one series: compute path changed: demo-history-seed@1 to live-serving-rollup@3
How this metric is measured changed inside the period this section would look back over, so counting hits across it would be counting two different measurements as one. This fills in once the whole window sits on one basis.