# SOP version not current: how to find and keep the right one

> For the full documentation index, see https://250highstreet.com/llms.txt

> Why nobody knows which version of a standard operating procedure is current, and a simple way to keep one approved copy, an owner and a review date.

Short answer: nobody knows which SOP is current because copies live in many places. Keep one approved copy of each SOP in one library. Give each SOP an owner, a review date and a status. Retire every other copy on purpose. Then add a short register list so anyone can see what is approved, what is due for review and who to ask.

## Why this happens

A standard operating procedure, or SOP, is a written set of steps for a task. It starts life as one file. Then someone saves a copy to their desktop. Someone else prints it and writes notes on it. A third person emails it to a new hire. A year later there are five copies and each one is a little different.

The cause is rarely carelessness. It is usually one of these:

- There is no single place that counts as the official one.
- Nobody owns the document, so nobody updates it.
- Updates are saved as new files, such as "SOP v2 final", instead of changing the one file.
- Old copies are never removed, so they keep showing up in search and in email.
- There is no review date, so a document is never checked after it is first written.

## Signs this is happening in your team

- Two people do the same task two different ways, and both say they follow the SOP.
- A new hire asks which file to use, and you have to think about it.
- You find a printed SOP on a wall that is older than the file on the server.
- An audit or customer asks for the current version and it takes a day to answer.
- Files have names like "final", "final2" and "use this one".

## Step 1. Pick one controlled place

Choose one place where official SOPs live. A SharePoint document library works well because it can keep a version history and can ask for approval before a change goes out. Tell the team in plain words: "If it is not in this library, it is not the official SOP."

One way to start: make one library called "SOPs" and move your ten most used procedures into it first. Do not try to move everything on day one.

## Step 2. Keep one file, not many

When a procedure changes, change the same file. Do not save a new file with a new name. SharePoint keeps the earlier versions for you.

Microsoft says a document library can create versions using either major versions only, or major and minor versions. You can also limit how many versions and drafts are kept. If someone saves a bad change, you can open Version history, choose an earlier version and select Restore. Microsoft says restoring adds the old version as a new version.

One way to start: use major versions only at first. It is the simplest rule: each saved change is a new numbered version of the same file.

## Step 3. Add an approval step

A draft and an approved SOP should not look the same. SharePoint can require approval of items. Microsoft says only people with Full Control or Design permissions can change these settings. A new item stays Pending until someone with the right permission approves it. Once approved, it is visible to anyone who can view the library. Microsoft also says you can choose who sees draft items: users who can read items, only users who can edit items, or only users who can approve items plus the item author.

Two cautions from the same page. When you turn approval on, items that are already in the library are marked Approved automatically, so review them first. And if your site lets every user read all items, people with Read permission can see Pending items too.

One way to start: choose the "only approvers and the author" setting for drafts. Then staff only see the approved copy and cannot follow a draft by mistake.

## Step 4. Give every SOP an owner and a review date

A library holds files. A register tells you about them. A register is a simple SharePoint list with one row for each SOP. One way to start is with these columns:

- SOP name
- Link to the file
- Owner (one person, not a team)
- Status (Draft, Approved, Retired)
- Approved date
- Next review date
- Where it applies (team or site)

Set the next review date when you approve the SOP. Many teams pick 12 months. That is a choice, not a rule. Pick a gap that fits how fast your work changes.

With the register you can sort by review date and see which SOPs are overdue. You can also filter by owner and see who has too many. For help picking between a list and a spreadsheet for this, see "[Replace a spreadsheet tracker with a SharePoint list](/guides/replace-spreadsheet-with-sharepoint-list/)".

## Step 5. Retire old copies on purpose

This is the step teams skip. Once the approved SOP is in the library, deal with every other copy:

1.  Search shared drives, email attachments and team chats for the SOP name.
2.  Delete or archive each old copy, or replace it with a link to the official one.
3.  Replace printed copies with a printout that shows the version, the approved date and the link.
4.  Tell the team on one day that the old copies are retired.
5.  Mark the old entry in the register as Retired, with the date.

Do not keep an old copy "just in case". The version history in the library already holds the earlier versions.

## Step 6. Put the version on the page

Put a small block at the top of every SOP: owner, version, approved date, next review date. Anyone who has a printed or downloaded copy can then see how old it is and check it against the register.

## Step 7. Run a short review each month

Open the register and sort by next review date. For each SOP that is due, the owner says one of three things: still correct, needs a change, or retire it. This takes a few minutes if you do it every month. It takes hours if you do it once every few years.

## Make links, not copies

When you share an SOP, share the link to the library file. Do not attach the file. A link always opens the current approved version. An attachment is a copy from the moment it is sent. For the same reason, link to the SOP from your training notes and checklists. See "[New hire onboarding checklist scattered](/guides/new-hire-onboarding-checklist-scattered/)" for how to keep those in one place.

## Honest limits

A library does not make people read the SOP. It makes the right one easy to find. People will still use old habits if the old copies stay around, so Step 5 matters most. Approval also adds a small delay to every change. For urgent fixes, agree in advance who can approve quickly. Start with one team and ten SOPs, fix what does not work, and then expand.

## When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: \$5,000 for one, built in 2 weeks. See "[What a SharePoint tracker costs](/guides/what-a-sharepoint-tracker-costs/)". Bring one example of the problem to a free call.

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: [Tools I built](/portfolio/)

## FAQ

### Do I need a special tool for SOPs?

Not to start. A SharePoint library for the files and a SharePoint list for the register cover the basics: one place, one owner, one status and one review date.

### Can I get back an older version of an SOP?

Yes, if versioning is on. Microsoft says you open Version history, choose an earlier version and select Restore. The restored version is added as a new version, so nothing is lost.

### How often should an SOP be reviewed?

There is no single right answer. One way to start is every 12 months, and sooner after any incident or change in the process. Put the date in the register so it is not left to memory.

### What do I do with printed copies?

Replace them with a printout that shows the version, the approved date and where the official file lives. Remove the older ones when you do.

### Who should own an SOP?

The person who does the task or leads the people who do it. Pick one name, not a group. If that person leaves, the register shows which SOPs need a new owner.

## Sources

- [Microsoft Support, Enable and configure versioning for a list or library](https://support.microsoft.com/en-us/sharepoint/lists/documents-and-library/enable-and-configure-versioning-for-a-list-or-library)
- [Microsoft Support, Require approval of items in a list or library](https://support.microsoft.com/en-us/sharepoint/lists/documents-and-library/require-approval-of-items-in-a-list-or-library)

## Related guides

- [Nobody knows which drawing revision is current](/guides/drawing-revision-register-sharepoint/)
- [SharePoint list version history is blank or missing](/guides/sharepoint-list-version-history-not-showing/)
- [Restore an older version of an Excel file online](/guides/excel-online-version-history/)

Source: https://250highstreet.com/guides/sop-version-not-current/