What this is
This is a workflow breaking new hire material prep into three stages — before day one, day one, week one — with Claude handling a different kind of task at each: organizing a chronological checklist beforehand, converting policy documents into plain language on day one, and compiling a team contact reference table during week one.
The three stages solve different problems, together covering a new hire's full journey from before they start to actually integrating with the team, rather than just handing over one document and calling it done.
Why this exists
This workflow exists because the problem with new hire onboarding materials usually isn't that the content doesn't exist — it's that it's scattered across too many places, in inconsistent formats: some in a formal handbook, some existing only in one person's verbal knowledge, some with no written record at all. Every time someone new joins, whoever's responsible for onboarding them has to piece these fragments back together, which is time-consuming and easy to miss things in.
The point of splitting it into three stages is having each stage handle only the information genuinely needed at that point, rather than cramming everything into one massive document for the new hire to digest all at once. Delivering in stages means a new hire only needs to absorb what's actually useful at that moment, making the load lighter and easier to genuinely retain.
How this affects your decisions
If your team regularly onboards new hires, this workflow changes when you prepare onboarding materials. You might previously have scrambled to organize materials right before a new hire's start date — now you can prepare each of the three stages' content ahead of time separately: the pre-onboarding checklist can be organized as soon as the start date is confirmed, while the day-one documentation and week-one contact table can be built as templates, quickly filled in once the new hire's specific details are set.
In practice, this means you don't need to rethink 'what materials do I need to prepare this time' from scratch every time — instead there's a fixed three-stage framework to follow, only needing this particular new hire's specific information filled in, significantly reducing the decision cost of preparing each time.
Advanced applications
Advanced users can extend this workflow into a continuously updated template, rather than regenerating brand-new content for every new hire. In practice, this means storing the three-stage template in a Claude Projects knowledge base — whenever an actual policy change happens (leave procedures changed, a new system tool was added), update the corresponding section of the template. Future onboarding just asks Claude to fill in this new hire's specific information based on the latest template, and the template itself stays current as company policy evolves, avoiding a situation where an outdated process gets handed to a new hire.
Another advanced technique is asking Claude, after compiling the three-stage materials, to also generate a 'commonly anticipated questions' list — based on questions new hires have frequently asked in the past, proactively adding answers into the materials rather than waiting for a new hire to ask first. This requires first having the team recall the questions asked most often across past onboardings, compiling those questions and answers into the materials together, so the answer is already at hand before a new hire even needs to ask — further reducing the back-and-forth communication on both sides.
Preparing onboarding materials for a new hire is rarely difficult because the content itself is hard to write — it's that the information is scattered across too many places: account setup means asking IT, office policies live in the employee handbook, team contact points exist only in one person's memory. Every time someone new joins, it all gets pieced back together from scratch. This workflow's goal is breaking down onboarding material prep into three clear stages, with Claude handling a different task at each one, rather than doing everything in a single pass.
Before a new hire starts, there's usually a pile of small but necessary information to prepare — account permission request procedures, where to pick up office equipment, who to report to on the first day. This information is normally scattered across different people's memory and different old documents. You can paste these fragments to Claude all at once and have it organize them into a clearly structured 'pre-onboarding checklist,' arranged in chronological order rather than a jumbled to-do list. This checklist also doubles as something the person responsible for onboarding the new hire can check, confirming every item has an owner.
Handbook policies are usually written formally, full of internal company jargon a new hire isn't familiar with yet — handing it over directly is a struggle to parse. You can ask Claude to rewrite the parts of the handbook most relevant to a new hire's first day — leave request procedures, office policies, emergency contacts — into plain language, with extra notes added for spots new hires are especially prone to misunderstanding. The point of this step isn't cutting content — it's converting a formal document into something a brand-new person who knows nothing yet can actually understand.
What most often trips up a new hire in their first week usually isn't not knowing how to do something — it's not knowing who to ask when something comes up. You can ask Claude to compile a 'who to ask about what' reference table based on team members' responsibilities — who handles system issues, who handles leave requests, who handles project content questions — so a new hire doesn't have to prefix every question in a group chat with 'sorry to bother everyone,' but instead has a clear direction to ask the right person directly.
If your team regularly onboards new hires, it's worth turning this three-stage material prep process into a template, permanently stored in a Claude Projects knowledge base — future onboarding only needs updating the small set of things that actually change (the new hire's name, the project they're joining), while most of the structured content carries over directly, without starting from scratch each time. What gets saved isn't just prep time — it's the mutual time both sides spend on a new hire figuring things out by trial and repeated asking.