Skip to content

Generated Documents

Generated Documents turns the control data you already maintain — scope, implementation status, owners, maturity, evidence, risks — into the documents an auditor asks for. A Statement of Applicability, a Risk Treatment Plan, domain policies and procedures.

The point is not the first draft. Any tool can produce a first draft. The point is the second one: you edit a generated document, your control data moves on, you regenerate, and your edits are still there.

Open it from Documents → Generated Documents in the sidebar.

Documents come in two families, and the difference matters for more than technical reasons.

These are rendered directly from your control data. No language model is involved, the output is deterministic, and the same inputs always produce the same document.

DocumentWhat it contains
Statement of ApplicabilityIn-scope controls with implementation status, owner, maturity level and justification, grouped by domain
Control Status ReportImplementation progress across every scoped control, with per-domain completion rates and an exceptions list
Risk Treatment PlanIdentified risks with inherent and residual scores, treatment decisions, owners and due dates
Evidence ScheduleEvidence artefacts your scoped controls require, with collection method, owner, frequency and current tracking state
Maturity Assessment ReportCapability maturity distribution by domain, the gap to target, and the controls holding each domain back
Governance Oversight ReportThe figures a board needs to exercise due care, with the red flags. See below

In the generator list these appear under Reports and Registers.

These ask a language model to write prose from your control descriptions and assessment objectives. What each document covers depends on your organisation’s document structure.

DocumentWhat it contains
PolicyFormal security policy, written from the domain principles, control descriptions and assessment objectives
ProcedureStep-by-step operational procedure, with responsibilities, triggers and records
StandardTechnical standard specifying the mandatory configuration and control parameters

Thirty-four policies of two pages each suit a large organisation with an owner per domain. They don’t suit a team of fifteen. An administrator chooses the structure in Org Settings → Document Generation → Document structure:

StructurePoliciesStandardsProceduresSuits
GranularOne per SCF domainOne per domainOne per domain250+ staff
Consolidated13 policy areas, such as Access Control or Supplier & Third-Party SecurityOne per policy areaSix operational topics50–249 staff
CompactSix policy areas, each with a Requirements section per domainBuilt into the policiesSix operational topics10–49 staff
EssentialsOne Information Security Policy ManualBuilt into the manualSix operational topicsFewer than 10 staff

The six procedure topics are Joiners, Movers & Leavers; Incident Response; Backup & Restore; Change Management; Vulnerability & Patch Management; and Supplier Onboarding & Review. Auditors usually sample procedures by activity, so these follow activities rather than SCF domains.

A policy that covers several domains is written one domain at a time, with a chapter per domain under Policy Statements. Your edits are kept per chapter, and when one domain’s controls change, only that chapter and the document’s framing sections are rewritten.

Under a bundled structure, “where is IAC-21 written down?” has no obvious answer from the library. Open Generated Documents and switch from Library to Document map.

  • The top of the map names your current structure, how many in-scope controls and domains it covers, and how many documents it produces, with a link to change it in Org Settings.
  • Find a control takes a control ID, part of a control name, or a domain name. Each matching control lists the policy, standard and procedure it lands in, with each document’s status. Select a generated document to open it; one you have not generated yet says Not generated yet.
  • Without a search, the map lists every policy, standard and procedure your structure produces, with the domains it draws on, its control count and its status.

The six procedure topics cover named control families, not every control. The map says how many in-scope controls have no procedure under your structure, and a search tells you whether a particular control is one of them. Controls outside your scope appear in no document.

Changing the structure deletes nothing. Documents produced under the previous structure stay in your library under Superseded by a change of document structure, readable and exportable, so an approved policy set is never lost. They can’t be regenerated unless you switch back.

If the change would supersede policies, standards or procedures you already have, Org Settings asks you to confirm first and says how many, and how many of them are approved or published. The new structure starts with none of its documents generated or approved. A superseded document carries a red Superseded label in the library, and when you open it a banner at the top says it is no longer current.

These are built from your ISMS Profile and the platform’s registers, with no language model, and are covered by the first switch only. Anything you have not recorded is shown as to be completed rather than written for you.

DocumentClauseBuilt from
ISMS Scope Statement4.3ISMS Profile scope, Systems Registry, Vendor Inventory, scoped frameworks
Context of the Organisation4.1, 4.2ISMS Profile issues and interested parties
Roles, Responsibilities and Authorities5.3Control owners, mapped to ISMS functions
Risk Assessment and Treatment Methodology6.1.2, 6.1.3Your risk thresholds and acceptance settings
Information Security Objectives6.2ISMS Profile objectives
Communication Plan7.4ISMS Profile communication plan
Document and Record Control Procedure7.5The document lifecycle, with a register of your generated documents
Risk Assessment Report8.2Risk register
Internal Audit Programme9.2ISMS Profile audit programme, with clause and domain coverage
Management Review9.3Inputs prefilled from the platform; decisions left for the meeting
Nonconformity and Corrective Action Register10.2Deficiencies (POA&M), open and closed
ISMS Manual4–10A chapter per clause with the registers as appendices; suits smaller organisations
Asset Inventory, Supplier Register—Systems Registry, Vendor Inventory
Legal, Regulatory and Contractual Requirements Register—Scoped frameworks and external interested parties
Incident Response Plan, Business Continuity Plan—Scoped IRO and BCD controls, systems, suppliers, communication plan

The top-level Information Security Policy (clause 5.2) is written by a language model from your ISMS Profile and policy set, so it sits behind the AI-augmented switch. Its prompt tells the model to write [To be completed] for any scope fact or objective you have not recorded.

ISO/IEC 27001 asks for documents that only your organisation can write: where the ISMS starts and stops, the issues and interested parties that shape it, its objectives, what it communicates and how it is audited. Documents → ISMS Profile holds those facts in six sections, each tied to its clause:

SectionClauseHolds
Scope4.3The organisation, boundaries, locations, products and services, interfaces and exclusions
Context4.1Internal and external issues, including whether climate change is relevant
Interested parties4.2Who has a stake, what they require, and how the ISMS addresses it
Objectives6.2What will be done, the measure and target, owner, resources, due date and evaluation
Communication7.4What, when, with whom, who communicates and how
Audit programme9.2Planned internal audits, their criteria, auditor, status and findings

Each section saves on its own and every save is recorded in the audit log. Interested parties and Communication offer common starter rows to edit. These are fixed examples, not AI output, and nothing is saved until you save the section. The clause documents are written from these registers, and anything left empty appears in them as to be completed rather than being made up.

  1. Open Documents → Generated Documents.
  2. Pick the documents you want. Policies, procedures and standards expand into a picker of domains, policy areas or procedure topics, depending on your document structure, each showing how many scoped controls it has. Only those with controls in scope are listed.
  3. Select Generate.

Generation runs in the background. Its progress shows in a card at the top of the library, so you can close the generate panel and keep working. The card shows:

  • one segment per document, coloured as each finishes;
  • the document being written now and its stage — check, load data, write, merge your edits, save;
  • the time elapsed and a rough estimate of the time left;
  • a row per document with its outcome: created, updated, unchanged or refused. Select a finished document to open it.

When the run ends, the card stays until you dismiss it. It tells you if any sections need your decision, if a document cites controls outside your scope, or if the run stopped at its time limit, in which case running it again finishes the rest.

One run at a time per organisation: if a colleague starts a run while yours is going, theirs waits rather than racing yours.

Why a document sometimes says “skipped”

Section titled “Why a document sometimes says “skipped””

Before generating, the platform fingerprints the inputs — the control data in scope, the template, the prompt, and your catalogue version. If nothing has changed since the last run, the document is left alone and reported as skipped.

That is the intended behaviour, not a failure. It means:

  • regenerating everything weekly costs nothing when nothing has moved;
  • an AI-augmented document is not rewritten (and not charged for) just because you pressed the button;
  • a document that does regenerate did so because something real changed, and the run tells you what — “4 controls changed”, “catalog 2025.2 to 2025.3”, “template updated”.

If you want to force a rewrite anyway — you have changed a prompt, or you simply want a fresh take — tick Force regeneration before generating.

Open any document to edit it section by section. The outline on the left lists every section with its current status; the editor on the right holds the Markdown.

Edits are saved per section. You are always editing the merged document — the thing your organisation actually publishes.

What happens to your edits when you regenerate

Section titled “What happens to your edits when you regenerate”

This is the part worth understanding properly, because it is the reason the feature exists.

The platform keeps every document as three layers:

LayerWhat it is
GeneratedThe most recent machine output. Never edited, only replaced.
HumanYour edits, held per section, independent of the generated layer.
MergedThe operative document — what you read, export and publish.

When you regenerate, each section is compared across both layers and given a status:

StatusWhat happenedWhat you get
UnchangedNeither layer movedNothing to do
UpdatedThe generated text changed; you had not edited this sectionThe new text
PreservedYou edited it; the generated text did not changeYour text, untouched
ConflictYou edited it and the generated text changedYour text. The machine’s alternative is kept in the version history for you to compare against
NewThe generator produced a section that did not exist beforeThe new section, flagged so you notice it
RetiringYour data no longer supports a section you haveThe section stays, flagged. Nothing is deleted for you

Two of those deserve emphasis.

On a conflict, your text wins. The generated alternative is not lost — it sits in the document’s history and the conflict is flagged in the outline so you can compare and decide — but the operative document never silently reverts to machine output over something a person wrote.

Nothing is ever deleted. If you de-scope a set of controls and a section no longer has data behind it, that section is marked Retiring, not removed. Deciding whether documentation should disappear is your call, not a side effect of a scoping change.

Documents move through four states:

Draft → In review → Approved → Published
TransitionWho can do it
Submit for reviewEditors and above
ApproveAdministrators
PublishAdministrators
Send back to draftEditors and above

Every transition is recorded — who, when, from what to what, and any reason you gave — and that record cannot be edited or removed. When an auditor asks who approved a policy and when, the document answers.

The approved SoA as your Living Control Set

Section titled “The approved SoA as your Living Control Set”

When you run an engagement on the SCRMS Prioritized Implementation Guide (PIG), your approved Statement of Applicability stands as the Living Control Set (LCS) revision: the control set your organisation has signed off. There is no separate LCS record to create. Approving the SoA is the act that pins the revision.

Supports PIG steps 1e, 2a and 30.

  1. Open Generated Documents and generate the Statement of Applicability.
  2. Review it, then submit it for review.
  3. An administrator approves it.

What you’ll see: the SoA’s status reads Approved. Its history records who approved it and when, and the approval is in the audit log. A journey stage with a documents_approved check using "generator": "soa" now reads Met. See Journey.

Who can do it: editors generate and submit the SoA; only administrators approve it.

What reopens it: editing an approved SoA, or regenerating it with changed inputs, sends it back to In Review. The journey check returns to Not met until an administrator approves it again. After you change your scope, regenerate the SoA and approve it again so that the pinned revision matches the controls you actually run.

The Governance Oversight Report gives a board the figures it needs to oversee the control programme. Generate it before each board review. Approving it is how the platform records that the board has reviewed it.

Supports PIG steps 2c, 27, 28 and 30.

It is a data-driven document, listed under Reports and Registers. You can also reach it from the Dashboard: How it has changed → Open Generated Documents.

The report has six sections. The first four each end with the question the board should answer:

SectionWhat it shows
1. Implementation and Known DeficienciesControls in scope and implemented, material controls, open deficiencies (material, past due, without a due date, without an owner), and each open material deficiency
2. Change in the Risk ProfileToday’s figures against the posture snapshot from three or more months ago; risk acceptance; risks by treatment status; suppliers
3. Validation: What Failed and What Was CorrectedControls validated within their cadence, overdue, never validated or with no cadence; deficiencies raised and closed in the last 90 days
4. Obligations in ScopeEach scoped framework with its basis (MCR or DSR), and controls by basis
5. Red FlagsPatterns a board should question, such as every control green with no documented exceptions, or accepted risks past their expiry
6. Review RecordA note that approving the document records the board’s review
  1. Open Generated Documents.
  2. Under Reports and Registers, tick Governance Oversight Report, then select Generate.
  3. Share the report with the board, then submit it for review.
  4. After the board has reviewed it, an administrator approves it.

What you’ll see: the report’s status reads Approved, and its history records the approver and the date. That approval is the review record.

Who can do it: editors generate and submit it; only administrators approve it.

If no snapshot from three or more months ago exists yet, section 2 says so and shows today’s figures alone. Snapshots are taken monthly; see Dashboard Overview.

Export any document as Markdown, HTML, or PDF from the document view.

Every exported document carries an attribution footer for the Secure Controls Framework. That is a licence requirement, it applies to all documents regardless of type, and it is not optional — but the wording differs depending on whether the document is derivative.

Generated documents are not evidence of themselves. A policy this feature produced is marked as platform-generated. It is a real document and you can treat it as one, but be deliberate about using a document the platform wrote as the evidence that a control the platform tracks is implemented.

Regeneration is safe to run often. Fingerprinting means an unchanged document is not rewritten, so a scheduled weekly run costs nothing and tells you exactly which documents your control data has outgrown.

A catalogue upgrade marks documents stale, it does not rewrite them. When your organisation moves to a new SCF catalogue version, existing documents are flagged as generated against the old one. Nothing regenerates until you ask it to. See Catalog Updates.