Select document-control software by tracing an instruction from ownership and review to its approved revision and the evidence kept after use. Start with the process the document supports. Then assess versioning, access, approval and retention separately, so an organised file library is not mistaken for a complete quality management system.
What information does the process need?
Choose a representative process and ask the people doing it which information they need to act. An operating instruction, an inspection form and a completed inspection record serve different purposes. Record those purposes before deciding how many folders, labels or approval stages the system needs.
ISO’s guidance on ISO 9001:2015 allows flexibility in how an organisation documents its quality management system. The guidance distinguishes a documented quality management system from merely having a system of documents. The ISO guidance on documented information for ISO 9001:2015 is useful precisely because it connects documentation with the effectiveness of the processes it supports.
ISO’s guidance describes documented information as supporting communication, evidence and knowledge sharing. For each proposed document class, write down which of those purposes it serves. A reference note might share knowledge; an authorised procedure might direct work; a completed record might provide evidence of what happened. Do not assume that the same editing and disposal rules should govern all three.
The guidance allows documented information in different forms and media. Choose the medium that works for the process and can be controlled appropriately. A software evaluation should explain how existing paper or other material is represented, referenced or handled, rather than assuming everything becomes a new digital file on the first day.
How should maintained instructions differ from retained records?
The guidance distinguishes information maintained to support processes from records retained as evidence of results. Use that distinction to frame ownership and change rules. Ask who may revise the instruction, who approves a new revision and how the person doing the work recognises the applicable version.
For a hypothetical inspection process, propose an instruction called Test Inspection Procedure and a separate completed sample record. The instruction describes the intended work. The sample record describes what someone entered during the exercise. Keep the sample synthetic while evaluating the system.
Ask what should happen when the procedure changes after a record has been completed. The organisation needs a clear relationship between the retained record and the instruction that applied at the time. Treat that as an acceptance requirement to demonstrate, rather than assuming a document-management product creates it automatically.
Nominate an owner for the classification decisions. A software administrator can configure fields and permissions, but the process owner should recognise why a document is maintained, why a record is retained and what evidence is required to support the decision.
What does version history demonstrate?
Microsoft says enabled list or library versioning can store, track and restore changed items or files. Microsoft version history can show when an item changed and who changed it. The Microsoft versioning guide provides a concrete product example for the software comparison.
Ask the evaluator to show the revision identity, the changed content and the relevant actor in a controlled sample. Then ask which of those facts establishes business approval. A recorded edit and an approval decision are separate things to define and inspect.
Microsoft distinguishes major versions from minor draft versions in libraries. Decide how the product’s version labels relate to your own draft, review and approved states. If a published major version is meant to represent an authorised procedure, identify the actual control that permits publication and the evidence it produces.
Restoring an earlier version makes that restored version the new current version. Include restoration in the proposed approval process. Ask how the owner would explain a deliberate return to earlier content and how the newly current version would be identified to users. Avoid treating a restore action as a way to erase the fact that a change occurred.
Which document-control questions should the evaluation answer?
Use this original revision-chain worksheet for one instruction and one related record. Follow the chain with synthetic content first, and keep the actual observations beside the intended outcomes.
| Step in the chain | Decision to establish | Evidence to request |
|---|---|---|
| Create the instruction | Named owner and intended process | Document identity and ownership record |
| Propose a revision | Who may edit and what requires review | Changed content and reason for the revision |
| Approve use | Who has authority to approve this class | Actual approval evidence and revision identity |
| Make it available | How the user identifies the applicable version | Task-based retrieval exercise |
| Record completed work | What relates the record to the instruction used | Completed synthetic record and revision reference |
| Replace or withdraw | How obsolete instructions are handled | Observed access and identification of the replacement |
| Retain evidence | Which records remain and for how long | Agreed retention decision and configured controls |
Do not fill an evidence cell with the product’s feature description. A description helps identify what to investigate; the assessment needs the configured behaviour and the owner’s decision about whether it meets the requirement.
For the hypothetical inspection, ask a reviewer to find the applicable instruction without being told its folder location. Next, propose a revision and examine how the workflow distinguishes content awaiting review from content authorised for use. Record the assistance needed and any ambiguous labels.
How should retention be checked?
Microsoft warns that earlier versions are deleted when a configured version limit is reached. Ask the organisation to define its required retention before treating a version-history setting as sufficient. The relevant decision may involve business, contractual or other obligations that this software guide does not determine.
Compare the chosen retention rule with what the configured product actually keeps. Include changes to file content, metadata and related approval evidence in the question. If those are stored separately, identify how they remain connected for the period the organisation requires.
Keep deletion and disposal outside a casual demonstration. Use synthetic material in a controlled exercise, document the intended result and obtain the appropriate owner decision before applying retention changes to live records.
What should the selection decision say?
Summarise the assessment in terms of the process: which document classes are covered, how applicable revisions are identified, who approves changes and what retained evidence supports the work. List unresolved gaps with an owner and the evidence needed to close each one.
If the product cannot demonstrate a required link between an instruction and a completed record, describe that specific gap. Avoid substituting a broad “ISO-ready” label for the actual result of the evaluation. The organisation can then decide whether configuration, another tool or a different process is needed.
For the implementation scope, see web development and business email. Discuss your requirements with Spout using a representative document class and the revision-chain worksheet.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.