Talk through a redline with your team without leaving the workspace. Comments live next to the AI's analysis and stay anchored even after re-running the review.
Written by Antonio Goncalves · Updated April 2026
What's new
Leave a comment on a playbook rule or an individual redline.
Choose between Internal (team-only) and On document (will be exported to the supplier).
@mention a teammate or a whole division.
Reference a specific redline so the comment carries a clickable breadcrumb.
See every comment, version, and decision in the unified Activity feed.
Comments stay anchored to the rule or redline even after a re-analysis.
Where to leave a comment
Comments live in two places, depending on what you want to discuss.
1. Playbook tab — on a rule
Open the Playbook tab in the right panel and expand any rule. The Rule Analysis card has a comment composer at the bottom. Use this when the conversation is about the rule itself or the AI's overall finding.
2. Redlines tab — on a single redline
Open the Redlines tab and expand a redline. Each redline card has its own composer and Activity feed. Use this when the conversation is about that specific change.
The composer
The composer is the same in both tabs. Three things to know:
Internal / On document toggle — controls who sees the comment.
Reference this redline — attaches a breadcrumb so the comment is tied to a specific change.
@mentions — tag a person or a division.
Internal vs On document
Pick the audience before you post. The padlock under the composer reminds you what mode you're in.
Internal — visible only to your team. Use for questions, context, or instructions for a colleague. Won't appear in the exported document.
On document — will be written into the DOCX as a Word comment when you download. Use for notes you'd want the supplier or counterparty to see.
Tip: Default to Internal. Switch to On document only when you're sure the note should reach the other side.
@mention people and divisions
Type @ in the composer to open the picker. You can mention an individual user or a whole division — useful when you don't know exactly who owns a category but you know which team should look at it.
Mentioned users and division members get notified. The mention is rendered as a purple chip in the comment.
Reference a redline as context
When you're commenting on a rule but want to point at a specific redline, click + Reference this redline above the text field. The card title becomes a chip in the composer.
Once posted, the reference shows as a clickable breadcrumb above the comment body. Anyone reading the thread can click it to jump straight to the redline.
The Activity tab
The Activity tab in the right panel is the unified timeline for the workspace. It shows version analyses, comments from both the Playbook and Redlines tabs, and decisions, all in chronological order.
Each comment carries the breadcrumb of where it came from — for example [rule-1002] - Supplier Information Fill-In. Click the breadcrumb to navigate back to the source card.
Comments stay anchored after re-analysis
Re-running the AI doesn't wipe your comments. They stay attached to the rule or redline they were posted on, so you can run a fresh analysis without losing the discussion.
Note: If a redline disappears after re-analysis (because the AI no longer flags it), comments tied to that redline move into the Activity feed with the original context preserved.
Tips & Workarounds
Tip: Use Reference this redline from the Playbook tab when the rule has multiple redlines and you want to call out one specifically.
Tip: @mention a division when the work hasn't been assigned yet. Anyone in the division can pick it up.
Note: On document comments are exported as Word comments in the DOCX download. They will be visible to whoever opens the file, including the supplier.
What to do next
Questions? [email protected]