Assemble an onboarding pack from what your team already wrote down

Turn scattered Slack threads and wiki pages into a single onboarding document that stays current.

For anyone whose onboarding is a person sitting next to you · 8 steps · 7 min

How it works today.

Someone joins on Monday. You sit them down with whoever is free and walk through how deploys work, where the staging environment lives, who approves what. You answer the same questions you answered for the last person. By Thursday you realise you forgot to mention the invoice approval flow, so you Slack them a paragraph.

Three months later another person starts. The explanation is different because the first person left out the part about API keys, and you have since moved to a new project management tool. Nothing is written in one place. Every onboarding is a live performance with no script.

Before you start.

All of it has to be true, or step one fails in a way that is annoying to debug.

Read access to your team Slack or equivalent chat history, going back at least six months.
Read access to any internal wiki, Google Drive folder, Notion workspace, or document repository where process notes live.
A list of the five to eight topics every new person asks about: deploy process, access requests, meeting cadence, tool logins, coding standards, or equivalent for your domain.
Write access to wherever you will store the finished onboarding document.

The steps.

Export the last six months of Slack messages from your team channel
Go to your Slack workspace settings, choose Import/Export Data, and export messages from your main team channel and any onboarding or questions channel. Download the JSON archive. If your plan does not allow export, ask an admin or use a memory agent with Slack integration to index the channel history instead.
Gather every onboarding-adjacent document you already have
Pull together the half-finished wiki page, the Google Doc someone wrote two years ago, the README in your main repository, and any email templates you send to new starters. Put them in one folder. If they are scattered across Notion, Confluence, and Drive, make a plain text file listing their URLs so the agent can reference them.
03
Feed your topic list and source material to a memory agent
Use a tool like Mem, Notion AI, or a custom GPT with file upload. Give it your Slack export, your documents, and your topic list. Ask it to surface every explanation, answer, or instruction related to each topic. Review the results to confirm it found the right threads and did not hallucinate steps.
Paste this
```
I need to build an onboarding document. I have attached Slack message exports and internal documents. For each of these topics—[your topic list]—find every place we explained the process, answered a question, or documented a step. Return a list of excerpts with their source so I can verify them.
```
04
Ask the agent to draft one section per topic
For each topic, prompt the agent to synthesise what it found into a single set of instructions. Specify the format: numbered steps, links to tools, who to ask if something breaks. Read each section and mark anywhere it combined two different processes or skipped a step that only lives in someone's head.
Paste this
```
Using the excerpts you found for [specific topic], write a step-by-step onboarding section. Include tool names, URLs where relevant, and who owns this process. If there are conflicting explanations in the source material, flag them so I can resolve them.
```
Fill the gaps the agent could not find
The agent will surface what was written down. It will not know about the verbal explanation you give every time or the workaround everyone uses but no one documented. Go through each section and add the missing steps yourself, or prompt the agent with the new information and ask it to integrate it.
06
Compile the sections into a single onboarding document
Combine the drafted sections in the order a new person would need them: access and accounts first, then tools, then workflows, then team norms. Add a table of contents. If your agent supports it, ask it to check for duplicate explanations or contradictory instructions across sections.
Paste this
```
I have attached the drafted sections for our onboarding document. Combine them into a single document with a logical order for someone starting on day one. Add a table of contents. Flag any place where two sections contradict each other or repeat the same instruction.
```
Test the document with your next new starter
Give the document to the next person who joins and ask them to follow it without asking you questions unless something is missing or broken. Take notes on where they get stuck. After their first week, ask them to mark every step that was unclear or outdated.
08
Set a quarterly reminder to update the document from recent Slack threads
Every three months, export the latest Slack messages and ask your memory agent to identify new explanations or changed processes. Review the suggestions and update the onboarding document. This keeps it current without requiring you to remember what changed.
Paste this
```
I have attached Slack messages from the last three months. Compare them to the attached onboarding document and identify any new processes, tool changes, or corrections to existing steps. Return a list of suggested updates with the source message for each.
```

What you keep.

Automating the typing does not move the accountability. These stay with a person.

Deciding which topics belong in onboarding and which are better explained in the moment.
Resolving conflicts when the agent finds two different explanations of the same process in your source material.
Testing the document with real new starters and updating it based on where they actually get stuck.
Judging when a process has changed enough that the onboarding section is now misleading rather than just incomplete.

Once it works.

The first run is the demo. These are where the time actually comes back.

Put it on a schedule

Run the Slack export and update check every quarter so the document does not drift from reality as your tools and processes change.

Fire it from an event

When someone asks an onboarding question in Slack that is not covered in the document, flag it automatically and add the answer to the next update cycle.

Run it on a loop

After each new starter finishes their first week, send them a form asking which sections were unclear, then feed their answers back to the agent to draft corrections.

Scale it wider

Once the document is stable, use the same process to build onboarding packs for other teams or roles by swapping in their Slack channels and topic lists.