Make Sure What Leaves With an Engineer Is Only the Engineer
A software exit runs through a long notice period during which the person is still employed and still has access. Handover is left to the individual, access is closed by a separate request, and settlement waits on clearances from several teams. We help you design the exit from acceptance of resignation to relieving letter, with handover, staged access and alumni records. GullyHR does not give legal advice; confirm your obligations with a qualified professional.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsThe starting point
Is Your Exit Process Protecting Code, Clients and Knowledge?
What leaves with a developer is not just the developer. It is knowledge of systems, relationships with clients and, if nobody is watching, access that outlives the notice period.
We help you run the exit as a planned process that begins on resignation, not on the last day.
You may be experiencing:
- Handover left to the individual, with a document or two and a few calls.
- Client and project transition decided by the manager, with no checklist.
- Access revocation requested from IT as a separate matter, sometimes on the last day and sometimes later.
- Shared credentials and service accounts not rotated after someone leaves.
- Laptops and devices chased by hand after the last working day.
- Final settlement waiting for clearances from several functions in turn.
- No rule on when a counter-offer is made during notice.
- Experience letters and rehire status given or withheld inconsistently.
What we can help with
Our Exit and Alumni Management Services for Software Companies
Resignation Acknowledgement and Notice Plan
Define how a resignation is received, acknowledged and recorded, who is told, and how the notice period is planned between resignation and last working day, including any agreed shortening.
Retention Conversation Rule
Decide who speaks to the person, when, and who may make a counter-offer, so a retention conversation is consistent and recorded without being a reflex.
Handover and Knowledge Transfer
Set a handover plan that covers systems owned and not just tasks: repositories, pipelines, documentation, known issues, workarounds and client or stakeholder introductions, with an owner who accepts it.
Staged Access Revocation
Tie access closure to the HR exit event, with a sequence: production and infrastructure first, then source control and cloud accounts, client systems and VPN, email and devices, with shared credentials rotated.
Parallel Clearances
Run clearances in parallel: IT, finance, admin, project and HR, each with a named owner and a time limit, so settlement is not delayed by waiting for each in turn.
Full-and-final Settlement Process
Define the steps, owners and timing of settlement for leavers, linked to leave balance, recoveries and clearance status, with a review before release.
Letters and Rehire Eligibility
Prepare relieving and experience letter formats, with an approval route, and a recorded rehire status given on stated grounds, so decisions are consistent.
Alumni Relationship
Keep a simple alumni record and a light-touch route for referrals and rehire, which matters in a market where former colleagues return productive and recommend others.
The deliverables
What You Receive
Depending on the agreed scope, you can expect:
- A resignation-to-relieving process map with owners.
- A retention conversation and counter-offer rule.
- A handover plan format and knowledge transfer checklist.
- A staged access revocation sequence tied to HR events.
- A parallel clearance checklist with time limits.
- A settlement process with a pre-release review.
- Letter formats and a recorded rehire status.
- A set-up of the exit workflow, reminders and records in your system or on GullyHR.
Step by step
How We Work
Review Recent Exits
We trace the last few exits, looking at handover, access closure and settlement timing, and ask managers what was missed.
Agree the Sequence
We settle what starts on resignation, what must be finished before the last working day and who owns each step.
Design the Formats
We write the handover plan, checklists, access sequence and letters, and test them on the next live exits.
Set Up the Workflow
We configure the exit workflow, access tasks and reminders so that clearances run in parallel and are visible to HR, IT and managers.
Review Against the Baseline
Before work starts we record where you stand, and review the results after a group of exits has gone through.
The difference
Close Exits Cleanly
A planned exit process helps your company:
We do not promise outcomes. We record a baseline before work starts, covering the time from last working day to access closure, the share of exits with a written handover and the days taken to settle accounts, and report against it, so you can see what changed and what did not.
- Start the handover on the day of resignation.
- Revoke access in a set order, tied to the HR event.
- Collect devices and assets on a schedule.
- Run clearances together and not one after another.
- Settle accounts on a defined sequence.
- Keep a record of rehire status and alumni.
Find your fit
Who This Service Is For
Product Companies Protecting Systems Knowledge
Make sure the person who knows a system hands it over.
IT Services Firms with Client Programmes
Transfer client relationships and project knowledge in order.
Companies with Long Notice Periods
Use the notice period for handover and not just waiting.
Firms Meeting Client Security Terms
Show that access was closed and devices were returned.
Growing Companies with Regular Exits
Replace case-by-case handling with a routine.
How it usually shows up in information technology and software
In software companies, exits run through long notice periods during which the resigning employee is still on the payroll and still has access. Handover is typically left to the individual: a document or two, a few calls and a hope that the code is understood. Client and project transition is decided by the manager. Access revocation is a separate request to IT, which may happen on the last day, or later. Asset return for laptops and devices is chased by hand, and full-and-final settlement waits on clearances from several functions. Retention conversations occur, but without a rule for when a counter-offer is made. Experience letters and rehire eligibility are given or withheld inconsistently. The alumni relationship, which could provide rehires and referrals, is usually neglected.
Common challenges
Where it goes wrong in information technology and software
Handover is optional
Knowledge transfer is left to the leaver's goodwill and the manager's attention.
Access outlives the exit
Revocation depends on a separate request that can be late or missed.
Notice is unmanaged
The notice period runs without a plan for client transition or a view of risk.
Alumni are ignored
Rehire and referral value is lost because the exit was handled coldly.
A better process
What a working version looks like
- 01
Start on acceptance
When the resignation is accepted, a checklist opens with owners for handover, clearance and settlement. The exit process sets the order.
- 02
Require a handover plan
Code, documentation, client contacts and open work are covered in writing and reviewed by a named receiver.
- 03
Stage the access
Access reduced as work is transferred and removed entirely on the last working day, triggered by the HR record. See exit and offboarding.
- 04
Run the clearances in parallel
IT, finance and the manager clear together, so the settlement is ready at the end.
- 05
Close well
Exit interview, relieving and experience letters, and a stated rehire position, with an alumni contact where appropriate.
What to check this week
- Review the last two handovers and see what was missing afterwards.
- Check when access was removed for the latest leaver.
- Ask who decides on a counter-offer and on what basis.
- Time the settlement from the last working day to payment.
- Read the rehire status recorded for recent leavers.
Confirm with a qualified professional. What applies depends on your establishment, your state and your sector, and it changes. This page describes a practice; it does not state a legal position.
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.
Questions on this, in information technology and software
That depends on your risk position and client terms. We help you set a staged sequence, with the most sensitive access changed first and the rest closed by the last working day, all tied to the HR exit record.
By defining what is handed over, to whom, and how acceptance is shown. The plan covers systems, ownership, known issues and introductions, and the receiving person confirms what they have understood.
Terms differ by contract. We design the process to handle a shortened notice, by recording who approved it and what handover was completed, and confirm contractual points with a qualified professional.
We define the steps, owners and timing, linked to clearances and leave balance. Calculations that touch statutory components are for your accountant, and GullyHR does not give legal advice, so confirm your obligations with a qualified professional.
In software it often pays: rehires arrive productive and former colleagues refer others. We help you set a light route for alumni records and rehire eligibility, and apply it consistently.
Often yes. We design the sequence first, then set up tasks, approvals and reminders in your HR system or on GullyHR, with links to access requests where your IT tools allow it.
With a plan from acceptance: handover tasks, client transition, a review of access and regular check-ins. An unmanaged notice period carries the most risk.
On the last working day, with sensitive access reduced earlier if the work has been handed over. Tie it to the HR exit record rather than to a separate request.
Code and repositories, documentation, environments, credentials rotation, client contacts and open issues, each signed off by the receiver.
Because rehires arrive productive and former colleagues refer good people. That depends on the exit having been handled respectfully.
Control What Leaves With Your People
If access, knowledge and settlement are handled differently every time, start with a defined sequence from resignation to relieving letter.
Prefer to talk first? Call +91 80958 58589 or write to hello@gullyhr.com.
Book an Exit Process Consultation
Tell us about your notice periods, systems and how exits run today.
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.
To run this in a system rather than on paper, see exit and offboarding 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.