Skip to main content

Career Tracks

The Career Tracks section within Aspire allows administrators to create, manage, and monitor structured career progression paths across the organization.

This page provides:

  • A high-level summary of track status

  • Visibility into competencies and linked positions

  • Quick access to view or edit tracks

  • The ability to create new career tracks

Access

Administrator View:
Main Menu → Aspire > Tracks

Employees will have a read-only or guided experience based on configuration and permissions.

Structure of a Career Track

A Career Track typically consists of:

  • A defined career path (for example: Engineering, Sales, Operations)

  • Multiple progression levels within the track

  • Associated competencies for each level

  • Clear expectations for skill growth and readiness

Tracks are built using competencies from the Aspire competency library (default and custom).

Using Competencies in Tracks

  • Each track level can reference one or more competencies

  • Competencies define the skills required to succeed at that level

  • The same competency can be reused across multiple tracks and levels

This ensures consistency across career paths and evaluations.

Managing Career Tracks (Admin Experience)

Administrators can:

  • View all existing career tracks

  • Create new career tracks

  • Edit existing draft/published tracks

  • Assign or update competencies within tracks

  • Delete tracks when no longer needed

  • Privileges are same as performance management reviews v3.

  • Tracks can be edited after publishing.

  • Versions are visible from 'Change History'

  • Legacy versions are available as read only for reference, can't be restored.

Career tracks can evolve over time as organizational needs change.

Career Tracks and Reviews

  • Career Tracks integrate with Reviews v3

  • Competencies used in tracks can be evaluated during reviews

  • This allows performance discussions to align with career progression expectations

  • If a career track is modified and published again mid review cycle, the existing participants in the cycle won't be impacted.

  • However, newly participants or new cycles would refer to the updated version that's active/published.

Did this answer your question?