Employee self-service handoff workbook
Fictional worked case: a UK People team keeps Personio as its HR record and Okta for access while Teamed employs a marketing analyst in Germany. This is a proposed workflow, not a tested customer setup. Edit each row to assess a real provider. “Fail” means the fictional acceptance test exposed an exception; it is not a measured provider failure.
Completed fictional payslip rehearsal: assume employee payslip access is available. The employee opens the current month, spots an approved allowance missing, contacts the designated person, and reaches the payroll specialist. The specialist checks the Personio approval against the EOR payroll record, corrects that record and issues a revised payslip; UK People reconciles the allowance and the employee receives an explanation. This is a buyer-designed passing path, not a Teamed demonstration. Its live result below starts at Not run.
For each event, name the authoritative record, the exact field, who starts and approves it, how it moves, who owns a failure, and what observable result proves completion. Changing any workflow field resets that row to Not run. Run the checks again after editing. Data stays in this browser page; export downloads a CSV locally.
Worked handoff, editable| Event | System of record | Field or artifact | Initiator | Approver | Sync or manual route | Exception owner | Acceptance test | Result |
|---|
Initial check
The leave-policy mapping is deliberately failed. Run handoff checks to see the recovery route.
Source context: Teamed’s Personio integration documents a Teamed-to-Personio time-off sync and an error for an unmapped leave policy. Teamed’s service page documents direct employee contact. Other rows are buyer-designed acceptance tests; confirm the exact account, role, country, permissions and service scope before contracting.