People & HR

How to offboard a departing employee as Foundation and Nonprofit Ops Teams

People & HRFor Foundation and Nonprofit Ops Teams3 apps12 steps~24 min to set up

When a program officer or grants manager leaves your 4-person ops team, you're not just losing a colleague — you're losing the person who knew which grantees were behind on reporting, which DocuSign envelopes were still floating, and which QuickBooks vendor codes map to which program area. Offboarding at a small foundation means manually chasing access revocations across Salesforce, DocuSign, QuickBooks, your donor portal, and whatever Google Drives they shared with grantees. There's no HR department to run the checklist. The ops director does it between board prep and a 990 deadline, usually over two weeks instead of two days.

Build this on Starch → See the apps used

People & HRFor Foundation and Nonprofit Ops Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A structured offboarding tracker that pulls the departing employee's active tasks, open DocuSign envelopes, and outstanding grantee touchpoints from Salesforce and Gmail — so nothing falls through the cracks when they hand off

An automated access-revocation checklist that logs which systems (Salesforce, QuickBooks, Google Workspace, donor portals) need to be touched, with completion status visible to your whole ops team

A knowledge-capture workflow that turns the departing employee's email threads, Notion pages, and Slack messages into a searchable handoff doc before their last day

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

Knowledge Management Task Manager Email Agent

Data sources & config

Starch syncs Gmail on a schedule to surface the departing employee's open grantee threads. Salesforce is connected from Starch's integration catalog and queried live to pull their open opportunities and contact ownership. Notion is synced on a schedule to identify pages they authored. Slack is synced on a schedule for channel membership. DocuSign and your community foundation donor portal are automated through your browser — no API needed.

Prompts to copy

Build me an offboarding tracker for a departing grants manager. Pull their open tasks from our task list, flag any Gmail threads where they're the last responder to a grantee, and generate a handoff summary organized by program area.

Create a knowledge capture app that scans our Notion workspace for pages this employee created or last edited, identifies any documentation that hasn't been updated in 90+ days, and drafts a 'what you need to know' brief for whoever is taking over their portfolio.

Set up an access revocation checklist with items for Salesforce, QuickBooks, DocuSign, Google Workspace, and our community foundation donor portal. Let me check off each one and note the date completed, and send me a Slack message when all items are done.

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

Walkthrough

Step-by-step

1 Connect Gmail (scheduled sync) and Salesforce (from Starch's integration catalog) so Starch can see the departing employee's active grantee threads and open contact/opportunity records.

2 Sync your Notion workspace so Starch can identify every page the employee created or last edited — these are your highest-risk knowledge gaps.

3 Open the Knowledge Management app and prompt: 'Scan Notion for pages owned or last edited by [name], flag any that haven't been updated in 90 days, and draft a handoff brief organized by program area.' Review and assign ownership to each section before their last day.

4 Open the Email Agent app and prompt: 'Find all Gmail threads where [employee email] is the last sender to an external grantee or donor contact, and summarize each open thread with the next required action.' This surfaces the conversations most likely to go dark after they leave.

5 Use the Task Manager app to build your access revocation checklist: Salesforce profile deactivation, QuickBooks user removal, DocuSign admin transfer, Google Workspace suspension, and any donor or community foundation portal logins. Assign each item a due date and owner.

6 Run a browser automation to log into your community foundation donor portal and confirm the departing employee's login — Starch automates the portal through your browser, no API needed — then add the deactivation step to your checklist.

7 Prompt Starch: 'Pull all open Salesforce opportunities where [employee name] is the owner and generate a reassignment list with grantee name, program area, next follow-up date, and recommended new owner from our team.' Send this to the executive director for sign-off.

8 Transfer DocuSign envelope ownership for any in-flight grant agreements — Starch can automate the DocuSign interface through your browser if your plan doesn't expose API access, or query it live from Starch's integration catalog if you have API access configured.

9 Have the departing employee do a 30-minute recorded screen share walking through their top three active grants. Use the Knowledge Management app to transcribe and store the recording summary in Notion, tagged to each grantee.

10 On the employee's last day, run the Email Agent app one final time: 'Draft out-of-office and transition replies for any grantee threads that came in this week, using [successor name] as the new point of contact.' Review and queue for sending.

11 Two weeks after offboarding, prompt Starch: 'Check whether any Salesforce contacts formerly owned by [name] have had no activity in the last 14 days and send me a list.' This catches grantees who fell through the cracks.

12 Archive the completed offboarding checklist in your Knowledge Management app as a reusable template — next time a team member leaves, you start from this instead of rebuilding from scratch.

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 — Senior Program Officer departure, Education portfolio

Sample numbers from a real run

Open Salesforce opportunities owned by departing officer	14
In-flight DocuSign grant agreements awaiting counter-signature	3
Grantee Gmail threads with no reply in 7+ days	6
Notion pages authored by departing officer, not updated in 90+ days	22
Systems requiring access revocation	7

Your senior program officer managing the Education portfolio gives three weeks' notice in early March. She owns 14 open Salesforce opportunities — grant renewals, new LOI reviews, site visit follow-ups — and 3 DocuSign agreements that are sitting with grantees waiting for counter-signatures worth a combined $480,000. Starch pulls her Gmail threads and surfaces 6 grantee conversations where she's the last sender, including one with a community college partner that's been waiting 11 days for a budget clarification. The Knowledge Management app scans Notion and finds 22 pages she authored; 8 of them haven't been touched in over 90 days and cover due-diligence criteria that only she knew. Starch drafts a handoff brief for each program area, flags the 8 stale docs for the incoming program associate to update, and generates a Salesforce reassignment list with recommended new owners based on existing portfolio load. The access revocation checklist gets her off Salesforce, QuickBooks, DocuSign, Google Workspace, your community foundation donor portal, and two grantee reporting platforms within 48 hours of her last day. Total ops director time spent coordinating the transition: about 4 hours over three weeks, instead of the usual two-week scramble.

Measurement

How you'll know it's working

Days to complete full system access revocation after last day (target: under 3 business days)

Percentage of active grantee relationships with documented handoff notes before departure date

Number of in-flight grant agreements or DocuSign envelopes with no assigned owner at time of departure

Stale Notion pages (90+ days unedited) converted to current documentation before the employee leaves

Grantee threads with no response more than 7 days post-departure

Comparison

What this replaces

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

BambooHR or Rippling offboarding module

Good for IT and HR task tracking but has no awareness of your Salesforce grantee relationships, open DocuSign envelopes, or Gmail threads — the foundation-specific handoff layer still has to be built manually.

Manual Google Sheets checklist + email

What most small foundations actually use today; works but requires someone to maintain it by hand, doesn't pull from live data, and gets abandoned after the first few items are checked off.

Notion offboarding template

Good for static documentation but doesn't connect to Salesforce or Gmail to surface what's actually open — you still have to go find the gaps yourself.

Fluxx or Foundant (purpose-built grants management)

These platforms manage grant lifecycle well but cost six figures, assume a dedicated grants team, and don't help you with the cross-system access revocation and knowledge capture that offboarding actually requires.

On Starch RECOMMENDED

One platform — knowledge management, task manager, email agent 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

We use Salesforce for grants management, but it was set up by a consultant and the schema is a mess. Can Starch still pull useful data from it?

Yes. Starch connects to Salesforce from its integration catalog and queries it live — it works with whatever objects and fields exist in your instance. You can tell Starch 'pull all open opportunities where the owner is [name]' and it will navigate your schema to find them, even if your field names are non-standard. You may need to tell it once what your custom fields mean, and it remembers.

What about DocuSign — can Starch actually touch in-flight grant agreements?

Starch can automate DocuSign through your browser — no API needed — to check envelope status, identify who the current owner is, and flag which agreements are waiting on counter-signatures. If you want to reassign envelope ownership, that depends on your DocuSign plan's permissions; Starch can navigate to the right screen and you complete the action, or it can do it automatically if the permission exists.

Is Starch SOC 2 certified? We have to be careful about what systems we connect to something new.

Starch is not SOC 2 Type II certified today. If your foundation's data policy requires SOC 2 before connecting a production system, that's a real constraint worth naming. For teams that can work with that tradeoff — many small foundations can — Starch handles data with care and doesn't store live-queried app data persistently.

Our outgoing program officer has years of Gmail history with grantees. Can Starch search all of it?

Gmail is synced on a schedule and Starch pulls up to 30 messages per page to avoid errors on long threads. It's designed for surfacing recent and active threads — the last 30-90 days of conversation — rather than archiving years of history. If you need to search a full Gmail archive, you'd want to export and index that separately; Starch is best used to surface what's open and unresolved right now.

Can we reuse this offboarding workflow the next time someone leaves?

Yes — that's the point of building it in the first place. Save your completed offboarding app and checklist in the Knowledge Management app as a template. The next time you run it, you update the employee name and Starch re-queries your live systems (Salesforce, Gmail, Notion) to generate a fresh handoff picture. A 4-person team shouldn't have to rebuild this from scratch every time.