Skip to content
FOR SPECIALIST TEAMS · BOWDENBowden

Your expertise.Across borders.

For a Bowden employee proposed for specialized-knowledge work, the file should explain both the actual organizational knowledge and the qualifying foreign employment. Repeated visits or a long relationship with the company do not establish those conditions by themselves.

Talk about L-1B
PurposeSpecialised knowledge transfer
Company linkQualifying related businesses
EvidenceSpecific knowledge and duties

IN THIS GUIDE · Distinguish the employee’s foreign knowledge history from a U.S. travel schedule

Start with the L-1B eligibility and application overview

01

Show the knowledge used by the proposed work

L-1B covers special knowledge of the organization’s products, services, research, equipment, techniques, management or other interests and international application, or advanced knowledge or expertise in its processes and procedures. Knowledge need not universally be secret, unique or proprietary. Describe the employee’s genuine experience and its relevance to the actual U.S. assignment.

02

Separate U.S. visits from qualifying foreign time

The ordinary rule generally requires a continuous full-time foreign year in the relevant preceding three years in managerial, executive or specialized-knowledge capacity. Brief U.S. visits need not break continuity, but the U.S. days do not count toward the year. Company tenure and qualifying foreign employment are not necessarily the same total.

03

Keep the entity and customer-site conditions complete

Actual ownership and control must establish qualifying related entities, with regular, systematic and continuous business in the United States and at least one other country during the stay. Principally unaffiliated-site work is ineligible if the unaffiliated employer principally controls and supervises the worker, or if it is essentially labor for hire rather than connected with the petitioner’s product or service requiring specialized knowledge. Short rotations do not waive these rules.

04

Identify the office stage independently of visit frequency

A U.S. organization doing business for less than one year is a new office. L-1B then needs sufficient premises and financial ability to pay the employee and begin business; initial approval is limited to one year. The number of prior visits is not the definition of doing business or a guarantee that future tasks are authorized.

05

Sort general skill from company-specific knowledge

Where the assignment would place the employee at a client site, say so, because offsite placement carries specific supervision and labour-for-hire restrictions that need a proper legal assessment. Manufacturer training on a purchased controller, certification on a third-party platform, and industry qualifications are all valuable and none of them is the company's own knowledge. Ask which records would allow a new reviewer to distinguish the knowledge from general industry skill: training histories, role progression, technical correspondence, controlled procedures or concrete examples may help. Training sequence, implementation records, system access, and examples of problem solving can show how the knowledge differs from ordinary familiarity. Processes change while someone is away, and a file claiming current advanced knowledge of a procedure introduced during the absence will not survive a question about when and how the person learned it. Training records, project histories, internal manuals, and knowledgeable supervisor statements may be useful when they accurately identify the employee's contribution. Branding alone does not establish that knowledge remains applicable, and a name change alone does not prove the employee must learn an entirely different system. A first review should produce a dated knowledge map: what the employee learned, where it was applied, which record corroborates it and which U.S. duty will use it.

06

Ask whose product or process the knowledge concerns

Provide the specialist's training history, the projects they led, and a statement of how many employees hold comparable knowledge. Familiarity with a widely used programming language, a common database or a public sensor protocol is industry knowledge. A controlled workflow, revision history, and documented exceptions may substantiate process knowledge; product-release records and cross-border implementation material may substantiate knowledge of the offering. Where the honest answer is broad familiarity built by time rather than advanced knowledge of the organization's own methods, say so early, while other routes can still be discussed.

L-1B · BOWDEN

YOUR QUESTIONS.
A CLEARER START.

KEEP EXPLORING

A LITTLE MORE CLARITY.