How to Build Immigration Law Case Management Software

An immigration attorney managing 200 active cases across family-based, employment-based, and asylum categories tracks different form sets, different deadlines, and different government queues for each. A missed RFE (Request for Evidence) response deadline doesn't just lose the case. It can trigger a denial and bar the client from refiling. The stakes make case management software a necessity, not a convenience.

According to USCIS, over 10.6 million immigration petitions and applications were filed in fiscal year 2024. Each one has its own deadlines, form versions, and priority date tracking requirements.

"Immigration practitioners face a unique compliance burden. The overlap of federal filing deadlines, monthly Visa Bulletin updates, and state-specific requirements creates a system where manual case tracking is not just inefficient -- it is a liability." -- Cyrus Mehta, Managing Attorney at Cyrus D. Mehta and Partners, quoted in Immigration Daily, 2024

What immigration case management software does

The American Immigration Lawyers Association estimates that over 15,000 immigration attorneys practice in the US. Most manage case loads of 100-300 active matters simultaneously across multiple visa categories and government queues.

A proper immigration case management system covers the full lifecycle from intake to resolution.

Case intake captures visa category, petitioner data, beneficiary data (including minors with separate parent records), assigned attorney, and conflict-of-interest check against existing clients.

Form pre-population pulls case data into USCIS forms: I-130 (Petition for Alien Relative), I-485 (Adjustment of Status), I-765 (Employment Authorization), I-131 (Advance Parole), I-539 (Extension/Change of Status), I-140 (Immigrant Petition for Alien Workers), and DS-260 (Immigrant Visa Application). Attorneys fill the case record once. The system writes the form fields.

Deadline tracking monitors RFE response deadlines, USCIS filing windows, visa bulletin cutoff dates, interview dates, and EAD expiration dates. Each deadline gets configurable lead-time alerts, typically 30, 14, and 7 days before due.

USCIS status tracking runs daily checks against receipt numbers attached to each active case. When USCIS updates a status, attorneys get a notification without manually checking each case.

Document checklist generates a required-document list by case type and gives clients a secure upload portal to submit their own documents. Attorneys see what's missing at a glance.

Attorney task management handles court dates, interview prep tasks, and internal deadlines on a shared calendar across the firm.

Billing tracks time by matter, generates invoices by case, and logs expenses against each file.

MVP vs. full platform

MVP (15 to 20 weeks)

• Case records with visa category, petitioner, beneficiary, receipt numbers, and priority date

• Deadline tracking with configurable alerts for RFE deadlines, filing windows, and interview dates

• Form pre-population for the 7 core USCIS forms

• Document checklist per case type with client upload portal

• USCIS case status automation via daily cron

• Attorney task calendar

• Basic billing by case

Full platform additions

• Visa Bulletin priority date monitoring with automated client alerts (details in the technical challenge section)

• Multi-attorney workload management with capacity views

• Integration with USCIS ELIS and MyUSCIS where APIs exist

• E-filing integration for supported form types

• Matter-based billing with time tracking and expense management

• Deportation defense case types with separate workflows

• Reporting on case volume, filing activity, and revenue by case type

Core architecture

The data model has four primary entities.

Case record stores: case_type (family, employment, asylum, naturalization), petitioner_id, beneficiary_id (may reference a minor with a separate parent link), assigned_attorney_id, receipt_numbers (array, since one matter can generate multiple filings), status, and priority_date (relevant for employment and family preference categories where a visa queue exists).

Form record stores: form_number, version_date (USCIS updates forms periodically; version matters for filing validity), case_id, field_values (JSONB, because form fields differ completely between form types), and status (draft, complete, filed).

Deadline record stores: case_id, deadline_type (RFE_response, filing_window, interview_date, EAD_expiration), due_date, alert_days_before (configurable per deadline type), and status (upcoming, triggered, completed, missed).

USCIS status check uses a daily cron that queries all receipt numbers attached to active cases, calls the USCIS Case Status API for each, stores the latest status response in a uscis_status_log table, and compares it against the previous stored value. If the status changed, it creates an attorney_notification record and queues an email or SMS.

The client portal is a separate login scope. Clients authenticate via Auth0 with a restricted permission set. They see only their own case, their document checklist, and a file upload interface. They cannot see case notes, billing data, or other clients.

The hardest technical challenge

RaftLabs has built legal case management systems where deadline accuracy was a first-class requirement. The consistent finding: Visa Bulletin tracking is where most immigration software either earns or loses attorney trust within the first 90 days.

Visa Bulletin priority date tracking is the most complex piece of this system, and the most valuable.

USCIS publishes a monthly Visa Bulletin at the start of each month. Each bulletin contains two charts: Chart A (Dates for Filing, used when USCIS accepts advance filing) and Chart B (Final Action Dates, the hard cutoffs for approval). Each chart lists cutoff dates for every visa preference category, broken down by country of birth: China, India, Mexico, Philippines, and All Other Countries.

A client with an EB-3 India priority date of January 2019 can file Form I-485 when the Visa Bulletin's EB-3/India cutoff advances past January 2019. That cutoff changes every month. Some months it advances. Some months it retrogresses. Attorneys managing preference-category cases need to know when their clients' dates become current, and when they retreat.

Build a Visa Bulletin importer as a monthly cron. The cron fetches the Visa Bulletin PDF from the USCIS website, parses the date tables using pdf-parse or pdfjs-dist, and stores the result as a visa_bulletin record keyed by year and month, with a JSONB column holding a nested map of category -> country -> cutoff_date.

USCIS uses a consistent table format for the bulletin, so the parser can target known column headers (the five country groups) and row labels (preference categories). Build the parser with a known-format assumption and a validation step that alerts if the parsed table doesn't match expected dimensions, which flags bulletin format changes before they cause silent errors.

After each import, run a query against all cases with a priority_date and a visa category that appears in preference charts. For each case, compare the new bulletin's cutoff date for their category and country against their priority date. Four cases to handle:

1. The client was not current last month and is now current: create an alert, "Client [X] is now current for EB-3/India. Recommend filing I-485."
2. The client was current last month and remains current: no alert needed.
3. The client was current last month but the date retrogressed past their priority date: create an alert, "Client [X]'s priority date is no longer current. Do not file until bulletin advances."
4. The client is not current and remains not current: no alert needed, but log the current gap for dashboard display.

This automation prevents both missed filing windows (which delay clients' green card timelines by months or years) and premature filings (which USCIS rejects and which firms must then explain to clients).

Build costs and timeline

MVP: $150,000 to $250,000 over 15 to 20 weeks

Typical team: 1 project manager, 2 backend engineers (Node.js + PostgreSQL), 1 frontend engineer (React), 1 QA engineer. The range accounts for form pre-population complexity. Pre-populating 7 USCIS forms requires mapping case fields to each form's specific field identifiers, which takes 2 to 3 weeks of careful engineering.

Full platform: $300,000 to $480,000 over 25 to 34 weeks

Adds Visa Bulletin automation (3 to 4 weeks), multi-attorney management, matter billing, and deportation defense workflows. The upper end applies when e-filing integrations or USCIS API partnerships require additional compliance review.

Ongoing running costs: $2,000 to $5,000 per month for hosting, storage (document volume is high), cron infrastructure, DocuSign API usage, Twilio SMS, and Auth0 tenant costs.

Build vs. buy

Four established products cover the immigration vertical.

Docketwise at $65 to $130 per user per month offers strong form automation and client portal features. It handles most standard immigration workflows for small to mid-size firms.

ImmigrationTracker at $50 to $100 per user per month is a case-centric system with deadline tracking and document management, suited for firms prioritizing simplicity.

INSZoom at $75 to $150 per user per month adds compliance tracking and employer-sponsored case management, making it popular with corporate immigration practices.

Cerenade at $100 to $200 per user per month is the most feature-complete off-the-shelf option, with billing, time tracking, and a client portal included.

Build custom when you have 10 or more attorneys and need intake workflows or Visa Bulletin automation that existing tools don't support at the field level. Also build custom when the product itself is the business: legal tech startups targeting the immigration vertical need custom architecture to support their own multi-tenant model, white-labeling, or API access for enterprise clients.

Tech stack

Backend: Node.js with TypeScript. PostgreSQL for the primary data store, with JSONB columns for form field values and visa bulletin tables. node-cron for daily USCIS status checks and monthly Visa Bulletin imports.

Frontend: React with TypeScript. Two separate apps: the attorney-facing case management interface and the client-facing document portal (separate Auth0 tenant configuration, restricted permission scope).

Form generation: Puppeteer renders pre-populated form data into HTML templates that match USCIS form layouts, then outputs PDF files attorneys can review and submit. This avoids the complexity of writing directly to official PDF form fields, which require strict AcroForm compatibility.

Visa Bulletin parsing: pdf-parse for text extraction, with a custom parser targeting USCIS's consistent bulletin table format. Add a validation step that compares parsed row and column counts against expected dimensions.

Document storage: AWS S3 with private bucket configuration and pre-signed URLs for client uploads. Document sensitivity is high (passports, tax returns, birth certificates), so treat it with HIPAA-adjacent controls even though immigration documents aren't formally HIPAA-regulated.

Client signatures: DocuSign for G-28 (Notice of Entry of Appearance as Attorney) and retainer agreements. Both require client signature before representation begins.

Deadline alerts: Twilio SMS for high-priority deadline alerts (RFE responses, filing windows) plus email via SendGrid. Attorneys configure which alert types go to SMS vs. email.

Authentication: Auth0 with two separate application configurations: one for attorney staff with full case access, one for the client portal with case-scoped access limited to the client's own matter.