Skip to main content

    Filter by Idea status

    Filter by category

    925 Ideas

    TJHObserver

    Document Markup Needs Reliable Persistence and Structured Redline Workflow SupportIdea Submitted

    SummaryDocument Markup is positioned as a way for recipients to propose and approve changes during signing, but in practice it does not reliably support back-and-forth negotiation between sequential signers. Below are the specific gaps identified through extensive testing on our account, along with the business impact of each. 1. Markup Data Is Not Reliably SavedWhen a signer applies markups and selects Finish Later instead of completing the envelope, the markup changes are not saved or visible to the next signer. The only way to preserve markup activity at all is to complete every required signature field and fully execute the envelope. This means markups effectively only persist if the document is signed, which defeats the purpose of a negotiation step that is meant to happen before signing.Business Impact: Teams cannot pause a negotiation mid-process without losing the redline history. This makes Markup unreliable as a tool for any agreement that requires more than one round of review. 2. No Oversight or Notification When Markups Are MadeWhen a signer applies markups, there is no notification, flag, or visual callout to alert the next signer that changes have been made. The only way to discover a markup is to manually review the entire document page by page.Business Impact: This creates a high risk of a signer missing material changes to a contract, particularly in multi-page agreements. It also removes the audit confidence that all parties were made aware of proposed changes. 3. No Structured Way to Respond to a MarkupThere is no accept and reject function, no threaded comments, and no version comparison. A signer can only initial a markup or attempt to edit it directly within the document and add their own initials. There is no clear mechanism for a counterparty to formally respond to a proposed change without simply overwriting it.Business Impact: This does not support genuine negotiation. Real-world contract negotiation requires the ability to propose, respond to, accept, or reject specific terms with a clear record of who proposed what and when. Markup does not provide this today. 4. Markup and Required Signature Fields Can Conflict in Sequential SigningIn testing, we found that the interaction between Markup and required signature fields in a sequential, multi-signer envelope behaves inconsistently. We have seen scenarios where an envelope completed without all required signers signing, and other scenarios where the markup activity was effectively erased unless the document was fully executed.Business Impact: This inconsistency makes Markup unsuitable for any workflow with enforced signing order, which is standard for two-party agreements requiring sequential approval, such as subcontractor and vendor agreements. Requested ImprovementsWe would ask that the product team consider the following enhancements to Document Markup:- Persist markup data and comments at every stage of the envelope lifecycle, regardless of whether the envelope is completed, including when a signer selects Finish Later.- Notify all recipients when a markup has been applied, including a visual indicator on the document itself showing where changes were made.- Add a structured accept and reject mechanism for markups, with the ability to leave a comment tied to a specific change, so that negotiation history is clearly tracked.- Ensure markup behavior is fully compatible and predictable when used within an envelope that has an enforced signing order and required signature fields for multiple recipients.We believe these improvements would allow Document Markup to function as the lightweight redlining tool it is intended to be, particularly for organizations using sequential signing workflows for vendor and subcontractor agreements.