CaseStatusTracker resources

USCIS Case Data Reading Guides

Updated 2026-10-15 · Editorial review pending

Start with the structure and limits of user-provided case JSON, timelines and timestamp comparisons.

Getting started: read the case object

The reader accepts either a case object or a data envelope containing one. The events field must be an array. An empty array is valid and means the input provides no events; it does not establish that no agency activity occurred. The tool accepts files up to 1 MB and 2,000 events.

JSON & event codes: preserve uncertainty

An eventCode is a label in the supplied data. The current dictionary has no reviewed meanings, so the tool marks every code Not verified. Do not infer a processing stage from a familiar-looking abbreviation. Look for official notices when you need to establish an action or request.

Status changes: compare like timestamps

Use ISO timestamps with an explicit time zone. The reader normalizes valid times to UTC. A record creation timestamp may differ from the time an event occurred. Missing or conflicting dates prevent a reliable silent-update conclusion.

A fictional example

A record updated at September 18, 2026, 14:00 UTC with a latest event at September 15, 2026, 09:15 UTC has a timestamp gap of about 3.20 days. That calculation shows only a difference between supplied timestamps; it cannot tell you what changed or what decision will follow.

Next steps

Use the sample input to explore the tool before entering your own data. Check warnings, review undated records, and compare important information against official USCIS notices. Detailed form and event-code articles will be published only after editorial review.

Independent service. Not affiliated with USCIS or the U.S. government.

Read your JSON locally →