Skip to main content

    Filter by Idea status

    Filter by category

    1117 Ideas

    backofficeNewcomer

    Improving workflow for compelling applicants to complete the signing process (gateway leading applicants from the ID verification step to signing relevant documents)Idea Submitted

    After the recipient processes the identification step during the E-signature process, recipients are asked to sign the fields they're assigned. However, if recipients did not complete the process by clicking the correct buttons such as Sign or Complete, the envelope will not be considered completed and shall remain in a limbo as pending which implies unnecessary follow up frictions with recipients.This is so because in DocuSign, recipients have the option to skip their signing at a later time. They can also leave their signature on the envelope, and if they do not properly complete the signing, the signature will be saved but will not be completed.Our past experience tells that clearing the ID verification to signing relevant paperwork is very often confusing or not properly guided within your current workflow display. We suffer ongoing failures from recipients failing to complete the signature process after having been identified.  They think they have completed the process but the actual processing status at DocuSign is recorded as signature pending. We understand the purpose of expecting clients to push a button to confirm submission after they have signed the forms. However, this extra layer of requirement for the final submission should be smoothen by clearly disclosing to recipients the need to push the “Complete” button.We think that there is a lack of specific guidance needed while recipients are processing the entire signature process. This could be perhaps quite easily upgraded by disclosing:Step 1- ID verificationStep 2 - SignatureStep 3 - Confirming submission by clicking the “Complete” button. Recipients that would have signed documents BUT forgot to also push the “Complete” button should be warned about the resulting pending status of their submissions, prompting recipients to Complete it if they want to move ahead.It would be great if you'd take this into account for quality improvements at your end. Thank you

    Malik PressNewcomer

    Docusign Part 11 Signing Reason AssignmentIdea Submitted

    Current ChallengeWhen signing Part 11 envelopes, signers must select a "Signing Reason" for every signature applied. Currently, the dropdown menu to select a Signing Reason displays all Signing Reasons defined for the selected system language. By default, Docusign Part 11 provides three Signing Reasons (Author, Reviewed, Approve). Through the "Signing Resource File" of a specific Brand, an Admin can modify these or add custom reasons. However, for GMP documents, there is a fixed hierarchy of required signatures: 1. Author signatures, then 2. Reviewer signatures, finally 3. Approver signatures (Approver signatures are mandatory for every GMP document; Necessity of Author/Reviewer signatures vary by GMP document). Consequently, when we create a Part 11 envelope, the selection and order of signers are based on these requirements. Each signer is assigned a fixed role (Author, Reviewer, or Approver), which dictates exactly which Signing Reason they must select. Currently, we assign these roles visually at document creation via a signature table within the document itself (columns: Role, Name/Function, Signature). We explicitly enter "Author," "Reviewer," or "Approver" in the role column of each signer row. Signers are trained to check this column and then manually select the matching Signing Reason in Docusign. Pain PointsUnfortunately, deviations frequently occur. Despite training and support materials, signers often select a Signing Reason that does not match their assigned role. When this happens, the entire Part 11 envelope must be voided, re-created, and re-sent for signatures. Additionally, I noticed that when adding custom Signing Reasons via the Signing Resource File, they must be added manually for all languages. Otherwise, the custom reasons do not appear if a signer uses a different system language. Proposed Solutions (User Stories)To improve the "First-Time-Right" rate for signers and reduce the administrative burden of managing Signing Reasons, I have defined the following requirements: High PriorityHP1: As an Admin, I want to create, update, and delete Signing Reasons in a dedicated Admin Setting Section, so that they are available for all Part 11 envelopes regardless of the selected Brand.HP2: As an Admin, I want to define a Default Label for each Signing Reason, so that the reason is displayed to all signers even if a specific translation is missing.HP3: As an Admin, I want to define labels for all available system languages for each Signing Reason, so that they appear correctly in the signer's selected system language.HP4: As a Sender, I want to select/restrict the specific Signing Reasons available to a signer when creating a Part 11 envelope, ensuring the signer cannot accidentally select an incorrect reason. Low PriorityLP1: As an Admin, I want to create, update, and delete "Signing Roles" in a dedicated Admin Setting Section.LP2: As an Admin, I want to assign one or more Signing Reasons to a specific Signing Role.LP3 (Alternative to HP4): As a Sender, I want to assign a "Signing Role" to a signer when creating an envelope. This would restrict the dropdown menu to only show the Signing Reasons assigned to that role, ensuring the signer cannot accidentally select an incorrect reason.

    KennyFllNewcomer

    Support PDF Embedded Attachments and Require Recipient Acknowledgement Before SigningIdea Submitted

    ProblemPDF files can contain embedded attachments, such as Excel spreadsheets. For example, a commercial proposal may include the main offer as a PDF and a detailed scope of work or pricing calculation as an embedded Excel attachment.These embedded files can be opened when viewing the PDF in applications such as Adobe Acrobat. However, when the same PDF is uploaded to DocuSign, the embedded attachments are not visible or accessible to the recipient.As a result, important contractual information may not be available during the signing process, even though it is technically part of the original PDF.Requested functionalityI would like DocuSign to support the following capabilities: Display embedded PDF attachments When a PDF contains embedded files, DocuSign should detect and display them separately in the envelope or signing interface. Senders and recipients should be able to view or download these files without having to extract and upload them manually as separate envelope documents. Require acknowledgement before signing Senders should be able to mark an attachment as required reading. Before the recipient can continue to the signature fields, the recipient should be required to: open or download the attachment, confirm that they have reviewed it, and only then proceed to sign the document. The acknowledgement should be recorded in the envelope history or certificate of completion, including the recipient, attachment name, date and time.Example use caseA company sends a proposal for signature. The main PDF contains the commercial terms, while an embedded Excel file contains the detailed project scope.The recipient should be able to download and review the Excel file directly within the DocuSign signing process. After confirming that the file has been reviewed, the recipient can proceed to sign the proposal.Business valueThis functionality would:ensure that recipients can access all relevant contractual documents, reduce the risk of recipients overlooking important attachments, improve transparency and auditability, avoid the need to manually extract and upload embedded files, and provide evidence that required supporting documents were made available and acknowledged before signing.