IN THIS GUIDE · Keeping duty evidence current when a cross-border project keeps changing scope
Start with the L-1B eligibility and application overview
Treat the duty description as a live document
The written account of duties should live somewhere the project manager can find it, not in an email thread from the time of the filing. Review it on a set rhythm — at each phase change, or quarterly, whichever comes first — and note what has moved. Most revisions will be minor and change nothing. The value of the habit is that when a genuinely significant change arrives, someone notices it while there is still time to seek advice. Give the document an owner by name rather than by role, since roles change hands and the file then belongs to nobody. The owner's job is small: read the description each quarter, ask the project manager what has moved, and record the answer even when the answer is nothing. A run of quarters recorded as unchanged is itself useful evidence.
Learn which changes actually matter
Not every adjustment is significant. Changes worth raising include a move to a different worksite, work performed mainly at a third party's premises, a shift from applying the organization's own methods to general project work, the addition of substantial supervisory content, a change in which entity directs or pays the person, and an extension beyond the period described. If in doubt, raise it; the review is cheaper than the correction. Add one more to that list: a change in who the work primarily benefits. Knowledge applied to the organisation's own products and procedures sits differently from the same skills sold as general consultancy to an unrelated customer, and a project that gradually reorients toward external clients can cross that line without a single decision that looks significant.
Put a review gate into the project's own process
Cross-border projects already have change control. Add one line to it: scope changes affecting a transferred worker's duties, location, or supervision go to a named owner before they are approved. That owner decides whether counsel needs to see it. Without this, changes get agreed in a delivery meeting by people who have never read the filing and have no reason to know it exists. Name the fallback in the same line of the process: if the review cannot be completed in time, the person stays on the existing scope until it is. Without a stated fallback, a change-control gate becomes advisory the first time a delivery date is threatened, and it is precisely then that it matters.
Keep a record of what actually happened
Alongside the current description, keep a short chronology: what the person worked on in each period, where, and under whose direction. It takes minutes a month and answers questions later that memory cannot. It also makes the next filing easier, whether that is an extension, an amendment, or a case for a different person. Store it where it survives the departure of the manager who kept it. The chronology also protects the individual. Where an extension is sought, the question is what the person actually did, and a contemporaneous log answers it in a way that a manager's recollection two years later cannot. Note the maximum period of stay as well: L-1B is limited to five years, and time already spent in L status counts toward it regardless of how the project has evolved.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.