For legal and compliance reviewers
Sign off on what the docs say, and keep the record
Product docs carry claims, terms and disclosures. When they are written in GitHub, often by AI, legal and compliance still need to approve the wording and show later that someone did. DraftView gives you the rendered page, precise edits and a record you can export.
The problem
Sound familiar?
You are asked to approve a diff
Reviewing contract-sensitive wording in raw Markdown source is slow and error-prone, and it is not what readers will see.
Approval lives in an email thread
"Looks good to me" in an inbox is hard to find later and does not say which version you approved.
AI content needs a human on record
Teams using AI to write customer-facing docs are being asked to show that a person checked the output before it was published.
How it works
Your part, step by step
Get invited by email
An admin invites you to your team's DraftView organization with your work email. You sign in with a magic link; you do not need access to the GitHub repo.
Mark up the exact wording
Comment on a sentence or propose a replacement. Every proposed edit shows who made it and stays as a suggestion until someone accepts it.
Record your sign-off
When the wording is right, record a sign-off on the PR. Sign-offs are append-only: they can be added, never edited or deleted.
Export the record
Download a sealed record of the review: files, participants and their roles, every comment, every edit and who decided it.
What you get
Built for how you review
Roles that match the job
Admins give each person a role: viewer, commenter, editor, maintainer or admin. A commenter can flag issues without editing; recording a sign-off needs maintainer.
Append-only review history
Comments, proposed edits, accept and reject decisions and sign-offs are logged with who and when, including the role the person held at the time.
Sealed audit records
Governance planExport a per-PR or per-review record as JSON with a tamper-evident seal, and check any exported file's seal later in DraftView.
Self-approval flags
Governance planThe oversight report shows edits that were accepted by the same person who proposed them, so independent review is visible, not assumed.
Outside counsel without accounts
Send a reviewer outside your company a review link with a password, an expiry date and a limit on submissions.
What you never have to do
- Get a GitHub seat or learn Git
- Read Markdown source to approve wording
- Keep approvals in an inbox
- Rebuild the review history by hand for an audit
Know before you choose
- DraftView records who reviewed what and when. It is evidence of human review, not legal advice or a certification that your process meets any law.
- Signing off on pull requests is recorded today; sign-off on doc reviews (reviews without a PR) is planned. Doc reviews already keep a full decision log.
- Sealed JSON exports, the oversight report and the org-wide ledger are on the Governance plan ($299 a month for 10 active reviewers). The Markdown review record is on every plan.
Common questions
- Can I approve wording without a GitHub account?
- Yes. Join with your email address and sign in with a magic link. You can comment and propose edits; your role decides whether you can also record sign-off.
- What is in the exported record?
- The files that were reviewed (by content hash), who took part and in what role, every comment thread, every proposed edit with its outcome and who decided it, and the full event log. The JSON export carries a seal you can verify later.
- Does this make us compliant with the EU AI Act?
- No tool can do that on its own. DraftView gives you a record that a person reviewed AI-written content before it shipped, which is the kind of evidence human-oversight requirements ask for. Your counsel decides what your obligations are.
- Can someone change the record after the fact?
- Sign-offs and review events are append-only. Exported JSON records are sealed with an HMAC over their content, so a changed file fails the seal check.
Last updated 2026-11-04