A good SOP folder has one index file and three folders: Current, Drafts and Archive. Only approved procedures live in Current, grouped by the task people are trying to do. Name every file with a stable ID plus a plain task title, such as FIN-003 Process supplier invoices, and track the version inside the document or the platform’s version history instead of in folder names.

SOPs/
├── 00 Start here - SOP index      (ID, title, owner, version, review date, link)
├── 01 Current/                    (approved only; everyone can read)
│   ├── Purchasing and invoices/   e.g. FIN-003 Process supplier invoices
│   ├── Customer onboarding/       e.g. CUS-001 Set up a new client
│   ├── Office and equipment/      e.g. OPS-014 Return company equipment
│   └── People and access/         e.g. HR-002 Grant building access
├── 02 Drafts/                     (owners and editors only)
└── 03 Archive/                    (superseded versions; read-only)

The number prefixes keep the folders in the same order for everyone. Group Current by process, not by department, so a colleague can find a procedure without knowing who owns it; record the owning department in the index instead. Keep it to two levels. If a five-procedure library does not need subfolders yet, skip them and let the index do the work.

The folder holds procedures, not case records. Confidential employee, financial or access records stay in their own restricted systems.

SOP file naming and versioning convention

Part Rule Example
ID Area prefix plus a number; never reused, even after a procedure is retired FIN-003
Title The task in plain words, starting with a verb Process supplier invoices
Version Whole numbers for approved releases, decimals for drafts v2.0 approved, v2.1 draft
Date Year-month-day so files sort in date order 2026-10-03
  • Living document (Google Docs, Word in SharePoint): FIN-003 Process supplier invoices. Leave the version out of the filename and let version history track it, so links never break.
  • Issued PDF or printed copy: FIN-003 Process supplier invoices v2.0 2026-10-03.
  • Never: final, final-new, final-approved-JS.

The whole-number and decimal pattern matches how SharePoint numbers major (published) and minor (draft) versions, so the filename and the library history tell the same story. For what the procedure inside a file like FIN-003 should contain, see the invoice processing SOP outline.

The SOP index

The index is the front door. A shared spreadsheet or a single document works.

Field Purpose
Stable ID Recognizes a procedure even when its title changes
Plain-language task title Matches what a colleague is trying to do
Link to the approved procedure One dependable starting point
Owner and approver Who maintains the instructions and who authorizes them
Version, effective and next review dates Shows which edition applies and when it gets checked
Status and supersedes reference Separates current guidance from a draft or replaced edition

How to create an SOP folder

  1. Create the top-level SOPs folder and the index file.
  2. Add 01 Current, 02 Drafts and 03 Archive. Give everyone read access to Current, limit Drafts to owners and editors, and make Archive read-only.
  3. Inventory existing procedures. Ask each named owner to confirm the current approved copy; do not pick it by modified date alone.
  4. Give each procedure an ID, move it into Current, and add a row to the index.
  5. Move older editions to Archive with a note pointing to the replacement. Keep them for as long as your retention rules require; tidying a folder is not a reason to delete records.
  6. Test the result as a regular reader: can a colleague find the purchasing procedure, see that it is current, identify its owner and open the form it needs, without help?

Repeat that access test when someone changes role or a procedure moves.

Setting it up in SharePoint or Google Drive

In SharePoint, versioning, draft visibility and content approval are library settings. Microsoft’s versioning explanation describes major and minor versions, and its configuration guide shows where to switch them on. Naming a folder “Approved” does not create any of those controls.

In Google Drive, Docs, Sheets and Slides keep a version history that editors can view and restore. When the same procedure should be found from several folders, use a shortcut instead of a copy. A shortcut points to the original and does not grant access to it, so check permissions as an intended reader, not as the owner.

When a shared drive stops being enough

Folders are easy to understand but awkward when one procedure belongs to several processes. Use the index, metadata or shortcuts for extra routes rather than editable copies. If you cannot reliably control approval, access, review ownership or current-version discovery with the tools you have, a different folder tree will not fix it; that is the point to look at dedicated SOP or document-control software. For deciding how many procedures the library needs and who owns each one, see building an SOP library.

Frequently Asked Questions

Should SOPs be organized by department or by process?

Choose the route readers understand. Process folders with department ownership in the index often help cross-team work; a small single-team library may need no subfolders at all.

Do version numbers belong in folder names or file names?

Neither, for a living document: use the platform’s version history and keep the filename stable. Add a version number and date only to separately issued PDFs or printed copies.

What belongs in an archive folder?

Superseded editions retained under your organization’s rules, clearly marked as replaced and pointing to the current version. Archiving is not approval to delete records.

Sources

This guide is desk research based on the vendor documentation below, not hands-on testing.