Drafting & revising documents with AI

Revise is how you write and improve compliance documents with the AI in the loop. You give it a goal — “Draft an access control policy for our cloud setup”, “Add a section on incident response to this procedure” — and it produces the work as a set of staged changes grounded in your project’s context and evidence. Nothing is written to your document library until you approve it, so the AI can do the heavy lifting while you keep the final say.

Starting a revision

A revision can begin in a couple of places:

• From the Revisions area under Documentation, where your recent revisions are also listed.
• From the Act stage of a gap analysis, where Start a revision has an agent act on the findings — drafting a management report, a regulatory plan, or documentation that closes a gap. The agent reads the gap analysis itself before it changes anything.
• From a document: Revise on an open document, or Revise with the agent on documents selected in the Documentation tree. The agent starts with those documents.
• From Chat: ask the assistant to change a document and it hands the request to Revise. The revision opens beside the conversation, and later requests in the same chat continue it. You review and apply there, or open the revision on its own page.

A revision can create new documents or modify existing ones, and a single revision can do both at once.

Manage: Revisions

Reviewing staged changes

A revision opens with the agent’s conversation on one side and the document on the other, its proposed changes marked in place as tracked changes. A Word document is shown as Word renders it, with the tracked changes inside the file itself; any other document is shown with its insertions and deletions marked inline. Each change carries the agent’s reason for proposing it. When a revision covers several documents, you switch between them one at a time. For what else changes when a document is a Word file, see Editing Word documents with AI.

A revision can work on any document in the project, not only Word files. A spreadsheet, PDF or HTML document is edited through its extracted text, so its accepted changes publish as a Markdown document rather than in the original file type. A document the agent drafts from scratch is created as a Word document.

You Accept or Reject each change. When you’re happy, Apply the revision to publish the accepted changes as a new version of each document; Discard throws the staged changes away without touching anything. Because every change passes through this review, an agent can never alter your evidence silently — applying is always a deliberate human step.

To give the agent feedback on a Word document, select a passage and choose Comment on selection; your comments sit in the review’s Comments tab. Ask the agent to address your comments and it reads them, answers in the thread, and makes the edits. It resolves a thread only when you ask it to, and Apply reminds you of any still open.

Going back to an earlier state

Beside the Changes list, the History tab lists every state the document has been in during the revision, newest first. A new state is recorded each time the agent edits the document and each time you accept or reject changes. Each row shows who made the change and when; for an agent edit it also shows the message you sent that led to it.

Restore this state puts the document back exactly as it was at that point: its text and which changes were still pending, accepted or rejected. Undo on the newest row takes back the latest step. A restore is recorded as a state of its own, so you can always restore forward again. You can also use Restore to before this message on a message in the conversation. Restoring is unavailable while the agent is working on the revision.

How drafts stay grounded

Revise doesn’t write in a vacuum. It draws on your project profile and the documents already in the project, so a drafted policy reflects your organisation’s actual context and references the evidence you hold rather than generic boilerplate. The better your profile and evidence, the closer the first draft lands.

Attaching files to the chat

You can also hand Revise material that isn’t in your project yet. Attach a file from the chat composer — or drop it anywhere on the chat panel — and the agent can read it while it works — an auditor’s report you want addressed, a standard you’re mapping against, a draft a colleague sent over. The file can be long; the agent searches it rather than reading it end to end.

Attached files go to the agent only. They are not added to your document library, and they don’t become documents unless you ask Revise to draft one from them. A file takes a moment to process after upload, and sending is held until it’s ready. Click an attachment’s name at any point in the conversation to download the original file back, unchanged.