Check e-signature completion evidence against the approved signer packet
Get the source data and prepare the review

Documentation-verified component path; proposed adaptation, not tested

WHAT WAS CHECKED
Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Menus/features are vendor-documented; prompts, field maps and human gates are editorial adaptations. No actual client work, account login, installation, connection, external write or site edit occurred.

BEFORE YOU START
- 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.

DATA ACQUISITION LIMITS
- 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.

WHEN THIS CAN RUN
Blocked until actual sources, permissions and required human approvals are supplied; no real inputs were available in this verification.

STEP 1: Acquire actual envelope history and certificate
Tool: Docusign eSignature
Open: Agreements > select envelope > Details > More options > History; Download icon > Certificate of Completion
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.
Use it next: Download/open the returned document artifact from the same envelope and compare its document IDs/ordering to the approved send register.
Check: No recipient event or required role is inferred from envelope-wide Completed. Missing certificate is an exception, not fabricated evidence.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source 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

STEP 2: Verify document and signer mappings locally
Tool: Docusign details, downloaded packet and approved send register
Open: Envelope Details and actual returned PDF/certificate alongside approved packet
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.
Use it next: Load the approved ledger into PDF Spaces as labelled TXT; optional kit tables are human-created mappings, not native exports.
Check: The certificate may contain sensitive metadata. No hash equality between unsigned/signed files; any mapping ambiguity blocks that row.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source 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

STEP 3: Load only the approved AI input
Tool: Acrobat PDF Spaces
Open: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.
Use it next: Use the AI Assistant message field in this same space for the next prompt.
Check: 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.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source 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

STEP 4: Run the bounded prompt and inspect citations
Tool: Acrobat AI Assistant
Open: The PDF Space AI Assistant message field
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.

PASTE THIS PROMPT
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.
Use it next: Save the checked draft as signature-evidence-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check: Test mentally against a required witness absent from a Completed envelope: it must remain missing, even if a signer completed.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

STEP 5: Human review and final handoff
Tool: Responsible staff reviewer and lawyer/process owner
Open: Local reviewed report beside the frozen source set
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.
Use it next: No agreement is accepted/signed and no envelope is changed or resent.
Check: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://support.docusign.com/s/document-item?bundleId=oeq1643226594604&language=en_US&topicId=zqd1578456343466.html

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.
