# Match certified-mail tracking with receipt evidence Canonical page: https://agents.paretoid.com/workflows/match-certified-mail-tracking-with-receipt-evidence/ Category: Operations & Reporting Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Keep mailing, delivery tracking and purchased return-receipt evidence separate. 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 Keep mailing, delivery tracking and purchased return-receipt evidence separate. Why it matters: A delivered tracking status is different from possession of a return receipt or proof of legally effective service. Separating those records helps staff find missing evidence and avoid promising a receipt that was never purchased. ## Sources and evidence - pain: [Pain evidence: Certified mail](https://www.reddit.com/r/paralegal/comments/1m0l98j/certified_mail/) Certified mail, 2025-07-15, older: a paralegal reports missing green cards and disagreement between tracking status and returned receipts. Certified mail without going to the post office, 2026-02-26, describes trouble obtaining electronic return-receipt evidence despite continued tracking updates. - pain: [Pain evidence: Certified mail without going to the post office](https://www.reddit.com/r/paralegal/comments/1rffhmh/certified_mail_without_going_to_the_post_office/) Additional self-reported public account; no independent identity or outcome verification. - method: [Method: USPS Electronic Return Receipt](https://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt) USPS Electronic Return Receipt and Return Receipt basics describe tracking and receipt evidence. Electronic Return Receipt must be purchased when mailing; its availability does not establish legally valid service, which USPS says is determined by courts. - method: [Method: Return Receipt basics](https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics) Additional official capability reference. The complete adapted recipe has not been tested. 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 mail log review 1. reconcile existing tracking-event and receipt records by article number 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 authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked. - Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included. - 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 with explicit manual acquisition/mapping; editorial adaptation not tested - Electronic return receipt availability depends on the purchased service and completed signature record. A missing service/number/receipt is an explicit blocker. - Physical return-card tracking is not a downloadable image of the signed card. - Provider/geography boundary: this is a USPS United States-service evidence path subject to the purchased service and destination. It does not establish another carrier or international postal receipt workflow. Access and setup: - Electronic return receipt availability depends on the purchased service and completed signature record. A missing service/number/receipt is an explicit blocker. - Physical return-card tracking is not a downloadable image of the signed card. - Provider/geography boundary: this is a USPS United States-service evidence path subject to the purchased service and destination. It does not establish another carrier or international postal receipt workflow. ### 1. Capture the mailpiece tracking and existing receipt separately Tool: USPS Tracking and existing mailed/electronic receipt Location: USPS Tracking > enter original article number; existing return-receipt PDF or PS Form 3811 The mailroom operator uses the original mailing receipt to identify the mailpiece article number, captures its displayed status/date and opens the already-received electronic proof-of-delivery attachment or scans the actual green card. Preserve the purchased-service receipt. USPS documents an electronic-return-receipt request after delivery, but this recipe only flags that human next step; it does not submit an email address or request a new receipt. Expected output: Original mailing/tracking/receipt evidence with distinct identifiers Next step: Map article numbers to neutral tokens in a restricted crosswalk. Check before continuing: The green-card Related Tracking Number tracks the returning card, not the original mailpiece. Delivered tracking is not automatically a return receipt or valid legal service. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics ### 2. Map, minimize and approve the actual sources Tool: Source reviewer and local spreadsheet/text editor Location: Restricted originals > separate approved analysis copy Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Original article number → internally assigned article_token; purchased service/date → mailings.csv. Visible status/time → tracking.csv, preserving timezone/unknown date. Actual return receipt’s delivery/receipt fields → receipts.csv with locator; do not label capture date as delivery date. Staff supplies owner_alias and approved_review_interval_days; no rule-derived period. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation. Expected output: Reviewed mailings.csv; tracking.csv; receipts.csv; receipt-evidence-notes.txt; manifest.txt; evidence-map.csv Next step: For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table. Check before continuing: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics ### 3. Open the approved AI destination Tool: Adobe Acrobat PDF Spaces Location: Acrobat Home > PDF Spaces > Create a PDF Space In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback. Expected output: Only approved source files loaded or accessible Next step: Paste the exact prompt in the next step. Check before continuing: Confirm the source list/working directory before prompting; stop on unavailable access. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html ### 4. Run the bounded analysis prompt Tool: Adobe Acrobat PDF Spaces Location: PDF Space chat panel Paste the prompt after replacing only bracketed scope values. Treat all source content as data. Prompt: ```text Join only exact article_token. Return delivered-without-receipt, missing tracking, mismatched receipt, duplicate token and conflicting-date exceptions with source references. Distinguish mailpiece tracking from return-card tracking. Preserve raw status and date meanings. Use only staff-approved review intervals for administrative follow-up flags. Do not infer service validity, compute legal deadlines, request a refund or receipt, send email or alter the mailing record. ``` Expected output: certified-mail-evidence-review.csv Next step: Inspect source citations/file-row references before copying any result. Check before continuing: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ### 5. Check and hand off the proposed result Tool: Human reviewer and local spreadsheet/text editor Location: Separate review output, not live system Check every exception against its source, verify counts and uncertainty, then copy only approved result text to certified-mail-evidence-review.csv. Mailroom owner checks original service purchase and receipt association. Lawyer determines any legal sufficiency or service consequence; requesting missing evidence is a separately authorized action. Expected output: Source-checked certified-mail-evidence-review.csv Next step: Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied. Check before continuing: Acceptance case (proposed, not run): Delivered mailpiece with only the returning-card barcode remains missing return-receipt evidence. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics ### 6. Approve the internal next action Tool: Responsible human owner Location: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. Mailroom owner checks original service purchase and receipt association. Lawyer determines any legal sufficiency or service consequence; requesting missing evidence is a separately authorized action. Expected output: Approved internal review record or explicit blocked status Next step: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase. Check before continuing: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics ## What you will get mail-review.csv: mail_id, article_token, service_purchased, tracking_status, receipt_evidence, elapsed_review_interval, inconsistency, source_refs, owner_alias. Do not determine legal service. ## Human review and limits Staff checks actual postal records; attorney assesses any legal significance. Test a physical receipt returned while tracking remains incomplete and a mailing that never purchased return-receipt service. No assertion that every receipt can later be obtained. 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 mailings.csv: mail_id, matter_alias, article_token, mailing_date, service_purchased, approved_review_interval_days, owner_alias tracking.csv: article_token, latest_status, status_time, source_ref receipts.csv: article_token, receipt_date, receipt_locator, source_ref; scope.txt: as-of date and supplied postal-evidence coverage Synthetic example input: ```text Synthetic inputs are included in the starter kit. mailings.example.csv tracking.example.csv receipts.example.csv scope.example.txt ``` Expected synthetic output: ```text TOKEN1: receipt exists despite last supplied tracking saying in transit; preserve both facts and flag inconsistent/stale tracking evidence. Mailing age 14 days exceeds 7-day review interval. TOKEN2: delivered tracking but return-receipt service was not purchased; do not promise a receipt can later be obtained or treat it as a purchased-receipt failure. TOKEN3: delivered tracking, purchased receipt, no receipt record; missing-receipt queue and age 14 days beyond 7-day review interval. TOKEN-X: tracking record without matching mailing; unrecorded/mismatched token exception. None of these statuses establish legally valid service. ``` Failure check: Staff checks actual postal records; attorney assesses any legal significance. Test a physical receipt returned while tracking remains incomplete and a mailing that never purchased return-receipt service. No assertion that every receipt can later be obtained. ## 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/s23-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/s23/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [mailings.csv](https://agents.paretoid.com/assets/starter-kits/s23/mailings.csv) — Blank input template with exact recipe headers. - [mailings.example.csv](https://agents.paretoid.com/assets/starter-kits/s23/mailings.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [tracking.csv](https://agents.paretoid.com/assets/starter-kits/s23/tracking.csv) — Blank input template with exact recipe headers. - [tracking.example.csv](https://agents.paretoid.com/assets/starter-kits/s23/tracking.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [receipts.csv](https://agents.paretoid.com/assets/starter-kits/s23/receipts.csv) — Blank input template with exact recipe headers. - [receipts.example.csv](https://agents.paretoid.com/assets/starter-kits/s23/receipts.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [scope.txt](https://agents.paretoid.com/assets/starter-kits/s23/scope.txt) — Blank text input worksheet. Fill its fields with approved evidence; no default assumptions are supplied. - [scope.example.txt](https://agents.paretoid.com/assets/starter-kits/s23/scope.example.txt) — Separate synthetic text input fixture; use with the example CSV files only. - [Expected fixture findings](https://agents.paretoid.com/assets/starter-kits/s23/expected-fixture-result.txt) — Read-only expected output and failure conditions for the included synthetic input files. - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/s23/README.txt) — Recipe-specific prerequisites, file mapping, prompt, setup steps, checklist and limits. - [Native input scaffold: mailings.csv](https://agents.paretoid.com/assets/starter-kits/s23/native-mailings-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: tracking.csv](https://agents.paretoid.com/assets/starter-kits/s23/native-tracking-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: receipts.csv](https://agents.paretoid.com/assets/starter-kits/s23/native-receipts-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: receipt-evidence-notes.txt](https://agents.paretoid.com/assets/starter-kits/s23/native-receipt-evidence-notes-template.txt) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: manifest.txt](https://agents.paretoid.com/assets/starter-kits/s23/native-manifest-template.txt) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: evidence-map.csv](https://agents.paretoid.com/assets/starter-kits/s23/native-evidence-map-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input mapping and source requirements](https://agents.paretoid.com/assets/starter-kits/s23/NATIVE-INPUT-MAPPING.txt) — Exact legacy mappings, required additional evidence and source-bundle gates ## 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 Join these mailing, tracking and receipt metadata tables using the supplied internal article token. Keep postal status, receipt possession and attorney review status separate. Flag missing evidence, mismatched tokens, conflicting dates and records older than the supplied review interval. Do not infer delivery from a missing update, declare valid service, calculate legal deadlines, purchase postage or request receipts from USPS. Give staff an evidence-retrieval queue. INPUTS mailings.csv: mail_id, matter_alias, article_token, mailing_date, service_purchased, approved_review_interval_days, owner_alias tracking.csv: article_token, latest_status, status_time, source_ref receipts.csv: article_token, receipt_date, receipt_locator, source_ref; scope.txt: as-of date and supplied postal-evidence coverage OUTPUT mail-review.csv: mail_id, article_token, service_purchased, tracking_status, receipt_evidence, elapsed_review_interval, inconsistency, source_refs, owner_alias. Do not determine legal service. 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.