What evidence do auditors commonly ask for on 7.5.1 Documented information: general?

A list of documented information required by the standard (scope, policy, risk methodology, SoA, treatment plan, objectives, competence evidence, audit and review results and others) with its location; A list of additional documents the organization considers necessary; Evidence each required item exists and is current; Rationale for the level of documentation chosen.

What is the most common gap auditors find on 7.5.1?

One or more mandatory documents are missing, often the risk treatment results or competence evidence

ISO/IEC 27001:2022 · Clause 7

`7.5.1` Documented information: general

The ISMS has to include both the documented information this standard requires and whatever further documented information the organization judges it needs for an effective ISMS. The note says the amount can vary with the size and type of organization, the complexity of processes and how they interact, and the competence of people.

Source: ISO/IEC 27001:2022, 7.5.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Evidence each required item exists and is current · Document repository

governing documentDocuments that govern the control

A list of documented information required by the standard (scope, policy, risk methodology, SoA, treatment plan, objectives, competence evidence, audit and review results and others) with its location · HR system / LMS
A list of additional documents the organization considers necessary · Document repository
Rationale for the level of documentation chosen · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

One or more mandatory documents are missing, often the risk treatment results or competence evidence
Excessive documentation nobody uses
Documents are scattered with no overview
Required retained records are not kept

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

7.4 Communication · 7.5.2 Documented information: creating and updating