A Guide to the SOP Process: Preparation, Review, and Approval

Every smooth-running store relies on a quiet backbone: a set of written instructions that tell staff exactly how each task should be done. These are Standard Operating Procedures, or SOPs. But a good SOP does not appear by accident. It moves through a deliberate sequence of preparation, review, approval, and periodic revision. Understanding this sequence is the difference between a document that genuinely guides daily work and one that gathers dust in a drawer. This guide walks through the full SOP process, drawing on quality-management practices used by government agencies, universities, and retail operations alike.

What the SOP process actually involves 🔗

An SOP is a document that captures routine or repetitive activities so they are performed consistently, regardless of who is on shift. The United States Environmental Protection Agency, whose SOP guidance is widely treated as a reference standard, describes the SOP life cycle as four connected stages: preparation, review, approval, and revision. Skipping or rushing any of these stages weakens the final product.

Think of it less as writing a single document and more as managing a small project. Someone decides a procedure needs to be documented, a knowledgeable person drafts it, others check it, an authority signs off, and the organisation commits to keeping it current. Each stage has its own purpose, and each protects the SOP from a specific kind of failure, whether that is inaccuracy, impracticality, or simply becoming outdated.

Step one: preparing the SOP 🔗

Preparation is the foundation. Get this stage right and the rest of the process becomes far easier.

Deciding which processes need an SOP 🔗

Before anyone writes a word, an organisation has to decide what actually needs documenting. The EPA guidance stresses that an organisation should have a clear procedure for determining which processes or activities require an SOP in the first place. Not every task warrants one. The activities that benefit most are routine, repetitive, and important enough that doing them inconsistently would cause problems. In a store, this typically means things like opening and closing, cash handling and reconciliation, stock receiving, returns processing, and visual merchandising. The University of Utah’s research compliance office similarly begins its SOP process by identifying the need and proposing a clear, descriptive title before drafting starts.

Why subject-matter experts should write SOPs 🔗

Here is the single most important principle of preparation: the people who write SOPs should be those who genuinely understand the activity. These are the subject-matter experts, the individuals who actually perform the work or use the process every day. The EPA guidance is explicit that SOPs should be written by individuals knowledgeable about both the activity and the organisation’s internal structure.

The reason is practical. A manager who has never operated the billing counter during a festival-season rush may write a procedure that looks neat on paper but falls apart in reality. The cashier who handles that counter knows where customers get confused, where the queue backs up, and which step is easy to forget. When that person’s knowledge shapes the SOP, the document becomes accurate and usable rather than theoretical. It also builds ownership: people are far more willing to follow procedures they helped create.

When a team approach works best 🔗

Some processes are simple enough for one expert to document. Others span several roles or departments. For these complex, multi-tasked processes, a team approach is far more effective. The EPA guidance notes that bringing together the experiences of several individuals is critical for multi-tasked processes and that this collaboration also promotes buy-in among the people who will eventually use the SOP.

Consider a store’s end-of-day closing procedure. It might touch the sales floor, the cash office, the security system, and inventory checks. No single employee owns all of those steps. Drafting it as a team, with input from each area, produces a procedure that reflects how the work really flows rather than how one person imagines it.

Step two: reviewing and approving the SOP 🔗

A first draft is never the final word. The review and approval stage exists to confirm that the SOP is accurate, workable, and authorised before anyone is asked to follow it.

Independent review and validation 🔗

Once a draft exists, it must be reviewed and validated by people with appropriate training and experience. The point of review is to catch errors, fill gaps, and confirm that the procedure actually achieves what it is supposed to. Many organisations use a layered approach. One widely cited industry practice describes a three-tiered review: first the subject-matter expert confirms technical accuracy, then management reviews for fit and feasibility, and finally a quality function checks the document against organisational standards.

The reviewer should not simply be the original author re-reading their own work. A fresh, experienced set of eyes is more likely to spot assumptions the writer made without realising it. The University of Utah’s process, for example, circulates the final draft to a review committee and gives members a defined window to submit comments before the document can move forward.

Testing the draft with real users 🔗

One of the most valuable steps, and one that organisations often skip, is testing the draft with people other than the writer. Hand the procedure to someone who was not involved in writing it and ask them to follow it exactly as written. If they can complete the task correctly using only the document, the SOP works. If they stumble, get confused, or have to ask questions, those are the gaps to fix before the SOP goes live.

This kind of real-world testing is exactly what general SOP best-practice guidance recommends, advising that procedures be reviewed and tested in real scenarios with relevant stakeholders before they are approved and implemented. In a retail setting this might mean having a newly hired associate run through a draft opening checklist, since they have no prior habits to fall back on and will rely entirely on what the document says.

Final approval under the Quality Management Plan 🔗

After review and testing, the SOP needs formal sign-off. Approval should follow whatever rules the organisation has set out in its Quality Management Plan, the document that defines who has the authority to approve procedures and how that authority is exercised. This is not a rubber stamp. Approval is the point at which the organisation officially commits to the procedure, which is why it usually rests with a designated manager, quality head, or committee rather than with the author alone.

Recording who authored, reviewed, and approved each SOP also matters. The University of Warwick’s SOP procedure requires every document to carry a cover page documenting exactly this, along with the effective date and the date the next review is due. That audit trail makes accountability clear and helps when questions arise later.

Keeping SOPs current: revisions and periodic reviews 🔗

An approved SOP is not finished forever. Procedures change, products change, regulations change, and a document that no longer matches reality is worse than no document at all, because it teaches people to do the wrong thing confidently.

Updating whenever procedures change 🔗

The first rule of keeping SOPs current is straightforward: update them whenever the underlying procedure changes. If a store adopts a new point-of-sale system, introduces a new returns policy, or reorganises its stockroom, the relevant SOPs should be revised at the same time rather than months later. Treating SOP updates as part of any process change keeps documentation and practice aligned.

Scheduling periodic reviews 🔗

Beyond change-driven updates, SOPs need a systematic, scheduled review even when nothing obvious has changed. The common standard is a review every one to two years. The University of Utah, for instance, conducts a periodic review roughly two years after initial approval and every two years thereafter, while the University of Warwick uses a biennial review cycle and reissues each document with a new version number and effective date even when no changes are needed. Some organisations build the review schedule directly into each SOP, so the document itself states when it is next due for examination.

Fast-moving environments may review more often. Retail operations in particular sometimes revisit procedures quarterly, because seasonal promotions, new merchandise, and changing customer expectations can make a procedure stale quickly. The right interval depends on how dynamic the activity is, but the principle holds: review on a fixed schedule, not just when something breaks.

Archiving obsolete SOPs 🔗

When an SOP is replaced or retired, it should not simply be deleted. Obsolete versions should be archived. Keeping superseded documents preserves a record of how things used to be done, which is valuable for audits, investigations, and understanding past decisions. At the same time, archived SOPs must be clearly separated from current ones so that no one accidentally follows an outdated procedure. Good version control, with clear effective dates and version numbers, is what makes this possible.

Why this matters for retail operations 🔗

In a store, the stakes of the SOP process are immediate and visible. A customer who gets warm, efficient service at one branch and a confused, slow experience at another is unlikely to return. SOPs are what allow a brand to deliver the same experience across every location and every shift. They also shorten training time, reduce billing and inventory errors, and give staff a common reference when something goes wrong. None of those benefits survive if the SOP was written by someone who does not do the work, never tested, or left unrevised for years. The process of preparation, review, approval, and revision is precisely what keeps an SOP trustworthy enough to rely on.

What do you think? If you had to write an SOP for a process you know well, who in your team would you bring in to review and test it before it went live? And looking at the procedures around you, which one is most overdue for a periodic review?

References

1. https://www.epa.gov/quality/guidance-preparing-standard-operating-procedures
2. https://qualitycompliance.research.utah.edu/sop-library/uu-sop-01.php
3. https://blog.montrium.com/experts/5-fundamental-steps-to-creating-powerful-standard-operating-procedures
4. https://www.manwinwin.com/standard-operating-procedure-sop/
5. https://warwick.ac.uk/fac/sci/med/research/ctu/ctuintranet/qa/sop/sop1_preparationreviewapprovalofsops_v4.0_25oct2023.pdf
6. https://www.research.yorkhospitals.nhs.uk/seecmsfile/?id=1290