Document review

Document review
without the email chain.

Redline is a collaborative review tool for HTML documents. Reviewers annotate and suggest changes. You queue them, apply them with AI, and publish a new version — all in one place.

Open RedlineFor document authors and teams who review with stakeholders.

How it works

From first draft to final version — without leaving the tool

01
Upload your document

Upload an HTML document. Redline renders it exactly as it appears, inside the review interface.

02
Invite reviewers

Share a review link with stakeholders — no account required. They annotate, comment, and suggest changes directly in the document.

03
Queue the feedback

Review all suggestions in a structured queue. Accept, reject, or modify each one before applying. Nothing gets applied without your sign-off.

04
Publish with AI

AI applies your queued changes and generates a new version. Each version is stored and versioned — so you can always go back.

Key features

Structured review. Clean output.

Everything teams need to go from messy feedback to a clean revised document.

Faithful HTML rendering

Your document renders exactly as it looks in a browser, with your original styles preserved. Reviewers see what they're actually commenting on.

Feedback queue

All feedback collects in a structured queue — like a cart of changes to apply. Review everything before anything gets changed. You stay in control.

AI-applied revisions

When you're ready, Claude AI applies your queued changes to the document and produces a new, clean version. No manual editing of HTML required.

v
Version history

Every published version is stored. See what changed between v1 and v3, share a specific version with a stakeholder, or roll back if needed.

External reviewer access

Share review links with anyone — clients, legal, external stakeholders. No account or login required. Token-based access keeps it secure and simple.

Document Brief

Auto-populated from a comment in your HTML file, the Document Brief gives reviewers the context they need: what this document is for, what kind of feedback is useful.

Who it's for

Anyone managing documents with multiple stakeholders

Document authors
Writers and content owners who need to collect structured feedback from multiple reviewers without losing track of who said what.
Internal review teams
Teams doing structured review cycles — legal, compliance, product spec review — where a clear feedback trail and version history matter.
Client-facing workflows
Agencies or consultants sharing deliverables with clients for approval. External reviewers access via a link — no setup required on their end.