How Petria works

From exhibits to filing-ready output

Petria is built around matters and jobs, not open-ended chat. Each petition moves through a defined pipeline so your team always knows what stage a case is in and what files are ready to review.

The core pipeline

1

Open a matter and upload exhibits

Create a matter for your petition type. Upload supporting documents in any language and assign exhibit labels. PII is tokenized before translation to the matter working language and drafting.

2

Submit a drafting job

Petria runs extraction, template-grounded generation, citation extraction, verification, and redraft as one coordinated job. Progress updates stream to your team in real time.

3

Review deliverables

Download the petition draft and verification artifacts as .docx files. Your attorneys review grounded output instead of starting from a blank document.

PII tokenization at intake

Petria replaces names, dates, and other identifiers with placeholders before any exhibit or intake field reaches the drafting pipeline. Inference runs on tokenized text only. Final .docx deliverables are restored for attorney review. This is implemented in the product architecture, not only described in a privacy policy.

Most immigration AI tools rely on SOC 2, encryption, and no-retention contracts. Petria adds a pre-model tokenization step so client PII does not enter generation prompts.

Outcome-verified learning

Onboarding teaches your firm's voice. Outcome learning is what happens after you file: when a petition is approved, receives an RFE, or is denied, that result is tied to the matter and adjusts emphasis on the next petition. The signal stays inside your firm. Petria does not train a shared model across customers.

  • Link a USCIS receipt after filing, or confirm the outcome manually
  • Approved, RFE, and denied results tune emphasis on future petitions
  • Compounds with voice from onboarding so associates inherit partner judgment, not a generic template

Your firm's structure, not a default skeleton

Standard and Pro draft against researched templates. Enterprise is for firms whose winning work follows a specific outline: section order, headings, where exhibits land, and which arguments get priority in each rubric. Petria learns that structure from your samples, your team approves it once, and every production job drafts the way your partners already expect.

  • Associates open a first draft that already matches your firm's table of contents and emphasis patterns
  • Section notes and exhibit placement reflect how your team actually wins cases, not a generic immigration outline
  • Approved structure is versioned through support so production jobs stay stable when you refine the playbook
  • Bring-your-own S3 (BYOB) so exhibits and deliverables stay in your bucket

See the pipeline on a real petition matter

In a guided demo we open a sample employment petition matter, upload labeled exhibits, run one full draft job, and download the verification report and Word deliverables. Bring the petition types your firm files most often (EB-1A, NIW, O-1A, and similar narrative work).

  • Exhibit upload with PII tokenization before drafting
  • Live job status from draft through verify and redraft
  • Lawyer-facing .docx outputs your team would review before filing
Request a demo