An immigration timeline: entry, request, decision and document

The event sequence crosses agency boundaries

Visa issuance is a Department of State event, admission is a CBP event and many domestic benefit requests are USCIS matters. A petition approval may concern a relationship or classification without granting permanent residence. The timeline should preserve those differences so an old visa, a new receipt and an unrelated approval are not treated as one continuous permission.

A source column is as important as a date column. Write passport stamp, complete agency notice or personal recollection as appropriate. That allows a reviewer to see which events are documented and which need corroboration without confusing uncertainty with an adverse legal conclusion.

A decision and a card shipment are not the same milestone

The I-765 owner distinguishes authorization and EAD-related records, while a delivery update concerns a physical document. Place the underlying request, actual decision and any production or delivery information on separate rows. If the timeline cannot show which request a notice addresses, that missing connection is a question to resolve rather than an invitation to assign a broader legal effect.

Create one row per event, attach its source and mark any missing document. Keep overlapping requests on separate rows. State uncertainty explicitly so a reviewer can distinguish a missing record from a conclusion that no event occurred.

Evidence that explains this particular question

Admission event: Preserve the record tied to each arrival rather than one undated status label. Benefit request: Note the request and filing-related record without assuming its legal effect. Decision notice: Connect the actual decision to the request it addresses. Departure evidence: Tickets and other travel records may help reconstruct movement but need corroboration where uncertain.

For example, list petition approval, a later residence filing and card delivery as separate events, each attached to its actual case. If an online message says approved, the timeline should show which request it concerns. A family relationship decision should not be relabeled as every later benefit.

The boundary to resolve before the next step

Give each timeline row an event label and owner. A relationship approval belongs beside the petition it decided, while a card-production message belongs beside its underlying benefit decision.