Preflight an e-filing packet against an approved checklist
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
- Actual final candidate packet, current court/case-specific official guidance and lawyer-approved checklist with source URLs/version/date; no jurisdiction is guessed.
- Acrobat desktop for inspection; existing approved Windows PowerShell is an optional read-only way to obtain file size.
- 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
- Filing-code choices, legal sufficiency and dates require human determination. A generic checklist or AI search does not establish the applicable court rules.
- File properties alone do not prove searchability, valid signatures, complete exhibits or acceptable grouping.

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: Freeze the packet and approved rule source
Tool: Acrobat and approved checklist document
Open: Open actual packet PDFs and the lawyer-approved checklist
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Give each final file a document/version ID. Record ordered document IDs and checklist criterion IDs, jurisdiction/case scope, official URL/version/date and lawyer approval. Open every packet file and visually confirm its role/order, pages and any required exhibits. If official guidance conflicts with a rejection instruction, preserve both for lawyer review.

Expected output: Frozen packet list and current approved criterion list.
Use it next: Obtain technical facts from these exact files; do not replace them with sample manifest values.
Check: Missing current court/case checklist means blocked, not a generic pass.
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/get-started/learn-the-basics/navigation.html
https://helpx.adobe.com/acrobat/desktop/edit-documents/edit-pdf-properties/pdf-properties.html

STEP 2: Acquire technical and visual evidence locally
Tool: Acrobat; optional existing PowerShell
Open: Acrobat page navigation and Menu/File > Document properties; PowerShell Get-Item
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Read page counts from the viewer and file metadata where exposed. On approved Windows PowerShell, (Get-Item -LiteralPath 'C:\approved\packet.pdf').Length provides exact bytes without changing the file. Test selecting/copying and searching a visually known phrase on every in-scope page; record tested/untested pages, not one blanket searchable flag. Visually record supplied signature-presence checks without validating signatures.

Expected output: Manually acquired packet facts with per-file/page evidence and explicit coverage.
Use it next: Copy reviewed technical/administrative facts and approved checklist to a separate minimized TXT; raw signed PDFs remain local.
Check: A successful search on one page does not certify all pages. File size units and filenames must be exact; unknown tests stay unknown.
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://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-item?view=powershell-7.5
https://helpx.adobe.com/acrobat/using/reusing-pdf-content.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 checklist and minimized packet-fact/inspection ledger.  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
Check only this packet-fact ledger against the supplied current lawyer-approved court checklist. For every criterion return criterion_id,official_source_ref,observed_evidence,pass|exception|unknown,document_id,source_ref and reviewer_action. Treat untested pages, absent evidence, unknown units and conflicting instructions as unknown. Check only supplied administrative rules such as file grouping, order, naming, size and observed searchability/signature presence. Do not choose filing codes, calculate deadlines, determine legal or signature sufficiency, modify signed documents, infer missing exhibits or submit anything.

Expected output: Criterion-level preflight report with evidence and coverage gaps.
Use it next: Save the checked draft as filing-preflight-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check: Each pass needs an actual observation for the correct final version; conflicted instructions cannot silently resolve.
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.

Experienced filer/lawyer checks the current official instructions and complete final packet, resolves conflicts and records approval.

Expected output: Reviewed administrative preflight checklist.
Use it next: Human performs any later e-filing separately and verifies its receipt; this report promises no acceptance.
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://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.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.