Check required signatures against returned evidence
Match approved signer roles and document versions to envelope events and returned artifacts.
Tools for the documented steps
Practice relevance
Cross-practice idea · Useful supporting administrative method; no claim of practice-specific legal instructions.
Scope: Docusign completion/history evidence and Acrobat; signature evidence only, NOT will execution, witnessing or testamentary validity.
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 & evidence
Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.
What’s been verified
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.
What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.
- Pain evidence: 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 evidence: The Invisible Work of Paralegals ↗Additional self-reported public account; no independent identity or outcome verification.
- Method: View the History or Certificate of Completion ↗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. We wrote these prompts. The adapted workflow hasn’t been tested.
Suggested approach
Start when: Staff is preparing to archive/use returned signatures
- compare lawyer-approved required document/signer/role list with envelope metadata, completion events and downloaded artifacts
- Keep source references and report unknowns instead of filling gaps.
- The responsible reviewer checks the report before any separately approved action.
Limits and review
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.
Who reviews it: 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.
What you need
Your firm-approved AI assistant · prepared files
- 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.
Check access and setup
- Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed.
Acquire actual envelope history and certificate
Docusign eSignature · 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.
Verify document and signer mappings locally
Docusign details, downloaded packet and approved send register · 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.
Load only the approved AI input
Acrobat PDF Spaces · 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.
Run the bounded prompt and inspect citations
Acrobat AI Assistant · 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.
- 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.
Human review and final handoff
Final human reviewResponsible staff reviewer and lawyer/process owner · 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.
What you’ll get
A list of missing signer, role, document or certificate evidence and inconsistent envelope IDs. Signature completion does not establish engagement acceptance.
Inputs and a sample test Synthetic example · not a measured result
Input files
- 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
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 output
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.
Test a failure
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.
Try with the sample files
Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.
Download inputs and checklist 11 files
Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.
- Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
- Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
- required blank template Approved document/version/signer/role requirements
- required synthetic example Approved document/version/signer/role requirements
- envelopes blank template Explicit envelope-to-source document mapping
- envelopes synthetic example Explicit envelope-to-source document mapping
- recipient_events blank template Recipient-level evidence; an envelope status cannot stand in for an absent recipient
- recipient_events synthetic example Recipient-level evidence; an envelope status cannot stand in for an absent recipient
- artifacts blank template Downloaded signed and completion-certificate metadata
- artifacts synthetic example Downloaded signed and completion-certificate metadata
- Setup and fixture review guide Recipe-specific setup, input rules, offline prompt, expected result and boundaries
Optional full review prompt for prepared inputs
Prepared-input review prompt with Your firm-approved AI assistant · prepared files
Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.