Documents & E-Signatures

Offboarding

The deliberate offboarding flow — the Offboard form, the one-transaction cleanup it performs across leaves, approvals, time, expenses, documents, projects and access, the guardrails, and offboarding checklists.

Offboarding

Offboarding is how a departing employee is cleanly removed from BookYourPTO. It is a deliberate action — there is no "silent deactivation." You either run the checklist from /users/:id?tab=offboarding, or you run the Offboard action, which performs the full cleanup.

Why a deliberate flow replaces silent deactivation. Just flipping an account off leaves a trail of orphaned work — pending approvals nobody can action, future leaves still on the calendar, scheduled shifts, managed projects with no owner. The Offboard action does a clean handoff, leaves an audit trail, and revokes access immediately.

The Offboard form

FieldRequiredNotes
Employment end dateYesThe departure date
Termination codeYesVoluntary resignation / Involuntary termination / Layoff / Retirement / End of contract / Mutual agreement / Other
Termination notice dateOptionalWhen notice was given
ROE completed dateOptionalRecord of Employment completion
Replacement head(s)ConditionalOne per department the user leads
NotesOptionalFree text, max 2000 characters

What the Offboard action does (one transaction)

When you confirm, all of the following happen atomically — it all succeeds or none of it does:

  • Leaves — cancels pending and future approved leaves
  • Leave approvals — reassigns pending leave approvers
  • Time tracking — auto-clocks-out any open time entries
  • Expenses — cancels draft expense reports; reassigns those awaiting approval
  • Documents — expires pending document assignments
  • Reporting line — reassigns direct reports up the chain
  • Department — reassigns the department head (using the replacement heads you named)
  • 1:1s — deactivates 1:1 series
  • Onboarding — cancels the user's own active onboarding
  • Projects — reassigns managed projects
  • Tasks — unassigns open tasks
  • Benefits — terminates active benefit enrollments
  • Shifts — cancels future scheduled shifts

Then it:

  • Sets the account inactive
  • Records termination metadata (the form fields above)
  • Writes an audit entry
  • Revokes all refresh tokens, trusted devices, and calendar feed tokens — immediate lockout
Immediate access revocation. The moment offboarding completes, the person can no longer authenticate from any device, and their calendar feed tokens stop working. There's no lingering session to clean up later.

Guardrails

Offboarding is destructive, so it's fenced:

RuleReason
ADMINISTRATOR / EXECUTIVE onlyDestructive, organization-wide action
Only an EXECUTIVE can offboard an EXECUTIVEProtects the top of the org
Cannot offboard the last active executiveThe org must always have an exec
Cannot offboard yourselfPrevents self-lockout
Cannot offboard an already-inactive userNothing to do
Multi-department head needs replacement headsNo department is left leaderless

Offboarding checklists

Offboarding checklists (return laptop, revoke SaaS access, exit interview) are not auto-created. An admin starts one from the profile's Offboarding tab. A checklist works like onboarding, but its due dates are anchored to the employment end date instead of the start date.

Roles & permissions

RoleRun Offboard actionOffboard an executiveStart a checklist
EMPLOYEENoNoNo
DEPARTMENT_HEADNoNoNo
ADMINISTRATORYesNoYes
EXECUTIVEYesYesYes

Troubleshooting

Error / symptomCauseFix
Offboard blocked — "last executive"You're removing the only active execPromote another executive first
Offboard blocked — "cannot offboard yourself"Self-offboarding is disallowedHave another admin/exec do it
Offboard blocked — "already inactive"The user is already deactivatedNo action needed
Offboard blocked — needs replacement headsThe user leads one or more departmentsName a replacement head for each department they lead
"Only an executive can offboard an executive"Target is an executive, you're an adminAn executive must run it
Departing user still receives approvalsOffboard wasn't run (silent change instead)Use the Offboard action — it reassigns pending approvers