How it works

Four things happen, in order, for every case.

Nothing here depends on someone remembering to check. It runs on its own, and it writes down what it did.

1. The check

Each A-Number, checked against the court’s record every working day.

On federal working days, EOIR Tracker asks the immigration court’s public case system about each A-Number your firm carries — the same record the court publishes for that number. It stands down on weekends and federal holidays, because court staff do not enter changes then and a check that day would say nothing new.

Every attempt is written down: when it ran, and whether it found a change, found nothing new, or failed to complete. So “no news” on a case is a fact with a date on it, not a hope.

What’s recorded

When each check ran
How it ended: changed, unchanged, or failed
The court’s record as it stood

2. The notice

When the court moves a hearing, your firm and your client both hear.

A change is one of a few things: a hearing set where there was none, a hearing moved, a hearing no longer listed, a decision entered. Each becomes its own email to your firm that says only what changed, with the case named by A-Number and the new date and time in the court’s city.

Your client receives a notice too, in English or Spanish, written for the person rather than the practitioner: what changed, when the hearing now is, and where. It goes to the address on the case; the firm’s copy goes to the login email and any others you register for the team.

What’s recorded

Each notice sent, to whom, and when
Which change it described

3. The calendar

Your calendar follows the court, at the court’s local time.

Connect Google Calendar or Outlook once. From then on each upcoming hearing on your docket is an event in that calendar, created at the time the court set, in the court’s own time zone — worked out from the hearing address, so a 1:00 PM hearing in San Francisco reads 1:00 PM San Francisco whichever zone you open the calendar in.

When the court moves the hearing, the event moves. When the court removes it, or you archive the case, the event is cancelled. Past hearings are never created or touched.

Each member of the firm has their own switch: follow the firm’s hearings in their calendar, or not. If the calendar provider ever refuses a token, the connection is marked as needing reconnection rather than quietly dropped.

What’s recorded

One event per case, per connected calendar
Moved, cancelled, or left alone — and why

4. The acknowledgement

The client confirms. The file remembers.

Each client notice carries a link that only that notice knows. It opens a page in the client’s language showing that one case, what changed, and a single button. Pressing it records the confirmation: the time, the page language, and the network the request came from.

A link that is merely opened does not count. Mail scanners and link checkers open links automatically, and recording on the visit would file confirmations for clients who never read the message. Only the deliberate press is recorded.

Your firm is emailed when the client confirms, and a certificate is produced and kept with the case. It is generated once, at the moment of confirmation, and stored with its checksum; correcting the client’s name next month does not alter it, because a document that changes after the fact is not evidence. Names render in the client’s own script.

The purpose is plain. When a former client says they were never told about a hearing — the question a Lozada motion turns on — the file answers.

What’s recorded

The time of the confirmation and the page language
The IP address and browser it came from
The certificate, frozen with its checksum

Ready to see it on your own docket?

Get started

Or compare plans first.