Exit and Alumni Management for Information Technology and Software
Resignation to relieving letter, in a defined order.
What this looks like in information technology and software
The parts of exit and alumni management that are specific to this sector, rather than general.
Notice, Knowledge Transfer and Access Revocation
The asset walks out every evening; at exit it does not come back.
What this coversHide
Notice, Knowledge Transfer and Access Revocation
The asset walks out every evening; at exit it does not come back.
What this coversHideIn knowledge work the exit risk is concentrated in two places: what the person knows and what the person can still reach. Both need closing deliberately and on different timelines.
Knowledge
- Documented handover of systems owned, not just tasks
- Code, repository and pipeline ownership transferred
- Client and stakeholder introductions made in person
- Known issues and workarounds written down
- Credentials rotated where shared
Access
- Production and infrastructure access revoked first
- Source control, cloud and admin accounts closed
- Client systems and VPN access notified and revoked
- Device return and disk handling
- Email forwarding and data retention decided by policy
We also build the alumni relationship, because in this sector it pays. Rehires arrive productive, and former employees are a consistent referral source — but only where the exit was handled well enough that they would come back.
The general method — what exit and alumni management covers, the questions it answers and what an engagement produces — is the same whatever the sector, and is set out on the exit and offboarding process page. What is above is the part that differs for information technology and software.
Other HR topics for information technology and software
Where to start
Most engagements begin with a review of how this runs in your business today, then a written process and the sequence to implement it.
See all HR topics for information technology and software, or another industry.