Have your ISO 27001 policies reviewed before you sign them.

Up to 20 documents per review. Each finding names the clause, quotes your text and, where words can fix it, proposes wording. You decide.

Early access: you turn document review on once. It sends document text through OpenRouter to Fireworks AI in the US, under zero data retention and no training.

What it checks

Gaps between your documents and the standard, each one shown with the passage behind it.

The standard

ISO/IEC 27001:2022, clauses and Annex A. Other frameworks are not reviewed yet.

Your documents

1 to 20 per review: policies, procedures, registers, plans or minutes, uploaded to ISMS Copilot or created there.

Each finding

The clause, a severity (low, medium or high), one sentence on what is wrong, the passage quoted from your document and, where words can fix it, proposed wording.

A second check

An independent check tests every finding before you see it. A review returns up to 10.

What a finding looks like

A review of a fictional company's information security policy: two findings wait for a decision, three are decided.

Information security policy v3, Harbor & Pine

Document reviewISO/IEC 27001:20221 document

Awaiting your decision5 findings, 2 to decide
  1. High severityClause 5.2Gap

    The policy leaves security objectives to an informal yearly conversation, so there is no stated way to set or measure them.

    From your document

    “Security goals are agreed informally between the operations lead and the founders each January.”

    Proposed wording

    Each year the leadership team sets information security objectives that support this policy, makes them measurable where it can, and records them with an owner and a target date in the objectives register.

    AcceptEditRejectExample buttons: in ISMS Copilot you accept, edit or reject each finding.
  2. Medium severityAnnex A 5.15Gap

    Access is granted by whoever owns a folder, with no rule tying it to business need or a regular review.

    From your document

    “Access to shared drives and project folders is given by the person who created the folder.”

    Proposed wording

    Access to information and systems is granted for business need only, approved by the information owner, and reviewed every [review interval]. Access is removed when a role ends.

    AcceptEditRejectExample buttons: in ISMS Copilot you accept, edit or reject each finding.
  3. Medium severityClause 5.2Gap

    The policy is only shared on request, so staff are not told about it and interested parties cannot easily get it.

    Accepted, 21 Nov

  4. Low severityAnnex A 5.1Gap

    The policy sets no planned interval for its own review, only an update when needed.

    Accepted with your wording, 21 Nov

    Your wording: This policy is reviewed every year, after any significant change and before each surveillance audit, and each new version is approved by the founders.

  5. Low severityClause 5.3Gap

    Security is assigned to a team, with no named role answerable for the ISMS or for reporting on it to leadership.

    Rejected, 21 Nov

    Reason kept: Roles are set out in our roles and responsibilities document, which is reviewed separately.

Example review of a fictional company's policy. You decide each finding in ISMS Copilot.

You decide, and it is kept

Your decision

Accept, edit or reject each finding in ISMS Copilot. An edit keeps your wording, and a rejection keeps your reason.

The record

Every finding and decision is kept in your ISMS Copilot account. Paid plans show every past review and export it for your auditor; the free plan shows your latest result.

Your documents

The review never changes them. You decide what goes into the next version.

Run it from Claude or in the app

Start the same review from either side. The decisions always happen in ISMS Copilot.

From Claude

Connect ISMS Copilot to Claude once, then ask for the review in your own words:

Example prompt: Review our information security policy against ISO 27001 with ISMS Copilot

Claude starts the review on the documents you name and reads the findings back to you. You decide each one in ISMS Copilot.

Connect ISMS Copilot to Claude

In our app

  1. Open your company and click Run a review.
  2. Pick up to 20 documents and click Start review.
  3. When the findings are ready, accept, edit or reject each one.

The first time, you turn on document review once: it is in early access.

In ChatGPT, ISMS Copilot answers, drafts and checks your work; starting and reading document reviews from your AI works in Claude today.

What it does not do

  • It does not certify you. It reads your documents against the standard; certification stays with your certification body.
  • It does not read your systems. It reviews only the documents you pick, not your tools or cloud accounts.
  • It does not decide for you. Every finding waits for your accept, edit or reject, and nothing is written back to your documents.
  • It does not invent your values. Where an owner, date or level is missing, the proposed wording leaves a placeholder such as [risk owner].
  • It does not catch everything. Read it as a careful second reader, and keep your own judgement on what it does not raise.
  • It does not run everywhere yet. Not yet for accounts with Advanced Data Protection (EU-only processing) or for team companies.

Plans and more reviews

Free includes one document review. Plus includes 4 reviews a month, Standard 20 and Pro 60, on monthly and yearly billing. If a review fails on our side, it is not counted. Compare plans.

Back to all ISMS reviews, or connect ISMS Copilot to Claude to start this review from your chats. It checks against the ISO 27001 standard. Running several clients? See it for consultants.

Review it before you sign it.

Start with one policy. Each finding names the clause, quotes your text and waits for your decision.