Staff offboarding.

The messy departure is the one where things stay open behind a name that has left: a login that still works, a salary that keeps computing, assets that never came back, a final payment argued over in the car park. YESS is built so that a separation is one deliberate action with a documented trail, not a scramble of half-remembered steps.

There are two screens in this story. Separation is initiated from the contracts screen at /dashboard/contracts — the Terminate action on an active contract. It is then worked from the offboarding workspace at /dashboard/offboarding, where the checklist and the final settlement live. This chapter walks both, and names the edges plainly.

The exit handled with the same care as the entry — nothing left open behind a departing name.

A separation begins on an active contract. On /dashboard/contracts, the Terminate action appears only on contracts whose status is active; it opens a dialog that captures the human facts of the departure before anything is executed.

Confirming the dialog calls a single database function, fn_separate_staff, which runs the whole exit as one atomic transaction. Six things happen together, or none of them do:

• The contract closes. Its status becomes terminated, with the termination date, reason, separation type, notice period, effective date, and the authorising user all recorded.
• The record is deactivated. The staff member is marked inactive and their employment status set to separated, with the separation date, type, and reason on file — so they drop off every active list (payroll runs, timetables, rosters) while the history stays honest.
• Payroll stops. The current salary assignment is closed and dated, so no future run computes pay for them.
• The login is switched off — if "revoke access" was ticked and the person has a linked user account, their account is deactivated so they can no longer sign in.
• A separation checklist is spawned — from a matching template, or a built-in default if none exists.
• A draft final settlement is opened for finance, in the contract's currency.

The checklist is worked from /dashboard/offboarding, which lists offboarding cards grouped into in-progress and completed. Each task carries one of six categories, so the exit reads as a coherent process:

• Asset return — laptops, keys, ID cards, textbooks.
• Access revocation — accounts, systems, building access.
• Knowledge handover — the handover notes, the class handoff.
• Final settlement — the finance side of the exit.
• Exit interview — the conversation on the way out.
• Compliance — the sign-offs that must be on file.

The built-in default checklist covers return assets, revoke system access, knowledge handover, final settlement, and the exit interview. Ticking a task stamps who did it and when; the checklist flips to completed once every required task is done. The workspace's headline tiles are exit-aware — beyond in-progress and completed counts, they surface how many exits still have access not yet revoked and how many have a settlement still pending, so nothing drifts.

The settlement opens as a draft with its line items laid out, and a single Calculate runs the arithmetic nobody enjoys. The compute function derives four components and sums them to a net figure in the school's currency:

• Pro-rated salary — the monthly wage scaled to the fraction of the final month actually worked, from the day of separation.
• Leave encashment — the cash value of unused leave, from the person's remaining and carried-forward balance valued at the daily rate.
• Severance — the monthly wage times a per-year-of-service rate your policy supplies, times years of service.
• Notice pay — the monthly wage times a number of notice months your policy supplies.

The net amount is a computed column — pro-rata plus severance plus leave encashment plus notice pay, less deductions — so it can never drift from its parts. The severance rate and notice months are the two policy inputs a finance user with the payroll permission enters before calculating; the pro-rata and leave encashment come straight from the contract, the salary, and the leave balances.

Two phrases in this module deserve exact reading.

"Access revoked" means the person's login account is deactivated so they cannot sign in — a real, immediate effect, not a checkbox. It does not, today, strip their individual role and permission grants; those rows remain until an admin clears them. Deactivating the login is what actually stops access, so the practical door is shut — but a thorough exit still removes the roles by hand. The "revoke system access" task on the checklist is a separate tick from that login deactivation, so ticking it does not itself revoke anything.

"Exit interview" is, today, a category on the checklist — a line you tick to say the conversation happened. There is no structured exit-interview form or captured feedback behind it yet. Record the substance elsewhere for now; the structured interview is planned.

The exit spine — the atomic separation, the login kill, the checklist, the settlement compute — is genuinely wired. The finishing work sits on the finance tail and a couple of the checklist categories.

Offboarding is the exit ramp of the employment relationship — the mirror of onboarding, driven by the contract, and handing the final settlement to finance.