People & HR

How to offboard a departing employee as Restaurant and Hospitality Founders

People & HRFor Restaurant and Hospitality Founders3 apps11 steps~22 min to set up

When a line cook, server, or shift manager leaves — whether they quit mid-service or you had to let them go — you're doing the offboarding in stolen minutes between prep and the dinner rush. You need to cut their access to 7shifts or Homebase, remove them from your Square or Toast location, notify your payroll provider (Gusto, ADP, or Paylocity), collect the drawer keys or uniform, and send final-pay paperwork — all while texting the floor manager about tonight's cover count. There's no checklist. Steps get missed. Two weeks later you realize their login still works on the POS tablet, or their direct deposit is still active.

Build this on Starch → See the apps used

People & HRFor Restaurant and Hospitality Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A step-by-step offboarding checklist automation that fires the moment you mark someone as departing — covering payroll, scheduling apps, POS access, and return of equipment

A task list assigned by role so nothing falls through: who notifies payroll, who pulls system access, who handles final-pay compliance paperwork

An email draft to the departing employee (and a separate internal summary to your managers) generated automatically with the right dates, final shift, and next steps

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Task Manager Email Agent Knowledge Management

Data sources & config

Starch syncs your ADP or Paylocity data on a schedule so the automation knows current employee status. Gmail is connected as a scheduled-sync provider so the Email Agent can send and track offboarding correspondence. Notion is connected as a scheduled-sync provider and powers the Knowledge Management wiki where your offboarding SOP lives. Your scheduling app (7shifts, Homebase) and POS (Square, Toast) are reachable through Starch's integration catalog or through browser automation — no dedicated API required.

Prompts to copy

Create an offboarding task list for a departing hourly employee at my restaurant. Include: remove from 7shifts schedule, disable Square POS login, notify Paylocity to process final paycheck, collect uniform and keys, send final-pay confirmation email, and archive their HR file in Notion. Assign each task a P1 or P2 priority and a due date relative to their last shift.

Draft a final-day email to a departing employee named Maria who worked as a server at our restaurant. Her last shift is this Friday. Include final pay timing, how to return her uniform, and a thank-you note. Keep it short and professional.

Create a Knowledge Management page titled 'Employee Offboarding — Restaurant Operations' that lists every step we take when someone leaves, which systems to revoke, what paperwork is required under state law for final pay, and who is responsible for each step.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Open Task Manager and type: 'Create an offboarding checklist for a departing restaurant employee with tasks tied to their last shift date.' Starch generates a prioritized task list with P1 items (payroll, POS access) due before the final shift and P2 items (archive HR file, return equipment confirmation) due within 48 hours after.

2 Connect your payroll provider — Starch syncs your ADP or Paylocity data on a schedule, so it can verify the employee's active status and flag if a final paycheck run needs to be triggered manually.

3 For your scheduling tool (7shifts or Homebase), Starch automates the removal through your browser — no API needed — logging in and pulling the employee off future shifts the same day you mark them as departing.

4 For Square or Toast POS access, Starch automates through your browser to disable or delete the employee's PIN or login from the back-office portal, no API required.

5 Open Email Agent and type: 'Draft a final-pay and offboarding email to Maria, last shift Friday, returning uniform to the manager on duty, final paycheck via direct deposit within 72 hours per state law.' Review and send with one click.

6 Send a second internal email to your floor managers: 'Draft a note to my management team that Maria's last shift is Friday, reminding them to collect her keys and log it in our equipment tracker.' Email Agent drafts it; you approve.

7 Open Knowledge Management and ask: 'Does our offboarding SOP page cover final-pay timing requirements for our state?' If the page is missing or stale, Starch flags it and you can update it in plain language — no formatting required.

8 Use Task Manager to check off each completed step in real time. Any task that hits its due date unfinished triggers an overdue alert so it doesn't get buried under tonight's dinner rush.

9 After the employee's last shift, run a final audit prompt: 'Show me all offboarding tasks for Maria — which are complete, which are overdue, and what's still open.' Starch surfaces a clean status summary.

10 Archive the employee's file: 'Create a Notion entry for Maria's offboarding — date of separation, final pay amount, equipment returned, and any notes from the manager.' Starch writes the entry directly into your Knowledge Management workspace.

11 Thirty days out, set a reminder task: 'If Maria files for unemployment or we receive any final-pay dispute paperwork, flag it as P1 and alert me.' Task Manager holds this as a standing reminder tied to her name.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

March 2026 — Line Cook Departure, Single-Location Restaurant (45 Seats)

Sample numbers from a real run

Final paycheck (40 hrs @ $18/hr)	720
Unused PTO payout (8 hrs)	144
Uniform replacement (not returned)	45
Time spent on offboarding admin (owner, ~2.5 hrs @ $80 imputed cost)	200

Carlos, a line cook, gave three days' notice on a Tuesday before a busy weekend. The owner opened Task Manager, typed the offboarding prompt, and had a 9-item checklist in under two minutes. Paylocity was already synced to Starch, so confirming Carlos's final hours and triggering the paycheck run took one review step rather than a phone call to the bookkeeper. 7shifts was automated through the browser — Carlos was off the Sunday schedule within the hour. The POS PIN was disabled the same way through Square's back office. Email Agent drafted Carlos's final-pay email (referencing California's 72-hour rule for voluntary separations) and a separate note to the floor managers about key collection. His Notion HR file was updated and archived the same afternoon. Total owner time: about 35 minutes spread across two days, versus the usual 2–3 hours of scattered back-and-forth. The uniform ($45 replacement cost) was flagged in the task list but not recovered — an honest outcome, and at least it was documented.

Measurement

How you'll know it's working

Time-to-complete offboarding (hours from departure notice to all system access revoked)

Final-pay compliance rate (percentage of separations where final paycheck issued within state-mandated window)

Equipment recovery rate (uniforms, keys, tablets returned vs. written off)

Offboarding tasks completed on time vs. overdue (tracked in Task Manager week over week)

Owner hours spent on offboarding admin per departed employee

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Paper checklist + group text to managers

Free and familiar, but the checklist lives in a drawer, the text thread gets buried under weekend comms, and there's no audit trail if a final-pay dispute comes up.

Gusto offboarding flow

Handles the payroll and I-9 side cleanly, but doesn't touch your POS, scheduling app, or internal knowledge base — you still coordinate the rest manually.

7shifts built-in termination workflow

Removes the employee from the schedule, but that's the only system it touches; you're on your own for payroll, POS, email, and documentation.

Google Sheets offboarding tracker

Customizable and shareable, but someone has to remember to open it, fill it in, and follow up — which doesn't happen during a busy service week.

On Starch RECOMMENDED

One platform — task manager, email agent, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Can Starch actually remove someone from 7shifts or Square, or does it just remind me to do it?

Starch automates both through your browser — no API required for either. It logs into the back-office portal the same way you would and makes the change. You review before it runs if you want, or set it to execute automatically once you confirm the departure.

What if I use Homebase instead of 7shifts, or Toast instead of Square?

Same answer. Homebase and Toast are reachable through browser automation — Starch navigates them the same way a human would. If they ever release a formal API, Starch can use that too, but you don't need to wait for it.

Does Starch know our state's final-pay rules automatically?

Starch can draft emails and tasks that reference the final-pay window you tell it (for example, 'California requires final pay within 72 hours for voluntary terminations'). It won't give you legal advice, and you should verify state requirements with your bookkeeper or HR resource — but it can hold and apply the rules you feed it consistently.

Is my payroll data safe if I connect ADP or Paylocity?

Starch uses those connections to read employee status and payroll data on a sync schedule. It's worth knowing that Starch is not SOC 2 Type II certified yet — that's an honest limit. If your payroll provider requires SOC 2 for third-party connections, check their terms before connecting.

We don't have an HR file system — we use a shared Google Drive folder. Does that work?

Yes. Google Drive is reachable from Starch's integration catalog; the agent queries it live when your app runs. You can also use the Knowledge Management app to start building a lightweight internal wiki for offboarding SOPs, so the information lives somewhere searchable instead of buried in a folder no one remembers to open.

What if the employee leaves on bad terms and I need to move fast?

The Task Manager checklist is designed for exactly that — P1 tasks (POS access, scheduling removal) surface immediately and can be executed the same hour. The browser automations don't wait for a sync window; they run on demand the moment you trigger them.