Quality management systems
Senior US-based engineers build the controlled library your quality management system describes: an explicit draft, published and obsolete lifecycle, a named approver who must sign before a revision is issued, a review date that raises its own task, superseded revisions retained rather than overwritten, read-and-acknowledge evidence per person and revision, and a change history you can export when a registrar asks for it — mapped to the documented-information requirements of ISO 9001 clause 7.5. One written scope, one fixed price agreed before work starts, typical delivery in 2–4 weeks with 30 days of hypercare.
Representative dashboard — sample data
What you get
A shared folder with version history is not a controlled document set. These are the specific behaviours an auditor tests for, each configured in the tenant you already own.
Every controlled item carries a document number, title, revision, process owner, approver, effective date and next review date as real columns — so the library itself is the register, and nobody maintains a parallel spreadsheet of what exists.
Content approval plus an approval route per document type means a draft stays a draft until the named approver signs it. The approval is recorded against that revision, so the evidence is a query rather than an inbox search.
Readers see the current published revision and nothing else. Drafts are restricted to authors and approvers, and withdrawn documents are marked obsolete and moved out of the working view instead of being quietly deleted.
A periodic review is a requirement that dies in a calendar reminder. Here the review date is a field, and a scheduled flow raises a task for the owner before it lapses, with an escalation route when it does.
Version limits are set on purpose rather than left at a default, and where a revision must outlive them, a Purview retention or record label blocks its deletion. An auditor asking for the previous issue gets the previous issue.
When a revision is issued, the named audience is asked to confirm they have read it, and each confirmation lands in a list against the person, the revision and the date — the training and awareness evidence people usually reconstruct by memory.
Customer specifications, drawings, codes and supplier documentation are not yours to revise, so they get a separate register recording source, edition and the date the edition was last checked — the gap most commonly found at surveillance.
Approvals, revisions, acknowledgements and disposition decisions come out as files you can hand over, rather than screenshots taken during the audit while the auditor waits for the page to load.
How it works
We take your existing documented information — procedures, work instructions, forms, external specifications — and your own control procedure, and write down what the system has to enforce: numbering, revision scheme, approver per type, review interval, retention, who must acknowledge.
Content types and columns, content approval, the approval routes, draft visibility, the published and obsolete views, the review-date task, version limits and retention labels, the external-origin register, and the acknowledgement capture. Configured in your tenant, against your naming, not a demo.
Controlled documents move in at their current revision with history preserved where it exists. Then we rehearse the requests an auditor actually makes, fix what is slow to answer, train the document owners, and stay on for 30 days of hypercare.
This is a narrow, evidence-driven build: the controlled-document half of a quality management system, implemented in SharePoint and Power Automate, so that the claims in your control procedure are enforced by the platform instead of by discipline. Deliverables are the controlled library with its content types and views, content approval and the approval routes per document type, the draft/published/obsolete lifecycle, review-date automation, version and retention configuration for superseded revisions, the read-and-acknowledge record, the external-origin document register, the migration of your existing controlled set at its current revision, owner documentation and training, and a rehearsed export of the evidence an auditor asks for. Work is performed remotely by senior US-based engineers from our Orange County, CA base, serving every US state, at one fixed price agreed after your free consultation.
It is equally important to say what this is not. We are not a quality consultancy and not a certification body: we do not write your quality manual, we do not decide what your processes should be, and we cannot certify anything. Interpreting the standard against your operation is your quality lead’s job and your registrar’s judgement. What we do is turn the document control clauses you are already committed to into configuration that holds up when someone tests it. ISO 9001:2026 now replaces ISO 9001:2015, with a three-year transition window for existing certificates, and the documented-information requirements in clause 7.5 carry across substantively — which is exactly why this is worth building properly once rather than twice.
Document control is one module of a larger quality system, and it is the one most companies build first. Where nonconformance, CAPA, internal audits or supplier qualification are also on the list, start with our SharePoint quality management system comparison, which weighs a native build against a licensed QMS product, a dedicated eQMS and a custom build before any module is scoped.
Three of our engagements touch this ground and they are bought at different moments. SharePoint intranet and document management consulting is the general build: information architecture, libraries, metadata, migration, an intranet designed rather than accumulated. That is the right purchase when the problem is that files are everywhere. This page is narrower and stricter — it assumes you have a quality system with clauses in it, and it builds the controls that make a specific library auditable.
SharePoint governance consulting services works one level up: tenant-wide policy, the group-based permissions model, who may create a site, lifecycle and sharing rules across the whole estate. It governs everything loosely; this engagement governs one document set tightly, down to who may publish a revision of a specific procedure. Organizations with both problems usually scope governance first and this second, because a controlled library inside an ungoverned tenant is a locked door in an open wall. Once either is live, keeping it healthy is a third job: SharePoint support and maintenance covers the broken flow, the permission drift and the storage warning after go-live.
Two adjacent builds come up constantly in scoping. The approval half of this system is an ordinary Power Automate approval with unusual requirements about evidence, and our guide to building an approval workflow in Power Automate walks the same mechanics for spend and requests. And because the organizations that carry ISO 9001 are so often manufacturers, the document set is usually one of several quality artefacts wanted at once — where the other is nonconformance, scrap and on-time-delivery reporting rather than documents, our Power BI consultant for manufacturing engagement builds that side.
Clause 7.5 of ISO 9001 covers documented information: creating and updating it, and controlling it. In substance it asks that each document be identifiable and described, reviewed and approved for suitability before issue, available where it is needed, protected from unintended alteration, change-controlled, and retained or disposed of deliberately — including documents that originate outside your organization. The table below is how we translate each of those into something a tenant can enforce and an auditor can test. Your written configuration is a filled-in version of it.
| What clause 7.5 asks for | What we configure | What the auditor is shown |
|---|---|---|
| Identification and description of each document | A controlled-document content type carrying document number, title, revision, process owner, approver, effective date and next review date as required columns | A single library view listing every controlled document, its owner and its current revision — the register, generated rather than maintained |
| Review and approval for suitability before issue | Content approval switched on for the library plus an approval route per document type, so publishing is blocked until the named approver responds | For any revision: who approved it, when, and what they were sent — retrieved by filtering, not by searching three mailboxes |
| Availability and suitability at the point of use | One published library as the single source, surfaced in the Teams channel and on the intranet page belonging to the process that uses it | That the document a shop-floor or front-desk user actually opens is the current revision, not a copy someone saved locally |
| Protection from unintended alteration | Read access for the audience, publish rights confined to owner and approver, drafts hidden from readers, and record locking where a revision must be frozen | That a reader cannot edit an issued document, and that a frozen revision refuses the attempt rather than relying on goodwill |
| Control of changes and version control | Major and minor versioning with a change reason captured at publish, and a revision numbering scheme that matches the one your procedure already claims | The change history of any document with the reason for each revision, in the numbering the quality manual uses |
| Retention and disposition of superseded revisions | Version limits chosen deliberately, retention or record labels where a revision must outlive them, and disposition review before anything is destroyed | The superseded issue an auditor names, plus evidence that nothing was disposed of without a recorded decision |
| Documented information of external origin | A separate register library for customer specifications, drawings, codes and supplier documents, recording source, edition and last-checked date | The register, and evidence that the edition in use was confirmed current — the finding that catches the most otherwise-tidy systems |
Two clauses either side of 7.5 are usually in scope by implication and we will say so during scoping rather than after. Acknowledgement evidence exists because competence and awareness have to be demonstrable, and the review-date automation exists because a document that nobody has looked at in four years is hard to defend as suitable. Neither is a document control requirement in itself; both are what auditors reach for when they doubt the document control is real. Acknowledgement is also where this engagement stops and another begins: confirming that a named person read a named revision belongs here, but a course catalogue, curricula assigned by job role, scored knowledge checks and warnings before a certification lapses are a training platform rather than a document library, which is what our SharePoint learning management system engagement builds.
The mechanism is unglamorous. Content approval on the library gives you the gate: SharePoint supports requiring approval of submitted items and restricting who can see drafts, as Microsoft sets out in its guidance on enabling and configuring versioning for a list or library (opens in new tab). The routing sits on top of it: a flow using the Start and wait for an approval action, documented in Microsoft’s approval workflow documentation (opens in new tab), which supports a single approver, first-to-respond, everyone-must-approve, and stages in sequence for the procedures that need a technical reviewer before the quality manager.
What matters for an audit is the by-product. The approval decision, the approver, the timestamp and any comment are written back against the revision, which is the difference between an evidence request that takes thirty seconds and one that takes a morning. Two design notes worth stating because they decide whether the system survives staffing changes: the flow’s connections should be owned by a service account rather than a person who might leave, and every document type needs a named deputy approver, because a controlled set with one approver on vacation is a controlled set that people start bypassing.
This is the part most in-house builds get wrong, because the default behaviour is not the behaviour a quality system needs. A library version limit is a ceiling, not an archive: Microsoft’s documentation on version history limits for document libraries (opens in new tab) states that when versions exceed the limit set on a library, the versions matching the criteria are marked for permanent deletion, bypassing the recycle bin entirely. If the tenth revision of a procedure quietly evicts the first, the control procedure claiming you retain superseded issues is no longer true.
| Mechanism | What it guarantees | What it costs you |
|---|---|---|
| Library version limit (count, or count plus expiration) | A defined number of recent revisions, restorable by an owner without administrative help | Versions trimmed past the limit are permanently deleted without passing through the recycle bin, so the ceiling has to be set against your retention rule, not guessed |
| A retention label that retains the item | The document and its versions survive deletion attempts for the retention period; Microsoft notes that library versioning limits are ignored while an item is under retention | Storage grows with every retained revision, and the label has to be published to the site before anyone can apply it |
| A retention label that marks the revision as a record | Version deletion is blocked outright and a locked record cannot be edited — the strongest form of protection from unintended alteration | Editing requires unlocking, which copies the prior revision into the site’s Preservation Hold library; it needs Purview licensing and a taxonomy somebody maintains |
| Disposition review at the end of retention | Nothing is destroyed until a named reviewer approves it, and the decision itself is recorded as evidence | Reviewers need the disposition role granted deliberately, and the review queue becomes a recurring job on somebody’s desk |
Which combination is right depends on your own retention rule, which is a decision for your quality lead rather than for us. Microsoft’s overviews of retention policies and retention labels (opens in new tab) and of record versioning in SharePoint (opens in new tab) describe the mechanics, including the lock-and-unlock cycle that lets a record be superseded while the previous record version is kept. Where destruction has to be witnessed rather than automatic, Microsoft’s documentation on disposition of content (opens in new tab) covers multi-stage review, reviewer assignment and the optional auto-approval timeout — all of which we configure to match what you have written down, not to a default.
Approvals, revisions and acknowledgements live in your own lists and libraries, so that history is yours for as long as you keep the items. The tenant-level activity record is different, and it is better to hear the constraint from us than from an auditor. Microsoft’s guidance on searching the unified audit log (opens in new tab) states that audit records are retained for 180 days under Audit (Standard), that Entra ID, Exchange and SharePoint activity is retained for one year by default for users with an E5 or equivalent license, and that a single search can span at most 180 days.
The practical consequence is a design rule rather than a problem: anything you must be able to evidence years later belongs in the library and its lists, captured as the work happens, not retrieved later from a tenant log that may have aged out. That is why the acknowledgement record is a list rather than a report, and why approval outcomes are written back onto the revision. We configure the audit log because it is useful for investigating a specific question — who changed that setting, when — not as the system of record for conformity.
The usual fit is an organization of roughly 20 to 500 people already paying for Microsoft 365, holding or pursuing ISO 9001, with a document set that lives in folders, an aging on-premises system, or a document control module nobody enjoys using. Manufacturers, engineering firms, contract producers, medical device suppliers and laboratories all arrive here with the same three triggers: a finding at audit about obsolete documents in circulation, a customer or prime contractor demanding evidence, or a transition deadline that makes the current arrangement untenable.
It fits badly in three cases, and we would rather lose the scope than take it. If your quality system exists only as an intention — no control procedure, no agreed numbering, no named approvers — then configuration will harden decisions nobody has made; write the procedure first, then call us. If your documents are scattered with no structure at all, the general SharePoint build comes first and this is phase two. And if what you need is someone to interpret the standard, run a gap analysis or represent you in front of a registrar, that is a quality consultancy, and we will tell you so in the consultation rather than sell you a library.
The table below sets out scope and timeline. The fixed fee is quoted only after we have seen the document set, because the honest drivers are how many document types you control, how many of them have genuinely different approval routes, whether acknowledgement and external-origin registers are in scope, how much legacy revision history has to be carried across, and whether retention is handled with library limits alone or with Purview labels and disposition review. Our fixed-fee process explains how the number is set and what is locked before work starts.
| Phase | Scope | Typical timeline |
|---|---|---|
| Phase 1 — read and decide | Inventory of your controlled documents and external-origin documents, a read of your own control procedure, and a working session settling numbering, revision scheme, approver and deputy per document type, review intervals, retention and disposition, and who must acknowledge what | About the first week |
| Phase 2 — build and configure | Content types and columns, content approval, approval routes, draft visibility, published and obsolete views, review-date automation with escalation, version limits, retention and record labels, disposition review where required, the external-origin register, and acknowledgement capture | Weeks 2–3 |
| Phase 3 — migrate, rehearse, hand over | Controlled documents migrated at their current revision with history preserved where it exists, obsolete issues filed rather than deleted, a dry run of the evidence requests an audit actually makes, owner training, written configuration documentation, then 30 days of hypercare | Week 4 and close-out |
Everything produced is yours from day one: the library, the flows, the lists, the labels and the written configuration all live in your own Microsoft tenant, never in ours, and the documentation is written so that your document owners can change a review interval or add an approver without calling anybody.
Related services
The general build: information architecture, libraries, metadata and an intranet designed rather than accumulated.
The tenant-wide control layer: permissions model, site provisioning, ownership, lifecycle and external sharing.
Fixed-fee repairs after go-live — permission drift, storage, search, failed flows and offboarding leftovers.
Further reading
Hand-written guides from our article library.
The intake, routing, reminders and write-back that turn an email chase into a queryable decision record.
Which system each kind of document belongs in — settled before a control procedure has to carry the confusion.
What an AI assistant is allowed to repeat back, and why obsolete documents left in circulation become its answers.
FAQ
Four things a normal library does not: a document cannot be published without the named approver signing it, staff see only the published revision, every superseded revision is retained rather than overwritten, and each document carries a review date that raises a task when it passes.
The library, versioning, content approval and approval flows use rights most Microsoft 365 business plans already include. Marking a revision as a record, disposition review and the longer audit retention come from Microsoft Purview, which is licensed separately in most plans. We check your tenant during scoping and say plainly which controls need which license.
No, and we will not claim otherwise. We build and configure the document control system your quality manual describes. Writing the manual, interpreting the standard for your processes and issuing the certificate are jobs for your quality lead and your accredited registrar, not for us.
Version history in the library lasts as long as the limit configured on it, and Microsoft warns that versions trimmed past that limit bypass the recycle bin. Where a revision must survive regardless, a retention label marking it as a record blocks version deletion entirely. We configure both deliberately.
Yes, though SharePoint has no built-in acknowledgement feature, so it is built. A flow asks the named audience to confirm they have read a specific revision, and each confirmation is written to a list with the person, the revision number and the date, which exports for an auditor.
Typical delivery is two to four weeks from kickoff, with the date written into your scope. The fixed fee follows how many document types you control, how many approval routes differ, whether acknowledgement and external-origin documents are in scope, and how much legacy revision history has to be carried in.
Book a free consultation
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.