About
Business

How to Write an SOP for a Business Handover

A practical guide to writing standard operating procedures that make an online business handover smooth, repeatable, and buyer-ready.

How to Write an SOP for a Business Handover

When an online business changes hands, most of its real value lives in the owner's head. The order in which tasks get done, the supplier who always answers quickly, the quirk in the checkout flow that nobody has documented, the way a refund is approved. A standard operating procedure, or SOP, moves that knowledge out of memory and onto paper so a new owner can keep the business running without the seller sitting beside them. Writing SOPs well is one of the most undervalued things a seller can do, and one of the first things a careful buyer looks for during due diligence.

This guide explains how to build a handover SOP library that is clear enough for someone who has never touched the business to follow, and complete enough that the day-to-day operation does not stall the moment the seller logs off for the last time.

Why SOPs Decide Whether a Handover Succeeds

A handover is not a single event. It is the slow transfer of hundreds of small decisions and habits from one person to another. Without documentation, that transfer depends entirely on live conversations, which are easy to forget, hard to schedule across time zones, and impossible to repeat once the seller has moved on. SOPs turn fragile verbal knowledge into a durable asset that survives the transaction.

From a valuation standpoint, a business with thorough procedures is worth more than an identical business that relies on an irreplaceable founder. Buyers discount owner dependence heavily, because it is a risk they inherit. A well-organised SOP library signals that the operation is a system rather than a personality, and that reassurance often shows up directly in the price and the speed of the deal. It also shortens the training period, which benefits both sides.

What to Document First

Trying to write down everything at once leads to exhaustion and half-finished notes. Instead, start with the tasks that are both frequent and high-stakes, because those are the ones a new owner cannot afford to get wrong. Think about order fulfilment, customer support responses, payment and refund handling, content publishing, and anything tied to money moving in or out.

A simple way to prioritise is to list every recurring task and sort it along two lines: how often it happens and how much damage a mistake would cause. Anything that is both common and consequential goes to the top of the writing queue. Rare but catastrophic tasks, such as recovering a locked hosting account, deserve a place too, even though they happen seldom. Low-frequency, low-impact chores can wait until the core library is in place.

  • Daily operations: order processing, inbox triage, social posting, stock checks.
  • Weekly and monthly tasks: reporting, supplier reorders, invoice reconciliation, newsletter sends.
  • Access and credentials: where logins live, how two-factor codes are recovered, who the registrar and host are.
  • Exceptions: chargebacks, outages, angry customers, supplier failures.

How to Structure a Procedure That People Actually Follow

A useful SOP reads like a recipe, not an essay. Each one should open with its purpose in a single sentence, state who is responsible, and then list the steps in the exact order they are performed. Steps should be short, start with a verb, and assume no prior knowledge. Where a step involves a screen, a screenshot or a short screen recording removes almost all ambiguity.

Write for the least experienced person who might ever do the job. Spell out the obvious, because what is obvious to a seller who has done something a thousand times is invisible to a newcomer. Include the small things that cause big problems: the exact tone to use with customers, the threshold above which a refund needs a second look, the supplier's cut-off time for same-day dispatch. End each procedure with a note on what a finished, correct result looks like, so the reader can check their own work.

Keep every SOP in one shared, searchable place, and give each a clear title and a last-reviewed date. A loose collection of documents scattered across folders and chat apps is almost as unhelpful as having none at all.

Handling Data and Customer Lists in the Handover

Some of the most sensitive material in a handover is the information held about people. It is worth being precise here. Customer records, subscriber rolls, membership databases, and follower lists are personal data, and data-protection law treats them accordingly. They cannot be sold off on their own as a standalone list to whoever will pay for it. They may transfer only as part of the sale of the whole business, and even then the buyer steps into the seller's shoes: the original consent the customers gave, and the privacy notice they were shown, continue to bind the new owner. Your SOPs should document where this data lives, how it is secured, and what the customers were originally told, so the buyer can honour those terms rather than guess at them.

Keeping SOPs Alive After the Sale

An SOP written once and never touched again rots quickly, because tools change, suppliers change, and the business evolves. Build in a light review habit: a quick check of each core procedure on a set cadence, and an immediate update whenever a process changes in practice. During the handover itself, the best test is to have the buyer, or their staff, perform a task from the SOP alone while the seller watches silently. Wherever they get stuck is a gap in the document, not a failure of the reader, and it should be fixed on the spot.

Treat the SOP library as a living part of the business rather than a closing-day formality. A seller who hands over clear, tested, current procedures gives the buyer the single most valuable thing in any acquisition: the confidence that the business will keep working tomorrow exactly as it did today.

Frequently Asked Questions

How many SOPs does a small online business actually need?

There is no fixed number, but most small online businesses are well covered by somewhere between ten and thirty core procedures. Focus on the tasks that happen often or carry real risk rather than trying to document every possible action. A tight, well-maintained set beats a sprawling library that nobody keeps current.

Should SOPs be written by the seller or the buyer?

The seller should draft them, because they hold the knowledge, but the buyer is the ideal tester. Having the buyer follow each procedure without help quickly reveals missing steps and hidden assumptions. The two sides then refine the documents together during the transition.

What format works best for a handover SOP?

A short, step-by-step format with numbered actions, screenshots, and a clear definition of a correct result works best. Keep everything in one searchable location with titles and review dates. Video walkthroughs help for anything visual or hard to describe in words.

Can I include passwords and logins directly in an SOP?

You should document where credentials live and how access is recovered, but store the actual passwords in a dedicated password manager rather than in the procedure text. Transfer the manager or its credentials securely at closing. This keeps sensitive access controlled and makes it easy to rotate passwords after the sale.

Advertisement
I

Ishita

Writer, E-commerce & Social

Ishita covers e-commerce, social platforms and the tools online sellers use to grow their stores and audiences.

More in Business

View all

Keep up with the web & AI

New guides and analysis on SEO, e-commerce, domains and AI — every week.

Subscribe via RSS Browse all topics