nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Comments on draft documents should not trigger redlines

Maja_R

Our workflow currently tags Legal for review whenever a draft document is “not generated from template.” Adding internal comments in the Ironclad editor triggers this condition, even if the document text is unchanged. This results in Legal being tagged unnecessarily. It seems there are no good solution for this and we either have to accept the unnecessary tags or stop using either the comments or the condition to automatically tag legal.

It would be great if comments could be left without triggering the "not generated from template" condition.

Find more posts tagged with

Status: None

Comments

Sarah_Lovequist

Great idea! We similarly struggle when items like business terms or entity names are redlined - these are not clauses that need to go to Legal, but there is no way to distinguish between legal clauses and factual items in a contract. Any change is considered a "redline" whether it rises to the level of legal review or not. Legal review could be triggered at the individual clause level, which then would require Legal to e.g., sign off on 10 clauses instead of clicking 'approve' once, but this concept doesn't solve the more common issue your post describes.