# Check required signatures against returned evidence Canonical page: https://agents.paretoid.com/workflows/check-required-signatures-against-returned-evidence/ Category: Operations & Reporting Practice relevance: cross-practice. Useful supporting administrative method; no claim of practice-specific legal instructions. Jurisdiction/provider scope: Docusign completion/history evidence and Acrobat; signature evidence only, NOT will execution, witnessing or testamentary validity. Match approved signer roles and document versions to envelope events and returned artifacts. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result. ## The problem Match approved signer roles and document versions to envelope events and returned artifacts. Why it matters: A completed envelope may omit a signer who was never configured. Checking the approved packet against the actual events and artifacts helps staff find missing evidence before a lawyer decides whether execution is sufficient. ## Sources and evidence - pain: [Pain evidence: Docusign](https://www.reddit.com/r/uklaw/comments/1nqv3e8/docusign/) Docusign, 26 September 2025, older, direct original read. A trainee solicitor reports failing to tag a required witness signature and putting a client in the wrong signing group. The Invisible Work of Paralegals, 16 August 2025, older; a lending paralegal describes receiving disordered signature pages that must be matched back to the closing checklist. The completion check is a proposed downstream safeguard derived from those setup/packet pains; it is not proof that these posters used it. - pain: [Pain evidence: The Invisible Work of Paralegals](https://www.reddit.com/r/paralegal/comments/1mrkcdh/the_invisible_work_of_paralegals/) Additional self-reported public account; no independent identity or outcome verification. - method: [Method: View the History or Certificate of Completion](https://support.docusign.com/s/document-item?bundleId=oeq1643226594604&language=en_US&topicId=zqd1578456343466.html) Docusign View the History or Certificate of Completion, documentation last updated 2 July 2026, describes envelope history and certificate download. Indexed official text read; clean support page renders a shell in direct fetch. The certificate may be separate from the combined PDF. This proves evidence is available, not that the platform knows every legally required signer. Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. ## Suggested approach Start when: Staff is preparing to archive/use returned signatures 1. compare lawyer-approved required document/signer/role list with envelope metadata, completion events and downloaded artifacts 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - Existing Docusign eSignature account with permission to view/download the exact envelope; lawyer-approved document/source-version/signer/role requirements and the original send register. - History and Certificate documentation was available as official indexed text; the public support page itself rendered only a shell. Account menu/plan visibility was not tested. - Existing firm-approved Acrobat Studio, AI Assistant add-on, or another plan including Acrobat AI; online services/cloud storage, language and region must be permitted. No purchase, login or connection is part of this verification. The manual route works without AI. - Preserve original evidence unchanged in restricted storage. Use synthetic material first. Prepare a separate, explicitly approved minimized AI input; aliases alone do not anonymize narrative or attachments. Do not upload raw originals or an alias key merely because another tab/file is sanitized. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-verified component path; proposed adaptation, not tested - Completed envelope status only describes configured recipients. It cannot satisfy a required signer omitted from configuration or establish legal validity. - Source version and per-document signer/role mappings may require the firm’s approved send register; Docusign history alone does not promise those fields. Missing mappings block the comparison. - Signed PDFs differ from unsigned originals; do not require their hashes to match. Access and setup: - Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed. ### 1. Acquire actual envelope history and certificate Tool: Docusign eSignature Location: Agreements > select envelope > Details > More options > History; Download icon > Certificate of Completion Locate the exact envelope using known envelope identity. Read full history and preserve its observed events in a restricted manual log with source references. Download the Certificate of Completion separately; do not assume it is included in a combined signed PDF. Record envelope ID and capture time. Expected output: Actual envelope history observations and separately downloaded completion certificate. Next step: Download/open the returned document artifact from the same envelope and compare its document IDs/ordering to the approved send register. Check before continuing: No recipient event or required role is inferred from envelope-wide Completed. Missing certificate is an exception, not fabricated evidence. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://support.docusign.com/s/document-item?bundleId=oeq1643226594604&language=en_US&topicId=zqd1578456343466.html https://support.docusign.com/s/document-item?bundleId=oeq1643226594604&language=en_US&topicId=ono1578456343275.html ### 2. Verify document and signer mappings locally Tool: Docusign details, downloaded packet and approved send register Location: Envelope Details and actual returned PDF/certificate alongside approved packet Visually verify every required document/version, configured signer/role, completion event and returned artifact. Map required document IDs to returned pages/files using the approved send record, not filename similarity. Record alias-based required rows, envelope/document mapping, observed recipient events and artifact/certificate evidence. Keep signature images, certificate IP/email data and original identities restricted. Expected output: Minimized required/envelope/recipient-event/artifact ledger with explicit null unknowns. Next step: Load the approved ledger into PDF Spaces as labelled TXT; optional kit tables are human-created mappings, not native exports. Check before continuing: The certificate may contain sensitive metadata. No hash equality between unsigned/signed files; any mapping ambiguity blocks that row. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://support.docusign.com/s/document-item?bundleId=oeq1643226594604&language=en_US&topicId=zqd1578456343466.html https://support.docusign.com/s/document-item?bundleId=oeq1643226594604&language=en_US&topicId=ono1578456343275.html https://helpx.adobe.com/acrobat/desktop/get-started/learn-the-basics/navigation.html ### 3. Load only the approved AI input Tool: Acrobat PDF Spaces Location: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space Add the approved alias-based requirements, envelope mappings, observed recipient events and artifact evidence only. Use clear source/version labels and verify the Files panel. Do not add originals that have not separately been cleared for Adobe processing. Expected output: Visible approved source set in the PDF Space; no account integration is implied. Next step: Use the AI Assistant message field in this same space for the next prompt. Check before continuing: Confirm every named source is actually loaded and readable. PDF Spaces supports up to 100 files, 100 MB and 600 pages per file; unsupported/password-protected/handwritten material blocks affected extraction. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/supported-formats-limitations.html https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/pdf-spaces-faq.html ### 4. Run the bounded prompt and inspect citations Tool: Acrobat AI Assistant Location: The PDF Space AI Assistant message field Paste the prompt below. Open each source-number citation, check it, and use Copy to transfer the answer into a new local Word document or text file. Correct errors using the originals before reliance. Prompt: ```text Match every approved document/source-version/signer/role requirement to a unique supplied envelope mapping, recipient event and returned artifact. Return packet_id,document_id,signer_id,role,envelope_id,exception,evidence_refs. Flag absent/duplicate mappings, source-version mismatch, incomplete required recipient evidence, missing signed artifacts/certificates and envelope-ID conflicts. A Completed envelope does not satisfy a required signer missing from its configuration. Do not infer witness/notary requirements, authenticate identity, validate execution, compare unsigned/signed hashes for equality, resend invitations, sign or change envelopes. ``` Expected output: Signer/document completion-evidence exceptions and lawyer-review checklist. Next step: Save the checked draft as signature-evidence-review.docx; carry source IDs, versions and reviewer corrections into the next review step. Check before continuing: Test mentally against a required witness absent from a Completed envelope: it must remain missing, even if a signer completed. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ### 5. Human review and final handoff Tool: Responsible staff reviewer and lawyer/process owner Location: Local reviewed report beside the frozen source set Lawyer opens actual packet and certificate, verifies authority, required signers, witnessing/notarization and legal sufficiency separately. Staff records evidence findings and unresolved mappings. Expected output: Reviewed execution-evidence register, not a validity certificate. Next step: No agreement is accepted/signed and no envelope is changed or resent. Check before continuing: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://support.docusign.com/s/document-item?bundleId=oeq1643226594604&language=en_US&topicId=zqd1578456343466.html ## What you will get A list of missing signer, role, document or certificate evidence and inconsistent envelope IDs. Signature completion does not establish engagement acceptance. ## Human review and limits Lawyer determines requirements and legal sufficiency, including authority, witnessing/notarization, signature method and permitted reuse. Staff opens actual returned packet and certificate. No legal agreements accepted or signed by the workflow. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema required.csv = packet_id,document_id,approved_source_version,signer_id,role. envelopes.csv = envelope_id,packet_id,document_id,source_version,envelope_status. recipient_events.csv = event_id,envelope_id,signer_id,role,status,event_at,source_ref. artifacts.csv = artifact_id,envelope_id,document_id,kind,sha256,source_ref where kind=signed_pdf|completion_certificate. roles/statuses are supplied platform vocabulary, not inferred legal requirements. Synthetic example input: ```text Approved D1/v2 requires S1 signer and W1 witness. Envelope E1 maps D1/v2, status completed; only S1 has completed event. Signed PDF present, certificate absent. ``` Expected synthetic output: ```text W1 required evidence missing and E1 certificate missing, despite completed envelope. If mapping is D1/v1, also flag source-version mismatch; do not compare unsigned/signed bytes as identical. ``` Failure check: Lawyer determines requirements and legal sufficiency, including authority, witnessing/notarization, signature method and permitted reuse. Staff opens actual returned packet and certificate. No legal agreements accepted or signed by the workflow. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/q06-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/q06/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [required blank template](https://agents.paretoid.com/assets/starter-kits/q06/required.template.csv) — Approved document/version/signer/role requirements - [required synthetic example](https://agents.paretoid.com/assets/starter-kits/q06/required.example.csv) — Approved document/version/signer/role requirements - [envelopes blank template](https://agents.paretoid.com/assets/starter-kits/q06/envelopes.template.csv) — Explicit envelope-to-source document mapping - [envelopes synthetic example](https://agents.paretoid.com/assets/starter-kits/q06/envelopes.example.csv) — Explicit envelope-to-source document mapping - [recipient_events blank template](https://agents.paretoid.com/assets/starter-kits/q06/recipient_events.template.csv) — Recipient-level evidence; an envelope status cannot stand in for an absent recipient - [recipient_events synthetic example](https://agents.paretoid.com/assets/starter-kits/q06/recipient_events.example.csv) — Recipient-level evidence; an envelope status cannot stand in for an absent recipient - [artifacts blank template](https://agents.paretoid.com/assets/starter-kits/q06/artifacts.template.csv) — Downloaded signed and completion-certificate metadata - [artifacts synthetic example](https://agents.paretoid.com/assets/starter-kits/q06/artifacts.example.csv) — Downloaded signed and completion-certificate metadata - [Setup and fixture review guide](https://agents.paretoid.com/assets/starter-kits/q06/README.txt) — Recipe-specific setup, input rules, offline prompt, expected result and boundaries ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Use only these synthetic tables. Match every approved document/version/signer/role to an envelope and recipient event. Flag absent or duplicated mappings, incomplete required recipient statuses, missing signed artifacts/certificates and envelope-ID conflicts. Preserve source refs and report unknowns. An envelope marked completed does not satisfy a required signer absent from its configuration. Do not infer witness/notary requirements, authenticate identity, validate execution, resend invitations, sign, change envelopes or delete drafts. Return packet_id,document_id,signer_id,role,envelope_id,exception,evidence_refs and a lawyer-review checklist. INPUTS required.csv = packet_id,document_id,approved_source_version,signer_id,role. envelopes.csv = envelope_id,packet_id,document_id,source_version,envelope_status. recipient_events.csv = event_id,envelope_id,signer_id,role,status,event_at,source_ref. artifacts.csv = artifact_id,envelope_id,document_id,kind,sha256,source_ref where kind=signed_pdf|completion_certificate. roles/statuses are supplied platform vocabulary, not inferred legal requirements. OUTPUT A list of missing signer, role, document or certificate evidence and inconsistent envelope IDs. Signature completion does not establish engagement acceptance. Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.