Prepare ISO 27001 documentation drafts from your scope and files

An AI ISO 27001 compliance generator drafts the ISO 27001 documentation set — Statement of Applicability sections, Annex A control narratives, and risk treatment notes — from your ISMS scope notes and reference files, and keeps unconfirmed facts visible as open items instead of smoothing them into final-sounding prose. Gixo drafts those artifacts and exports them as PDF, DOCX, HTML, and TXT for legal, audit, or management review. It does not monitor controls, collect evidence automatically, or grant certification: that decision rests with an accredited certification body after an audit.

Lex · real output

Read the matter facts and the resulting draft together.

This is a real Lex export for invented parties. Inspect the input and clauses as a worked example, with professional review kept separate from automated drafting and checks.

Mutual Non-Disclosure Agreement (worked example)

A mutual non-disclosure agreement of 14 numbered clauses between two invented parties: definitions, what counts as confidential information, exclusions, the receiving party's obligations, permitted disclosures, return of materials, remedies, term, survival, governing law, notices and signature blocks. Its first page says it is a worked example, not a legal document.

Inspect the source brief or data

Draft a Mutual Non-Disclosure Agreement between Larkfield Analytics Ltd (Party A) and Fenwick & Dale Stores Ltd (Party B). Governing law: England and Wales. Effective date: 2027-01-15. Term: Two years from the effective date. Confidentiality: Three years after disclosure. A mutual agreement: each party may disclose and receive confidential information. State on the first page that the parties, people and addresses in this agreement are invented and that it is a worked example, not a legal document. The notice email address of Larkfield Analytics Ltd is notices@larkfield-analytics.example and of Fenwick & Dale Stores Ltd is notices@fenwick-dale.example (both invented).

Open PDF ↗Open Word ↗

Read the sample review notes

Read mechanically against the intake, not by a lawyer: all 12 facts the intake gave are in the draft, nothing is left as a placeholder, and it states no term the intake did not give.

Make the intake specific

Supply the parties, document kind, jurisdiction, obligations, dates and reference material. Review imported content and retain its source identity before using it in a new matter.

Inspect clauses and changes

Use the legal workspace's permitted structural tools, Draft Checks and review paths. Compare proposed changes with the saved draft and original material; unsupported Word edits must be handled explicitly.

Approve the exact version

Have qualified counsel review enforceability, local requirements and the actual commercial intent. Check the current approval state and the downloaded document after a change.

Structured clause proposals and permitted changes

Select the target clause and give Ask Lex a bounded instruction. Missing facts remain visible for review. Inspect the before-and-after proposal, required clause checks and any explicit outside-matrix or mandatory-clause override before versioned application. Use the legal workspace's structural allowlist rather than assuming every general content-editor block is available.

Playbooks, source evidence and obligations

Inspect immutable playbook versions, anchored findings, provenance and precedent variants before staging a change. Matters retain original sources, quotation findings and source-version comparisons. Review extracted obligations for timing, ownership and source revision; negotiation turns and agreement-pack review cells have their own decisions and current-version requirements.

Original Word, redlines and the delivery receipt

Original-format Word export, tracked changes against an original and saved-version redlines are separate paths. Unsupported edits must be surfaced rather than silently claimed as preserved. Inspect the layout, validator notes and downloaded file, then retain its delivery receipt. Counsel's review applies to the actual matter and version.

AI contract review, key terms and review of every document

Every contract in Lex, drafted or imported, gets an AI contract review: each clause the document type expects marked present, weak or absent; up to 25 risks with a level, the party each falls on, why it matters and replacement wording; and provisions that cannot both be followed. Every quotation is checked against the contract text, findings are decided before approval, and there is no single risk score. The same review reads the key terms and obligations with the words they quote and proposes them into the Agreement Pack. Review every document puts up to 25 documents of an Agreement Pack, or up to 200 in a matter, into one table with your own questions as columns and an Excel export. Approvers can be named in order, and signing supports up to 10 signers with an optional signing order and automatic reminders; it is a simple electronic signature, not a qualified one. A qualified reviewer still decides what the contract says.

Lex does not provide legal advice or certify compliance. The public specimen is not a universally reusable legal template. Word fidelity depends on the supported original-document and saved-version path; unrestricted Power Edit and image insertion are not legal editing features.

ISO 27001 artifact drafts, not certification promises

Prepare compliance drafts designed to surface missing facts as review items. Reviewers still verify every fact and conclusion before action.

How it works: drafting an ISO 27001 Statement of Applicability

How should teams evaluate ISO 27001 documentation work?

Use your actual ISMS scope and a safe source pack to evaluate drafting quality. Keep document preparation, operational monitoring, and certification decisions as separate responsibilities.

ISO 27001 documentation drafting vs. compliance automation platforms vs. manual docs

Three different jobs. Gixo drafts the ISO 27001 documentation itself — Statement of Applicability sections, control narratives, and treatment notes — from your ISMS scope notes and reference files, and keeps open items visible in the document, exporting as PDF, DOCX, HTML, and TXT. A compliance automation platform typically ships a built-in Annex A control library, holds platform data and workflows, and runs always-on monitoring; the document work is usually indirect. Manual docs start from a blank file. None of the three grants certification: that decision rests with an accredited certification body after an audit. Category descriptions are as of mid-2026, not vendor quotes; confirm current capabilities with each product.

The other columns describe what each kind of tool is generally for, not a test of a named product, and products differ. Run the same brief and reference files through anything on your shortlist, then compare the draft, the review trail and the export.

Frequently asked questions