1. Talent Suite
  2. Features
  3. Performance
Feature · Performance

Performance

Tie goals and reviewer decisions to a dated performance cycle.

OverviewReviews submitted
Talent Suite · Performance

Reviews submitted

Approval conditions

New
Review numberCycleSubjectReviewerOverall rating
PR-23382PC-6473Below expectations
PR-57754PC-1269Meets
PR-11261PC-3167Exceeds
PR-82639PC-4128Outstanding
PR-82720PC-4101Below expectations
6 of 6 records
PC-6473Performance reviews · PR-23382
Below expectations
Example screen with sample data

What you can do

Keep the decision with the record

HR Business Partner (HRBP) manages performance cycles, goals and reviews. The cycle sets the period and review dates. Each review identifies its subject, reviewer and type, then carries narrative, rating and decision status. A submitted manager review can be considered in calibration before it is released and later acknowledged.

Employee can update own goals; a goal links back to its employee and cycle. Progress against a goal is different from the final rating recorded after review. Keep the review with the right subject and cycle when discussing a development need. L&D Admin can then manage a separate course enrollment, with completion recorded in learning records.

How the work is organized

  • Open a cycle. HR Business Partner (HRBP) sets the cycle dates and review deadlines, then associates goals and reviews with that cycle.
  • Collect the review. The reviewer records the review type, subject, narrative and rating before submission.
  • Release the result. Calibration and release follow the submitted review, with acknowledgement tracked on the same review record.

What to agree during setup

Agree which employees enter each cycle, who reviews them and which dates control self and manager reviews. Employee can manage own goals; HR Business Partner (HRBP) manages goals and reviews. A goal’s progress and final rating serve different purposes, so decide when each is updated. Check that a review’s subject and reviewer are the intended employees.

Before calibration, decide who checks submitted ratings and what must be resolved before release. CHRO / VP People has read access for oversight. The team should record the review’s submitted, released and acknowledged dates when those states are reached. Course assignment can follow a development goal, but a review status does not itself complete learning.

Check the handoff on an actual case

Use a manager review whose subject has a development goal in the same cycle. HR Business Partner (HRBP) checks the cycle and due date; the reviewer checks the goal’s progress and records the narrative and rating. After submission, HR Business Partner (HRBP) compares the review with other submitted work in the cycle before calibration. The released result remains separate from the employee’s later acknowledgement.

Try a review entered under the wrong cycle. Correct the cycle reference and confirm the subject, reviewer and deadlines again before release. Then choose a training course for the development need, with L&D Admin owning the enrollment. The course progress should remain visible in its own record rather than being assumed from the review outcome.

What your team sees

  • Reviews submitted — Submitted reviews with cycle, subject, reviewer and rating visible.
  • Active employees — Current employees available to match against review subjects.

Follow the work through

See the connected process for the decision sequence and the data model for the record links.

What it keeps track of

Data model
Performance cycles
Annual, mid-year and probation performance cycles.
Goals
Employee goals tied to a performance cycle.
Performance reviews
Subject-by-reviewer review within a cycle.
Employees
Central person record for every worker in the organization.

Who uses it

Permissions
HR Business Partner
(HRBP) owns the main review.
Other configured roles see or update only the records granted to them.
Test each handoff with the person's normal access before broadening it.

Set up Talent Suite your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started