DPO Radio

A governance document has to carry the clauses the underlying framework requires. That holds whether it is an acceptable use policy, an access control policy, a business continuity policy, a change management policy, a data classification policy, an incident response policy, a retention policy, or a vendor management policy. Missing a required clause is the kind of audit finding that takes weeks of remediation work.
The policy gap detection workflow runs against a governance document, compares clause-by-clause against the required-clause registry per policy type, and surfaces missing clauses with suggested wording. The compliance specialist reviews per gap and applies through the standard document editor.
The workflow runs against the document record. The policy type drives the required-clause registry lookup.
Acceptable use, access control, business continuity, change management, data classification, incident response, retention, and vendor management. Each carries its own required-clause registry.
The workflow compares the document against the required-clause registry per policy type. Missing clauses surface with the citation to the framework requirement.
Where Forseti can suggest the missing clause wording (drawn from the organisation's clause library or framework templates), the suggestion ships with the gap.
The compliance specialist reviews per gap, accepts the suggestion or proposes alternative wording.
Accepted suggestions apply through the standard document editor with operator confirmation per edit.
Standard workflow audit shape.



Each missing-clause citation grounds against the framework requirement. Suggested wording draws from the organisation's clause library or framework templates.

The workflow does not auto-apply. The compliance specialist accepts per gap; the application is an operator action.

The audit trail walks each gap from detection through operator decision and document edit.
| Framework | How Policy Gap Detection Supports It |
|---|---|
| ISO 27001 | Checks governance documents against ISO 27001-relevant required clauses. |
| SOC 2 | Checks governance documents against SOC 2-relevant required clauses. |

Use gap detection on a governance document. Policy workflows additionally prepare new drafts and compare approved text with recorded practice. See Policy Workflows.
Ready to see a governance document walked against the required-clause registry with suggested wording per gap? Request a personalised demo.


Run policy gap detection across your governance document set for one quarter.

Talk to our team about how the workflow fits your policy refresh cadence.
Acceptable use, access control, business continuity, change management, data classification, incident response, retention, and vendor management. Each carries its own required-clause registry, and a document is checked against the registry for its own declared type.
No. The compliance specialist accepts per gap. Application runs through the standard document editor with operator confirmation per edit.
Yes. The registry is organisation-scoped. The compliance team curates the registry; the workflow compares against the current curated state.
The compliance specialist proposes alternative wording or revises the suggestion before applying. The audit trail records the alternative.
Yes. Each run sends requests to the AI provider your organisation has configured, and your provider bills your organisation for them directly. A run is never refused because a Forseti allowance ran out, and the Usage page reports what each feature consumed.