@@ -22,7 +22,7 @@ It is the perfect timing to ensure that every employees has:
|
||||
In theory, you already have an onboarding plan for your new employees (if not,
|
||||
Onboarding for new joiner](data/onboarding-for-new-joiner.md)) and a to-do for
|
||||
your admin running the onboarding (if not,
|
||||
[Onboarding admin checklist](data/onboarding-admin-checklist.md)).
|
||||
[Onboarding admin checklist](templates/onboarding-admin-checklist.md)).
|
||||
|
||||
On your employee to-do, be sure to include:
|
||||
|
||||
|
||||
@@ -27,6 +27,6 @@ they left!
|
||||
- Revoke all access to systems
|
||||
|
||||
(if you don't have an offboarding checklist →
|
||||
[Offboarding admin checklist](data/offboarding-admin-checklist.md))
|
||||
[Offboarding admin checklist](templates/offboarding-admin-checklist.md))
|
||||
|
||||
2. Upload a screenshot of your checklist that contains those bullet points below
|
||||
|
||||
@@ -24,7 +24,7 @@ right, it is only about documenting it.
|
||||
|
||||
⇒ Define the recruitment process you follow when bringing on a new member (if
|
||||
you don’t have one formalized, here is a structure:
|
||||
[Recruitment process](data/recruitment-process.md)).
|
||||
[Recruitment process](templates/recruitment-process.md)).
|
||||
|
||||
## Evidence
|
||||
|
||||
|
||||
Reference in New Issue
Block a user