Legal & Immigration
Translation for legal and immigration work. Audit-ready, format-aware, fast.
Contracts, depositions, USCIS submissions, certified translations. Files come back with tags intact, locked content untouched, and an auditable QA report your reviewer can hand to the client.
Who uses Fily for legal & immigration
Law firms, immigration attorneys, certified translation providers, court reporting agencies, and corporate legal teams that move contracts, depositions, USCIS documents, foreign judgments, and discovery materials across languages.
What hurts today
- Contract language has zero room for interpretation drift — defined terms must propagate exactly across hundreds of pages.
- Deposition audio comes in low-quality phone recordings; transcription has to be verbatim, with speaker labels, for filing or discovery.
- USCIS submissions require certified translations following specific formatting and certification statement requirements.
- Scanned ID documents, foreign judgments, and old contracts arrive as image-only PDFs.
- Tracked changes from opposing counsel must be preserved across translations of redlines.
- Confidentiality is non-negotiable — no model training, no third-party sharing.
How Fily fits this workflow
Defined-term consistency enforcement
Glossary cascade enforces defined terms across an entire matter: "Buyer", "Seller", "Effective Date" stay byte-for-byte consistent across documents, regardless of length.
Verbatim deposition transcription
Audio recordings get state-of-the-art diarized transcription with speaker labels, timestamps, and optional verbatim preservation of disfluencies for discovery use.
Scanned PDF + image-only document OCR
Old contracts, foreign judgments, and scanned IDs run through dual-backend OCR. Output as searchable PDF or DOCX with reconstructed layout.
Tracked changes preserved
Redline DOCX with <w:ins> and <w:del> tracked changes round-trips through translation without losing the change history. Reviewer keeps the audit trail.
QA report for chain-of-custody
Every job ships with a 12-step QA report showing glossary hits, forbidden-term replacements, and segment-level scoring. Attach to client deliverables.
On-prem deployment available
For confidentiality-sensitive matters, Fily runs on your infrastructure with the same pipeline. Files never leave your network.
Shipped, not roadmapped
Pipelines we built for work like this
Real legal & immigration workflows that didn't fit a standard pipeline — so we built one.
docx_tracked_delta_v2
Tracked changes that survive translation
An LSP had already translated v1 of a Word doc to Spanish. The client edited the English with tracked changes and wanted v2 in Spanish with the same redlines applied — not a fresh re-translation.
We built a delta-aware DOCX pipeline that ingests EN + redlines + ES_v1 and emits ES_v2 with the equivalent insertions and deletions in Spanish. The reviewer keeps the audit trail — hours instead of days per round.
pdf_qa_12step_v2 + image_qa
Dual-backend OCR for impossible scans
Healthcare LSPs were hitting walls with 150-DPI faxed medical records that generic OCR failed on silently — returning blank pages without warning.
A fallback chain: a frontier vision-language OCR as primary, automatic failover to an alternate backend on truncation or JSON errors. Page-level retry, confidence flagging, and handwriting detection in the QA report.
bring your own template
Transcripts in your client's branded document
Sonix, Rev and Otter hand back their default DOCX. Then a PM spends an hour re-formatting into the client's template: logo, case number, signature block, footer.
Upload the client template once. Every future transcript for that client lands inside it — speaker labels, timestamps and translations placed exactly where the template expects them. Zero re-branding.
mendoza_fda_delta
Delta translation against an approved TM
A regulated-content client updates FDA-reviewed documents constantly, but only a few lines change each cycle. Re-translating the whole file risked drifting away from language a regulator had already approved.
A delta pipeline that diffs the new source against the previous version, translates only what changed, and locks everything else to the approved TM byte-for-byte. New wording gets the AI; approved wording never moves.
Got an edge case your current vendor can't handle?
Talk to our Account Manager teamFormats this industry usually translates
All ship through the same 12-step QA pipeline.
Ready to test it?
Upload one file. See it come back. No card. No demo form.