How do I keep an audit record of human review for AI-written docs?

Short answer

Record who reviewed which version, what they said, what changed, and who approved it, in a log that nobody can quietly edit. DraftView keeps an append-only sign-off record, exports it as sealed JSON you can verify later, and can commit a Markdown review record into your repository.

What the record should answer

An auditor or a customer usually wants a few plain facts.

  • Which document and which version was reviewed.
  • Which people reviewed it, and in what role.
  • What they commented on and what they changed.
  • Who made the final decision, and when.
  • Whether anyone approved their own edit.

What DraftView records

For pull requests, each sign-off is an append-only row, and you can export a per-PR oversight record.

For doc reviews, every comment, edit and decision goes into an event log. Edit events keep the before and after text, so the record shows what was added and removed.

Sealed exports you can check later

On the Governance plan, JSON exports carry a tamper-evident seal. Anyone with the file can upload it under Oversight, then Verify a record, to confirm it has not been changed since export.

The org-wide ledger lists every pull request and doc review in a period, as CSV or sealed JSON.

A copy that lives in your repo

When a maintainer finishes a doc review, DraftView commits a Markdown review record with the pull request. The default folder is .draftview/reviews. If you ever leave DraftView, the history stays in Git.

What to know before you rely on this

  • A record is evidence of oversight. It does not by itself make you compliant with any law or standard, including the EU AI Act. Ask your compliance team what applies to you.
  • Sealed JSON export and the oversight report need the Governance plan. The Markdown record is available on every plan.
  • DraftView records what happens inside DraftView. Work done in other tools is not captured.

Common questions

Can someone edit the record afterwards?
Sign-offs and review events are append-only in DraftView. Exported JSON is sealed, so a changed file fails verification.
Does it measure whether reviewers did real work?
It reports the share of reviews with at least a comment or an edit before sign-off, and for doc reviews the share of edits decided by someone other than their author.
Which formats can I export?
Sealed JSON and CSV for the org ledger, sealed JSON per review, and a Markdown record for doc reviews.

Keep reading

Last updated 2026-10-17