Staff Departure Workflows: Is This the Last Day at Work or the End of Employment?
An employee has stopped attending work. Should your staff app now mark their employment as ended, send a final-pay instruction and close every outstanding responsibility? Not from that fact alone. Before commissioning a departure workflow, distinguish the date someone stops performing duties from the professionally confirmed end of their employment and the separately authorised operational actions.
That distinction matters when a notice period is not worked in the ordinary way. One vague “leaving date” can create contradictory instructions for managers, payroll and system administrators. The useful software requirement is a reviewed departure arrangement with explicit dates and responsibilities, not a calendar entry that guesses the legal outcome.
Start with the arrangement, not the badge
Acas's guidance on not working a notice period describes different situations for people with the legal status of employee: asking to leave early, payment in lieu of notice and garden leave. These should not become interchangeable choices labelled “not working”.
The guidance explains that an employee remains employed during garden leave even though they are not working. It contrasts this with its explanation of contractual payment in lieu of notice, where work stops and the contract ends straight away. It also distinguishes cases where payment in lieu is provided for in the contract from those requiring agreement.
These are Acas employment-guidance examples for Great Britain, not universal rules for every worker or country. Have appropriate HR or legal advisers confirm the arrangement, applicability and dates. This article does not calculate notice entitlement, determine an individual's employment status or authorise dismissal.
Give the dates names that describe their meaning
Ask the reviewer which dates the business actually needs. They may include notice received, intended departure, last day performing duties, start of a nonworking arrangement and confirmed employment end. Not every case needs every field, and a requested date must remain distinguishable from a confirmed one.
Keep the evidence for the approved arrangement with its case. Acas says someone seeking to leave before their notice period ends should obtain the employer's agreement in writing. A date typed by an employee is not the same evidence as that agreement.
If a date is disputed or awaiting review, show that honestly. A compulsory final date field should not force reception or a manager to invent an answer merely to save the record. Give the unresolved question an owner and prevent it from silently becoming a final instruction to another team.
Do not let one status run every downstream action
Payroll needs a reviewed instruction about the applicable arrangement, dates and outstanding questions. It should not have to infer the legal treatment from an attendance record. Acas describes continuing usual pay and contractual work benefits during garden leave; a screen saying “no longer working” must not imply that pay has already stopped.
Separately define operational handovers. Who takes over open customer matters? Who reviews delegated approvals? What happens to equipment and organisation accounts? The correct action may have a different effective date from employment ending.
Do not promise that leaving a person marked employed means all access remains available, or that closing an app account settles contractual obligations. Information-security decisions, payroll processing and the employment record need their own authorised owners. The application should expose a missing handover rather than treating the departure badge as evidence that every external system was changed.
Preserve changes without rewriting the past
Suppose an intended working-notice arrangement is replaced by another reviewed arrangement. Keep the original proposal, the authorised change and its effective dates understandable. Updating a default must not make it appear that the person had always been recorded under the new arrangement.
Ask each receiving team to acknowledge the version it has processed. If payroll has already acted on an earlier instruction, show the discrepancy and route it for reconciliation. Do not issue an automatic reversal or duplicate final-pay instruction simply because the employee record was edited again.
A withdrawn or corrected departure record also needs a deliberate path. Restoring a profile's active badge does not prove that external access, customer ownership or previously scheduled actions have been restored. Show what has actually been confirmed.
Demonstrate the nonstandard departures
Use fictional employees and professionally reviewed expected outcomes to test:
- A requested early departure is saved but not yet agreed.
- Work stops while the person remains employed on garden leave.
- A reviewed payment-in-lieu arrangement has different consequences from garden leave.
- A proposed date changes after a downstream team has processed an earlier instruction.
- A system-access action is complete while a separate payroll review is outstanding.
- A corrected case retains its earlier evidence and identifies remaining reconciliation work.
Check dates, instruction versions and outstanding owners, not just the colour of the staff profile. The demonstration verifies the agreed software behaviour; it is not an employment-law opinion or a payroll calculation test.
For a staff-workflow app, bring a redacted departure example and identify the HR, payroll and access-control decision makers. An explainable handover is a better deliverable than an automatic “employee offboarded” message that hides unfinished decisions.
Source and limits
Acas: When an employee does not have to work notice. The distinctions about early agreement, contractual payment in lieu and continued employment during garden leave come from that guidance. The proposed date model, version acknowledgements and cross-team reconciliation are commissioning recommendations. Contract terms and individual circumstances require competent review; software must not invent the applicable rule.