Features
Built around one question.
If this location lost its general manager on Monday, who takes it — and if the honest answer is nobody, how long have we known? Every screen below exists to answer some part of that.
The pipeline
A ladder, not a directory.
People are tracked on rungs — Team Member, Manager, General Manager, Director by default — and each rung points at the one it promotes into. The pipeline draws those steps as they actually are in your organization, with candidates sorted most-ready first and grouped under the location they work at today.
- Expand a region to see the locations under it, and the bench under each.
- Switch between the tree and a flat sortable list without losing your filters.
- Narrow by rung, and by readiness or flight risk, from the bars above the tree.
- A location with candidates but none ready says so where you open it, rather than leaving you to notice.
The person record
Enough to decide, and no more.
A record holds what a promotion decision needs: where they are, what rung they are on, how ready they are, how they rate on your talent grid, whether anything in their file would block a promotion today, what is holding them back, and what happens next.
It deliberately does not hold home addresses, personal phone numbers, compensation or performance-review history. This is a planning tool that sits beside your system of record — it is not trying to become one.
- Readiness — Ready Now, 3–6 Months, or Identified.
- Talent rating — a nine-box grid of performance against potential.
- Promotion readiness — whether anything on file blocks a move, with the detail.
- Development and follow-up — free text and a date, because real development notes do not fit a picklist.
- Flight risk — a separately permissioned category, described below.
Relocation coverage
Ask a location who could fill it.
Most talent tools make you start from a person and hope. This one lets you start from the empty chair: pick a location and see every candidate who has said they would move there — or who is open to anywhere — ranked by readiness, and filtered to what you are allowed to see.
There is no requisition object to create first. The question is asked of a location, because that is how the problem arrives.
- Per-location coverage: how many people at each rung could move in.
- Supply across the organization: who would move, and from where.
- Willingness is set on the person, so it stays current with them.
Reporting
Numbers you can act on this week.
Every figure on the dashboard is scoped to what you can see, excludes you, and is computed on the server rather than assembled in the browser — so a count is a count, not a count of the rows that happened to load.
- Coverage gaps — locations with no ready successor, and locations nobody would move to, counted separately.
- Readiness distribution — the shape of the bench at each rung.
- Promote actuals — promotions this fiscal year against last, on your fiscal calendar.
- Follow-ups due — the development commitments that have come due or slipped.
- Recent activity — what changed in your scope, most recent first. The record itself carries who last edited it.
Access
Permission is a category, not a checkbox.
Named permission sets carry capabilities and a depth of visibility, and they are assigned to people. What that produces is a per-viewer record: the same person opened by two leaders is not the same page.
Per-category visibility
Information is grouped into categories, and each one is viewable and editable on its own terms. Flight-risk assessments carry their own permission, separate from everything else, because that is the field that gets a manager in trouble if it travels.
Depth, not just breadth
A set says how far down the tree you can see from where you sit — your own location, your region, the whole brand. Leaders at the same rung in different regions cannot see each other's people.
You are never in your own list
Your record is filtered out of every list, count, chart and search result you see, at every level. It is applied in the database, so there is no view of the product where it lapses.
Absent, not greyed out
A category you cannot see is simply not on the page. A control you cannot use is disabled with a line telling you which capability it needs — never a dead button and never a shrug.
Enforced in the database
Row-level security policies do the filtering, and the interface reads the same rules. There is no request that returns data the interface then hides.
A ceiling on granting
Nobody can grant access they do not hold themselves. Permission sets are ranked, and the rank is what stops an administrator quietly out-ranking their own scope.
Set-up
Configured to your organization, in your words.
Your structure
- Nest regions, markets and divisions as deep as your real hierarchy goes
- Locations carry a number, a name and a market — and the number is the one your operators already say out loud
- Several brands inside one organization, each with its own configuration
- The tree is built to be re-parented rather than rebuilt, so a restructure does not orphan anyone’s history
Your vocabulary
- Name the rungs of the ladder and say which one each promotes into
- Choose which rungs are tracked and which are just structure
- Set the organization’s fiscal year so promote counts land in the right year
- Renaming changes the words, never the meaning — the readiness states keep their sense underneath, so roll-ups across brands still line up
- The starting configuration is a working one, not an empty form
Live for everyone at once
When a colleague changes a record inside your scope, the pipeline updates in place. No refresh, and no two people editing yesterday's copy.
Search that respects scope
One box over people and locations. It searches only inside what you can see, so a name you are not entitled to will not surface as a near-miss.
Notifications that stop
Told when someone is added, promoted, transferred, removed or restored in your scope — with a switch per kind. A tool that nags gets muted, and a muted tool is not a tool.
Promotions leave a record
Promoting archives the person out of the pipeline and keeps the event, so a location's promote count survives long after the individual record does.
Photos, if you want them
A face makes a list of twelve names usable in a district meeting. Optional per organization, and served through short-lived links that are re-checked against your permissions.
Every edit is recorded
Who made the change, when, and which fields moved. Recent activity across your scope appears on the dashboard.
See it against your own structure.
The fastest way to judge it is to look at your own regions in it. Tell us how yours is shaped.