SOP writing and process documentation for businesses in Canada.
I turn the way your team does recurring work into instructions another person can follow. I interview the people who do the task, review the tools and source material, write the procedure and check it with the process owner. Where a step is not confirmed, it goes on a list of open questions instead of into the procedure as a guess.
What does SOP writing include?
Written procedures with a purpose, trigger, steps, checks, where the output goes and who to ask; checklists for work that crosses several teams; a reference page for an automation or system; screen-recorded video walkthroughs; and onboarding packs for a new hire. I work remotely from Moncton, New Brunswick, for businesses across Canada and the US.
When the process lives in someone's head.
Businesses usually ask for SOPs when recurring work still depends on memory, training changes with each person, or a key person is about to leave. You may be noticing that:
- A new hire learns by interrupting whoever is busiest.
- The answers to how a task is done are spread across months of Slack or email threads.
- An automation works, but only one person knows how it is set up.
- Work that touches several teams, like closing an account, sometimes gets missed by one of them.
- Customers or staff keep asking the same how-to questions.
What I can write for you.
Standard operating procedures
One procedure per task, each with the same shape: purpose, trigger, steps, the checks that make it done, where the output goes and who to ask. I can deliver them as documents or as one workbook with a sheet per procedure.
Onboarding packs for a new hire
The SOPs a new person works from, a task inventory sorted by how ready each task is to hand over, and a register of questions that still need an answer from the owner.
Checklists for cross-team work
A checklist for work that several teams touch, such as closing a cancelled account across engineering, billing and records, so each step is done and written down.
System and automation references
One page that explains how an automation works: the tools involved, the end-to-end flow, each trigger and action, the email sequence, the daily checks and any known limitation, called out where the team will see it.
Video SOPs and help lessons
Screen walkthroughs recorded in Loom or Camtasia and edited with captions and even sound. I use them for team SOPs and for help lessons that answer your customers' repeat questions.
Updates after a change
When a tool, policy or role changes, I update the procedure and its screenshots, and record what changed. I can keep this going as part of ongoing operations support.
Where the documents live.
I write in the tools your team already uses, so the procedures are where people look for them.
Documents
- Google Docs and Sheets
- Excel workbooks
- Microsoft 365
- A page on your website
Source material
- Slack and email history
- Recordings and transcripts
- Existing notes and templates
- Interviews with the team
Video
- Loom
- Camtasia
- Descript
- CapCut
What a project can include
Depending on the scope we agree.
- Interviews with the process owner and the people who do or review the task
- A review of your forms, templates, screenshots, recordings and existing notes
- Required steps separated from judgement calls, exceptions and local preferences
- Procedures with purpose, trigger, steps, checks, output and who to ask
- An open-questions register, so unconfirmed steps go to the owner as questions
- A task inventory sorted by readiness when the work is a full role
- Screen-recorded walkthroughs with captions where a video is clearer
- An owner and review date on each document, so it stays current
Examples from the work.
Telecom company: 15 SOPs from six weeks of Slack
An accounting role with no manual. I wrote the procedures, tiered the task list by how ready each part was to hand over, and kept a register of what still had no answer.
Coaching business: a booking system reference
A six-section page covering the tools, the flow, three Zaps, the email sequence, daily checks and the one known limitation, so a new team member can take it over.
Software company: 10 help lessons
I grouped the questions members kept emailing about and recorded 10 screen walkthroughs. The first was reviewed and published within a day.
What I need from you.
You do not need polished notes. You do need someone who knows the process and can check the draft. Gather the most recent examples of the work, the tools involved, the templates you use, known exceptions and any rules that cannot change. Pick one normal example and one difficult one to walk through.
If you can, record the task from start to finish while the person doing it explains each decision. Leave out client, employee, payment, health or legal information I do not need. If you want to start on your own, the free one-page SOP template on the resources page is a fillable PDF.
Choose a starting point.
A defined set of procedures
For one important workflow, an onboarding pack for a role, or a reference page for a system your team relies on.
Documentation inside ongoing support
For procedures written and kept up to date as part of your operations support, alongside the coordination work they describe.
How the work runs.
- 01
Name the processes
Tell me which tasks need writing down and who does them now. We agree the scope by named processes and deliverables, not by page count.
- 02
Collect and interview
I read the source material, interview the people involved and walk through a normal and a difficult example of each task.
- 03
Write and check
I write the draft, then the process owner checks it. Anything I could not confirm goes on the open-questions list instead of into the procedure.
- 04
Test and hand over
Someone who did not write it tests the draft. I correct anything unclear, add an owner and review date, and hand over the final files.
Documentation case studies.
Creating an Onboarding Pack from Working Instructions
15 SOPs, a task inventory in three readiness tiers and an open-questions register for an accounting role that had never been written down.
Read case studyBuilding and Documenting a Booking Workflow
I connected Stan Store, Zapier, Flodesk and Google Forms, then wrote a reference covering the flow, reminders, segments and limits.
Read case studyClosing a Customer Account Cleanly
I ran a cancellation checklist across engineering, accounting, number inventory and E911, and documented every step.
Read case studyProcess documentation guides
Standard operating procedure writing services
What a procedure writer does, what to prepare and how procedures stay accurate after delivery.
Read the guideProcess mapping consultant vs SOP writer
Which kind of process help fits, depending on whether the process already works.
Read the guideVirtual assistant onboarding checklist
What to prepare before a handover, and how to review the first completed cycle together.
Read the guideCommon questions
SOP Writing FAQ
Other ways I support businesses
Operations Support
SOPs, project coordination, vendor and client follow-ups, and recurring process ownership.
Explore Operations SupportAdministrative Support
Inbox, calendar, documents, trackers and client follow-up handled reliably.
Explore Administrative SupportCRM & Workflow Support
Workflow and automation repairs, with documentation your team can maintain.
Explore CRM & Workflow SupportTell me which process needs writing down.
Share the task, who does it now and where the instructions live today, even if that is a Slack thread. I review inquiries personally and normally reply within one business day. If the work is a good fit, we can arrange a free consultation.
Book a free callEverything starts with the form. I read each inquiry myself and send scheduling details once it looks like a genuine fit.
Tell me what you need help with, and I will suggest where to start.
Book a free call