Document content
Governance → Policy Management → (a document) → Content
A governing document in Vantage can carry its body two ways, and most organisations use both over a document's life:
- A structured body — Markdown, held in English and Arabic, editable in the platform, exportable as a PDF. This is what the AI author writes and what the redline reviewer revises.
- An uploaded file — a PDF or Word document, the artefact your organisation already has. See Versions and files.
The structured body is what makes a document workable: it can be drafted, diffed, revised and translated. The uploaded file is what makes it legal — publication requires one.
English and Arabic
Every document holds both languages. The EN / ع toggle on the Content tab switches the whole body, and the Arabic view renders right-to-left.
The Arabic body is always derived from the English one. When AI drafts a document it writes the English first and then translates it, so the two stay faithful to each other rather than drifting into two documents that say different things. If the translation step fails, the English draft is still saved — you get an untranslated document rather than no document.
Drafting with AI
Draft with AI on an empty document, Regenerate on one that has content.
The author is given the document's title, class, category, description and every framework control the document is mapped to, and asked to write a complete document that addresses all of them, in a fixed structure:
| A policy gets | A procedure gets |
|---|---|
| 1. Purpose | 1. Purpose |
| 2. Scope | 2. Scope |
| 3. Policy Statements | 3. Procedure |
| 4. Roles & Responsibilities | 4. Roles & Responsibilities |
| 5. Compliance & Enforcement | 5. Records & Evidence |
| 6. Review & Maintenance | 6. Review & Maintenance |
Policy statements are directive "shall" requirements citing the control ref-ids they satisfy. Procedure steps are concrete instructions naming who performs them, when, with which systems, and what record they produce — and a procedure is grounded in its parent policy so it operationalises that policy rather than restating it.
Drafting a document with no control mappings is refused: "Map the document to framework controls first." The mappings are the brief. A document drafted against nothing is generic text. Add them on the Mappings tab, then draft.
Regenerate does not overwrite in place. Each draft lands as a new draft version, so an earlier attempt is never lost.
Editing by hand
Edit opens the body in a Markdown editor — one language at a time, switched with the EN / ع toggle. Save writes to the document's latest draft version, creating one if the last version is no longer a draft.
Content is editable only while the document is in draft. Once it has been
submitted for review the body is frozen, and a save is refused with "Document
is not in draft — content can only be edited before review." Changing an
effective document means a new version, which is the point: the
body of a document people have acknowledged must not change under them.
Suggesting a revision (redline)
Suggest revision, below the content, asks the review agent to revise the current body: cover every mapped control, tighten and de-duplicate the language, close gaps and ambiguity, keep the existing section structure.
The result is not applied. It arrives as a policy_redline
proposal rendered as a line-by-line diff of the current body
against the proposed one, with the reviewer's own summary of what changed.
- Accept creates a new draft version carrying the revision, with the change summary as its change reason. The existing version is untouched.
- Reject dismisses it, keeping the record that it was considered.
Accepting a redline does not publish anything. The new version goes through review, approval and publication like any other.
PDF export
PDF renders the English structured body as a formatted PDF, headed with the document's class, category, version, status and effective date. It exports the current version's content, falling back to the latest version.
A document with no structured body cannot be exported — "No content to export. Draft the document first." The PDF is generated from the body, not from an uploaded file; to get the uploaded artefact, use Download.
Every export is recorded in the audit log.
What reaches the AI provider
Drafting, redlining and translation send policy titles and full body text, including unpublished drafts, plus the framework and control text the document is mapped against, to whichever model provider your organisation has configured.
None of it runs until an organisation administrator has turned AI on for the governance module in Settings → AI assistance. A configured API key is the vendor's decision; permission for your material to reach a third-party model is yours. With AI off, every agent action in this module returns a refusal and nothing leaves your network.