Write your first onboarding document
A complete new-hire, new-client, or new-vendor doc from a single conversation
After this, you'll be able to write a complete onboarding document (new hire, new client, or new vendor) in under 30 minutes by giving Claude a structured description of what the new person needs to know, who they contact, and what commonly causes friction.
Before you start
You'll want a working sense of The SOP prompt structure: four inputs before writing a multi-section onboarding document, which leans on the same context and format inputs to come out usable.
The idea
Claude can produce a complete new-hire, new-client, or new-vendor onboarding document in under 30 minutes, faster than most teams take just to find the last version. The cost of skipping it is real: only 12% of employees say their company does a great job of onboarding (Gallup), and a shaky first few weeks is one of the most common reasons new hires quit early. The document is not the whole answer, but the absence of one makes every other answer harder to give.
Here is the before and after: An agency owner spending her Sunday writing a new-client onboarding doc starts from a blank Google Doc, spends two hours on it, and sends something she is only 60% satisfied with. With Claude, she describes six things every new client needs to know in the first week, the tools they get access to, and who their contact is at each stage. The result is a formatted, section-divided onboarding document she can reuse for every client with minor edits.
Now try it: Ask Claude "Write an onboarding document for a [new hire / new client / new vendor] at my [describe your team type and size]. Include week 1 essentials, key contacts, tools they receive, and the 2 to 3 friction points most common in the first 30 days."
A rough onboarding document that exists beats a perfect one that does not. Every time.
Try it (15 min)
Watch out for
- Writing a welcome paragraph that explains the company's mission instead of what the new person needs to do in the next 5 days. New people need operational information first, company culture second.
- Listing tools without explaining what each tool is used for. 'We use Asana, Slack, Google Drive, Figma, and Harvest' does not tell a new person which one to open when a client asks for a status update.
- Omitting the common friction points input. This is the section that most directly improves on your current onboarding and Claude will default to generic warnings without it.
- Treating the Claude output as the final document. Review it with one person who went through your onboarding recently and ask what is missing before using it with the next person.
- Including real names, salaries, or personal contact details in the draft without checking your plan's data settings first. Use placeholders for sensitive fields, or confirm your workspace privacy settings before pasting real personnel information.
Paste this into Claude
Write a complete onboarding document for a [choose one: new hire / new client / new vendor] at our organization. Here is the context you need: ORGANIZATION TYPE: [describe your business, e.g., "a 12-person boutique branding agency working with consumer brands"] WHAT THEY NEED TO KNOW IN THE FIRST WEEK: [List 5-8 things the new person must understand in week one. Be specific: tools, processes, communication norms, key contacts, expectations.] WHO THEY CONTACT FOR WHAT: [List the people or roles they will interact with and what each person handles. Include how to reach each one.] TOOLS AND ACCESS THEY RECEIVE: [List every tool, system, or access credential they need by name, with a brief note on what each is used for.] COMMON FRICTION POINTS: [Describe 2-3 things that most commonly cause confusion or frustration in the first 30 days for this type of new person.] Please format the document as: 1. A welcome paragraph explaining the purpose of this document 2. Week 1 essentials (numbered) 3. Key contacts and when to use them (table format) 4. Tools and access (with brief description of each) 5. Common questions and answers (based on the friction points I listed)
What good looks like
- The document has all five sections: welcome, week 1 essentials, contacts, tools, and FAQ
- The contacts section is formatted as a table with role, responsibility, and contact method
- The FAQ section addresses the specific friction points you described, not generic ones
- You could hand this to a new person tomorrow and it would give them a better first week than what you currently provide
When this breaks
- Breaks when the week 1 essentials are described at a strategic level ('understand our brand values') rather than an operational level ('read the client intake form template before your first client call'), because strategic onboarding documents do not give new people enough to act on.
- Produces an overly long document when you include too many friction points (more than 5), because Claude writes a detailed answer to each one and the result becomes too long to read. Limit friction points to the 3 that cause the most re-work.
AI can help with this
Use Claude, ChatGPT, Gemini, Microsoft Copilot, Codex, Notion AI, or another approved work AI based on the system your team actually uses. Paste the lesson prompt with one real process or workflow, require the assistant to separate facts from assumptions, then verify the owner, exception path, and human review point before you use the output.
You can now
You can complete the lesson outcome against a real operations process, source, or recurring workflow.
- You can verify that the document has all five sections: welcome, week 1 essentials, contacts, tools, and FAQ.
- You can verify that the contacts section is formatted as a table with role, responsibility, and contact method.
- You can verify that the FAQ section addresses the specific friction points you described, not generic ones.
- You could hand this to a new person tomorrow and it would give them a better first week than what you currently provide.
Key takeaways
A well-structured onboarding document starts with operational information (tools, contacts, week 1 actions), not company culture. Claude produces a complete draft from a description in under 30 minutes.
- A weak first few weeks is a leading reason new hires quit early. A complete onboarding document is one of the highest-impact retention moves available.
- Operational information first. New people need to know what to do before they need to know why the company exists.
- Tools and contacts in a table format are more usable than prose lists. Format matters for onboarding documents.
- The common friction points section is the most important input. It is the part that distinguishes your document from a generic template.
- Review the Claude output with one recent new person before using it. Their feedback improves it more than another round of editing.