What Does a Departing Colleague Know That an AI Agent Can Keep?
Build an AI agent in Gumloop that turns the folders a departing colleague names and their typed answers into an index of who knows what and where it lives.
For a departing colleague, an AI agent in Gumloop builds a hand-over index from the folders they point to and the short questions it asks them: each recurring task, where its files are, the outside people involved, habits written nowhere, and what's still open. It judges no one, and its instructions tell it to contact no one.
Your colleague's last day is on the calendar. Whatever they've written down sits in folders you can open today. The rest leaves on that day, and it includes the things they do from habit.
This AI agent asks your colleague one question at a time and keeps what they say in one place.
If your colleague works on donors, How to Automate Donor Pipelines & Sustain Giving Across Leadership Changes covers what the donor record itself should hold.
What does the hand-over index hold for each task?
One row for each recurring task, with five columns: the task, where its files are, the people outside your organization involved in it, what's done by habit and written nowhere, and what's still open.
Your colleague knows the habit around last year's report, such as sending it early to one outside reviewer.
The AI agent takes every place and name from what your colleague types. It adds a file name when a file in the folders matches the task, and it flags a place your colleague named that has no file, and a task in the files they didn't mention.
What do you paste into the instructions for the hand-over index?
You help me, [YOUR NAME], [YOUR ROLE] at [ORGANIZATION], keep what [COLLEAGUE'S NAME] knows before their last day. You're building a hand-over index for [SUCCESSOR OR TEAM]. Use two things only: the files in your knowledge sources, and what [COLLEAGUE'S NAME] types here. Ask them one question at a time, in plain messages. First ask which tasks they do every week, month or year. Then, for each task, ask where its files are, who outside [ORGANIZATION] is involved, what they do from habit that isn't written anywhere, and what is still open. Build the index as a table with one row per task and these columns: Task, Where its files are, Outside people involved, Done by habit and written nowhere, Still open. Take each place and each name from what [COLLEAGUE'S NAME] types. Where a file in your knowledge sources matches a task, add its file name. If a place they named has no matching file, write "Named, not found in the files." If the files show a task they didn't mention, add a row marked "Seen in the files, not yet explained." If an answer is missing, write "Not yet answered." Make no judgment about [COLLEAGUE'S NAME] or their work. Don't rank tasks. Contact no one, and don't send, share or save anything outside this chat.
How do you build the hand-over index AI agent in Gumloop?
- 01
Ask the colleague to list their tasks and point to where each lives.
Have your colleague write the name of every recurring task and, beside it, the folder or document where its files sit.
- 02
Attach the folders the colleague named, and nothing wider.
In Gumloop, start a new AI agent, open the tab named Agent, paste the block into the instructions box and press Save, because nothing saves until you do. In Knowledge Sources, click + Source and drill into the exact files and folders from step 01. Add no connectors. An edit made mid-sitting reaches the AI agent after the next sync, about every hour, or right away with Re-sync in the source's three-dot menu. Checked on 2026-11-11 against the tabs table, Connectors and Knowledge sources sections of Gumloop's AI agent builder page and How often does Brain sync?. What Do I Put in an AI Agent's Knowledge Source? covers what belongs in a source.
- 03
Switch off web search, web fetch and the multiple-choice questions.
In the Abilities section, switch off Web Search and Web Fetch. A new AI agent has the browser on when you're allowed to use it, so turn it off in the Browser section too. Switch off Ask Question, which pauses the AI agent to ask you a multiple-choice question. After you save, check that the first question arrives as an ordinary message. Checked on 2026-11-11 against the abilities table on Gumloop's AI agent builder page and Gumloop's AI agent browser page.
- 04
Check who can reach it.
Open the tab named Access, which lists Owners, Who Can Use and the other settings for who can reach the AI agent. See who's on it before the outside names go in. Checked on 2026-11-09 against the tabs table on Gumloop's AI agent builder page.
- 05
Turn off what carries one colleague's sitting into the next index.
Turn off Edit Own Instructions, the toggle under the instructions box, since a correction given in chat persists across future tasks. Change a rule by editing the block. Switch off Search Past Tasks in the Abilities section, which is on by default. Reflections can still propose instruction changes, so open the Reflections settings and set Apply Suggestions to Review Queue, where nothing changes until you accept it. Checked on 2026-11-11 against the self-improving instructions and abilities sections of Gumloop's AI agent builder page and Gumloop's Reflections page.
- 06
Check the first row against a task you know from the inside.
Sit with your colleague, start a task and type: begin the hand-over index. They answer the questions themselves. Then read the row for a task you've watched them do against what you know.
I am an ambassador for Gumloop. Code NONPROFITAGENTS takes 20% off your first month.
What should your colleague correct in the first sitting?
Take any three rows and look for the file each names in the "Where its files are" column. A place that isn't there goes back to your colleague as a question.
An empty habit cell for a task they've done for years is a second question for the next sitting, and so are the rows marked "Seen in the files, not yet explained."
Ask your colleague to make the introductions to the outside people before the last day. For a development role, What Should an AI Agent Brief Me On Before a Major Donor Meeting? is where the successor's first donor meeting can start.
Frequently asked questions
What if my colleague only has time for one sitting?
The index still builds. Any cell they haven't answered reads "Not yet answered."
How do I get the finished index out of Gumloop?
Ask the AI agent to export it as a file. Gumloop's page says to ask for an export for a file to keep or share. Decide who should see the outside people column before you share it.
Can it tell me whether my colleague's answers are right?
It compares the places they named with the files in the folders and flags a mismatch. A habit has no file to check, so the index records what they said and the person taking over confirms it.