Review Studio
The Review Studio is where a draft gets imported, marked up, rewritten and exported. Flag exact passages with margin comments, ask Iris to rewrite anchored sections in the document's voice, or run a panel of specialist review lenses before you ship.
An editing workspace, not an approval system. You can apply your own anchored comments or solicit AI specialist and simulated-stakeholder reads. Their verdict labels are review signals; they do not record a real person's approval or complete an external workflow.
❝ Inline comments
Flag any passage with a margin note and a severity — note, concern or blocker.
❝ Rewrites in your voice
Iris applies each comment as document prose, preserving your facts and register.
❝ Review lenses
Specialists review from their domains; saved people can be simulated and are labeled sim.
❝ Import & export
Bring PDF, Word, Markdown, HTML or rich text; export PDF, text, Markdown, HTML or a review bundle.
/review in the composer, or click the Open chip — or jump straight back into a saved session.What it is#
The Review Studio keeps the document, anchored comments and rewrites together. Export creates a file or clipboard result when you ask for one; the session does not maintain a separate export-history ledger. Comments are tied to real passages and stale anchors are held back from rewrite, so feedback cannot silently land on a paragraph that changed underneath it.
Bringing in a draft#
Start blank, paste rich text from Google Docs, or import PDF, Word, Markdown, HTML, plain text, or a previously exported .zimac-review bundle. Google Docs is a clipboard round-trip rather than direct document editing: paste its formatted content into Review, then copy the result back with formatting. You can also open the studio from chat, run /review, or ask Sage to hand a draft into it.
Flagging sections#
Select a passage and leave a margin comment on it — as specific as you like. Each comment carries a severity, so the important ones stand out from the nitpicks:
Comments are anchored to the exact text they mark, so they stay attached to the right spot as you work — and a comment whose anchor text has changed is held back from driving a rewrite until it's re-anchored, so feedback never lands on the wrong paragraph.
Rewriting in your voice#
Once you've flagged what needs work, Iris rewrites only the flagged sections, applying each comment precisely. This is The Cut: remove drag without sanding off the author's identity. A rewrite is document prose, not a reply — it reads as if you wrote it in one sitting, flowing naturally from the paragraph before into the one after. So a comment that asks "is this true?" gets answered inside the narrative in the document's declarative voice, never with a question or a "here's a tighter version". Facts, numbers and names are preserved unless a comment says otherwise, and each rewrite stays roughly the length of the original unless you asked to expand or tighten.
A panel review#
When you want outside pressure on a draft, run a panel review: active specialists read it through their configured domain lens — Cassandra on data, Kai on rollout, Finn on cost, and so on. You can also choose saved people from People; those results are predictions generated from the saved profile and carry a visible sim badge. They are never represented as words, consent, or approval from the actual person. Each reviewer returns a review verdict and a one-line take:
Comments are verbatim-anchored to the passages they mark and kept tight. A verdict helps prioritize edits inside this session; it is not a signature, policy gate, stakeholder decision, or proof that the document is ready.
Saving & resuming#
Reviews save themselves. A session — the document, your comments, the rewrites — persists on its own, so you can park one mid-review and pick it back up later from the studio's list of saved sessions. Long documents and multi-pass edits don't have to happen in one go.
Exporting#
Export the clean document as PDF, plain text, Markdown, or standalone HTML; copy rich text for Google Docs; save a text copy in Zimac Documents; or export a .zimac-review bundle that preserves the document and its comments for a later Review Studio import. Copying for Google Docs does not publish or update a Google document automatically.