Why does offboarding need to run as one process instead of each office keeping its own checklist?

Because the failure mode of offboarding is not any single office doing its step badly. It is the handoff between offices. A checklist in the human resources office and a separate one in the technology office can both be complete and correct while a step that belongs to neither sits undone, because each list only shows its own office's work. One process means one sequence: every step visible in the same place, every owner able to see what is pending, and a single record of what actually happened. The offices keep doing their own work. What changes is that the district can see the whole chain instead of hoping four separate lists add up.

Does the offboarding process handle the resignation or termination approval itself?

No, and it should not. The separation is approved through its own routed process, a personnel action request, with its own approvers and its own record. Offboarding begins when that approval completes. Keeping the two separate matters because they answer different questions: the action request records that the district decided to end the employment, and offboarding records that the district closed it out cleanly. If a question ever surfaces later, those are two different records serving two different purposes.

What happens when the employee leaves before finishing their part?

The process keeps running, because almost none of it depends on the departing employee. Equipment return and key collection are steps the building completes and records whether or not the employee shows up for a formal checkout. The exit interview is the one step that genuinely needs the person, which is the reason to schedule it before the last day rather than on it. If it does not happen, the step is recorded as incomplete rather than silently forgotten, which at minimum tells the district something about how the separation went.

Who sees the exit interview responses?

The people the process routes them to. When the interview workflow is built, the district decides where completed responses go, and that is where they go: the human resources director, the superintendent, or whoever the district names. Responses are not sitting in a file drawer that anyone with a key can open. That routing decision is worth making deliberately, because candor in an exit interview depends on the departing employee believing the answer to exactly this question.

Running exit paperwork and offboarding when an employee leaves

Flow Forms · HR and personnel operations

The short answer

Offboarding begins after a separation is approved and covers everything that has to close before the employee is gone: equipment returned, system access ended, final pay routed, and an exit interview if the district conducts one. Almost none of that work belongs to a single office. It moves as a chain of handoffs across human resources, payroll, technology, and the building, and because no one office sees the whole chain, the steps get tracked by memory and email. Done well, offboarding runs as one defined process, with every step assigned to a named person and recorded as it completes.

Why the existing system does not cover it

The payroll or human resources system closes the employment record. It processes the final paycheck, ends benefits, and sets the official last day. That is its job, and it does it. The work around that record is a different kind of work. Equipment return belongs to the building or the technology office. Access removal belongs to technology. Keys belong to facilities. The exit interview belongs to human resources. The system that closes the employment record was never built to route tasks between those offices, so districts cover the gap with a checklist. A checklist is a document, not a process. It names the steps. It does not assign them, move them, or record when they happened.

How districts handle it now

In most districts, offboarding runs on a checklist and a set of emails. The checklist lives in the human resources office, on paper or in a spreadsheet, and someone walks it through by hand: an email to the technology director, a note to the head custodian about keys, a reminder to payroll about the final check. The exit interview, where it happens at all, is usually a paper form. The departing employee fills it out on their last day, or takes it home with a return envelope, and the completed forms go into a file drawer where no one reads them again. Whether every step actually finished depends on the person keeping the checklist, and on every office answering the email.

Where it goes wrong

Separations cluster at the end of the school year. Resignations and retirements land in May and June, which means offboarding runs during the weeks when buildings are emptying out and the people responsible for each step are hardest to reach. The steps with hard deadlines take care of themselves: the final paycheck forces payroll's step, and the building checkout forces the keys. The steps without a deadline are the ones that slip. A login still works in September for someone who left in June, because the email to the technology office arrived during checkout week and never got a reply. The exit interview slips first of all, because nothing forces the conversation, and whatever that employee could have told the district about why they left walks out the door with them.

What doing it well actually requires

Offboarding starts where the approval ends. The separation itself, whether a resignation, a retirement, or a termination, was already routed and approved as a personnel action request with its own record. Offboarding picks up from that approval. It does not re-approve the separation, and it should not wait for someone to notice the approval happened and start a second process by hand.

From there, the requirement is ownership. Every step is assigned to a named person: the technology director owns access removal, the building owns equipment and keys, human resources owns the exit interview, payroll owns the final routing. Each owner can see what is pending on their own list, and a reminder reaches them without anyone composing an email. The process does not disable the account; the technology office does that, the same as always. What changes is that the step is assigned, visible while it waits, and recorded when it is done, instead of riding on an email that may have landed during the busiest week of the year.

The exit interview deserves more structure than an open comment box. Sublette County School District #9 in Wyoming runs its exit interview through a single form with structured fields: the type of interview, the factors pulling the employee toward something else, the factors pushing them away, and the impact of their supervisor. Before that, it was a paper form. Because the fields are structured, the record captures the same signal no matter who conducts the interview or how the conversation wanders. The same form supports a stay interview with a current employee by switching the interview type, but the exit conversation is the one a district never gets a second chance at.

Finally, the record has to outlast the people involved. Every completed step carries who did it and when. Exit interview responses accumulate as records rather than papers in a drawer, and they can be pulled together later, when someone finally asks why one building lost four teachers in two years. That question always comes. The answer only exists if the interviews were captured somewhere that keeps them.

Common questions

Questions we hear from every human resources office.

Why does offboarding need to run as one process instead of each office keeping its own checklist?: Because the failure mode of offboarding is not any single office doing its step badly. It is the handoff between offices. A checklist in the human resources office and a separate one in the technology office can both be complete and correct while a step that belongs to neither sits undone, because each list only shows its own office's work. One process means one sequence: every step visible in the same place, every owner able to see what is pending, and a single record of what actually happened. The offices keep doing their own work. What changes is that the district can see the whole chain instead of hoping four separate lists add up.
Does the offboarding process handle the resignation or termination approval itself?: No, and it should not. The separation is approved through its own routed process, a personnel action request, with its own approvers and its own record. Offboarding begins when that approval completes. Keeping the two separate matters because they answer different questions: the action request records that the district decided to end the employment, and offboarding records that the district closed it out cleanly. If a question ever surfaces later, those are two different records serving two different purposes.
What happens when the employee leaves before finishing their part?: The process keeps running, because almost none of it depends on the departing employee. Equipment return and key collection are steps the building completes and records whether or not the employee shows up for a formal checkout. The exit interview is the one step that genuinely needs the person, which is the reason to schedule it before the last day rather than on it. If it does not happen, the step is recorded as incomplete rather than silently forgotten, which at minimum tells the district something about how the separation went.
Who sees the exit interview responses?: The people the process routes them to. When the interview workflow is built, the district decides where completed responses go, and that is where they go: the human resources director, the superintendent, or whoever the district names. Responses are not sitting in a file drawer that anyone with a key can open. That routing decision is worth making deliberately, because candor in an exit interview depends on the departing employee believing the answer to exactly this question.

How Flow Forms handles it

Sublette County's exit interview runs in Flow Forms. The surrounding chain is the kind of routing Flow Forms builds with a district directly: the offboarding sequence gets defined around how the district already handles separations, each step is assigned and recorded, and the district can have it changed whenever the work changes.

See how it would work for your district →