Feedback & Comments
Lens has a built-in feedback loop designed for the review phase of an engagement. Instead of editing findings directly — which would bypass the reasoning chain — you leave a comment on specific text, and the comment becomes an instruction that updates the document when you resolve it.
This keeps the document’s history intact: every edit is traceable to the comment that requested it.
How it works
1. Select text and add a comment
While working in the Canvas workspace, select any text — a finding title, a sentence in a summary, a metric value, anything. A 💬 Add feedback button appears near the selection.
Click it. A small composer opens showing the selected text as a quote. Type your comment — a correction, a clarification, a request to rephrase — and click Add feedback.
The comment appears in the Feedback Rail on the right side of the Canvas. It shows:
- The section it was made in
- The quoted text it references
- The comment body
2. Review comments in the Feedback Rail
The Feedback Rail collects all open comments for the engagement. A count of open comments appears on the Feedback tab when the rail is closed.
Comments stay open until you explicitly resolve them. You can accumulate a batch of feedback — from multiple reviewers or from your own review pass — and work through them all before resolving.
3. Resolve a comment
When you are ready to apply a change, click Resolve → on the comment. Lens applies the edit to the relevant section and creates a new document version. The comment closes and shows the resolution.
If the edit cannot be applied automatically, Lens will tell you. In that case, make the edit manually in the section notes or by adding a new action to the finding, then resolve the comment as complete.
4. View resolved comments
Resolved comments are hidden by default — the rail only shows open items. To see the history, click Show resolved at the bottom of the Feedback Rail. Each resolved comment shows what was changed and a link to view the version where the change was applied.
What feedback is for
The feedback loop is designed for three scenarios:
Self-review — you finish drafting the engagement and then review the Principal view as the Dealer Principal would see it. Anything that needs adjustment, you mark with a comment and resolve before sign-off.
Internal review — a senior consultant or Account Owner reviews your engagement before it goes to the dealer. They leave comments; you resolve them. The document updates, the history is preserved.
Pre-sign-off refinement — you share the draft report with the Dealer Principal informally before signing. They request a clarification or a softer phrasing. You capture the request as a comment and resolve it. The signed version reflects the agreed language.
A comment is an instruction, not a sticky note. When you click Resolve →, the document changes. Leave comments for things you intend to act on — not observations you want to preserve as annotations.
What feedback does not do
Feedback does not change the underlying finding data — the money figures, the metrics, and the reasoning chain remain as computed. If you believe a finding’s core data is wrong, add a comment explaining the correction needed. The resolution updates the document narrative; the finding’s data reflects the resolution.
Feedback also does not replace the audit itself. It is a refinement tool for the review stage, not a way to re-run the analysis.