Internal SOP Platform for Distributed Team

The Problem

A distributed services business with staff across the UK and Europe had accumulated standard operating procedures the way most growing businesses do: by accident. Documents lived in several Google Drive accounts (depending on which director had originally written them), a Notion workspace that had been adopted with enthusiasm and then drifted, a couple of long internal wiki pages, and several Slack threads pinned by managers as “the way we do X”.

The visible symptom was that new starters got different answers depending on who they asked. The deeper symptom was that the business had no confidence in its own consistency. When a process question came up (“how do we handle X?”), there were typically two or three plausible documents and no way to tell which was current. Staff defaulted to asking colleagues, which solved the immediate problem but reinforced the inconsistency.

Previous attempts to fix this had not stuck. Notion was supposed to be the home; it had become one more place SOPs lived in alongside everywhere else. The business had also tried a generic knowledge-base tool, but adoption decayed because nothing structurally prevented people from going back to the documents they were used to.

The Approach

We built a dedicated SOP platform with two design decisions that the previous attempts had skipped. First, every SOP has a named owner who is responsible for its accuracy, with a review cadence enforced by the system. SOPs older than the review interval show a “may be out of date” banner until the owner confirms. This created a structural force pushing the system toward currency rather than relying on culture.

Second, search was treated as the front door rather than the document tree. Most SOP lookups are “how do I do X” rather than “navigate to the right folder”. The platform indexes the full content of every SOP and ranks results by frequency of access, recency of review, and explicit owner-confirmed status. Browsing exists but is secondary.

Migration involved auditing every existing document across the four legacy locations, deduplicating, identifying canonical versions, and assigning owners. A large share of the documents were retired during migration as obsolete or duplicates. A significant cleanup, and an unplanned one.

The System We Built

A Laravel-based SOP platform with full-text search, named ownership on every document, configurable review cadences, version history with diff view, and an embed-friendly model so SOPs can be referenced from the team’s other tools. Slack integration surfacing SOP search results when someone asks a how-to question in a channel, gently redirecting the team toward the canonical source. A dashboard for managers showing which SOPs are overdue for review and which are accessed most often.

The Outcome

“Where is the SOP for X” becomes a search instead of a question in Slack, which matches how people want to find procedures. The named-owner model created accountability without imposing process. Owners get pinged on review dates and update or confirm, and the system stays alive without anyone having to police it.

Migrating also forces a review. Moving each SOP across means checking whether it still describes what the business does, and each one is either updated or formally retired.

What We Learned

The previous tools had failed because nothing structurally pushed against entropy. People left, owners changed, processes evolved, and the documents drifted. Building review cadence and named ownership directly into the platform’s structure is what makes the difference. When the system enforces review dates and tracks ownership, the knowledge base stays current without anyone having to police it.

Same SOP Problem at Your Business?

If your operating procedures are scattered across Drive folders, Notion pages, and Slack threads and nobody is sure which version is current, get in touch to talk through what a centralised platform could look like. The spreadsheet to internal platform migration and recruitment automation workflow replacement case studies cover similar work on internal tooling. Our digital SOPs system page covers what we built here. The case studies overview has the full list.