Back to journal

25 October 2026 · 9 min read · Hiring

15 Processes to Document Before You Hire Your First Team Member

What processes to document before hiring? Here are 15, grouped by area, with what to capture and a fast way to draft them. Get your first hire set up.

A founder writing process notes before hiring her first team member

Your first hire starts on Monday. On Monday morning they ask, "How do you onboard a new client?" and you realise the answer is "Er, I just sort of... do it."

The short answer: before you hire, document the processes your new team member will touch in their first month: client onboarding, core delivery, communication rules, invoicing, scheduling, marketing basics and tool access. You don't need a perfect manual. You need a minimum viable version of each, recorded in your own words, that someone else can follow without asking you every five minutes.

This post is the what. If you want the how, read How to Write an SOP Your First Hire Can Actually Follow alongside it.

Which processes should you document first?

Document the processes your first hire will do most often, and the ones where a mistake costs you money, a client or your reputation. Everything else can wait.

Founders often ask me on discovery calls whether they need to document everything first. No. You need enough for your hire to be useful in week one and confident by week four.

Client onboarding processes

Client onboarding is the first thing a new team member is likely to help with, and the first thing a client notices if it goes wrong.

1. Proposal to signed contract

What to capture: how a lead becomes a client. Which proposal template you use, what goes in it, how it's sent (I use PandaDoc), how you follow up and what happens once it's signed.

Minimum viable version: a five-step checklist plus links to your proposal and contract templates.

2. New client welcome and setup

What to capture: the welcome email, the intake form, the folders and project boards you create, and any access you need from the client.

Minimum viable version: a copy-and-paste welcome email and a setup checklist with every folder and board named.

3. Kick-off call

What to capture: how the call is booked, the agenda, who attends, where notes go and what gets sent afterwards.

Minimum viable version: a one-page agenda template and a follow-up email template.

Delivery processes

Delivery processes describe how the actual work gets done, so your hire can take tasks off your plate without changing the quality.

4. Your core service workflow

What to capture: the steps from "client said yes" to "work delivered" for your main offer. Who does each step, which tool it lives in and how long it usually takes.

Minimum viable version: a template project in ClickUp or Trello that you duplicate for every client, with the steps as tasks.

5. Quality check before anything goes out

What to capture: what "done" looks like. Spelling, brand colours, links tested, the client's name spelled right.

Minimum viable version: a 5 to 10 point checklist attached to the final task in your workflow.

6. Client wrap-up and offboarding

What to capture: final handover, the last invoice, feedback request, archiving files and removing access.

Minimum viable version: an offboarding checklist and a wrap-up email template.

Communication processes

Communication processes set the rules for how your team talks to clients and to you, which prevents the "should I have told you about that?" moments.

7. Inbox triage

What to capture: which emails your hire handles, which they flag for you, which they ignore. Labels or folders you use.

Minimum viable version: a simple three-column list: "handle it", "flag it", "leave it".

8. Client communication standards

What to capture: response times, tone of voice, sign-offs, which channels clients use and what never goes in writing without your approval.

Minimum viable version: a half-page "how we talk to clients" note with two or three example replies.

9. Internal check-ins and escalation

What to capture: when you meet, where updates go, and what counts as urgent enough to interrupt you.

Minimum viable version: one recurring check-in in the calendar and a short list of "message me immediately if..." scenarios. Your First 30 Days With a New VA, Week by Week has a check-in rhythm you can borrow.

Admin and finance processes

Admin and finance processes keep cash coming in and calendars working, which is why they're often among the first tasks founders hand over.

10. Invoicing and payment follow-up

What to capture: when invoices go out, what's on them, which tool you use, how and when late payments are chased, and what your hire can and can't approve.

Minimum viable version: an invoicing calendar plus three reminder email templates (friendly, firm, final).

11. Calendar and scheduling

What to capture: your working hours, meeting types, buffer time, which meetings your hire can book or move and which are off limits.

Minimum viable version: a list of your scheduling rules and your booking links.

Marketing processes

Marketing processes help your hire keep you visible without you having to approve every single comma.

12. Responding to new enquiries

What to capture: where enquiries arrive, how fast they get a reply, what the reply says and how they're tracked.

Minimum viable version: a reply template and a simple tracking list (a Trello board works).

13. Content creation and scheduling

What to capture: your content pillars, where ideas are stored, how posts are designed (Canva templates, for example), how they're scheduled (I use Metricool) and who approves them.

Minimum viable version: a weekly content checklist and a folder of ready-to-use templates.

Tools and access processes

Tools and access processes cover how your hire gets into your systems safely and how they get out again when they leave.

14. Tool access and passwords

What to capture: every tool your hire needs, what access level they get, how logins are shared and how access is removed if they leave.

Minimum viable version: a tool list with access levels. Give each person their own login where the tool allows it, share passwords through a password manager rather than email, and turn on two-step verification. The UK's National Cyber Security Centre calls 2-step verification "one of the most effective ways to protect online accounts when passwords are still in use" and recommends removing accounts that are no longer needed.

15. File storage and naming

What to capture: your folder structure, file naming rules and where the "final" version of anything lives.

Minimum viable version: a screenshot of your folder structure and three naming examples.

Which processes matter most? (priority table)

Prioritise processes your hire will use in their first two weeks and processes where mistakes are expensive. Use this table to decide what to document this week and what can wait.

#ProcessWhy it mattersEffort
1Proposal to signed contractDirectly affects revenueMedium
2New client welcome and setupFirst impression for every clientLow
3Kick-off callSets expectations for the whole projectLow
4Core service workflowThe work itself. Your hire can't help without itHigh
5Quality checkProtects your reputationLow
6Client wrap-upFinal invoice, feedback and referralsLow
7Inbox triageBiggest time saver for most foundersLow
8Client communication standardsKeeps your voice consistentMedium
9Check-ins and escalationStops small issues becoming big onesLow
10Invoicing and follow-upCash flowMedium
11Calendar and schedulingProtects your timeLow
12Responding to enquiriesSlow replies can lose leadsLow
13Content creation and schedulingKeeps you visibleMedium
14Tool access and passwordsSecurity and clean offboardingLow
15File storage and namingStops "which version is final?"Low

If you only have one week, start with 2, 4, 7, 10 and 14.

How can you document processes quickly?

The fastest way to document a process is to record yourself doing it, talking out loud as you go, then use Claude to turn the transcript into a draft SOP. You do the task once, and you get a first draft without staring at a blank page.

  1. Record. Next time you do the task, record your screen or a voice memo and narrate every step, including the "oh, and I always check this" bits.
  2. Get the transcript. Many recording and meeting tools produce a transcript. Save it as a text, Word or PDF file. Claude, the AI assistant made by Anthropic, accepts file types including PDF, DOCX and TXT.
  3. Ask Claude for a draft. Upload the transcript and ask: "Turn this into a step-by-step SOP for a new team member. Include the purpose, tools needed, numbered steps, a quality checklist and any decisions they might need to make. Flag anything that's unclear."
  4. Fix the gaps. Read the draft and fill in what Claude flagged.
  5. Test it. Ask your new hire to follow it while you watch quietly, then update anything that tripped them up.

Tip: set up a Claude Project for your SOPs. Projects are self-contained workspaces with their own chat histories and knowledge bases, so you can add your templates and tone of voice once and reuse them for every SOP. Before uploading anything containing client data, check your plan's data settings and Anthropic's privacy policy.

For the detail on structuring each SOP, go back to How to Write an SOP Your First Hire Can Actually Follow.

What comes after documenting your processes?

Once your core processes are written down, you're ready to write the role and plan the handover. Your process list effectively becomes the task list for the job, so it feeds straight into How to Write a Job Brief for Your First Virtual Assistant.

Not sure which tasks to hand over first? How to Delegate as a Founder starts with five. And if you want a wider view of what your business needs before it grows, use the small business operations checklist.

Key takeaways

  • Document the processes your first hire will use in their first month, not everything.
  • Group them by area: onboarding, delivery, communication, admin and finance, marketing, tools and access.
  • A minimum viable version (a checklist, a template, a screenshot) is enough to start.
  • Prioritise high-frequency and high-risk processes first.
  • Record yourself doing the task, then use Claude to turn the transcript into a draft SOP.
  • Give your hire their own logins, use a password manager and turn on two-step verification.

Frequently asked questions

Do I need SOPs before hiring a VA?

You need some, not all. Document the handful of processes your VA will do in their first two weeks so they can start without constant questions. The rest can be written together during their first month, which also helps them learn the business.

How long does it take to document a process?

Using the record-and-transcribe method, a simple process can often be drafted in under an hour, including recording, drafting with AI and a quick review. Complex processes take longer, mostly because you'll discover decisions you've never written down before. Budget a few hours a week for a month rather than trying to do it all at once.

How much detail should process documentation include?

Enough for someone who has never done the task to complete it correctly. If your hire has to ask you more than one or two questions, add detail there. Screenshots and examples usually help more than extra paragraphs.

Can my new hire document processes instead of me?

Yes, and it can work well. Do the task once on a recorded call while they take notes, then ask them to write the draft. You review it. This shares the work and shows you quickly what they've understood.

Where should I store process documentation?

Somewhere your team already works and can search. A shared folder, your project management tool or a dedicated wiki all work. What matters is having one place, a clear naming system and a link to each SOP from the task it relates to.

What if my processes change after I've documented them?

They will, and that's fine. Add a "last updated" date to each SOP and make updating it part of the process itself. A quick review every few months keeps everything current.

Want help getting your business ready to hire?

If you'd like someone to map your processes with you, the AI Operations Audit is a 90-minute session that leaves you with a recording and a written Priority Action Plan, including which processes to document first.

If you'd rather have it done with you, the 90-Day AI Operations Sprint builds your SOPs and systems ready for your first hire, and the AI-Powered Operations Retainer gives you ongoing operations support once your team is in place.

Or book a free call and tell me where you're stuck.

Want a second pair of eyes on your operations?

Book the Audit

Not sure where to start? Book a free call.

Free download

The 10-Minute Operations Audit

A quick, honest checklist that shows where your business is actually leaking time, money, and focus. Score yourself in ten minutes.

No spam. Unsubscribe anytime. We email you the PDF and occasional operations notes for founders.

AboutServicesProcessBlogContact