Skip to content
APPLICATION ANSWERS · L-1B FIELD GUIDE

What if the U.S. rollout changes to a different product version?

Sources checked:

THE DIRECT ANSWER

Explain the change and have the assignment reassessed where relevant. The earlier preparation may describe knowledge or duties that no longer match the proposed work.

Compare the old and new responsibilities

Identify which tasks remain, which are new and what evidence shows the employee's experience with them. Save the revised assignment plan. The project team should not assume that a similar product name means every immigration fact remains unchanged.

Hypothetical example: A company that makes automated grain-sampling equipment wants its sensor-diagnostics specialist in the United States before a software deployment, but the deployment date may move. The first review identifies fixed facts—employment dates, entity relationship, and known knowledge records—and variable facts—customer installation dates and final duties. Dated assignment records settle past knowledge; the final statement of work settles how it will be used. Preserve both versions if the schedule changes, and update the filing rather than assuming the original product label covers new tasks. The usual problem is collecting documents late, after technical personnel have moved on or source files are overwritten. The employee generally needs one continuous qualifying foreign year in the preceding three years, and L-1B time is generally capped at five years. Build evidence collection into the project schedule. Keep this L1B timing record aligned with final filing facts and issued source materials, then preserve a dated copy internally before formal submission for future reference and review by responsible staff if questions arise later.