Start date
A first week that runs itself
Accounts, intros, docs and check-ins, on the right day.
Tables
Employee offboarding agentNothing forgotten on the way out.
Before someone's last day, the agent reads their row in your people table and writes a checklist for handover, access and equipment. It tells each owner their part, after you approve.
Your first signup includes $50 in free credits.
Last day
Wrap up a leaver's last day
- Reads
- People table, shared files
- Grows
- An offboarding checklist
- Lands in
- Google Docs, Slack
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
Three days before someone's last day, make an offboarding checklist in Docs from our template. List the files they own in Drive for handover, and tell the manager, IT and HR what each of them must do.
TulipFarm
I made an agent called Offboarding helper and a workflow that starts before the last day in your People table. It reads the row, your template and the person's files in Drive. Creating the Doc and posting in Slack asks you first. Activate it?
ActivateEdit first
Three days before a last day.
Every run is saved as an agent task you can open, check and rerun.
- Date in a table
A last day in the People table is 3 days away
Run startedStarted - Reads
The leaver's row: role, manager, equipment
1 leaver - Reads
Files owned by the leaver in Drive
23 files, 4 shared - Writes
A checklist by owner, using your offboarding skill
1 checklist, 9 tasks - Asks first
Create the Doc and post each owner's tasks in Slack
Approved - Creates
Doc in Google Docs, messages in Slack
1 Doc, 3 messagesCompleted
The checklist in Google Docs.
Each task has an owner, so nothing sits with no one.
Google DocsOffboarding checklist · Leaver 3
Manager
- Pick owners for the 4 shared files.
- Hand over open work and contacts.
IT
- Remove access on the last day.
- Collect the laptop and badge.
HR
- Final pay and paperwork.
- Exit conversation booked.
What gets planted.
Three parts you own and can change at any time.
- Agent
Offboarding helper
Its instructions, and the table and files it may read.
- Skill
Offboarding checklist
Your tasks, with an owner for each.
- Workflow
Before the last day
Starts on a date in your People table.
Uses
- TablesTables
- Google Docs
- Google Drive
- Slack
Add if you use it
- Google Calendar
Gmail
It reads quietly. It asks before it acts.
Reads without asking
- The leaver's row in your People table
- Files they own in Drive
- Your offboarding template
Asks you first
- Creating the checklist Doc
- Posting in Slack
- Moving or sharing any file
It uses your own connections, so it never sees more than you can.
Grow it your way.
Book the exit talk
Draft a calendar event for the exit conversation.
File transfer list
Ask it to propose a new owner for each file, for the manager to confirm.
Weekly list
Post all upcoming leavers to a private HR channel each Monday.
Questions, answered.
Does it remove access?
No. It tells the owner, such as IT, what to do. It does not turn off any account.
Does it move files?
No. It lists them for handover. Moving a file would be a change, and that asks you first.
Who sees this?
Only people you share the Doc and the Slack messages with. Keep it to the managers and teams involved.
New response
Handle access requests
Checks each request against policy and routes it for approval.
On mention
Answer policy questions
Staff ask in Slack and get an answer from your written policies.
A tidy goodbye, every time.
Public beta, open to everyone. Your first signup includes $50 in free credits.