Daily Operations SOP for Small Businesses (WooCommerce) (Preview)

The Standard Operating Procedure Manual

A complete, ready-to-use SOP toolkit and training program for small business owners and operators who need to document, run, delegate, and continuously improve daily operations.

Foreword

Most small businesses fail not because the founder lacked vision, talent, or hustle. They fail because the day-to-day work that keeps the lights on — sending invoices, answering inquiries, closing the books, onboarding a customer, reconciling a deposit — was held together by memory, habit, and the personal heroics of one or two people. When those people get sick, take a vacation, or leave, the system collapses. Standard Operating Procedures (SOPs) are the antidote to that fragility.

This manual is written for the owner-operator running a team of two to fifty people, the office manager trying to bring order to a chaotic back office, the founder preparing to delegate so they can finally take a week off without their phone, and the operations lead building the foundation for a business that will run reliably whether or not the boss is in the room. It is also written for the operator who wants to sell the business someday: a business that runs on documented systems is worth two to four times more than one that runs on tribal knowledge.

The SOPs in this manual cover ten functional areas that every small business has, regardless of industry: admin and office, customer service, sales, marketing, finance and bookkeeping, hiring and HR, project and task management, quality and risk, and implementation and maintenance. Together they form a complete operating system. You do not need to implement every SOP on day one — Module 10 contains a thirty-day sprint plan that prioritizes the ten that will produce the biggest return on the time you invest in writing them. Start there, then work outward.

Every SOP in this manual is written to the same template: Purpose, Scope, Owners, Frequency, Tools and Inputs, Procedure, Quality Standards, Common Failures, and Metric. That repeating structure is itself part of the system. When everyone in the business knows that every SOP answers the same nine questions in the same order, training time drops, errors drop, and the documents become genuinely useful instead of becoming binder-shelf decoration.

Read the front matter first — it explains the conventions used throughout the manual, defines the terms you will see repeatedly, and gives a brief executive summary of what each module covers. Then go directly to Module 10 and read the SOP Build Sprint Plan before you start writing or adapting anything else. That sequence will save you weeks.

About This Manual

This manual is intended to be used in two ways. The first use is as a complete, off-the-shelf SOP library that you can adapt to your business in roughly thirty to sixty days. The second use is as a reference and template engine — you copy the structure of any SOP and rewrite it to match your specific tools, customers, and team. Both uses are valid. Most businesses end up doing some of each.

The manual is opinionated where opinions matter and flexible where they don't. We are opinionated about structure (every SOP has the same nine sections), about ownership (every SOP has exactly one accountable owner and one backup), about review cadence (every SOP is reviewed at least once every twelve months and re-tested by a non-author), and about measurement (every SOP has at least one metric that tells you whether it is working). We are flexible about tools: where a procedure references Gmail, Outlook, QuickBooks, Xero, Slack, Microsoft Teams, Asana, ClickUp, or Notion, the principle applies regardless of which tool you actually use. Substitute your own.

The manual assumes a small business with between one and fifty employees, annual revenue between $100,000 and $20 million, and a mix of in-person, remote, and hybrid work. It does not assume any specific industry. The procedures have been written so that a retail shop, a professional services firm, a home-services contractor, an agency, a clinic, an e-commerce store, or a light-manufacturing operation can all apply at least eighty percent of the content with minor adaptation. The remaining twenty percent is industry-specific work that you will do once and then never have to do again.

How to Use This Manual

Begin by reading the foreword and front matter end to end. Skim Modules 1 through 9 to get a sense of what is in each. Then read Module 10, which explains the sprint sequence for implementation. Do not try to write or roll out all fifty SOPs at once. The single most common failure mode for small-business SOP programs is attempting to document everything in the first month, exhausting the team, and abandoning the project. Pick ten, ship them, prove the value, then expand.

For each SOP you decide to implement, complete the following five-step adoption cycle. First, read the SOP as written. Second, customize the tool names, role names, time thresholds, and approval limits to match your business. Third, walk the SOP through with the person who will own it and the person who will back them up. Fourth, have a third person — someone who has never performed the task — attempt to follow the SOP without assistance. Fifth, revise the SOP based on where they got stuck, then publish it in your shared workspace and add it to your SOP inventory.

The first time you complete this cycle it may take a full day for a single SOP. By the tenth SOP you will be doing one in under ninety minutes. The cycle compounds, both because your team gets faster at writing and because each new SOP reuses formats, headers, and approval flows from the SOPs that came before.

Document Conventions

Throughout this manual, the following conventions are used consistently. Roles are written in title case (Owner, Backup Owner, Approver, Reviewer). Tools are written in plain text and are illustrative only. Time thresholds are expressed in business hours unless otherwise noted; "respond within four business hours" means four hours during your published operating hours, not four clock hours including overnight. Currency amounts are expressed in generic dollars and should be adapted to the currency, tax rules, and approval thresholds appropriate to your jurisdiction.

The word "must" indicates a requirement that, if skipped, will cause the SOP to fail or expose the business to material risk. The word "should" indicates a strong recommendation that may be adapted to the team's capacity or context. The word "may" indicates an optional step that some teams find useful and others omit. The word "owner" means the single person accountable for the SOP being followed correctly; the word "approver" means the person who must sign off before the work goes out the door; the word "reviewer" means the person who periodically audits the SOP itself for accuracy and currency.

Every SOP includes a Metric section. A metric is a specific, measurable indicator that tells you whether the procedure is producing the result it was designed to produce. Metrics are not vanity numbers. If a metric does not change anyone's behavior or decisions, it is the wrong metric. Replace it.

Executive Summary of the Ten Modules

Module 1, SOP Foundations and Setup, establishes the operating system: what an SOP is, how SOPs are organized and named, how processes get documented in the first place, and how accountability is assigned. Without Module 1, every later module collapses into a pile of disconnected documents.

Module 2, Daily Admin and Office Operations, covers the workflows that make the workday itself function: opening and closing the business, processing email, managing the calendar, organizing files, and routing internal communication to the right channel.

Module 3, Customer Service and Client Experience, covers every customer-facing touchpoint from first inquiry through complaint resolution and post-purchase follow-up. These are the SOPs that protect your reputation and your retention numbers.

Module 4, Sales and Lead Management, covers lead capture, qualification, discovery, proposals, and follow-up. Every leak in the sales pipeline is a leak in revenue, and every leak is closed by an SOP.

Module 5, Marketing Operations, covers content planning, social media, email newsletters, campaign launches, and brand asset governance. Marketing without SOPs produces sporadic output and inconsistent quality. Marketing with SOPs produces a publishing engine.

Module 6, Finance and Bookkeeping, covers invoicing, accounts receivable, accounts payable, cash and deposit reconciliation, and expense tracking. These are the SOPs that keep the business solvent and audit-ready.

Module 7, Hiring, HR, and Team Management, covers job posting, interviewing, onboarding, daily role expectations, and performance review. Bad hires are the single largest avoidable cost in most small businesses; structured SOPs cut that cost significantly.

Module 8, Project, Task, and Workflow Management, covers how work gets created, assigned, planned, handed off, and closed. This module connects the operational SOPs in Modules 2–7 to the strategic work that moves the business forward.

Module 9, Quality Control, Risk, and Compliance, covers final review, error reporting, data security, contract management, and emergency continuity. These are the SOPs that prevent the disasters you cannot afford.

Module 10, Implementation, Training, and Maintenance, covers how to roll out the program, train the team, validate that the SOPs actually work, version-control them over time, and measure whether the operations function is improving. Module 10 is the difference between a binder on a shelf and a living management system.

Glossary of Key Terms

SOP (Standard Operating Procedure). A written document that describes how a specific recurring task is performed, by whom, using which tools, to what standard, and with what verification. An SOP is not a policy; a policy describes what the business has decided. An SOP describes how the decision is executed.

Owner. The single person accountable for an SOP being followed correctly. The Owner is not necessarily the person who performs every instance of the task, but is responsible for ensuring it gets done to standard.

Backup Owner. A second person trained to perform the SOP when the Owner is unavailable. Every SOP must have a Backup Owner; "we'll figure it out" is not a continuity plan.

Approver. The person who must sign off before the output of an SOP leaves the business or affects a customer, employee, or financial record. Not every SOP requires an Approver; high-risk SOPs always do.

Reviewer. The person who audits the SOP itself — not the output, but the document — on a defined schedule, confirming that the steps still match reality and the tools and links still work.

RACI. A four-letter accountability framework: Responsible (does the work), Accountable (is on the hook for the result), Consulted (provides input), Informed (kept in the loop). Used in Module 1 to assign roles across all SOPs.

Version Control. The discipline of tracking every change to an SOP, who made it, when, and why, so that the team always knows which version is current and can roll back if a change causes problems.

Definition of Done. The explicit, written criteria that determine whether a task or SOP is complete. "I think it's done" is not a Definition of Done. "Invoice sent, recorded in CRM, marked Paid in accounting software, and customer notified" is.

Quality Standard. The measurable bar that the output of an SOP must clear. Quality Standards convert subjective opinions ("looks good") into objective tests ("subject line under sixty characters, no typos, links tested, sender address verified").

Metric. A number tracked over time that tells you whether the SOP is producing the intended result. Metrics drive review and improvement.

Sprint. A short, time-boxed period — usually one to four weeks — during which a defined set of SOPs is documented, tested, and rolled out. Sprints prevent SOP work from sprawling into a multi-year project with no momentum.

Module 1: SOP Foundations and Setup

Module 1 is the foundation that every later module rests on. The five SOPs in this module are not about doing customer service or sending invoices — they are about how SOPs themselves get written, organized, named, stored, owned, and maintained. If you skip this module and try to jump straight to operational SOPs, you will end up with a folder full of inconsistent documents that nobody can find, nobody owns, and nobody updates. Within three months that folder will be ignored. Within six months it will be deleted.

The work in this module is one-time setup work, but it deserves real care. Decisions you make in Module 1 about folder structure, naming conventions, document templates, and accountability matrices will propagate through every other SOP you write. Take a day to do Module 1 well, and the remaining nine modules become significantly easier.

SOP 1.1 — SOP Operating System Overview

Purpose. Establish a shared understanding across the team of what an SOP is, where SOPs live, how they are organized, and how they fit into the daily rhythm of the business. This SOP exists to onboard new team members into the SOP system itself and to give every existing team member a consistent answer to the question, "Where do I find the procedure for that?"

Scope. Applies to every team member with a role that performs, approves, or owns any recurring business task. Does not apply to one-time strategic initiatives, which are handled through the Project Kickoff SOP in Module 8.

Owner. Operations Manager (or owner-operator if the business is under ten employees). Backup Owner. Office Manager or designated SOP Coordinator. Approver. Owner-operator. Reviewer. Operations Manager, annually.

Frequency. Read by every new hire during onboarding, reviewed by the whole team annually, updated whenever the SOP system structure changes.

Tools and Inputs. A central SOP repository (Google Drive, SharePoint, Notion, ClickUp, or equivalent), a folder map document, the SOP inventory spreadsheet, and the SOP template library described in SOP 1.2.

Procedure. First, the team member opens the SOP repository at its designated location. Second, they open the folder map document, which is a single-page diagram showing how SOPs are organized by department (Admin, Customer Service, Sales, Marketing, Finance, HR, Operations, Quality). Third, they open the SOP inventory spreadsheet to confirm the current count and status of SOPs across the business. Fourth, they identify the SOPs relevant to their role using the role-to-SOP cross-reference in the inventory. Fifth, they read each role-relevant SOP and acknowledge it in the inventory's acknowledgment column.

Quality Standards. Every new hire completes this onboarding within their first five business days. Every team member can locate any role-relevant SOP within ninety seconds. The folder map matches the actual folder structure exactly; any drift triggers an immediate update.

Common Failures. SOPs scattered across personal drives instead of a central repository. Folder names that differ between team members. Acknowledgments collected on paper that no one keeps. Each failure is corrected by enforcing the single source of truth and the inventory spreadsheet.

Metric. Time-to-find: the elapsed seconds between a team member needing an SOP and opening the correct version. Target under ninety seconds; reviewed quarterly.

SOP 1.2 — SOP Template Library

Purpose. Provide every SOP author with a consistent starting template so that every SOP in the business follows the same nine-section structure: Purpose, Scope, Owner, Frequency, Tools and Inputs, Procedure, Quality Standards, Common Failures, and Metric. Consistent structure makes SOPs faster to write and dramatically faster to read.

Scope. Applies whenever a new SOP is created, an existing SOP is rewritten, or a process is documented for the first time. Does not apply to informal checklists or single-page job aids, which use the lighter Checklist Template described in the appendices.

Owner. SOP Coordinator. Backup Owner. Operations Manager. Approver. Operations Manager. Reviewer. SOP Coordinator, semi-annually.

Frequency. Used every time a new SOP is drafted; the template itself is reviewed every six months for structural improvements.

Tools and Inputs. Editable SOP templates in Google Docs, Microsoft Word, Notion, ClickUp, and PDF formats; the standard SOP header containing title, owner, version number, last reviewed date, and next review date; a screenshot tool for capturing visual references; the business's brand guidelines for any customer-facing language.

Procedure. First, the author opens the template in their preferred tool. Second, they fill in the header fields (title, owner, version, dates). Third, they complete each of the nine sections in the order listed, leaving no section blank — if a section truly does not apply, the author writes "Not applicable" with a one-sentence explanation rather than deleting the heading. Fourth, the author embeds screenshots, links, and reference files inline where they are most useful, not in a separate appendix. Fifth, the author submits the draft to the SOP Coordinator for a structural review before content review.

Quality Standards. Every published SOP contains all nine sections in the standard order, fits within the standard header format, and uses the standard heading hierarchy. Every screenshot is current within the last twelve months. Every external link has been tested and resolves to the intended destination.

Common Failures. Authors invent their own structures because the template "didn't quite fit." Screenshots go stale because tools change but the SOP doesn't. Both failures are prevented by the annual review schedule and by the structural review that precedes content review.

Metric. Template compliance rate, measured as the percentage of new SOPs that pass structural review without revision on the first submission. Target ninety percent or higher.

SOP 1.3 — SOP Naming and Filing System

Purpose. Ensure that every SOP, regardless of which team member creates it or which tool it lives in, follows a single naming convention and resides in a predictable folder location. A consistent naming and filing system reduces time-to-find, prevents duplicate SOPs from being created accidentally, and makes the SOP inventory accurate by construction.

Scope. Applies to every SOP, checklist, template, and supporting reference document in the SOP repository. Does not apply to project-specific working files, which follow the file naming convention in the Document Management SOP (Module 2).

Owner. SOP Coordinator. Backup Owner. Office Manager. Approver. Operations Manager. Reviewer. SOP Coordinator, quarterly.

Frequency. Applied every time an SOP is created, moved, renamed, or retired.

Tools and Inputs. The folder hierarchy diagram, the naming convention reference card, and the SOP inventory spreadsheet. The naming convention is: [Department Code]-[SOP Number]-[Short Title]-[Version].[ext]. Department codes are three letters: ADM (Admin), CSR (Customer Service), SLS (Sales), MKT (Marketing), FIN (Finance), HRM (Human Resources), OPS (Operations), QLT (Quality).

Procedure. First, the author identifies the correct department folder using the folder hierarchy diagram. Second, they consult the SOP inventory to assign the next available SOP number within that department. Third, they construct the filename using the naming convention. Fourth, they save the file in the department folder with the correct extension. Fifth, they add the new SOP to the inventory with its owner, status, and review date. Sixth, they confirm the file is accessible to every role listed in its Scope section by checking the folder's sharing settings.

Quality Standards. Every file in the SOP repository conforms to the naming convention with no exceptions. Every SOP appears in the inventory within twenty-four hours of being saved. Every SOP appears exactly once in the inventory; duplicates are merged or one of them is retired.

Common Failures. Authors save SOPs to their personal drives or to their email drafts folder. Duplicates accumulate because two team members write the same SOP independently. Both failures are prevented by enforcing the inventory check before any new SOP work begins.

Metric. Naming compliance rate, measured as the percentage of files in the repository that conform to the convention. Target one hundred percent; audited quarterly.

SOP 1.4 — Process Documentation Workflow

Purpose. Convert the institutional knowledge that currently lives only in a team member's head into a written SOP that any qualified person could follow. This SOP is the bridge between "we just do it that way" and a documented, transferable system.

Scope. Applies whenever a process has never been written down, when a process is being delegated for the first time, or when an existing SOP has drifted from how the work is actually performed.

Owner. SOP Coordinator (facilitates), Process Performer (subject expert). Backup Owner. Operations Manager. Approver. Department head for the affected function. Reviewer. SOP Coordinator, annually.

Frequency. Triggered on demand whenever a new process is identified or an existing process needs documentation.

Tools and Inputs. A screen recording tool (Loom, OBS, or the operating system's built-in recorder), an interview script, the SOP template from SOP 1.2, and the documentation quality rubric.

Procedure. First, the SOP Coordinator schedules a one-hour observation session with the Process Performer. Second, the Process Performer records themselves performing the task end to end, narrating what they are doing and why. Third, the Coordinator reviews the recording and drafts the SOP in the template, transcribing each step in the recorded order. Fourth, the Coordinator schedules a thirty-minute follow-up interview with the Performer to fill gaps where the recording was unclear, missed an edge case, or omitted approval steps. Fifth, the Coordinator writes the Quality Standards, Common Failures, and Metric sections in consultation with the Performer. Sixth, the draft is submitted for structural review, then content review, then test-driven validation per SOP 10.3.

Quality Standards. The drafted SOP reproduces every step the Performer actually performs, not an idealized or compressed version. Edge cases and exceptions are documented under Common Failures, not hidden. The Performer signs off that the SOP matches their actual practice.

Common Failures. Documenting the idealized process instead of the real one — the SOP then fails the test in SOP 10.3 because no one can follow it. Skipping edge cases because they are "rare" — the SOP then fails the first time a rare case occurs. Both failures are prevented by recording the actual work and by validating with a non-author.

Metric. First-attempt validation pass rate: the percentage of SOPs that a non-author can execute correctly on the first attempt using only the document. Target seventy percent or higher; SOPs below this rate are revised before publication.

SOP 1.5 — Roles, Owners, and Accountability Matrix

Purpose. Assign a clear, single accountable Owner to every SOP, every recurring task, and every business process. Eliminate the ambiguous "we" that hides accountability and produces the failure mode in which everyone assumed someone else was doing it.

Scope. Applies to every SOP and every recurring task in the business. Does not apply to one-off project tasks, which are owned through the Project Kickoff SOP in Module 8.

Owner. Operations Manager. Backup Owner. Owner-operator. Approver. Owner-operator. Reviewer. Operations Manager, quarterly.

Frequency. Updated whenever a new SOP is published, when a team member joins or leaves, or when responsibilities are reassigned. The full matrix is audited quarterly.

Tools and Inputs. The Accountability Matrix spreadsheet (one row per SOP, columns for Responsible, Accountable, Consulted, Informed, Approver, Reviewer, and Backup), the team roster, and the org chart.

Procedure. First, the Operations Manager opens the matrix and identifies any row with a missing or vague entry. Second, for each gap, they consult the relevant department head to identify the correct person by name, not by title. Third, the named person is notified and confirms the assignment in writing in the matrix. Fourth, every SOP in the repository is updated so that the names in its header match the names in the matrix. Fifth, the matrix is published in the SOP repository at a predictable location and announced to the team. Sixth, the next quarterly review is scheduled on the operations calendar.

Quality Standards. Every SOP row in the matrix has exactly one Accountable name. No name is Accountable for more than seven SOPs at any one time (a heuristic for preventing single-point-of-failure overload). Every Accountable name has a different Backup name; an SOP cannot be its own backup.

Common Failures. Multiple Accountable names per SOP, which functionally means no Accountable. Backups that are also the primary owners of seven other SOPs, making them unable to cover. Both failures are caught in the quarterly audit and corrected before they cause a real continuity problem.

Metric. SOPs with a single named Accountable plus a distinct named Backup: target one hundred percent. Reviewed quarterly.

Module 2: Daily Admin and Office Operations SOPs

Module 2 documents the workflows that make the rest of the business operable. Email, calendar, files, opening, closing, and internal communication may not feel glamorous, but every one of them is a vector for lost information, missed commitments, or wasted hours. A business that runs Module 2 well looks calm from the outside because the predictable work has been removed from anyone's attention. A business that runs Module 2 poorly looks frantic, and the frantic energy is usually misread as "busy and growing" when it is actually "leaking and inefficient."

The five SOPs in this module map to the five recurring questions every admin function answers daily: How does the day begin and end? How is the inbox handled? How is the calendar protected? Where do files live? Where does communication go? Documenting answers to those five questions removes most of the friction in a small business's typical day.

SOP 2.1 — Daily Opening and Closing SOP

Purpose. Define a consistent set of opening and closing steps that prepare the business for the day and close it down cleanly, so that no day starts with confusion about whether yesterday's work was finished and no day ends with loose ends that surprise the team tomorrow.

Scope. Applies to every operating day on which the business serves customers, processes payments, ships product, or has staff on site or remotely on shift. Branch offices, retail locations, and remote teams each follow a parallel adaptation of this SOP.

Owner. Shift Lead or Office Manager. Backup Owner. Operations Manager. Approver. Operations Manager. Reviewer. Office Manager, semi-annually.

Frequency. Twice every operating day — once at opening, once at closing.

Tools and Inputs. Daily Opening Checklist, Daily Closing Checklist, point-of-sale or payment processor dashboard, security alarm code, cash drawer (if applicable), task management board for the day's priorities, internal communication channel for the day's standup note.

Procedure. At opening, the Shift Lead unlocks and physically inspects the workspace, confirms that lighting, climate, and signage are correct, logs into the operating systems (POS, scheduling tool, communications platform, alarm), reviews the prior day's closing notes, reviews the day's calendar and task board, posts a brief standup note to the team channel, and confirms staffing for the day. At closing, the Shift Lead reconciles the day's transactions (per SOP 6.4), files any physical paperwork, completes the closing checklist, posts a closing note summarizing exceptions and next-day priorities, secures the workspace, sets the alarm, and confirms via the team channel that closing is complete.

Quality Standards. Both checklists are completed in full every operating day with no skipped items. The closing note is posted within fifteen minutes of physical close. The opening note is posted within thirty minutes of physical open. Any missed item triggers an entry in the error log per SOP 9.2.

Common Failures. "Quick" closes that skip reconciliation, leading to next-day discoveries of missing deposits. Opening without reading the prior day's closing note, leading to repeated mistakes. Both are prevented by treating the checklist as the Definition of Done for the shift, not as a nice-to-have.

Metric. Opening-and-closing checklist completion rate, target one hundred percent over a rolling thirty-day window. Reviewed weekly by the Operations Manager.

SOP 2.2 — Email Inbox Management SOP

Purpose. Convert email from a reactive interruption into a managed channel with predictable response times, clear routing, and a defined empty state. Reduce the cognitive cost of email so that team members can focus on the higher-value work between inbox sessions.

Scope. Applies to every shared business inbox (support@, sales@, billing@, info@) and to every individual inbox associated with a customer-facing or partner-facing role. Does not apply to purely personal inboxes.

Owner. Inbox Owner named in the role description. Backup Owner. Designated backup named in the role description. Approver. Department head for the function the inbox serves. Reviewer. Operations Manager, semi-annually.

Frequency. Inboxes are processed at scheduled times — typically three times per day at the start of each three-hour block — rather than continuously. Continuous monitoring is reserved for documented urgent channels.

Tools and Inputs. Email platform (Gmail, Outlook, or equivalent), label or folder system with these standard labels: Action, Waiting, Reference, Reply Drafted, Archive. Canned response library for the top ten recurring inquiries. CRM or ticketing tool for customer-facing inboxes.

Procedure. First, the Inbox Owner opens the inbox at the scheduled time and processes every new message in order from oldest to newest. Second, for each message, the Owner decides among five actions: archive (no response needed), reply now (under two minutes), delegate (forward with assignment), defer (label Action and set a due date), or convert to ticket (for customer support inboxes). Third, every reply uses a canned response where one exists, customized with the recipient's name and specifics. Fourth, any reply that requires another person's input is drafted, labeled Reply Drafted, and routed to the right colleague. Fifth, the inbox is left at Inbox Zero in the Active tab at the end of each session; deferred items are visible only by label.

Quality Standards. Customer-facing replies are sent within four business hours of receipt. Internal replies are sent within one business day. Inbox is at Active-zero at the end of each scheduled processing session. No message sits unanswered for more than two business days without an interim acknowledgment.

Common Failures. Treating the inbox as a to-do list rather than as a triage queue. Skipping the canned response library because "this one is special" and rewriting from scratch. Both are prevented by treating the inbox window as a closed session rather than as an open tab.

Metric. Average first-response time, target under four business hours for customer-facing inboxes. Reviewed weekly.

SOP 2.3 — Calendar and Appointment Management SOP

Purpose. Maintain a calendar that accurately reflects commitments, protects focused work time, prevents double-booking, and gives customers and team members a frictionless way to book meetings and appointments.

Scope. Applies to every customer-facing calendar (sales, support, professional services), every team member with public booking availability, and every shared resource calendar (conference room, vehicle, equipment).

Owner. Each calendar owner for their own calendar; Office Manager for shared resource calendars. Backup Owner. Calendar delegate named per calendar. Approver. Department head for customer-facing calendars. Reviewer. Office Manager, quarterly.

Frequency. Continuous; reviewed at start of day during opening per SOP 2.1.

Tools and Inputs. Calendar platform (Google Calendar, Outlook, or equivalent), booking tool with availability rules (Calendly, Acuity, Microsoft Bookings, or equivalent), confirmation email templates, reminder cadence (twenty-four-hour and one-hour reminders by default), cancellation and rescheduling templates.

Procedure. First, define recurring availability windows on every customer-facing calendar; protect at least one half-day per week for focused work that is never bookable. Second, publish the booking link in email signatures, the website footer, and the relevant CRM templates. Third, every booking automatically triggers a confirmation email and adds a calendar invite with the meeting agenda or pre-call form. Fourth, twenty-four hours before each appointment, an automated reminder is sent; one hour before, a final reminder with the meeting link or address is sent. Fifth, cancellations and reschedules use the templated language and free the slot for re-booking within five minutes. Sixth, shared resource calendars require booking before use; ad-hoc grabs are not permitted.

Quality Standards. Zero double-bookings per quarter. Show-up rate above eighty-five percent for confirmed appointments. Every appointment has a written agenda or pre-call form attached. Every cancellation is acknowledged within one business hour.

Common Failures. Manual scheduling via email, which produces double-bookings and exhausts the scheduler. Skipping the agenda field, which produces unfocused meetings. Both are prevented by enforcing the booking tool as the only intake path.

Metric. Combined appointment-system score: show-up rate plus zero double-bookings plus agenda attachment rate. Each component reviewed monthly.

SOP 2.4 — Document Management and File Storage SOP

Purpose. Ensure that every business file — contracts, invoices, client documents, internal records, marketing assets, employee files — lives in a predictable location, follows a consistent naming convention, and is retained for the appropriate period. Eliminate the question, "Where do we keep the X?"

Scope. Applies to every digital file owned or generated by the business across all storage locations: cloud drive, accounting system, CRM, project management tool, and any local file servers.

Owner. Office Manager. Backup Owner. Operations Manager. Approver. Operations Manager (for retention rules), Legal (for contracts retention). Reviewer. Office Manager, quarterly; legal-required files audited annually.

Frequency. Applied every time a new file is created; the structure itself is reviewed quarterly.

Tools and Inputs. Primary cloud storage (Google Drive, OneDrive, Dropbox Business, SharePoint, or Box), folder template, file naming convention, retention schedule, access permission matrix.

Procedure. First, the file creator identifies the correct top-level folder (Clients, Internal, Finance, Marketing, HR, Operations, Legal) using the folder template. Second, they navigate to the correct subfolder (typically by year and then by client or by topic). Third, they save the file using the naming convention: YYYY-MM-DD_[Client or Topic]_[Document Type]_[Version].[ext]. Fourth, they confirm that the file is accessible to the roles defined in the access permission matrix and that it is not accidentally world-readable. Fifth, files past the retention period are archived to a read-only archive folder by the Office Manager during the quarterly review.

Quality Standards. Every file in active folders follows the naming convention. Every file's location can be predicted by a non-author within thirty seconds. Every file containing personally identifiable information, financial data, or contracts is restricted to named roles, never shared by link to anyone with the URL.

Common Failures. Files saved to desktops or downloads folders that never reach the shared drive. Files named "Final_v3_FINAL_revised.docx" that defeat any naming convention. Both are prevented by the quarterly audit and by training every new hire in this SOP during onboarding per Module 7.

Metric. Time-to-locate, measured quarterly by asking a non-creator to find five randomly selected files. Target under thirty seconds average.

SOP 2.5 — Internal Communication SOP

Purpose. Match every type of message to the right channel so that synchronous tools (chat, phone, meetings) carry truly synchronous content and asynchronous tools (email, project comments, documents) carry truly asynchronous content. Reduce notification fatigue and improve response quality.

Scope. Applies to every internal message between team members, contractors, and partners. Does not apply to customer communication, which is handled in Module 3.

Owner. Operations Manager. Backup Owner. Office Manager. Approver. Owner-operator (for policy changes). Reviewer. Operations Manager, annually.

Frequency. Continuous; the channel decision chart is reviewed annually and updated whenever a new tool is added.

Tools and Inputs. Chat platform (Slack, Microsoft Teams, or equivalent), email, project management comments, meeting platform, phone, and the published Channel Decision Chart that maps message types to channels.

Procedure. First, the sender identifies the urgency of the message (now, today, this week, no rush) and the audience (one person, a small group, a whole department, the whole company). Second, they consult the Channel Decision Chart: emergencies use phone or paging; today-urgent messages use chat with @mentions; same-week non-urgent messages use email or project comments; reference and policy use the SOP repository. Third, the sender includes a clear subject or first line, the action requested, and the deadline. Fourth, recipients respond within the channel's defined service level: phone immediate, chat within two business hours, email within one business day, project comments within two business days. Fifth, any thread that exceeds three rounds without resolution is escalated to a fifteen-minute call.

Quality Standards. Chat is reserved for messages requiring same-day attention. Meetings are reserved for decisions, complex coordination, or relationship work — not for status updates. Status updates are written, not spoken. No team member receives more than three @mentions per day on routine work.

Common Failures. Using chat for every message, which produces interruption load that makes deep work impossible. Using meetings as a substitute for written decisions, which prevents new hires from learning what was decided. Both are prevented by reviewing the chart annually and by managers modeling the right channel choice.

Metric. Median response time within each channel against its target. Reviewed quarterly via a sampling audit.

Module 3: Customer Service and Client Experience SOPs

Module 3 covers every customer-facing interaction from the first inquiry through long-term relationship management. Customer service is the area where most small businesses lose money silently. A complaint that is not resolved becomes a refund; a refund becomes a chargeback; a chargeback becomes a public review; a public review costs ten future customers. SOPs in this module are not about being nice — they are about responding consistently, fast, and at a quality bar high enough that the customer trusts the business with their next purchase.

The five SOPs in this module form a customer lifecycle in miniature: first inquiry, onboarding, complaint, refund, and follow-up. If a customer interaction is not covered by one of these five SOPs, it likely belongs in Module 4 (sales) or Module 9 (legal escalation). Together with the email and calendar SOPs from Module 2, these SOPs handle the great majority of front-line customer work.

SOP 3.1 — Customer Inquiry Handling SOP

Purpose. Respond to every new customer inquiry within a defined service level, capture the information needed to qualify and route the inquiry, and ensure that no inquiry is lost between intake and the team member who can answer it.

Scope. Applies to every inquiry that arrives via email, phone, website form, chat widget, social media direct message, marketplace message, or in-person walk-in. Does not apply to existing-customer complaints, which use SOP 3.3.

Owner. Customer Service Lead. Backup Owner. Sales Lead. Approver. Operations Manager. Reviewer. Customer Service Lead, quarterly.

Frequency. Continuous during operating hours; out-of-hours inquiries receive an automated acknowledgment and are first-touched within the first business hour of the next operating day.

Tools and Inputs. Shared support inbox, CRM with intake form, response template library, internal routing rules document, ticket numbering system.

Procedure. First, the inquiry is acknowledged within fifteen minutes during operating hours, automatically out of hours. Second, the Customer Service Lead categorizes the inquiry as sales-qualified, support, billing, partnership, or spam. Third, the inquiry is logged in the CRM with name, contact, source, category, and original message. Fourth, a ticket number is assigned and shared with the customer. Fifth, the inquiry is routed to the responsible role per the routing rules: sales inquiries to the sales pipeline (Module 4), support to the resolution queue, billing to Finance. Sixth, the assigned owner sends a substantive first reply within four business hours, not a stalling reply. Seventh, the resolution and time-to-resolution are recorded against the ticket.

Quality Standards. Every inquiry receives an acknowledgment within fifteen business minutes and a substantive reply within four business hours. Every inquiry has a CRM record with a category, source, and resolution. No inquiry is closed without a recorded resolution.

Common Failures. Inquiries received and replied to but never logged, so trends are invisible. Inquiries routed to the wrong department and re-routed multiple times without acknowledging the customer. Both are prevented by the rule that no reply is sent before the CRM record is created and acknowledged.

Metric. First-response time and resolution time, segmented by category, reviewed weekly.

SOP 3.2 — Customer Onboarding SOP

Purpose. Convert a new customer or client from "signed contract" or "first purchase" to "successfully using the product or service" through a structured, repeatable onboarding flow that captures the information needed, sets clear expectations, and reduces the first-month support burden.

Scope. Applies to every new customer who signs a service agreement, every new client engagement, and every new subscription account above a defined revenue threshold. For very small one-time purchases, a lighter version of this SOP (welcome-only) is used.

Owner. Customer Service Lead or Account Manager. Backup Owner. Sales Lead. Approver. Operations Manager. Reviewer. Customer Service Lead, quarterly.

Frequency. Triggered by every new customer signing or purchase that meets the threshold.

Tools and Inputs. Onboarding checklist, welcome email template, intake form (digital), kickoff call agenda, access provisioning checklist, first-thirty-days timeline.

Procedure. First, within one business day of the signed agreement, the Account Manager sends the welcome email containing the kickoff call link, the intake form, and the first-thirty-days timeline. Second, the customer completes the intake form before the kickoff call; the call is rescheduled if the form is not completed. Third, during the kickoff call, the Account Manager confirms goals, success criteria, points of contact, escalation paths, and communication preferences. Fourth, within two business days of the call, the Account Manager provisions all access (logins, shared drives, scheduled meetings, deliverable templates) per the access checklist. Fifth, the Account Manager sends a recap email documenting goals, dates, deliverables, and the agreed cadence. Sixth, the customer is checked on at day seven, day fourteen, and day thirty per the onboarding cadence; any blockers identified become tickets per SOP 3.1.

Quality Standards. Every onboarded customer completes the intake form before kickoff. Every kickoff is documented with a recap email. Every onboarding hits the four checkpoints (kickoff, day seven, day fourteen, day thirty). Customer onboarding satisfaction at day thirty is measured at four out of five or higher.

Common Failures. Skipping the intake form because the customer is impatient, which produces missing context and surprise scope. Treating onboarding as one call rather than a thirty-day program, which produces customers who use ten percent of what they bought. Both are prevented by enforcing the four checkpoints and by treating the recap email as a deliverable, not a courtesy.

Metric. Day-thirty onboarding satisfaction and the percentage of customers completing all four checkpoints. Reviewed monthly.

SOP 3.3 — Customer Complaint Resolution SOP

Purpose. Receive, log, investigate, and resolve customer complaints with empathy, speed, and documentation, so that the complaint does not become a refund, a chargeback, or a public review — and so that the underlying cause does not produce ten more complaints next week.

Scope. Applies to every customer message that expresses dissatisfaction, alleges an error or defect, requests a remedy, or threatens escalation. Includes complaints received privately and publicly. Does not apply to standard refund requests where the customer is satisfied with the policy (SOP 3.4).

Owner. Customer Service Lead. Backup Owner. Operations Manager. Approver. Owner-operator for resolutions above the standard authorization threshold. Reviewer. Customer Service Lead, monthly.

Frequency. Continuous; complaint queue is reviewed at the start and end of every business day.

Tools and Inputs. Complaint log, escalation flowchart, scripted phrases (empathy, ownership, next-step), resolution catalog with pre-authorized remedies, root-cause template.

Procedure. First, acknowledge the complaint within thirty minutes during operating hours with an empathy statement that names the customer's experience without admitting legal liability. Second, log the complaint in the complaint log with date, customer, channel, summary, and severity. Third, gather facts from the customer and from internal records within four business hours. Fourth, propose a resolution selected from the resolution catalog or escalated for approval if it exceeds the standard authorization threshold. Fifth, confirm the resolution with the customer in writing, execute it, and confirm execution again in writing. Sixth, complete a brief root-cause entry naming the originating SOP or process and assign any corrective action per SOP 9.2.

Quality Standards. Every complaint is acknowledged within thirty minutes and resolved within five business days (target: three). Every complaint receives a written resolution and a root-cause entry. Resolution offers are pulled from the catalog or approved by name; no off-the-cuff give-aways without an approver's sign-off.

Common Failures. Replying defensively, which converts a fixable complaint into a churn event. Resolving without recording the root cause, which guarantees the next ten customers experience the same thing. Both are prevented by training the scripted phrases and by enforcing the root-cause entry as part of the Definition of Done.

Metric. Complaint resolution time and complaint reopen rate. Reviewed monthly with a root-cause trend analysis.

SOP 3.4 — Refund, Return, and Cancellation SOP

Purpose. Process refunds, returns, cancellations, subscription changes, and no-shows consistently, fairly, and quickly, so that customers experience the policy as predictable and the business experiences predictable costs.

Scope. Applies to every request for a refund, return, exchange, subscription change, or cancellation. Includes both customer-initiated and business-initiated cancellations (for example, when a customer fails to meet conditions).

Owner. Customer Service Lead. Backup Owner. Finance Lead. Approver. Finance Lead for refunds above the standard authorization threshold; Owner-operator for exceptions to written policy. Reviewer. Finance Lead, quarterly.

Frequency. Continuous; refund queue is reconciled daily during closing per SOP 2.1.

Tools and Inputs. Published refund and cancellation policy, refund decision tree, refund log, accounting and payment processor refund functions, response templates, customer notification scripts.

Procedure. First, the request is received and logged with date, customer, amount, reason, and policy section invoked. Second, the decision tree is applied: in-policy requests are approved by the Customer Service Lead and processed within one business day; out-of-policy requests are escalated to the Finance Lead with a written justification. Third, approved refunds are issued in the payment processor and recorded in the accounting system with the matching original transaction. Fourth, the customer is notified in writing with the amount, the date funds will appear, and the closure of any subscription or account access. Fifth, returns require a return authorization number, a return shipping label or instructions, and inspection on receipt. Sixth, cancellations close access on the agreed effective date and trigger any data-export obligations.

Quality Standards. In-policy refunds are processed within one business day; out-of-policy within three business days of approval. Every refund is matched to its original transaction and a reason code. Cancellation effective dates are honored exactly; no retroactive billing.

Common Failures. Refunds processed without policy justification, which accumulates into uncategorized losses. Cancellations honored verbally but not in the billing system, leading to double-billing complaints. Both are prevented by the decision tree and by the daily reconciliation.

Metric. Refund rate as a percentage of revenue and time-to-process. Reviewed monthly with trend analysis by reason code.

SOP 3.5 — Customer Follow-Up and Feedback SOP

Purpose. Maintain the customer relationship after the immediate sale or service so that satisfaction is measured, testimonials and referrals are captured, and repeat purchases are prompted at the right moment.

Scope. Applies to every customer at defined post-purchase or post-service intervals. Frequency varies by business model: transactional businesses follow up at day three, day fourteen, and day ninety; subscription businesses follow up at day seven, day thirty, day ninety, and renewal; professional services businesses follow up at delivery, day thirty, and quarterly.

Owner. Customer Service Lead, with Marketing Lead consulted on referral and review prompts. Backup Owner. Sales Lead. Approver. Operations Manager. Reviewer. Customer Service Lead, quarterly.

Frequency. Continuous; the cadence is automated where possible and reviewed monthly.

Tools and Inputs. Email automation tool, survey tool (NPS or CSAT), review platform links (Google, industry-specific), referral program description, repeat-purchase prompt templates, tracking spreadsheet or CRM dashboard.

Procedure. First, at the defined first checkpoint, send a thank-you message that confirms successful delivery and invites a one-question satisfaction rating. Second, customers who rate four or five stars are offered a review or testimonial path; those who rate one to three stars are routed to the complaint flow per SOP 3.3. Third, at the second checkpoint, send a usage tip or success story relevant to their purchase. Fourth, at the third checkpoint, send a repeat-purchase or referral prompt with a personalized incentive where appropriate. Fifth, every customer reply is logged; reviews are tracked; referrals are converted to leads per SOP 4.1.

Quality Standards. Follow-up emails reach all eligible customers at the defined intervals with no gaps. Reply rates and review-conversion rates are tracked monthly. Customers who request not to be contacted are flagged in the CRM and removed from the cadence.

Common Failures. Follow-up that is generic or sales-heavy at the wrong moment, which produces unsubscribes. Following up customers who have a live complaint, which produces resentment. Both are prevented by routing through the CRM, which suppresses follow-ups for active complaint cases.

Metric. Reply rate, review conversion rate, and repeat-purchase rate per follow-up cohort. Reviewed monthly.

Module 4: Sales and Lead Management SOPs

Module 4 covers the work of turning interest into revenue. Every step in the sales pipeline is an opportunity to lose a deal — leads that vanish between the website form and the CRM, qualifying calls that don't qualify, proposals that sit in inboxes, follow-up that arrives at the wrong cadence. Each of these failures is silent: nobody complains about a lead the business never followed up on. The five SOPs in this module make the pipeline visible, predictable, and disciplined.

These SOPs assume a small-business sales motion that may include inbound web leads, outbound prospecting, partner referrals, and walk-in traffic. They do not assume an enterprise sales operation with a separate SDR and AE function, although they scale well as the business grows. The single most important discipline in Module 4 is that no lead leaves a stage without an explicit next-step commitment recorded in the CRM.

SOP 4.1 — Lead Capture SOP

Purpose. Capture every lead from every source into a single source of truth with consistent, complete fields, so that no lead is lost and every lead can be routed, scored, and followed up.

Scope. Applies to leads from website forms, inbound calls, referrals, events, paid advertising landing pages, social media direct messages, and partner introductions. Walk-in retail traffic is captured when the customer has expressed interest in a future purchase, not at every transaction.

Owner. Sales Lead. Backup Owner. Marketing Lead. Approver. Owner-operator. Reviewer. Sales Lead, monthly.

Frequency. Continuous; the capture is automated where possible and manual capture is required within fifteen minutes of the inbound contact.

Tools and Inputs. CRM platform, website form integration, ad platform lead-form integrations, call-tracking tool with capture, business card scanner, lead intake template, lead source taxonomy.

Procedure. First, every lead source publishes into the CRM through an integration or a documented manual-entry route — no source is allowed to send leads to a personal inbox alone. Second, the standard lead fields are captured for every lead: name, email, phone, company (if applicable), inquiry topic, source, source detail, captured-by, captured-at, and consent for follow-up. Third, leads from events and walk-ins are entered into the CRM within twenty-four hours of the event end. Fourth, each lead is automatically routed to the responsible salesperson based on the routing rules, with an SLA timer started for first-touch. Fifth, duplicate detection runs on every new lead; duplicates are merged with the most recent activity preserved.

Quality Standards. Every lead has all required fields populated. Every lead has a source. Every lead is routed within fifteen minutes of capture. No lead lives in a personal inbox for more than one business day before being captured to the CRM.

Common Failures. Leads received by email and kept in personal inboxes, never reaching the CRM. Leads captured without a source, which makes attribution impossible. Both are prevented by integrations and by manager-level visibility of the capture log.

Metric. Capture completeness (percentage of leads with all required fields) and capture latency (median minutes from inquiry to CRM record). Reviewed weekly.

SOP 4.2 — Lead Qualification SOP

Purpose. Determine, quickly and consistently, whether a lead is a good fit to pursue, so that salesperson time goes to leads with real revenue potential and unqualified leads are nurtured or politely closed without burning hours of discovery time.

Scope. Applies to every lead before it advances to a full discovery call or proposal. Does not apply to repeat customers, who are routed directly to a fulfillment or account-management flow.

Owner. Sales Lead. Backup Owner. Sales Development Representative or Account Executive. Approver. Sales Lead. Reviewer. Sales Lead, monthly.

Frequency. Performed on every newly captured lead before the first scheduled discovery call.

Tools and Inputs. Qualification checklist, scoring rubric (a small-business variant of BANT or MEDDIC, calibrated to the business's price point), qualifying-call script, CRM stage definitions, automated email nurture for unqualified-yet leads.

Procedure. First, the qualifier reviews the lead's source detail and any pre-call form responses. Second, the qualifier calls or messages the lead within the first-touch SLA. Third, the qualifier follows the qualifying script to confirm budget range, need fit, decision-maker authority, and timing. Fourth, the qualifier scores the lead against the rubric and assigns one of three outcomes: qualified (advance to discovery), nurture (not now but eligible later), or closed-not-fit (with reason recorded). Fifth, qualified leads receive a discovery-call invitation immediately; nurture leads are routed into a documented nurture cadence; closed-not-fit leads receive a polite written close with referral options when appropriate.

Quality Standards. Every lead is qualified within two business days of first-touch. Every qualification decision has a recorded score and reason. Disqualified leads receive a written response, not silence.

Common Failures. Treating every lead as qualified, which consumes salesperson hours on leads that will never close. Closing leads without recording why, which prevents marketing from learning. Both are prevented by enforcing the rubric and by monthly review.

Metric. Qualification accuracy, measured retrospectively as the percentage of qualified leads that close, and conversion rate from qualified to closed. Reviewed monthly.

SOP 4.3 — Sales Call and Discovery SOP

Purpose. Run a sales call that uncovers the prospect's actual situation, problems, goals, and constraints, so that the proposal that follows is tailored, accurate, and likely to close — and so the prospect leaves the call feeling understood rather than pitched.

Scope. Applies to every scheduled discovery call with a qualified lead. Does not apply to product-demo-only calls, which use a separate Demo Script SOP for product-led businesses.

Owner. Account Executive or Sales Lead. Backup Owner. Sales Lead. Approver. Sales Lead (call reviews). Reviewer. Sales Lead, monthly.

Frequency. Performed on every discovery call.

Tools and Inputs. Pre-call form responses, call agenda template, discovery script with primary and follow-up questions, CRM note template, recording tool with consent prompt, next-step language library.

Procedure. First, prepare for the call by reviewing the lead's CRM record, the pre-call form, and any public information (website, LinkedIn, recent news). Second, open the call by stating the agenda and confirming time available. Third, ask the discovery questions in the order in the script — situation, problem, goals, constraints, decision process, timing — taking notes in the CRM template in real time. Fourth, summarize back to the prospect what you heard to confirm accuracy. Fifth, outline what a tailored proposal would include and ask whether to proceed. Sixth, commit to an explicit next step with a date and time before ending the call; "I'll send a proposal next week" is not a commitment, "I'll send a tailored proposal by Friday and we'll review it on the call we just scheduled for Tuesday at 2pm" is. Seventh, update the CRM within sixty minutes of the call with notes, score, and next steps.

Quality Standards. Every discovery call ends with a recorded next step and a scheduled time. Every discovery call has a CRM note within sixty minutes. No more than one discovery call per prospect before a proposal or a clear close.

Common Failures. Talking more than the prospect on a discovery call, which gathers no information. Ending without a scheduled next step, which lets the deal cool. Both are prevented by following the script and by tracking talk-time on recorded calls.

Metric. Discovery-to-proposal conversion rate and median days from discovery to proposal. Reviewed monthly.

SOP 4.4 — Proposal and Quote Creation SOP

Purpose. Produce proposals and quotes that are accurate, scope-clear, priced correctly, and delivered on time, so that the sales pipeline does not stall in the proposal stage and the business is not committed to scope or pricing it cannot deliver profitably.

Scope. Applies to every formal proposal, statement of work, quote, or estimate sent to a prospect. Does not apply to verbal quotes for low-value transactional services, which use a one-page Quote-Lite template.

Owner. Sales Lead. Backup Owner. Operations Manager. Approver. Operations Manager for non-standard scope; Finance Lead for non-standard pricing or terms. Reviewer. Sales Lead, quarterly.

Frequency. Triggered by a qualified discovery call that requests a proposal.

Tools and Inputs. Proposal template, pricing sheet with standard SKUs and ranges, scope library of pre-written modules, terms-and-conditions block, e-signature platform, internal approval checklist, follow-up email templates.

Procedure. First, the salesperson assembles the proposal from the standard template using scope modules and pricing from the published sheet. Second, any deviation from standard scope or pricing is flagged for approval before the proposal is sent. Third, the proposal is internally reviewed by the Operations Manager for delivery feasibility and by Finance for pricing and terms; reviews are completed within one business day. Fourth, the proposal is sent through the e-signature platform with an expiration date of fourteen days. Fifth, a follow-up email is auto-scheduled for day three, day seven, and day twelve. Sixth, accepted proposals trigger the Customer Onboarding SOP (3.2); declined proposals trigger a structured win/loss note.

Quality Standards. Every proposal is sent within two business days of the discovery call. Every proposal has an expiration date. Every non-standard proposal has a written approval. Every accepted proposal has a matching record in the project plan or onboarding system within one business day.

Common Failures. Proposals that miss the expiration date, leaving stale pricing in the market. Proposals that include scope the business cannot deliver, producing immediate margin loss. Both are prevented by the dual review (operations + finance) and by the standard template.

Metric. Proposal turnaround time and win rate by proposal value band. Reviewed monthly with a quarterly win/loss review.

SOP 4.5 — Sales Follow-Up SOP

Purpose. Ensure that every open opportunity receives the right next contact at the right interval, so that deals close at the right velocity and lost opportunities are recognized and closed rather than left to linger as fake pipeline.

Scope. Applies to every qualified opportunity from discovery through closed-won or closed-lost. Does not apply to top-of-funnel marketing nurture, which is owned by Marketing.

Owner. Account Executive responsible for the opportunity. Backup Owner. Sales Lead. Approver. Sales Lead. Reviewer. Sales Lead, weekly during pipeline review.

Frequency. Continuous; follow-up tasks are auto-generated in the CRM based on stage and last-activity date.

Tools and Inputs. CRM with automated task generation, follow-up cadence definitions per stage, email template library, call script library, dead-deal close-out template, weekly pipeline review meeting agenda.

Procedure. First, each opportunity has a defined target close date set at qualification. Second, follow-up tasks are auto-generated based on the cadence: after a sent proposal, follow up on day three, seven, and twelve; after a verbal yes, follow up daily until signed; after a "not now," nurture for ninety days at a published cadence. Third, every follow-up uses a templated message customized with two or three specific references to the prior conversation. Fourth, opportunities with no response after five touches at the stage cadence are closed-lost with a recorded reason and a final close-out message. Fifth, the weekly pipeline review removes ghost deals and confirms next steps on every open opportunity.

Quality Standards. No opportunity goes more than the stage-defined number of business days without contact. No opportunity is open in the CRM without a scheduled next step. Closed-lost reasons are categorized using the standard taxonomy.

Common Failures. Generic follow-up messages with no reference to the prior conversation, which produce zero responses. Pipeline that contains dead deals owners are reluctant to close, which inflates the forecast and starves the marketing budget. Both are prevented by template discipline and by weekly cleanup.

Metric. Time-in-stage by stage and closed-lost reason distribution. Reviewed weekly.

Module 5: Marketing Operations SOPs

Module 5 covers the systems that produce, distribute, and measure marketing output. Marketing in most small businesses is sporadic — bursts of activity followed by silence — because the work depends on the owner's spare attention. The five SOPs in this module convert that sporadic motion into a predictable publishing engine. They do not depend on having a large marketing team; a single person operating these SOPs part-time can sustain a content calendar, weekly email, and consistent social presence.

These SOPs are channel-agnostic about which platforms the business uses. The principles apply to any blog, newsletter, social network, video platform, or local promotional channel. Substitute platform names in step five of every SOP and the procedure remains valid.

SOP 5.1 — Content Planning SOP

Purpose. Maintain a forward-looking content plan that aligns blog, newsletter, social, video, and promotional output with business goals, seasonal moments, and the team's actual capacity to ship work.

Scope. Applies to every piece of owned-channel content. Does not apply to paid advertising creative, which uses a separate Campaign SOP (5.4).

Owner. Marketing Lead. Backup Owner. Content Coordinator. Approver. Owner-operator (quarterly themes), Marketing Lead (individual pieces). Reviewer. Marketing Lead, monthly.

Frequency. Plans are built quarterly, refined monthly, and adjusted weekly.

Tools and Inputs. Editorial calendar (spreadsheet, Notion, or Airtable), topic backlog, audience persona reference, channel cadence definitions, capacity worksheet, approval workflow.

Procedure. First, at the start of each quarter, the Marketing Lead defines two to four themes aligned with the business's quarterly goals. Second, themes are translated into a topic backlog with one row per piece, capturing title, format, channel, target audience, status, owner, due date, and approval state. Third, at the start of each month, the Lead drafts a monthly calendar by selecting backlog items that fit the team's capacity worksheet — no more pieces than the team can demonstrably ship in a month. Fourth, the weekly stand-up confirms what is shipping that week and surfaces blockers. Fifth, every published piece is logged back into the calendar with its publish date, channel, and initial performance reading at seven days.

Quality Standards. The calendar always covers at least the next thirty days. No content is published that is not on the calendar; emergency pieces are added to the calendar before publication, not after. Every piece has an owner, a due date, and an approval state.

Common Failures. Planning more than the team can ship, which produces a calendar full of red. Skipping the seven-day performance reading, which prevents learning. Both are prevented by the capacity worksheet and by the monthly review.

Metric. On-time publish rate (percentage of pieces published on the originally planned date) and audience reach by channel. Reviewed monthly.

SOP 5.2 — Social Media Posting SOP

Purpose. Maintain a consistent, brand-aligned presence on selected social channels with a workflow that produces, approves, schedules, publishes, and tracks posts reliably even when the founder is unavailable.

Scope. Applies to every brand-owned social account on the selected channels. Does not apply to personal accounts of team members, which follow the published social media policy.

Owner. Social Media Coordinator or Marketing Lead. Backup Owner. Content Coordinator. Approver. Marketing Lead. Reviewer. Marketing Lead, monthly.

Frequency. Weekly batch creation and scheduling; daily monitoring during operating hours.

Tools and Inputs. Social management tool (Buffer, Later, Hootsuite, Sprout Social, or native schedulers), brand asset library per SOP 5.5, caption templates, hashtag library, image and video specifications per channel, comment-response guidelines.

Procedure. First, draft the week's posts in the social management tool by the previous Friday using the planned topics from the content calendar. Second, every post includes platform-appropriate copy, an asset that meets channel specifications, the required hashtags, and a clearly stated call-to-action. Third, posts are submitted for approval; the approver reviews for brand voice, accuracy, link integrity, and compliance within one business day. Fourth, approved posts are scheduled at the channel-specific best times defined for the business. Fifth, comments and direct messages are monitored during operating hours and replied to within four business hours using the response guidelines. Sixth, performance is captured at day seven for every post and rolled up monthly.

Quality Standards. Every post meets channel specifications. Every post has been approved before scheduling. No post contains a broken link, a typo, or an outdated promotion. Every customer-relevant comment receives a reply within four business hours.

Common Failures. Posting from a personal phone with no approval, which produces brand drift and the occasional embarrassment. Letting comments accumulate, which signals neglect. Both are prevented by the scheduling tool's approval workflow and by the monitoring SLA.

Metric. Posts published on schedule, engagement rate by channel, and response time on comments. Reviewed monthly.

SOP 5.3 — Email Newsletter SOP

Purpose. Produce and send the regular email newsletter with consistent quality, reliable deliverability, and measurable engagement, so that the email list remains the most controllable marketing channel the business owns.

Scope. Applies to the regular marketing newsletter and to all broadcast emails to the subscriber base. Does not apply to transactional emails (order receipts, password resets), which follow Module 9 security and deliverability standards.

Owner. Email Marketing Coordinator or Marketing Lead. Backup Owner. Content Coordinator. Approver. Marketing Lead. Reviewer. Marketing Lead, monthly.

Frequency. On the business's published newsletter cadence — weekly, biweekly, or monthly. The cadence does not vary without an approved change.

Tools and Inputs. Email service provider, audience segmentation rules, newsletter template, subject-line worksheet, preview-text guidance, test-send list, deliverability monitoring (open rate, click rate, bounce rate, spam complaint rate, unsubscribe rate), legal compliance check (unsubscribe link present, physical mailing address present).

Procedure. First, draft the newsletter against the template, including a single primary call-to-action and at most three secondary links. Second, run the subject-line worksheet: write five candidates, pick two for an A/B test if the list supports it, otherwise pick one and predict open rate. Third, route the draft for approval; the approver checks copy, links, and segmentation within one business day. Fourth, send to the test-send list (two internal addresses on two different email clients) and review on desktop and mobile. Fifth, schedule the send to the audience segment per the cadence. Sixth, at twenty-four and seventy-two hours after send, capture open, click, bounce, complaint, and unsubscribe rates and compare to the rolling average; investigate any metric that drifts more than twenty percent.

Quality Standards. Every send goes to the right segment with no accidental cross-sends. Every send has the legally required unsubscribe link and physical address. Bounce rate stays under two percent; spam complaint rate stays under one tenth of one percent.

Common Failures. Sending to the entire list when a segment was intended, which produces unsubscribes and complaints. Skipping the test send and discovering a broken link after fifty thousand opens. Both are prevented by enforcing the test send and segment confirmation as gates.

Metric. Open rate, click rate, and unsubscribe rate trends. Reviewed monthly with a quarterly engagement review.

SOP 5.4 — Promotion and Campaign Launch SOP

Purpose. Plan and execute time-bound campaigns — discounts, seasonal promotions, product launches, service offers, local events — with all assets, channels, and measurement in place so that the campaign produces the intended business result rather than a chaotic scramble.

Scope. Applies to every campaign that is bounded in time and has a defined offer or outcome. Does not apply to ongoing always-on marketing, which is handled by the Content Planning SOP.

Owner. Marketing Lead. Backup Owner. Sales Lead. Approver. Owner-operator (offer and pricing), Operations Manager (fulfillment readiness). Reviewer. Marketing Lead, after every campaign in the post-mortem.

Frequency. As planned; typically four to twelve campaigns per year for a small business.

Tools and Inputs. Campaign planning worksheet (offer, audience, channels, assets, dates, success metrics, fulfillment plan, budget), timeline template, asset checklist, channel-specific launch checklists, post-campaign report template.

Procedure. First, four weeks before launch, the Marketing Lead drafts the campaign planning worksheet and submits it for owner and operations approval. Second, three weeks before launch, assets are produced and reviewed against the brand asset SOP. Third, two weeks before launch, all channels are configured (email segments, social posts, ad creative, landing page, sales scripts, customer-service FAQs). Fourth, one week before launch, fulfillment and customer-service teams are briefed; the Operations Manager confirms fulfillment readiness. Fifth, on launch day, the Marketing Lead confirms all channels live and monitors the first six hours of performance against the success metrics. Sixth, during the campaign, daily performance is reviewed and channel adjustments are made within the pre-approved range. Seventh, within five business days of campaign close, a post-campaign report is published with the metrics, the wins, the misses, and the corrective actions for the next campaign.

Quality Standards. Every campaign has a written plan, approval, and success metrics before any asset is produced. Every campaign has a fulfillment confirmation before launch. Every campaign has a post-mortem within five business days of close.

Common Failures. Launching without fulfillment readiness, which produces a wave of complaints. Skipping the post-mortem, which guarantees the same mistakes next quarter. Both are prevented by enforcing the gates.

Metric. Campaign result against pre-declared success metric and post-mortem completion rate. Reviewed per campaign and rolled up quarterly.

SOP 5.5 — Brand Asset and Approval SOP

Purpose. Govern the use of brand assets — logos, colors, typography, imagery, voice — so that every customer-facing output is recognizably the business's, regardless of which team member or contractor produced it.

Scope. Applies to every customer-facing asset: marketing materials, sales decks, proposals, packaging, signage, website, social content, and email. Does not apply to internal-only documents, which use a lighter house style.

Owner. Marketing Lead. Backup Owner. Brand Coordinator or Owner-operator. Approver. Marketing Lead (standard usage), Owner-operator (logo placement on permanent assets, vehicle wraps, building signage). Reviewer. Marketing Lead, semi-annually.

Frequency. Continuous; the asset library and brand guidelines are reviewed every six months and after any rebrand.

Tools and Inputs. Brand guidelines document, asset library in the shared drive (logos, fonts, color codes, image library, templates), approval workflow, usage-rights tracker for licensed assets, quality checklist.

Procedure. First, brand assets are stored in a single, version-controlled library accessible to every team member who creates customer-facing material. Second, every asset is named per the file naming convention and tagged with its usage rights (owned, licensed with conditions, third-party with permission). Third, every customer-facing output is reviewed against the brand quality checklist before approval: correct logo version, approved color codes, approved fonts, approved tone, image rights verified, accessibility considered. Fourth, contractors and partners receive the brand guidelines and a usage agreement before being granted asset access. Fifth, the library is audited semi-annually for outdated assets, expiring licenses, and missing approvals.

Quality Standards. No customer-facing output uses an unapproved logo variant, an off-palette color, an unlicensed image, or an off-brand voice. Every licensed asset has a documented expiration date and renewal owner.

Common Failures. Outdated logo versions used in templates that were saved years ago, which carry through to every new proposal. Unlicensed images grabbed from search results, which produce takedown notices and fines. Both are prevented by the audit and by the centralized library.

Metric. Brand compliance audit pass rate, sampled monthly across recent outputs. Target ninety-five percent or higher.

Module 6: Finance and Bookkeeping Operations SOPs

Module 6 covers the financial workflows that keep the business solvent, paid, and audit-ready. Of all the modules, this one is the most often delegated to a single person and the most often broken when that person is unavailable. The five SOPs in this module exist primarily to make finance work survivable when the bookkeeper takes vacation, when the accountant retires, or when the business grows past the point at which one person can hold every number in their head.

These SOPs deliberately do not give accounting advice. They define the operational handling — who does what, when, with what verification — that produces the records an accountant or tax professional can then use. Always consult a qualified accountant for jurisdiction-specific tax, payroll, and reporting requirements.

SOP 6.1 — Invoice Creation and Sending SOP

Purpose. Issue invoices that are accurate, on time, professional, and easy for the customer to pay, so that revenue is recognized correctly and cash arrives in the bank without avoidable delay.

Scope. Applies to every customer invoice issued by the business. Does not apply to point-of-sale receipts for immediate retail transactions.

Owner. Bookkeeper or Finance Lead. Backup Owner. Office Manager. Approver. Finance Lead for non-standard amounts or terms; Operations Manager for scope changes. Reviewer. Finance Lead, monthly.

Frequency. Continuous; invoices are issued on the schedule defined in each contract (typically at delivery, at milestones, or monthly for retainers).

Tools and Inputs. Accounting and invoicing platform (QuickBooks, Xero, FreshBooks, Wave, or equivalent), customer master record with billing contact and address, invoice template with required fields, payment-method options, contract or proposal as the source of scope and amount.

Procedure. First, the Bookkeeper confirms the delivery or milestone trigger and pulls the contract or proposal for scope and amount. Second, the invoice is drafted against the template with customer details, line items matching the contract, amounts, taxes per jurisdiction, payment terms, due date, and accepted payment methods. Third, the invoice is reviewed against the contract before sending; any discrepancy is resolved before issue. Fourth, the invoice is sent via the platform's delivery channel (email link, portal) with a courteous cover note and a clear payment link. Fifth, the invoice is recorded against the customer in the CRM and the accounting system simultaneously. Sixth, the customer's billing contact is reconfirmed at least quarterly for active accounts.

Quality Standards. Every invoice is issued within one business day of the triggering event. Every invoice line ties to a contract or approved change order. Every invoice contains a clickable payment method, a clearly stated due date, and the business's tax identifier where required.

Common Failures. Invoices sent to outdated billing contacts that bounce. Invoices that omit a tax line and require a corrective re-issue. Both are prevented by the quarterly contact reconfirmation and by the template's required fields.

Metric. Invoice-issue latency and re-issue rate. Reviewed monthly.

SOP 6.2 — Accounts Receivable and Payment Follow-Up SOP

Purpose. Track open invoices, follow up at the right cadence, escalate appropriately, and convert receivables into cash within the agreed payment terms, while maintaining the customer relationship.

Scope. Applies to every open customer invoice from issue through paid. Includes credit notes, partial payments, and disputed balances.

Owner. Bookkeeper or Finance Lead. Backup Owner. Office Manager. Approver. Finance Lead for write-offs and payment-plan agreements. Reviewer. Finance Lead, weekly during the receivables review.

Frequency. Receivables are reviewed weekly and at month-end; follow-ups are sent at defined intervals based on age.

Tools and Inputs. Accounting platform aging report, follow-up email templates by aging bucket, escalation decision tree, payment-plan template, customer communication log.

Procedure. First, the Bookkeeper pulls the aging report every Monday morning. Second, invoices in the zero-to-thirty bucket past their due date receive a courteous reminder on day three past due. Third, invoices in the thirty-one-to-sixty bucket receive a firmer reminder with a phone-call follow-up. Fourth, invoices in the sixty-one-to-ninety bucket trigger a Finance Lead review; the customer is contacted directly and a payment plan is offered or the account is paused. Fifth, invoices past ninety days are escalated per the published policy — collections, legal, or write-off — with approval recorded. Sixth, every customer touch is logged so that the next person in the queue has the full history.

Quality Standards. Days Sales Outstanding (DSO) is maintained within the target range for the business. Every invoice past thirty days has a logged follow-up action. No invoice is written off without recorded approval.

Common Failures. Avoiding follow-up because it feels awkward, which results in writeoffs that could have been collected. Aggressive collection language too early, which damages relationships with otherwise good customers. Both are prevented by the templated cadence and by training in the scripted language.

Metric. Days Sales Outstanding (DSO) and percentage of receivables collected within terms. Reviewed weekly.

SOP 6.3 — Bill Payment and Accounts Payable SOP

Purpose. Process incoming bills accurately, approve them in line with authorization limits, schedule payment for the right date, and maintain a clean audit trail, so that the business pays what it owes, on time, and with verification.

Scope. Applies to every supplier invoice, recurring subscription, contractor invoice, and reimbursable expense. Does not apply to payroll, which is governed by the Payroll SOP appendix (industry-specific).

Owner. Bookkeeper or Finance Lead. Backup Owner. Office Manager. Approver. Department head per approval limit matrix; Finance Lead for cross-department or above-threshold bills. Reviewer. Finance Lead, monthly.

Frequency. Bills are processed in two weekly cycles (Tuesday and Thursday) unless time-sensitive.

Tools and Inputs. Accounting platform with payable workflow, vendor master record with banking and tax forms, three-way matching (purchase order, receipt confirmation, invoice) for inventory or contract work, approval limit matrix, payment scheduler.

Procedure. First, incoming bills are received in a single dedicated inbox and forwarded into the accounting platform. Second, the Bookkeeper codes each bill to the correct general-ledger account, project, and tax treatment. Third, three-way matching is performed where applicable; mismatches are returned to the originating department for resolution before payment. Fourth, the bill is routed to the appropriate approver per the matrix; approval is captured in writing or in the system, never verbally. Fifth, payment is scheduled to land on or just before the due date using the agreed payment method (ACH, wire, check, card). Sixth, paid bills are archived against the vendor record with the approval, the invoice image, and the payment confirmation.

Quality Standards. Every payment has documented approval and a matched invoice. No payment exceeds the approver's authorization limit. No duplicate payments. Vendor master records are reconfirmed annually.

Common Failures. Approvals given verbally and lost, which produces audit gaps. Duplicate payments when the same invoice is processed twice. Both are prevented by the matrix and by duplicate detection in the accounting platform.

Metric. On-time payment rate, duplicate payment rate, and percentage of payments with documented approval. Reviewed monthly.

SOP 6.4 — Daily Cash, Deposits, and Reconciliation SOP

Purpose. Reconcile each operating day's sales, deposits, and cash so that bank balances match accounting records, discrepancies are caught within twenty-four hours, and fraud or error is impossible to hide for long.

Scope. Applies to every operating day on which the business takes payment in any form. Adapt the steps to the business's payment mix (cash, card, ACH, marketplace deposits).

Owner. Shift Lead (cash count), Bookkeeper (reconciliation). Backup Owner. Operations Manager. Approver. Finance Lead for unresolved variances. Reviewer. Finance Lead, weekly.

Frequency. Daily reconciliation; weekly verification against bank statements.

Tools and Inputs. Point-of-sale system reports, payment-processor settlement reports, marketplace settlement reports, cash count form, deposit slip log, accounting platform daily entry, variance investigation worksheet.

Procedure. First, at end of day, the Shift Lead pulls the POS day-end report and counts the cash drawer per the cash count form. Second, payment processor settlements for the day are pulled and compared to the POS card totals; any variance over the published threshold triggers investigation before the day is closed. Third, marketplace settlements (if applicable) are matched to platform orders. Fourth, the Bookkeeper enters the day's deposits into the accounting platform with the correct general-ledger split. Fifth, deposits are matched to bank-statement entries within two business days. Sixth, variances over the threshold are investigated using the worksheet; root causes are recorded and corrective actions assigned per SOP 9.2.

Quality Standards. Every operating day is reconciled by end of next business day. Variances are categorized and resolved within five business days. No "ghost" deposits and no orphaned bank credits remain in suspense for more than five business days.

Common Failures. Reconciliation skipped on busy days, which compounds into untraceable variances by month-end. Cash overages quietly absorbed instead of investigated, which conceals the next pattern of error or fraud. Both are prevented by daily discipline and by weekly variance review.

Metric. Reconciliation timeliness and aged variance count. Reviewed weekly.

SOP 6.5 — Expense Tracking and Receipt Management SOP

Purpose. Capture every business expense with the documentation required for accurate books, tax compliance, and timely reimbursement, so that the business deducts what it legally can and does not pay twice or pay for ineligible items.

Scope. Applies to every business expense paid by company card, employee card, personal card with reimbursement, or cash. Includes recurring subscriptions and travel.

Owner. Bookkeeper or Finance Lead. Backup Owner. Office Manager. Approver. Department head per the approval matrix for reimbursement claims. Reviewer. Finance Lead, monthly.

Frequency. Continuous; submissions are due within five business days of the expense.

Tools and Inputs. Expense capture app (mobile receipt scanner integrated with accounting platform), expense category list mapped to the chart of accounts, business-purpose field, mileage tracker, receipt retention policy, reimbursement form for personal-card expenses.

Procedure. First, the spender photographs or imports the receipt into the expense app within five business days of the expense. Second, they select the correct category, enter the business purpose in a single sentence, and tag the project or customer where applicable. Third, expenses above the approval threshold are routed for approval; below threshold expenses post directly. Fourth, the Bookkeeper reviews the weekly expense queue, requesting clarification on any category, business-purpose, or receipt-quality issue. Fifth, approved expenses are posted to the accounting platform and reimbursements (for personal-card expenses) are scheduled on the next payroll or scheduled pay run. Sixth, receipts are retained for the required period per the published retention policy.

Quality Standards. Every expense has a receipt and a business purpose. Every expense is categorized correctly on first submission ninety percent of the time. No expense is reimbursed without approval where one is required.

Common Failures. Receipts piling up for weeks and lost. Generic business-purpose entries ("client lunch") with no client or project named. Both are prevented by the five-business-day rule and by the Bookkeeper's weekly review.

Metric. Expense submission latency, percentage with complete documentation, and reimbursement turnaround time. Reviewed monthly.

Module 7: Hiring, HR, and Team Management SOPs

Module 7 covers the people work that small businesses too often improvise. Bad hires are the single largest avoidable cost in most small businesses; vague onboarding is the second; missing performance feedback is the third. The five SOPs in this module are designed to be implemented by an owner-operator or office manager without a dedicated HR function, while remaining defensible in the event of a dispute. Always check the procedures against your jurisdiction's employment law and consult an employment attorney for sensitive personnel matters.

SOP 7.1 — Job Posting and Recruiting SOP

Purpose. Define open roles clearly, attract a qualified pool of candidates, and track applicants through a consistent intake so that every open role closes within target time-to-hire with a candidate who matches the role's actual requirements.

Scope. Applies to every open hire — full-time, part-time, and contract. Does not apply to interim help engaged via a vetted contractor list.

Owner. Hiring Manager for the role. Backup Owner. Operations Manager. Approver. Owner-operator (headcount and budget), Hiring Manager (description and criteria). Reviewer. Hiring Manager, after each hire in the retrospective.

Frequency. As needed; the recruiting workflow itself is reviewed annually.

Tools and Inputs. Job description template (purpose, responsibilities, required experience, preferred experience, schedule, compensation range, working conditions), applicant tracking system or shared spreadsheet, screening checklist, interview invitation templates, posting platforms.

Procedure. First, the Hiring Manager drafts the job description against the template and submits it for headcount and budget approval. Second, the description is posted on the approved channels with a closing date and consistent application instructions. Third, applications flow into the tracker; each is screened against the screening checklist within three business days of submission. Fourth, qualified applicants receive an invitation to interview within two business days of screening; unqualified applicants receive a polite written close within five business days. Fifth, the recruiting funnel is reviewed weekly during the role's open period; if pipeline is thin, the channel mix and description are revisited.

Quality Standards. Every open role has an approved description and budget before posting. Every application receives a written response within five business days. Time-to-hire is tracked from posting date to accepted offer date against the role's target.

Common Failures. Reposting last year's job description without updates, which attracts mismatched candidates. Letting applications sit unscreened for weeks, which loses the best candidates to faster employers. Both are prevented by the description review and by the three-business-day screening SLA.

Metric. Time-to-hire and percentage of applicants receiving a response within five business days. Reviewed per hire.

SOP 7.2 — Interview and Candidate Evaluation SOP

Purpose. Run structured interviews that produce comparable evaluations across candidates, reduce hiring bias, and surface the information needed to make a confident hiring decision.

Scope. Applies to every candidate who advances past initial screening to a formal interview. Includes phone screens, on-site interviews, panel interviews, and skills assessments.

Owner. Hiring Manager. Backup Owner. Operations Manager. Approver. Owner-operator for final offer; Hiring Manager for shortlist. Reviewer. Hiring Manager, after each hire.

Frequency. Per open role; the interview structure for a given role is reviewed annually.

Tools and Inputs. Interview guide with role-specific questions, scoring rubric tied to the role's required competencies, reference-check template, scheduling tool, candidate comparison matrix, legal-compliance checklist (questions to avoid, accommodations to offer).

Procedure. First, the Hiring Manager assembles a panel of two to three interviewers and distributes the interview guide and rubric before any interview. Second, each interview follows the guide; every interviewer scores the candidate on the rubric within one hour of the interview, before discussing impressions with other panelists. Third, the panel meets within two business days of the final interview to compare scores, surface disagreements, and arrive at a recommendation. Fourth, references are checked for the top candidate with the standard template before the offer is extended. Fifth, the offer is made in writing with compensation, start date, role expectations, and any contingencies; verbal offers are confirmed in writing within twenty-four hours.

Quality Standards. Every interview uses the guide and rubric. Every interviewer scores independently before group discussion. References are checked before every offer. Offers are extended in writing with no contingencies that have not been disclosed.

Common Failures. Skipping the rubric in favor of "gut feel," which reproduces bias and weakens defensibility. Skipping references because the candidate seems great, which misses signals that are hard to surface in interviews. Both are prevented by treating the rubric and references as required gates.

Metric. First-year retention rate of new hires and percentage of hires meeting performance expectations at ninety days. Reviewed quarterly.

SOP 7.3 — New Hire Onboarding SOP

Purpose. Bring a new hire from accepted offer to fully productive contributor through a structured thirty-day program that handles paperwork, tools, training, introductions, and clear expectations, so that the hire reaches productivity quickly and the team does not absorb avoidable disruption.

Scope. Applies to every new hire — full-time, part-time, and long-engagement contractor. Short-term contractors follow a lighter Contractor Onboarding checklist.

Owner. Hiring Manager. Backup Owner. Office Manager. Approver. Operations Manager. Reviewer. Hiring Manager, after each onboarding.

Frequency. Triggered by every accepted offer.

Tools and Inputs. Onboarding checklist by role, welcome email template, day-one schedule, paperwork packet (tax forms, direct deposit, handbook acknowledgment, role-specific agreements), tool-access provisioning list, role-relevant SOPs from this manual per SOP 1.1, training schedule for the first thirty days, manager check-in cadence.

Procedure. First, on offer acceptance, the Hiring Manager initiates the onboarding checklist and assigns owners for paperwork, tools, workspace, and training. Second, the welcome email is sent with the start date, the day-one agenda, parking and dress code, and the first-day contact. Third, on day one, the new hire completes paperwork, receives tool access, meets the team, and is walked through their day-one SOPs per Module 1. Fourth, week-one training follows the schedule with role-specific SOPs and shadowing. Fifth, the Hiring Manager holds check-ins at end of day one, end of week one, end of week two, and end of week four. Sixth, at day thirty, both the manager and the new hire complete a brief written evaluation: how onboarding went, what is missing, what to fix for the next hire.

Quality Standards. Day one runs to schedule with all access in place. The new hire can locate every role-relevant SOP by end of week one. Every check-in occurs on schedule. Day-thirty evaluations produce at least one improvement for the next onboarding.

Common Failures. Day one with no laptop, no access, and no one to greet the new hire, which signals neglect from the first hour. Onboarding that ends after week one, which leaves the new hire to figure out the rest alone. Both are prevented by the checklist and by the manager check-ins.

Metric. Onboarding checklist completion rate and ninety-day retention. Reviewed quarterly.

SOP 7.4 — Employee Daily Task SOP

Purpose. Make every role's daily duties, priorities, and Definition of Done explicit so that team members know what excellence looks like for their role and managers can identify gaps quickly.

Scope. Applies to every team member with a recurring set of role-specific daily duties. Does not apply to leadership roles whose work is project-based, which use the Project SOPs in Module 8.

Owner. Direct Manager. Backup Owner. Department Head. Approver. Department Head. Reviewer. Direct Manager, quarterly.

Frequency. Daily checklist used every shift; the SOP itself is reviewed quarterly or whenever the role changes materially.

Tools and Inputs. Daily task checklist template, role dashboard with task tracker, manager review checklist, escalation rules document.

Procedure. First, the Direct Manager and the team member co-create the daily checklist that captures every recurring duty, its frequency, its deadline within the shift, its standard, and the tool used. Second, the checklist is published to a shared location accessible to the manager and the team member. Third, the team member completes the checklist each shift, marking exceptions and escalations. Fourth, the Direct Manager reviews the prior day's completed checklist during the daily standup or asynchronously by end of the next business day. Fifth, exceptions trigger coaching, an SOP update, or an error report per SOP 9.2. Sixth, the checklist is revised every quarter or when role duties change.

Quality Standards. Every role has a written daily checklist. Every checklist has owners, standards, and escalation rules. Manager review occurs within one business day of each shift's completion.

Common Failures. Checklists that are written but never reviewed, which devolves into compliance theater. Checklists that have grown to thirty items, which guarantees skipping. Both are prevented by quarterly review and by capping the daily checklist at the duties the team member can actually complete in a shift.

Metric. Checklist completion rate and exception rate. Reviewed weekly with the team member.

SOP 7.5 — Performance Review and Feedback SOP

Purpose. Run regular, structured feedback and review conversations that document performance honestly, recognize good work, address gaps early, and produce a written record that supports development and, where necessary, defensible employment decisions.

Scope. Applies to every employee. Long-engagement contractors receive a lighter quarterly review against contract deliverables.

Owner. Direct Manager. Backup Owner. Department Head. Approver. Department Head for written reviews; Owner-operator for compensation changes. Reviewer. Operations Manager, annually.

Frequency. Weekly one-on-ones (thirty minutes), monthly progress reviews, formal written reviews semi-annually.

Tools and Inputs. One-on-one agenda template, monthly review template, semi-annual review template tied to role competencies, goal-tracking sheet, feedback scripting guide (positive and corrective), performance log for ongoing observations.

Procedure. First, every manager holds weekly thirty-minute one-on-ones with each direct report using the agenda: wins, blockers, priorities, feedback, development. Second, observations are logged in the performance log throughout the period so that no review surprises either party. Third, at the monthly review, the manager and the team member compare progress to goals and adjust priorities. Fourth, at the semi-annual review, the manager writes the formal review against the role competencies, the team member completes a self-review, and both meet to discuss; the final review is signed by both. Fifth, corrective feedback is delivered against specific, observable behavior and includes a concrete next step with a deadline; if patterns persist, formal performance management procedures are initiated per the employee handbook.

Quality Standards. Every team member has a one-on-one every week. Every formal review references specific observed behavior, not generalized impressions. Every corrective conversation produces a written summary within one business day.

Common Failures. Skipping one-on-ones during busy periods, which produces feedback debt that becomes confrontation at the semi-annual review. Writing reviews that compliment without specifics, which provides no traction for improvement. Both are prevented by the cadence and by the performance-log discipline.

Metric. One-on-one cadence adherence and percentage of reviews completed on schedule. Reviewed quarterly.

Module 8: Project, Task, and Workflow Management SOPs

Module 8 covers how work gets created, assigned, planned, handed off, and closed. The operational SOPs in Modules 2 through 7 describe the recurring work; Module 8 describes the non-recurring work — projects, initiatives, client engagements, internal improvements — that moves the business forward. Without a project discipline, small businesses tend to overcommit, drop initiatives mid-flight, and lose institutional memory each time a project ends without a closeout.

These SOPs are tool-agnostic. They work in Asana, Trello, ClickUp, Monday, Notion, or a well-structured spreadsheet. The shape of the discipline matters more than the brand of the tool. Pick one tool, use it consistently, and resist the temptation to migrate every six months.

SOP 8.1 — Task Creation and Assignment SOP

Purpose. Convert incoming requests, meeting decisions, and ideas into tasks that have an owner, a due date, a clear action verb, and a Definition of Done, so that work either gets done or is consciously deprioritized — but does not vanish into the gap between intention and execution.

Scope. Applies to every actionable item generated in meetings, emails, chat threads, customer interactions, or planning sessions. Does not apply to ideas not yet committed to action, which live in a separate backlog.

Owner. Project Manager or task creator. Backup Owner. Team lead for the function. Approver. Department Head for tasks exceeding a defined effort threshold. Reviewer. Operations Manager, monthly.

Frequency. Continuous; every meeting and decision point produces tasks captured in the system within the same business day.

Tools and Inputs. Project management platform, task template (title, description, owner, due date, priority, files, Definition of Done), standard priority levels, project structure.

Procedure. First, the task creator writes a title in imperative form ("Send Q2 customer-satisfaction survey," not "Q2 survey"). Second, they fill the description with context the assignee needs and the Definition of Done in measurable terms. Third, they assign exactly one Owner; tasks with multiple owners are split into separate tasks. Fourth, they set a due date that reflects the real deadline, not a hopeful one. Fifth, they attach relevant files and link to the parent project. Sixth, they confirm the assignment with the Owner so that the assignment is acknowledged, not just dispatched.

Quality Standards. Every task has a verb, a single Owner, a due date, and a Definition of Done. No task has more than one Owner. Tasks captured in meetings are entered in the system within the same business day.

Common Failures. Tasks created with vague titles ("Customer feedback") that no one can pick up cold. Tasks assigned without acknowledgment that the assignee never sees. Both are prevented by the template and by the confirmation step.

Metric. Task completion rate by due date and percentage of tasks meeting template standards in a monthly audit.

SOP 8.2 — Weekly Planning and Team Meeting SOP

Purpose. Run a weekly planning meeting that reviews priorities, blockers, KPIs, project progress, staffing, and upcoming deadlines so that the team enters every week aligned on what matters most.

Scope. Applies to every operating department and to the leadership team. Cadence may vary for small departments, but the structure remains the same.

Owner. Department Head. Backup Owner. Operations Manager. Approver. Owner-operator (leadership meeting cadence). Reviewer. Operations Manager, quarterly.

Frequency. Weekly, at a fixed time, with a fixed duration of forty-five to sixty minutes.

Tools and Inputs. Standing meeting agenda (review prior week's commitments, KPIs, project status, blockers, this week's priorities, decisions, action items), notes template, project management dashboards, KPI dashboard, action-item tracker.

Procedure. First, the meeting starts on time with the agenda visible to all attendees. Second, the team reviews completion of the prior week's commitments; missed commitments are explained and either reset or closed. Third, the KPI dashboard is reviewed against targets; metrics moving in the wrong direction are discussed and assigned an owner for investigation. Fourth, each active project's status is reviewed in a one-minute update against the standard format: on track, at risk, off track. Fifth, blockers are surfaced and assigned. Sixth, this week's top three priorities per team member are agreed. Seventh, decisions and action items are captured in the notes with owners and dates and distributed within one business hour of meeting end.

Quality Standards. Meetings start and end on time. Notes are distributed within one business hour. Every action item has an owner and a date. KPIs are reviewed every week with no skipped weeks.

Common Failures. Status updates that consume the whole meeting and leave no time for blockers and decisions, which makes the meeting a report rather than a working session. Notes that are written but never distributed, which guarantees forgotten commitments. Both are prevented by the agenda time-box and by the one-business-hour distribution rule.

Metric. Action-item completion rate by the following meeting and meeting on-time start rate. Reviewed monthly.

SOP 8.3 — Project Kickoff SOP

Purpose. Start every project with a written brief, a defined scope, named owners, a timeline, identified risks, and a communication plan, so that the project starts with shared understanding rather than discovering disagreements in week three.

Scope. Applies to every project — client engagement, internal initiative, operational improvement, product launch — that has more than two participants and lasts longer than two weeks. Smaller efforts use a one-page Lite Kickoff template.

Owner. Project Manager. Backup Owner. Operations Manager. Approver. Department Head sponsoring the project. Reviewer. Operations Manager, after kickoff.

Frequency. Once per project.

Tools and Inputs. Kickoff checklist, project brief template (purpose, scope, success metrics, timeline, deliverables, roles, risks, communication plan, budget), stakeholder list, kickoff meeting agenda.

Procedure. First, the Project Manager drafts the project brief and circulates it to stakeholders for input two business days before kickoff. Second, the kickoff meeting is held with all key stakeholders; the agenda walks the brief section by section and surfaces objections. Third, every disagreement is resolved before kickoff ends; unresolved items become risks with an owner and a resolution date. Fourth, the brief is finalized and signed off in writing by the sponsor and the Project Manager. Fifth, the project is set up in the project management tool with milestones, tasks, owners, and the agreed communication cadence. Sixth, the brief and the project workspace are published to every stakeholder.

Quality Standards. Every project starts with a signed brief. Every brief covers all nine sections of the template. Risks are explicitly identified and owned, not left implicit.

Common Failures. Starting a project on enthusiasm before the brief is signed, which leads to scope creep and conflict. Listing risks as a formality without assigning owners, which means risks become incidents. Both are prevented by treating the signed brief as the gate to project setup.

Metric. Percentage of projects starting with a signed brief and on-time milestone completion rate. Reviewed per project and rolled up quarterly.

SOP 8.4 — Project Handoff SOP

Purpose. Transfer in-progress work between team members, departments, contractors, or client-facing teams without losing context, files, deadlines, or quality.

Scope. Applies to every handoff: planned (vacation coverage, role change), unplanned (illness, departure), and milestone-based (engineering to QA, sales to delivery, project to ongoing operations).

Owner. Outgoing team member. Backup Owner. Project Manager. Approver. Receiving team member's manager. Reviewer. Project Manager, after the handoff.

Frequency. As needed.

Tools and Inputs. Handoff template (project context, files, current status, decisions made, open items, risks, key contacts, next steps, communication preferences), handoff meeting agenda, sign-off form.

Procedure. First, the outgoing team member drafts the handoff document with sufficient detail that the receiving team member can resume work cold. Second, a thirty-to-sixty-minute handoff meeting is held; the document is walked through and questions are answered. Third, the receiving team member confirms understanding and identifies any gaps to be closed before the handoff is signed. Fourth, gaps are closed within two business days; the handoff is then signed by both parties and the receiving team member's manager. Fifth, the outgoing team member remains on call for clarifying questions for the first five business days post-handoff.

Quality Standards. Every handoff produces a written document and a signed acknowledgment. Every handoff meeting occurs before the outgoing team member's last day or before the handoff date. No critical project has its handoff completed on the last day.

Common Failures. Verbal handoffs that lose half the context within a week. Handoffs scheduled for the last day, which leave no time to close gaps. Both are prevented by treating the signed acknowledgment as the gate and by scheduling handoffs at least five business days before the outgoing team member's last operating day.

Metric. Handoff signoff rate and post-handoff issue rate within the first two weeks. Reviewed per handoff.

SOP 8.5 — End-of-Project Closeout SOP

Purpose. Close projects deliberately with a final review, sponsor approval, file archive, billing reconciliation, lessons learned, and follow-on commitments captured, so that the project's value is fully realized and its lessons are usable on the next project.

Scope. Applies to every project that started with a kickoff per SOP 8.3. Smaller efforts close with a single-line completion note in the project tool.

Owner. Project Manager. Backup Owner. Operations Manager. Approver. Project sponsor. Reviewer. Operations Manager, quarterly across all closeouts.

Frequency. Once per project at completion.

Tools and Inputs. Closeout checklist, debrief form (what went well, what did not, what we would do differently), final delivery email template, archive folder structure, billing reconciliation against contract, testimonial request template.

Procedure. First, the Project Manager completes the closeout checklist confirming deliverables delivered, sponsor approval received, files archived per the file SOP, invoices issued and reconciled per Module 6, and follow-on commitments captured as new tasks. Second, the project debrief is held with the team within five business days of closeout; the debrief form is completed and stored with the project. Third, the final delivery email is sent to the client or sponsor with the deliverables, the final invoice or summary, and a testimonial or feedback request where appropriate. Fourth, lessons learned are translated into SOP improvements or new SOPs as needed. Fifth, the project is marked complete in the project tool and the team is publicly recognized for delivery.

Quality Standards. Every project produces a closeout, a debrief, and a final delivery message. No project lingers in "almost done" for more than ten business days past the planned end date without an explicit re-plan or close. Lessons learned produce at least one concrete improvement.

Common Failures. Projects that drift into perpetual "wrap-up" status, which consumes team capacity for the next initiative. Debriefs that produce a list of lessons that no one acts on. Both are prevented by enforcing closeout within ten business days of completion and by converting lessons into tracked improvements.

Metric. On-time closeout rate and number of lessons-learned items converted to acted-on improvements. Reviewed quarterly.

Module 9: Quality Control, Risk, and Compliance SOPs

Module 9 covers the SOPs that prevent the disasters small businesses cannot afford. Quality slips become refunds; errors become incidents; data breaches become lawsuits; missed renewals become operational paralysis; emergencies become closures. The five SOPs in this module are insurance, paid in the cheap currency of routine discipline rather than the expensive currency of cleanup after a crisis.

The principle running through all five SOPs is the same: catch problems early, document them as they happen, and turn them into prevention. Where the operational SOPs of Modules 2 through 8 produce throughput, Module 9 SOPs produce reliability. A business that runs Module 9 well rarely has emergencies, and when it does, it survives them without panic.

SOP 9.1 — Quality Review SOP

Purpose. Catch errors, omissions, and quality issues before work leaves the business — before invoices are sent, marketing is published, products ship, or deliverables reach customers — so that the cost of correction is paid in minutes rather than in customer trust.

Scope. Applies to every customer-facing or financially material output. Each function publishes its own quality checklist appropriate to its work; this SOP defines how those checklists are used and audited.

Owner. Quality Reviewer per function. Backup Owner. Department Head. Approver. Department Head. Reviewer. Operations Manager, quarterly across all checklists.

Frequency. Continuous; every output passes a quality review before release.

Tools and Inputs. Function-specific quality checklist (admin, sales, customer service, marketing, finance, operations), error log per SOP 9.2, sample-audit schedule, escalation rules.

Procedure. First, before any output is released, the Owner of the work runs the function's quality checklist against the output. Second, items that fail the checklist are corrected before release; items that cannot be corrected within the deadline are escalated to the Approver. Third, for high-risk outputs (contracts, financial filings, public announcements, regulated content), a second-party reviewer runs the checklist independently. Fourth, every released output is logged with its reviewer; a quarterly sample audit re-checks a random subset against the checklist. Fifth, recurring failures trigger an update to the SOP that produced the output, not just the checklist.

Quality Standards. No customer-facing output ships without a checklist review. High-risk outputs receive a second-party review. Audit pass rate of at least ninety-five percent in the quarterly sample.

Common Failures. Treating the checklist as theater and ticking boxes without reading. Reviewers who are the same person as the producer, which produces blind spots. Both are prevented by the quarterly sample audit and by the two-party rule on high-risk outputs.

Metric. Audit pass rate and pre-release defect rate (defects caught by review per hundred outputs). Reviewed quarterly.

SOP 9.2 — Error Reporting and Correction SOP

Purpose. Log every error consistently, assign correction, identify root cause, and prevent recurrence, so that the business gets smarter rather than repeating the same mistakes.

Scope. Applies to every operational error — incorrect invoice, missed deadline, mis-shipped product, defective deliverable, missed appointment, internal mistake — regardless of whether the customer noticed. Does not apply to strategic misjudgments, which are reviewed in quarterly retrospectives.

Owner. Person who discovers the error initiates; Department Head owns resolution. Backup Owner. Operations Manager. Approver. Operations Manager for high-severity errors. Reviewer. Operations Manager, monthly trend analysis.

Frequency. Continuous; errors are logged within one business day of discovery.

Tools and Inputs. Error log (date, discoverer, function, error type, severity, customer impact, immediate fix, root cause, corrective action, owner, due date), root-cause categories (process, training, tools, communication, supplier, customer-driven), corrective-action worksheet, no-blame culture statement.

Procedure. First, the discoverer logs the error in the error log within one business day. Second, the Department Head applies the immediate fix to limit customer impact, before any root-cause work. Third, within five business days, the Department Head completes the root-cause analysis and proposes a corrective action with an owner and a due date. Fourth, the corrective action is implemented and verified to be in place. Fifth, the SOP or training that produced the error is updated and the team is notified of the change. Sixth, the Operations Manager reviews the log monthly to identify trends; trends of three or more similar errors in ninety days trigger a deeper review.

Quality Standards. Every error has a logged entry, a fix, a root cause, and a corrective action. Every corrective action has an owner and a verified completion. Errors are discussed without blame; people are protected, processes are improved.

Common Failures. Suppressing errors out of fear, which guarantees their recurrence. Logging errors but never completing the corrective action, which makes the log a dead document. Both are prevented by the no-blame culture and by the monthly trend review.

Metric. Error log completeness, corrective-action completion rate, and recurrence rate. Reviewed monthly.

SOP 9.3 — Data Security and Password Management SOP

Purpose. Protect customer data, employee data, and business-confidential information through consistent access control, password discipline, two-factor authentication, and offboarding so that data breaches and account compromises are unlikely and recoverable.

Scope. Applies to every system that stores or processes customer, employee, financial, or proprietary business data. Every team member with system access is responsible for their own credentials.

Owner. Operations Manager or designated Security Lead. Backup Owner. Office Manager. Approver. Owner-operator for policy changes. Reviewer. Security Lead, semi-annually; access audit quarterly.

Frequency. Continuous; access reviews quarterly; password manager and 2FA setup on every new hire.

Tools and Inputs. Password manager licensed for every team member, 2FA enforcement on every business system that supports it, access control matrix per role, account creation and removal checklist, incident response plan.

Procedure. First, every business account is created through the Security Lead, never directly by team members, so that credentials are owned by the business. Second, every account uses a strong unique password stored in the password manager; passwords are never shared via email or chat. Third, 2FA is enforced on every system that supports it; backup codes are stored in the password manager. Fourth, role-based access is provisioned per the matrix; least-privilege is the default. Fifth, when a team member leaves, their access is revoked on the day of departure per the offboarding checklist; shared credentials are rotated. Sixth, the quarterly access audit reviews every account against the matrix and removes anomalies.

Quality Standards. No shared passwords on customer-data systems. 2FA on every system that supports it. Departing team members' access revoked on the day of departure. Quarterly access audit completed on schedule.

Common Failures. Shared logins for "convenience," which produce uninvestigable incidents. Departing employees with active access for weeks after departure, which is a real and not theoretical risk. Both are prevented by the password manager and the offboarding checklist.

Metric. Percentage of accounts in the password manager, 2FA coverage percentage, and time-to-revoke on departure. Reviewed quarterly.

SOP 9.4 — Legal Document and Contract Review SOP

Purpose. Manage the full lifecycle of business contracts and policies — creation, review, approval, signature, storage, renewal — so that the business is not surprised by expired contracts, missed renewals, or terms it did not realize it had agreed to.

Scope. Applies to every customer contract, vendor agreement, partnership agreement, lease, license, and internal policy document. Does not constitute legal advice; an attorney must be consulted for non-standard or material contracts.

Owner. Operations Manager (operational handling), Owner-operator (signature authority). Backup Owner. Office Manager. Approver. Owner-operator for signature. Reviewer. Operations Manager, quarterly.

Frequency. Continuous; contract tracker reviewed monthly, full audit annually.

Tools and Inputs. Contract tracker (owner, party, contract type, start date, end date, renewal date, auto-renew terms, signed location, key terms, storage path), e-signature platform, contract templates approved by counsel, approval routing.

Procedure. First, every new contract uses an approved template or is reviewed by counsel before signature. Second, the contract is routed for internal approval per the matrix before signature; non-standard terms require an explicit approval. Third, signature is captured through the e-signature platform; paper signatures are scanned to the contract tracker within one business day. Fourth, the contract is logged in the tracker with all required fields. Fifth, renewal alerts are configured at ninety, sixty, and thirty days before renewal; the Owner reviews and decides to renew, renegotiate, or terminate before the auto-renew window. Sixth, the annual audit reviews every active contract against actual practice; discrepancies trigger renegotiation or termination.

Quality Standards. Every active contract is in the tracker with renewal dates set. No contract auto-renews without an active decision. Counter-signed copies are stored centrally, never only on personal drives.

Common Failures. Auto-renewal of services no longer used, which silently bleeds cash. Contracts signed under pressure with unfavorable terms that go unnoticed for years. Both are prevented by the renewal alerts and by the annual audit.

Metric. Tracker completeness, percentage of contracts with renewal alerts configured, and auto-renew surprises (target zero). Reviewed quarterly.

SOP 9.5 — Emergency and Business Continuity SOP

Purpose. Define how the business operates under stress — staff absence, system outage, payment processor failure, weather closure, facility issue, cybersecurity incident, owner unavailability — so that critical operations continue and recovery is faster than the disruption that caused the interruption.

Scope. Applies to every event that prevents the business from operating normally for more than two hours. Distinct from one-off errors, which use SOP 9.2.

Owner. Operations Manager. Backup Owner. Owner-operator. Approver. Owner-operator. Reviewer. Operations Manager, annually with a tabletop exercise.

Frequency. Continuous readiness; tabletop exercise annually; plan updated whenever the business adds a critical system or location.

Tools and Inputs. Emergency contact sheet (key staff, owner, vendors, suppliers, insurance, IT, legal, bank), continuity plan covering the most likely disruption scenarios, decision tree for first-hour response, backup task-coverage matrix per role, communication templates for customers and team, off-site backup of critical data and SOPs.

Procedure. First, on detection of a disruption, the first responder identifies the type and notifies the Operations Manager within fifteen minutes. Second, the Operations Manager opens the relevant section of the continuity plan and follows the first-hour response. Third, internal communication is sent within thirty minutes of detection per the template; external communication, if needed, is approved by the Owner-operator within sixty minutes. Fourth, critical operations are maintained per the backup coverage matrix; non-critical work is suspended. Fifth, the disruption is logged with timeline, impact, and decisions; recovery is verified against the plan before normal operations resume. Sixth, within five business days of resolution, a post-incident review identifies plan updates and assigns owners.

Quality Standards. Plan reviewed at least annually with a tabletop exercise. Emergency contacts current within ninety days. Critical data backed up off-site and the restore process tested at least annually. Every incident produces a written review and at least one plan improvement.

Common Failures. A plan that exists on paper but has never been exercised, so that no one remembers it when it is needed. Backups that exist but have never been restored, so that restoration fails when it matters. Both are prevented by the annual tabletop and by the annual restore test.

Metric. Time-to-first-response on incidents, restore-test pass rate, and plan exercise completion. Reviewed annually with quarterly readiness checks.

Module 10: Implementation, Training, and Maintenance

Module 10 closes the loop. The first nine modules describe what to do; Module 10 describes how to roll the program out, train the team, validate that the SOPs actually work in practice, control versions over time, and measure whether the operations function is improving. Without Module 10, every previous module risks becoming a binder on a shelf. With Module 10, the SOP library becomes a living management system.

The five SOPs in this module are ordered for sequential use: a sprint plan to roll out the first SOPs, a training system to bring the team up to speed, a validation method to confirm the SOPs work cold, a version-control discipline to keep them current, and a metrics dashboard to make the whole operations function visible at a glance.

SOP 10.1 — SOP Build Sprint Plan

Purpose. Roll out the SOP program in a focused thirty-day sprint that documents the most important daily operations first, demonstrates value early, and builds momentum so the team continues writing SOPs after the sprint ends.

Scope. Applies to the initial SOP rollout and to any subsequent sprint to address a specific operational area.

Owner. Operations Manager (sprint lead). Backup Owner. Office Manager. Approver. Owner-operator. Reviewer. Operations Manager, after each sprint.

Frequency. Initial thirty-day sprint at launch; subsequent sprints as needed.

Tools and Inputs. Sprint calendar, prioritization worksheet (frequency × risk × delegation value), task tracker, progress dashboard, training schedule, weekly retrospective agenda.

Procedure. First, the Operations Manager scores the candidate SOP list using the prioritization worksheet and selects ten SOPs for the first sprint. Second, owners are assigned to each SOP with a draft date and a publication date. Third, the sprint kicks off with a one-hour all-team meeting explaining the rationale, the sequence, and the support available. Fourth, weekly retrospectives review draft progress, surface blockers, and adjust the plan. Fifth, each completed SOP is announced to the team and added to the inventory. Sixth, at sprint end, a retrospective documents what worked, what did not, and what the next sprint should tackle.

Quality Standards. The first sprint produces at least ten published SOPs covering critical daily operations. Every SOP in the sprint has an assigned owner and a published date. The retrospective produces a written plan for the next thirty days.

Common Failures. Choosing SOPs by emotion rather than by score, which produces a portfolio that does not move the business meaningfully. Treating the sprint as an event rather than a program, which produces ten SOPs and then silence. Both are prevented by the prioritization worksheet and by the retrospective-to-next-sprint chain.

Metric. Sprint completion rate (SOPs published versus planned), and post-sprint adoption rate measured at thirty days. Reviewed after each sprint.

SOP 10.2 — SOP Training System

Purpose. Train team members on new and updated SOPs through reading, walkthroughs, shadowing, practice, and sign-off, so that publication of an SOP translates into changed behavior, not just a new document in the library.

Scope. Applies to every published SOP. The training intensity scales with the SOP's complexity and risk; simple SOPs require reading and sign-off, complex SOPs require shadowing and practice.

Owner. SOP Owner per SOP; Operations Manager for system. Backup Owner. Office Manager. Approver. Department Head. Reviewer. Operations Manager, semi-annually.

Frequency. Triggered on every new or materially updated SOP.

Tools and Inputs. Training checklist by SOP type, attendance tracker, competency sign-off form, learner-feedback survey, training records archive.

Procedure. First, the SOP Owner classifies the training intensity: read-only, walkthrough, shadow, or hands-on. Second, the training is scheduled within five business days of publication for affected team members. Third, training is delivered per the type: read-only training requires acknowledgment via signed checklist; walkthrough training requires a recorded session with Q&A; shadow training requires the trainee to observe the SOP performed and complete a competency sign-off; hands-on training requires the trainee to perform the SOP under observation. Fourth, every training session ends with the trainee acknowledging the SOP and the trainer signing competency. Fifth, training records are archived with the SOP and with the team member's onboarding file.

Quality Standards. Every published SOP has a training record for every required team member within five business days of publication. Competency sign-offs are completed by an observer, not by self-attestation. Training records are stored against both the SOP and the team member.

Common Failures. Publishing an SOP and assuming the team will read it on their own, which produces no behavior change. Letting trainees sign their own competency sheets, which produces a false record. Both are prevented by the training checklist and by the observer-required sign-off.

Metric. Training-completion rate within five business days of publication and post-training error rate against the SOP. Reviewed monthly.

SOP 10.3 — SOP Testing and Validation Process

Purpose. Confirm that a published SOP can be followed by a qualified person who did not author it, with no additional explanation, so that the SOP is genuinely transferable rather than only useful to the person who wrote it.

Scope. Applies to every new SOP before formal publication and to existing SOPs in the annual review.

Owner. SOP Coordinator. Backup Owner. Operations Manager. Approver. Department Head. Reviewer. SOP Coordinator, quarterly.

Frequency. Before publication for every new SOP; annually for every existing SOP.

Tools and Inputs. Validation instructions, observer notes sheet, revision form, qualified tester (someone with the role's general skills but no prior experience with this specific SOP).

Procedure. First, the SOP Coordinator assigns a tester who has the role's skills but has not performed this SOP before. Second, the tester is given the SOP and the inputs the SOP claims to require, but no verbal coaching. Third, the tester performs the SOP while an observer records every place they stop, ask, hesitate, or improvise. Fourth, the SOP Coordinator and the author revise the SOP based on the notes; gaps are filled, ambiguous steps clarified, missing inputs added. Fifth, a second validation pass is performed with a different tester; the SOP is published only when a tester can complete it without intervention. Sixth, validation results are archived with the SOP.

Quality Standards. No SOP is published without at least one passed validation. Validation evidence is archived. Existing SOPs that fail their annual revalidation are reopened for revision.

Common Failures. Validating with the author's preferred colleague who already knows the work, which produces false passes. Skipping validation under deadline pressure, which produces SOPs that no one outside the author can follow. Both are prevented by the rule that the tester must not have performed the SOP before.

Metric. First-pass validation rate and annual revalidation pass rate. Reviewed quarterly.

SOP 10.4 — SOP Review and Version Control SOP

Purpose. Keep the SOP library accurate over time by scheduling reviews, tracking revisions, archiving old versions, and approving changes — so that the SOPs the team reads today match the way the business actually runs today.

Scope. Applies to every published SOP. Lighter checklists and templates follow the simpler annual-review process.

Owner. SOP Coordinator. Backup Owner. Operations Manager. Approver. Department Head for the affected function. Reviewer. Operations Manager, annually across the library.

Frequency. Every SOP is reviewed at least annually; high-risk SOPs are reviewed semi-annually; SOPs are also reviewed on demand when a process changes.

Tools and Inputs. Revision log, review calendar tied to each SOP's next-review date, approval workflow, change-summary template, archived versions folder.

Procedure. First, the SOP Coordinator monitors the review calendar and notifies Owners of upcoming reviews thirty days in advance. Second, the Owner walks through the SOP with the active performer to confirm it still matches reality; updates are drafted as needed. Third, every change is recorded in the revision log with the date, the author, the change summary, the reviewer, and the approver. Fourth, the version number is incremented per the convention (major version for material changes, minor version for clarifications). Fifth, the previous version is moved to the archive folder and the new version replaces it in the active library. Sixth, affected team members are notified per SOP 10.2 and re-trained if the change is material.

Quality Standards. No SOP is past its review date by more than thirty days. Every change has a revision log entry with all required fields. Archived versions are retained for the legally required period.

Common Failures. Letting the review calendar slip, which produces SOPs that quietly drift from reality. Editing live SOPs without recording the change, which destroys the audit trail. Both are prevented by the calendar and by treating the revision log as part of the SOP itself.

Metric. Percentage of SOPs reviewed on schedule and revision log completeness. Reviewed quarterly.

SOP 10.5 — Metrics and Operations Dashboard

Purpose. Make the health of operations visible at a glance through a dashboard that tracks SOP completion, task accuracy, customer response time, overdue invoices, project status, employee training, and process errors, so that operational decisions are based on data, not on gut feel.

Scope. Applies to the business as a whole. Each department contributes its function's key metrics to the dashboard.

Owner. Operations Manager. Backup Owner. Office Manager. Approver. Owner-operator. Reviewer. Operations Manager, weekly; trend review monthly.

Frequency. Updated weekly; reviewed weekly during the leadership meeting; trended monthly and quarterly.

Tools and Inputs. Dashboard tool (Google Sheets, Excel, Looker Studio, or equivalent BI), metric definitions document, data sources and their owners, target ranges per metric, trend bands.

Procedure. First, the Operations Manager defines the dashboard's metrics, each tied back to one or more SOPs in this manual. Second, data sources are identified and the data owner per source is named; the data refresh cadence is documented. Third, weekly inputs are entered or imported by the named owners by end of day Friday; the Operations Manager reviews completeness before the leadership meeting. Fourth, during the leadership meeting, every metric outside its target range is discussed and assigned an owner for investigation per SOP 8.2. Fifth, monthly trends are reviewed; metrics that have been outside target for two consecutive weeks trigger a corrective action per SOP 9.2. Sixth, the dashboard is updated quarterly to add new metrics, retire metrics that no longer change decisions, and adjust target ranges.

Quality Standards. Dashboard is updated every week with no skipped weeks. Every metric has a target, an owner, and a definition. No metric on the dashboard fails the "would this number change my decision?" test.

Common Failures. Dashboards that grow into wallpaper, with so many numbers that none get acted on. Metrics that no one updates because the source is too hard to pull. Both are prevented by the quarterly review and by limiting the dashboard to the smallest set of metrics that drive real decisions.

Metric. Dashboard update timeliness and percentage of out-of-range metrics that received a documented investigation. Reviewed monthly.

Appendix A: Master SOP Inventory

The following is the complete inventory of the fifty SOPs in this manual. Copy this table into your SOP inventory spreadsheet and customize the Owner, Backup, Status, and Next Review columns to match your business. The Department codes use the convention defined in SOP 1.3.

Module 1 — SOP Foundations and Setup. SOP 1.1 SOP Operating System Overview (OPS-001). SOP 1.2 SOP Template Library (OPS-002). SOP 1.3 SOP Naming and Filing System (OPS-003). SOP 1.4 Process Documentation Workflow (OPS-004). SOP 1.5 Roles, Owners, and Accountability Matrix (OPS-005).

Module 2 — Daily Admin and Office Operations. SOP 2.1 Daily Opening and Closing (ADM-001). SOP 2.2 Email Inbox Management (ADM-002). SOP 2.3 Calendar and Appointment Management (ADM-003). SOP 2.4 Document Management and File Storage (ADM-004). SOP 2.5 Internal Communication (ADM-005).

Module 3 — Customer Service and Client Experience. SOP 3.1 Customer Inquiry Handling (CSR-001). SOP 3.2 Customer Onboarding (CSR-002). SOP 3.3 Customer Complaint Resolution (CSR-003). SOP 3.4 Refund, Return, and Cancellation (CSR-004). SOP 3.5 Customer Follow-Up and Feedback (CSR-005).

Module 4 — Sales and Lead Management. SOP 4.1 Lead Capture (SLS-001). SOP 4.2 Lead Qualification (SLS-002). SOP 4.3 Sales Call and Discovery (SLS-003). SOP 4.4 Proposal and Quote Creation (SLS-004). SOP 4.5 Sales Follow-Up (SLS-005).

Module 5 — Marketing Operations. SOP 5.1 Content Planning (MKT-001). SOP 5.2 Social Media Posting (MKT-002). SOP 5.3 Email Newsletter (MKT-003). SOP 5.4 Promotion and Campaign Launch (MKT-004). SOP 5.5 Brand Asset and Approval (MKT-005).

Module 6 — Finance and Bookkeeping Operations. SOP 6.1 Invoice Creation and Sending (FIN-001). SOP 6.2 Accounts Receivable and Payment Follow-Up (FIN-002). SOP 6.3 Bill Payment and Accounts Payable (FIN-003). SOP 6.4 Daily Cash, Deposits, and Reconciliation (FIN-004). SOP 6.5 Expense Tracking and Receipt Management (FIN-005).

Module 7 — Hiring, HR, and Team Management. SOP 7.1 Job Posting and Recruiting (HRM-001). SOP 7.2 Interview and Candidate Evaluation (HRM-002). SOP 7.3 New Hire Onboarding (HRM-003). SOP 7.4 Employee Daily Task (HRM-004). SOP 7.5 Performance Review and Feedback (HRM-005).

Module 8 — Project, Task, and Workflow Management. SOP 8.1 Task Creation and Assignment (OPS-101). SOP 8.2 Weekly Planning and Team Meeting (OPS-102). SOP 8.3 Project Kickoff (OPS-103). SOP 8.4 Project Handoff (OPS-104). SOP 8.5 End-of-Project Closeout (OPS-105).

Module 9 — Quality Control, Risk, and Compliance. SOP 9.1 Quality Review (QLT-001). SOP 9.2 Error Reporting and Correction (QLT-002). SOP 9.3 Data Security and Password Management (QLT-003). SOP 9.4 Legal Document and Contract Review (QLT-004). SOP 9.5 Emergency and Business Continuity (QLT-005).

Module 10 — Implementation, Training, and Maintenance. SOP 10.1 SOP Build Sprint Plan (OPS-201). SOP 10.2 SOP Training System (OPS-202). SOP 10.3 SOP Testing and Validation Process (OPS-203). SOP 10.4 SOP Review and Version Control (OPS-204). SOP 10.5 Metrics and Operations Dashboard (OPS-205).

Appendix B: Thirty-Day Implementation Roadmap

The roadmap below sequences the first thirty days of SOP implementation for a business starting from zero. It produces ten published, trained, and validated SOPs in four weeks. The selection prioritizes SOPs that protect cash, protect customers, and protect continuity.

Week 1 — Foundation. Day 1: read the foreword, front matter, and Module 1; appoint an SOP Coordinator. Day 2: implement SOP 1.3 (naming and filing) and SOP 1.5 (accountability matrix) at a draft level. Day 3: draft SOP 2.1 (opening and closing). Day 4: draft SOP 6.1 (invoice creation). Day 5: validate and publish SOP 2.1 and SOP 6.1 per SOP 10.3.

Week 2 — Customer Protection. Day 6: draft SOP 3.1 (customer inquiry handling). Day 7: draft SOP 3.3 (complaint resolution). Day 8: draft SOP 6.2 (receivables follow-up). Day 9: validate and publish SOP 3.1, SOP 3.3, and SOP 6.2. Day 10: train the team on the published SOPs per SOP 10.2.

Week 3 — Cash and Quality. Day 11: draft SOP 6.4 (daily cash and reconciliation). Day 12: draft SOP 9.1 (quality review) and the first function-specific quality checklist. Day 13: draft SOP 9.2 (error reporting). Day 14: validate and publish SOP 6.4, SOP 9.1, and SOP 9.2. Day 15: train the team on the published SOPs.

Week 4 — Stability and Cadence. Day 16: draft SOP 8.2 (weekly planning) and SOP 10.5 (metrics dashboard). Day 17: stand up the dashboard with five initial metrics. Day 18: validate and publish SOP 8.2 and SOP 10.5. Day 19: hold the first weekly leadership meeting using SOP 8.2. Day 20: complete the thirty-day retrospective and plan the next sprint per SOP 10.1.

By end of week four, the business will have ten SOPs published, validated, trained, and in active use. From this base, the business adds five to ten SOPs per month until the full library is in place, typically within six to nine months for a small team.

Appendix C: Closing Note

The work in this manual is straightforward, not easy. It is the work that distinguishes a business that runs from a business that depends on the people in the room today. Most of the gains compound: the second SOP is easier than the first, the tenth easier than the second, the fiftieth becomes routine. The cost of writing and adopting these SOPs is days of focused work; the cost of not writing them is paid for the life of the business in repeated mistakes, missed revenue, and the founder's nights and weekends.

Begin with the foreword. Read Module 10 next. Then pick ten SOPs from Appendix B and ship them in thirty days. The manual is a system; treat it as one and it will repay every hour invested in it many times over.

End of Manual.