Why SharePoint Makes Document Control Hard to Sustain

SharePoint is the default answer when manufacturers ask IT for a document management system. It’s already licensed, it’s familiar, and it stores files. What’s the problem?

ISO 9001 clause 7.5 asks for more than a place to store documents. It requires controlled documents: reviewed and approved to the degree each warrants, kept under change control, and available in the right version to the people who use them. In practice, auditors also expect to see who approved which version before it took effect.

SharePoint stores files well. Control is something you have to build on top of it, and keep working.

Four places SharePoint leaves the work to you

1. Approval is something you set up and maintain. SharePoint’s content approval can hold a new version back from readers until someone with approval rights approves it. Its newer library approvals can send a file to several approvers and require all of them to respond, but Microsoft says they are not integrated with content approval, the setting that holds a draft back from readers. Anything beyond that is usually built in Power Automate, and a flow that runs on one person’s account can stop working when that account is removed.

2. Version history is not a document lifecycle. SharePoint keeps each version. It can require check-out, so only one person edits a file at a time, and a Microsoft Purview retention label that marks a file as a record can stop its contents being changed. But each of those is a setting someone has to apply and keep in place, and none of them gives a revision an effective date.

3. The approval record sits apart from the document. Version history shows who saved each version and when. SharePoint’s library approvals show the latest request on the file, with its approvers and their responses, and Microsoft points to the Teams Approvals app for the full history. When approval runs through a Power Automate flow, the responses are kept with the flow’s approvals, and only what the flow writes back reaches the document.

4. Keeping obsolete files out of use is up to people. When a new revision is saved as a separate file rather than as a new version of the same one, nothing in SharePoint marks the old file as out of date. Keeping it out of use depends on folder discipline and permissions.

SharePoint’s capabilities as Microsoft documented them on 17 October 2026.

What ISO 9001 § 7.5 actually requires

In short: each document has to say clearly what it is and be reviewed and approved to the degree it warrants; the people who need it must be able to get the right version; it has to be kept safe from misuse and tampering; and you manage who can see or change it, how changes to it are controlled, and how long it is kept and what happens to it afterwards.

That’s a control requirement, not just a storage requirement.

ClearVue’s Document Control module was built to support § 7.5 — with enforced approval workflows for documents you create in Document Control, a controlled revision lifecycle, and a record of who approved each revision and when. See how it works