Standard Operating Procedures for a Small Online Business

Document work that has become stable

Start with a process that repeats and already has a reasonably reliable path. Documenting a broken process makes the failure easier to repeat. Observe the work, remove obvious waste, then record the current method.

Prioritize processes where a missed step affects a customer, cash, access, compliance, or a deadline.

Reusable SOP template

Copy these fields into the business knowledge base or print them for a working session.

• Purpose and expected outcome.
• Owner and backup owner.
• Trigger, frequency, and deadline.
• Required access, source records, and inputs.
• Numbered procedure with verification after critical steps.
• Exceptions, escalation path, and stop conditions.
• Evidence retained and retention location.
• Last tested date, reviewer, and next review date.

Test with someone other than the author

Ask a second person to complete the work using the document. Record every question and every hidden assumption. Update the SOP, then test again after a meaningful system or policy change.

Access instructions should name the approved password or secrets system, never include credentials in the SOP itself.