On & Off-Boarding
Employee Onboarding & Off-boarding Policy
1. Purpose To establish a standardized process for securely onboarding new employees and off-boarding departing personnel, ensuring compliance with legal obligations, confidentiality standards, and operational integrity.
2. Scope Applies to all full-time, part-time, contract, and temporary employees at MFC Safe.
3. Onboarding Procedure 3.1 Pre-Employment Requirements:
Signed employment contract
Completed NDA and confidentiality agreements
Identity verification and background checks
3.2 Access Provisioning:
Email and account setup (e.g., Google Workspace, Didge platform)
Role-specific platform access
VPN, GitHub, and API keys (if applicable)
Logging of access in secure audit registry
3.3 Initial Training:
Orientation on company policies (e.g., Security, Data Retention, Compliance)
Job-specific tool and system training
Introduction to internal communication protocols and escalation procedures
3.4 Compliance Checklist:
ISO 27001 Security Awareness Briefing
Acceptance of Code of Conduct
Acknowledgement of Acceptable Use Policy
4. Off-boarding Procedure
4.1 Notification & Documentation:
Written notice of resignation or termination
Exit interview documentation
Off-boarding plan approved by HR and direct manager
4.2 Access Revocation:
Disable access to all systems (email, platform, VPN, admin consoles)
Retrieve company-issued devices (phones, laptops, tokens)
Revoke third-party service access (e.g., AWS, MongoDB, Slack)
Review audit logs for anomalous access prior to departure
4.3 Final Compliance Checks:
Reaffirmation of NDA obligations
Return of confidential documents (physical or digital)
Deletion or transfer of relevant knowledge base items
Update HR and IT records
5. Responsibilities
HR Team: Oversight of onboarding/off-boarding workflows
IT Admins: Account provisioning/deprovisioning
Line Managers: Ensuring access relevance and task handover
6. Policy Review This policy is to be reviewed annually or after major organizational changes.
7. Versioning
Version: 1.0
Approved by: Director of Operations
Effective Date: 02 April 2025
Last updated
Was this helpful?
