Creating SOPs for Repetitive Author Tasks
There's a concept in business operations called the 'dependency bottleneck' — the point in any process where everything has to flow through one person before it can continue. For most indie authors working without systems, that bottleneck is themselves. Every recurring task in their publishing business runs through their own memory, their own judgment, their own availability. When they're writing, nothing else moves. When they onboard a VA, the bottleneck shifts temporarily to 'explaining to the VA how things are done' — and if they never solve that problem with documentation, they've replaced one bottleneck with another.
A Standard Operating Procedure, or SOP, is the solution. An SOP is a written (or recorded) description of how a specific recurring task gets done in your publishing business — detailed enough that someone who has never done that task before could execute it correctly by following the document. It's not a policy or a strategy guide. It's a how-to: step one, step two, step three, when to check in, what done looks like, and what to do if something goes wrong.
SOPs are the infrastructure that makes genuine VA independence possible. Without them, your VA is always either executing from memory (inconsistently) or asking you for direction (which defeats the purpose). With them, your VA can execute recurring tasks correctly, consistently, without involving you — which is the whole point.
Why Authors Resist Building SOPs
I'll be direct about this: most authors find SOP writing boring, and they deprioritize it accordingly. It feels like administrative overhead that takes time away from real work. The irony is that the time spent building SOPs returns itself many times over — every re-explanation a VA needs because a process isn't documented costs more time than the SOP would have taken to write.
The other resistance is perfectionism: authors who want to write the perfect, comprehensive SOP for every task often write none, because starting feels overwhelming. The practical answer is to start imperfect and improve. A rough SOP that captures 80% of what a VA needs to know is infinitely more useful than a perfect SOP that doesn't exist yet. Build it, use it, correct the gaps when they surface.
What to Document First
Not every task needs an SOP immediately, and trying to document everything before you start delegating is a recipe for never starting. Prioritize SOPs for tasks in this order:
High-frequency recurring tasks: anything your VA will do weekly or more often should be documented first — social media scheduling, newsletter formatting, ARC email management. These are the tasks where inconsistency accumulates fastest and where a clear process document pays back most quickly
High-stakes tasks where errors are costly: anything involving your email list, your retail account metadata, or reader-facing communications falls here — the tasks where a mistake damages something important
Complex multi-step tasks with branching logic: ARC coordination, launch week management, and promotional submission processes involve enough steps and enough decision points that documentation is essential rather than optional
Tasks you personally hate explaining: if there's a task you've already re-explained to multiple people and found yourself frustrated by the repetition, that's the SOP that will relieve the most psychic burden immediately
How to Write a Good SOP
The format of an SOP matters less than its clarity and completeness. A Loom video walkthrough can be an excellent SOP for tool-based tasks. A numbered checklist can be a perfect SOP for a straightforward sequential process. A narrative document with screenshots works well for complex multi-platform tasks. Use whatever form makes the information clearest to the person executing the task.
Whatever format you choose, a complete SOP answers six questions:
A Sample Author SOP: Newsletter Formatting
Here's what a practical author SOP looks like for a common task — newsletter formatting and scheduling. This is abbreviated for illustration; a real SOP would be more detailed.
TASK: Newsletter Formatting and SchedulingFREQUENCY: Every other MondayTOOLS NEEDED: MailerLite (editor access), Google Drive (newsletter folder), Canva (brand kit)STEPS:1. Open the newsletter Google Doc in the shared 'Newsletters' folder. The current issue will be titled with the send date.2. In MailerLite, click Campaigns > Create Campaign > Regular Campaign.3. Name the campaign [MONTH YEAR — Newsletter Issue #]. Example: 'June 2026 — Newsletter Issue 12.'4. Select the 'Newsletter — Standard' template.5. Copy the subject line from line 1 of the Google Doc into the Subject field.6. Copy the preview text from line 2 of the Google Doc into the Preview Text field.7. In the email editor, replace the header image with the current month's header from Canva (file named 'Newsletter Header — [Month Year]').8. Copy the newsletter body text from the Google Doc into the email body, section by section.9. Test all links by clicking each one before scheduling.10. Schedule for the date in the doc title at 9:00 AM Eastern.DONE LOOKS LIKE: Campaign status shows 'Scheduled' with the correct date and time. Draft doc moved to 'Sent' subfolder.IF SOMETHING GOES WRONG: Screenshot the error and message in Slack. Do not reschedule until [author] has confirmed.
Building Your SOP Library Over Time
SOPs are living documents, not archives. They need to be updated when tools change, when you make a process decision that differs from what's documented, or when a VA's experience with the task reveals a better approach. Build the update into the process itself: whenever a VA flags that a step in an SOP doesn't match what actually happens, update the document before the next execution cycle.
Over time, your SOP library becomes one of the most valuable assets in your publishing business — a complete institutional memory of how your operation works, independent of any individual VA. When a VA leaves and you hire a new one, the SOPs mean the knowledge stays with your business rather than walking out the door. When you scale to a second VA, the SOPs mean you're not starting from scratch on documentation. When you eventually look back at how you were doing things five years ago, the SOPs are a record of how your operation evolved.
The authors who build SOPs consistently and early tend to say the same thing: it feels like extra work until the first time a new VA executes a recurring task correctly on the first try without asking a single question. At that point, the value of the system becomes undeniable.
Author Tasks That Are Particularly Well-Suited to SOPs
Newsletter formatting and scheduling — exact steps vary by platform but always sequential and repeatable
ARC team management — recruitment, delivery, reminder schedule, thank-you and review follow-up
Social media content scheduling — platform-specific formatting rules, hashtag sets, posting times
BookFunnel group promo applications — how to find eligible promos, application criteria checklist, how to add titles
Author website content updates — blog post publishing process, cover reveal page creation, back matter link updates
Promotional newsletter submission — which services to submit to and when, submission requirements, pricing tiers
Metadata review cycle — which tools to check, what to look for, how to propose changes for author approval
Review monitoring — where to look, what to track, what requires the author's attention versus what the VA handles
Conclusion
SOPs are the mechanism that transforms a VA relationship from 'someone I manage' to 'a system that runs.' The investment in documentation is front-loaded and concrete; the return is continuous and compounding. Every task you've documented is a task you no longer need to re-explain, re-supervise, or worry about when you're heads-down on a manuscript. The next article — Managing Your VA Effectively — covers the ongoing relationship mechanics that keep the systems you've built running smoothly over time.
Hello, I'm Randall Wood. When I'm not pounding the keyboard or entertaining my giant dog I like to build tools for my fellow indie authors. In these articles, you'll find lessons learned over sixteen years spent in the indie author world. I share it all here to help you get one step closer to where you want to be.— Randall