What it is about
Documented information is the shared term the standards use for everything that is recorded: requirements such as the policy, procedures and work instructions, and evidence such as inspection records, training records or audit reports. This used to be called documents and records, and in everyday work the distinction is still useful.
Clause 7.5 asks for two things. First, the documented information the standard explicitly requires and the documented information the organisation itself considers necessary; how much that is depends on size, activities, complexity and the competence of staff. Second, control: documents are identified, reviewed and approved, available where they are needed, protected, and their changes can be traced. For records, retention and disposal are defined, and documents of external origin, such as standards, customer drawings or data sheets, are included as well.
The aim is not a mountain of paper. A lean system with a few up-to-date documents that everyone can find is stronger in the audit than a 300-page manual nobody opens. What matters is that the valid version is at the workplace and that someone is responsible for every document.
Because documented information touches every other clause, it shows up in every audit. Almost every sample ends at a document or a record, and that is exactly where it becomes clear whether control is working.
What the auditor checks
“Which version of this work instruction applies, and how does the workshop know?”
The classic. Auditors compare the version at the workplace with the one in the register. If there is a printout in the workshop, it must be clear that it is valid, or there must be a way of preventing outdated printouts.
“Who is responsible for this document, and when was it last reviewed?”
Whether every document has a responsible person who keeps it up to date, and whether review dates are kept. The whole clause hinges on this question: a document without an owner goes out of date because nobody feels responsible for it.
“What has changed in this version compared with the previous one?”
Whether changes can be traced, with a change note, approval and date, and whether the people affected have been told about them.
“How long do you keep inspection records, and where would I find one from three years ago?”
Whether retention periods are defined, from law, customer contract or the organisation’s own decision, and whether records remain legible and retrievable during that time.
“How do you handle documents from outside, such as customer drawings or safety data sheets?”
Whether external documents are identified and their revision status is controlled. A customer drawing with an old revision index in production is a common finding.
“Who may see this document, and who may change it?”
Protection against loss, unauthorised access and unintended change. For ISO 27001 this weighs particularly heavily, because documents can themselves be information that needs protecting.
Which evidence convinces
A document register with identifier, version, status, responsible person and next review
It shows at a glance what applies and who looks after it. Whether in software or a well-kept spreadsheet makes no difference; it has to be up to date.
Approval and change history for each document
Who approved what and when, and what changed. This proves control rather than merely claiming it.
The valid version at the workplace
The most convincing evidence is not found in the office but where people work to the document.
Defined retention periods for records
A short overview is enough: which record, how long, where, who disposes of it. It answers a question that would otherwise be asked separately in every area.
Controlled access
Distribution lists or permissions showing who may see and change what, and backups that protect against loss.
Typical nonconformities
Documents out of date or without an owner
The most common nonconformity in this clause, from many audits: a document describes a process that no longer exists in that form, or nobody has been named as the responsible person (owner), and so nobody keeps it up to date either. The two are connected, because whoever owns a document notices when it is no longer right. If it concerns individual documents, that is a minor nonconformity. If hardly any document has an owner or a current status, control is not working, and it becomes a major nonconformity.
Outdated version at the workplace
In the register, version 4 applies; at the machine, version 2 is posted. Usually this is down to printouts that nobody collects when a new version is released.
Approval missing
Documents are changed and used without anyone having reviewed and approved them, or the approval cannot be seen.
External documents not controlled
Standards in an old edition, customer drawings without the current index, safety data sheets older than the manufacturer’s current version.
Records missing or not retrievable
An inspection is supposed to have taken place, but the record is missing, or there is no retention period and records were destroyed too early. What is not recorded is treated in the audit as not having happened.
Differences by standard
ISO 9001ISO 9001
ISO 9001 explicitly requires documented information in many places: as requirements, for example the scope, the quality policy and the quality objectives; as evidence, for example on competence, measuring equipment, design and development, supplier evaluation and release. Records that serve as evidence of conformity must be protected from unintended alteration. In the 2026 edition the German titles of 7.5.2 and 7.5.3 change slightly; in substance nothing significant changes.
ISO 14001ISO 14001
ISO 14001 requires documented information on, among other things, the environmental aspects and their criteria, compliance obligations, environmental objectives, operational control and emergency preparedness to the extent necessary, and the evaluation of compliance. External documents such as permits, conditions imposed by authorities and safety data sheets play a large part here and belong under control.
ISO 27001ISO/IEC 27001
ISO/IEC 27001 requires, among other things, the scope, the policy, the process and results of risk assessment and risk treatment, the Statement of Applicability and the objectives as documented information. In control, protection carries more weight: confidentiality, integrity and availability also apply to the organisation’s own documents, and access here means both reading and changing.
How IMScollect covers it
In IMScollect you control documented information in the document register: every document has an identifier, a type, a confidentiality level, a validity period, a responsible person and the date of the next review. The status shows draft, in review or valid, the history shows every version with its change, and documents that are no longer needed are archived rather than deleted.
Approval is given directly by the responsible person, or approval is requested. When you approve, you can start the acknowledgement at the same time so that the people affected learn about the new version. Ahead of the next review the responsible person gets a task, and the distribution list on the folder decides who can see a document. That way every document has an owner who keeps it up to date.
Frequently asked questions
Do we still need a quality manual?▾
None of the three standards requires one. Many organisations keep a short overview because it makes things easier for newcomers and auditors. More important than a manual is that the required documents exist, are up to date and can be found.
What is the difference between documents and records?▾
Documents set out how work is done and are changed when something changes. Records show what has happened and are no longer changed. The standards use documented information for both, usually with “maintain” for requirements and “retain” for evidence.
Do documents have to be reviewed regularly?▾
The standards do not set a fixed period, but documents must be suitable and up to date. A review date for each document has proved its worth, every one to three years depending on importance, plus a review whenever the process changes.
Are printouts at the workplace enough?▾
Yes, provided it is ensured that only valid versions are there, for example because old versions are collected when a new one is released, or because printouts are only valid on the day they are printed. Access to the valid version on screen is usually simpler.
