Skip to main content

Performance Cycles and Appraisal Periods

Summary​

A review cycle defines the named period and lifecycle that accepts appraisals.

Audience​

HR administrators, managers, employees, product owners, implementation partners, engineering, QA, support, architecture, and security reviewers as applicable.

Overview​

Cycles begin as Draft, can be opened, and can be closed. The status model contains intermediate review phases, but no implemented phase-advance commands move cycles through those intermediate phases.

Confirmed business behavior​

Creating a cycle records its period and notes. Opening makes a Draft cycle active and eligible for appraisals. Closing ends any non-closed cycle. The admin UI exposes create, open, and close actions.

Business rules​

Tenant context and a valid date window are required. Only Draft can open; Closed cannot reopen. Appraisals can be created in the implemented accepting cycle states. Closing does not currently cascade appraisal closure.

Maturity​

The capability is Transitional because canonical staged behavior coexists with compatibility behavior and incomplete authorization governance.

Requires confirmation​

Phase scheduling, eligibility population, reminders, automatic opening/closing, cycle reopening, and appraisal-close cascade require confirmation or are Not implemented.

See Also​

Keywords​

  • Performance
  • Appraisal
  • Draft documentation

Source References​

  • microservices/src/performance-service/Domain/ReviewCycle/ReviewCycle.cs
  • microservices/src/performance-service/Domain/Common/Enums.cs
  • microservices/src/performance-service/Domain/Common/ValueObjects.cs
  • microservices/src/performance-service/Application/Commands/ReviewCycleCommands.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsx

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly