How to onboard a new hire without pre-written SOPs

Executive overview

Most hiring advice tells you to document everything before your new hire starts. For busy owners, this delays hiring, invites procrastination, and produces SOPs written from the wrong perspective.

A five-step alternative lets you onboard systematically without writing a single SOP in advance. Define the role, assign recurring tasks, then have the new hire write the SOPs themselves through structured shadow sessions.

The new hire is always the right person to write the SOPs — not you.

Three reasons to skip pre-hire SOPs

• You don't have time: the reason you're hiring is because you're already overloaded
• Pre-hire SOP writing is productive procrastination — it delays the hire without moving it forward
• SOPs written before the hire are based on assumptions; the new hire brings the right perspective and terminology

Step 1: Define responsibilities

• List specific, recurring activities — not job-description abstractions like "manage brand voice"
• Focus only on repeating obligations that form the backbone of the role
• Exclude one-off projects and ad hoc tasks
• If you can't list at least four recurring obligations, reconsider whether you have a real role to hire for

Step 2: Assign a frequency to each responsibility

• For every responsibility, define how often it recurs (daily, weekly, monthly, quarterly)
• It's fine if one or two tasks have variable cadence — estimate the normal frequency

Step 3: Turn responsibilities into assignable tasks

• Enter each responsibility as a recurring task in your task management tool (or a spreadsheet)
• Set each task to recur at the frequency you defined
• Assign all tasks to the new hire before day one so their workload is ready on arrival

Step 4: Attach a blank SOP template to each task

• Paste a blank SOP skeleton (purpose, procedure, FAQs) into every task — do not fill it in
• This gives the new hire a fill-in-the-blank structure to complete after their shadow sessions
• Once templates are attached, stop — no more SOP work until the hire starts

Step 5: Schedule shadow sessions on day one

• Book short video or in-person sessions with the new hire to walk through each process
• Record the sessions as a backup reference
• The new hire's job after each session: write the SOP from the recording and their notes
• If you're not the process expert, have whoever currently does the task run the session instead

Why this approach works better

• New hire contributes a tangible output from day one, even if they leave quickly
• SOPs are written in the new hire's language and at their level of detail — more useful for future hires
• A current team member can review the draft, adding a second perspective and ensuring accuracy
• The new hire has ownership and buy-in in the SOP they authored, making them more likely to keep it updated