Skip to main content

Probation and Confirmation

Summary​

Employee employment context includes an optional confirmation date. No probation state, duration, extension, review, completion, notification, or approval workflow was confirmed.

Audience​

  • HR managers, HR executives, and HR administrators
  • Business analysts, product owners, solution architects, and QA engineers

Purpose​

Prevent the presence of a confirmation-date field from being interpreted as a complete probation process.

Confirmed capability​

  • A confirmation date may be recorded and updated as part of employment context.
  • The date is distinct from joining date.
  • The current Employee statuses do not include Probation or Confirmed.

Requires confirmation​

  • Whether every employee is subject to probation.
  • Probation duration, start date, expected confirmation date, and eligibility rules.
  • Manager assessment, HR review, approval, and employee notification.
  • Extension count, duration, reasons, and escalation.
  • Early confirmation, failed probation, and resulting employment status.
  • Timeline entries and downstream effects for confirmation or extension.
  • Relationship with Performance and Workflow.

No flow diagram is presented as implemented because only the confirmation-date field is confirmed. A future approved process may define review, extension, confirmation, or exit branches.

Evidence basis​

The Employee employment model was reviewed for fields, status values, commands, and timeline behavior. No dedicated probation or confirmation workflow was found.

See Also​

Keywords​

  • Confirmation date
  • Probation policy
  • Requires confirmation

Revision Information​

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