The Person Who Comes Back

Before re-employing somebody who left, check three things: why they left and what the file says about it, whether service continuity applies, and whether anything was agreed on departure that affects the position. Re-hiring is common, usually a good idea, and routinely done without anybody looking at the file.

The workflow in “The Person Who Comes Back” becomes more reliable when work records, approvals and later corrections can be distinguished. For teams exploring attendance sheet template, this practical resource can provide practical context, while policy ownership, employee explanation and final decisions remain with accountable people.

The file matters because organisations forget. Somebody dismissed for conduct four years ago can be re-hired by a manager who was not there, into a team that does not know, and the first anyone remembers is when it resurfaces.

For an independent reference relevant to “The Person Who Comes Back”, consult the CSO insider-threat guide. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

Continuity of service

Where somebody returns after a short gap, service may be continuous for some purposes, which affects notice, entitlements and the length of time the person has been employed for every rule that depends on it.

Whether it applies, and after what gap, differs by jurisdiction and sometimes by the reason for the break. It is a question for somebody qualified in the place concerned, and getting it wrong produces an error that compounds quietly for years — a notice period calculated from the wrong start date, a termination payment understated, a probation period applied to somebody who should not be on one.

Settlement terms that survive

Where the departure was settled, the agreement may contain something relevant: a term about re-employment, a warranty that the person has not applied, or an agreed reference inconsistent with hiring them back.

Read it before offering. An organisation that paid to settle a departure and then re-hires the person without checking has at minimum created a confusing record and may have done something it agreed not to.

The do-not-rehire marker

Most organisations keep some form of marker and most keep it badly: added by whoever processed the exit, with no reason recorded, no review and no idea who can remove it.

• Record the reason, in a sentence, not just the flag.
• Record who applied it and when.
• Set a review date rather than leaving it indefinite.
• Define who may remove it and on what basis.
• Make sure it is covered by the retention schedule, like anything else.
• Remember that the person may be entitled to see it.

The last point is the one that catches organisations out. A marker reading "difficult, do not touch" is a record about a person, and it will not read well to the person it is about.

Checking consistently

The check has to apply to everyone or it is worse than not having one. Looking up the file for candidates somebody vaguely remembers, and not for those nobody does, produces exactly the inconsistency that causes problems.

Build it into recruitment as a standard step: has this person worked here before, and if so what does the record say? It takes a minute and it is the only way the marker is worth keeping at all.

What to tell the returning person

Where somebody returns after a difficult exit, say what has changed and what has not. If the previous matter is closed, say so. If a condition attaches — a role, a reporting line, a period of review — say that too, in writing.

Leaving it unspoken means both sides are operating on assumptions, and the assumptions differ. It is a question worth settling once, before the start date, rather than when something reminds everybody.

The internal move that is almost the same thing

Much of this applies to somebody moving between parts of the same group, or between entities, where employment technically ends and begins again. These are processed as transfers and the record frequently does not follow.

Check what actually happens to continuity, to the contract and to the file when somebody moves between entities. In several organisations the answer is that a new record is created and the old one is closed, which produces a person whose service history has a gap that never existed.

The ones you should re-hire

The useful counterweight to all of this is that people who left well and want to come back are frequently the best available candidates: they know the organisation, they chose it twice, and they cost almost nothing to onboard.

An organisation that handles exits badly loses this entirely. That is rarely counted as a cost of a poor leaver process and it is a real one, visible in the number of former employees who would consider returning — which is a question worth asking, once a year, of anybody who left in the last three.