Questions we are actually asked.

It tracks who in your organization is ready for promotion, at every location, and turns that into coverage: which locations have a ready successor, which do not, and who would move to fill a gap. It is a live view rather than an annual exercise.

No. It holds a deliberately small record — name, location, level, readiness, talent rating, notes — and no payroll, benefits, compensation or personnel-file data. It sits beside your system of record and answers a narrower question.

It also has no review cycles, no rating-calibration machinery and no task manager. Those are the parts of talent software that go unused after the first quarter, and leaving them out is the point.

An administrator in your organization invites them. Accounts are normally given to leaders who manage a team; being tracked in the pipeline does not by itself create a login, and an account reaches an organization's data only once it is attached to a place in that organization's structure.

Sign-in uses one shared GroupWork account, so anyone who already has one for GroupWork uses the same credentials here. Access to each application is granted separately.

The ladder is yours: you name each rung and say which one it promotes into, and you choose which rungs are tracked. Renaming changes the words and not the meaning — the readiness states keep their sense underneath — so organization-level roll-ups across differently configured brands still line up.

Renaming the readiness labels and the rating grid is not self-service yet; tell us what you call them and we will set them for your brand.

Permission sets control both how far down the structure a person can see and which categories of information they can view or edit. Flight-risk assessments carry their own permission. Nobody sees their own record in their own pipeline. The rules are enforced by row-level security in the database, not by hiding fields in the interface.

More detail is on the Security page.

In the United States, on Supabase for the database and authentication, and on Cloudflare for photos and uploaded documents. Traffic is encrypted in transit with TLS and data is encrypted at rest by those providers. The full list of providers is in the Privacy Policy.

Yes. The same application runs in a mobile browser with the same data and the same permissions. There is nothing to install.

yourtalentpipeline.com and app.yourtalentpipeline.com over HTTPS, plus the Supabase host over HTTPS and WebSocket. The complete list, with the optional entries and TLS-inspection guidance, is on the Security page — it is written to be forwarded to a network administrator as-is.

No, and we do not claim certifications we have not earned. The Security page describes the controls that are actually in place; if a control is not listed there, assume it is not in place and ask.

Removing a person takes them out of every view immediately and moves the record to an archived list an administrator can restore from. Promotion counts survive as counts, so a location's history is not rewritten by turnover, and the record of who changed what is kept for the life of your organization's account.

Backups are the exception, and the Privacy Policy says so plainly: a monthly snapshot is retained indefinitely for disaster recovery, so a deleted record still exists in snapshots taken before the deletion.

Pricing depends on the size and shape of the organization, so it is quoted rather than listed. Email questions@groupwork.cloud with roughly how many locations you run.