IN THIS GUIDE · Explain knowledge built through product versions and implementation work
Explain the knowledge standard and the qualifying transfer
The standard concerns special knowledge of the organization's interests and their application in international markets, or advanced knowledge of its processes and procedures. The evidence must connect that knowledge to the proposed work; proprietary technology is not a universal prerequisite. A qualifying corporate relationship, doing business and the generally required continuous year of qualifying foreign employment within the relevant three-year period also need assessment. A new office requires sufficient premises and has an initial approval maximum of one year. Separate company-specific knowledge from experience common in the occupation. The first can be supported by internal assignments, training, or process records; the second is not enough by itself.
Name the knowledge used in the rollout
Describe the specific implementation, configuration or troubleshooting knowledge being claimed. Explain the company context and the tasks it enables. Avoid a list of product names that tells the reader nothing about the employee's understanding or responsibilities. For each version or deployment, name the employee's task, the relevant source record, and the practical outcome. That avoids broad claims based only on tenure.
Connect versions to actual experience
Build a chronology of relevant assignments or training, using records the company holds. Distinguish participation from responsibility for a particular task. Do not imply the employee designed a feature merely because they attended a release meeting or worked for the business at the time. Ask what work the U.S. team cannot complete without this particular knowledge. A clear work sequence is stronger than a conclusion that replacement would be difficult.
Describe what the receiving team needs
Identify the U.S. duties and how the claimed knowledge will be applied. Include who directs the work and any customer placement. A rollout plan should remain a factual description of the assignment, not a general claim that the employee is too valuable to replace. Identify whether the assignment involves a customer site and who controls day-to-day work. Those details can affect how the role must be described and documented.
Keep the supporting explanation readable
Use a short glossary for unfamiliar terms and link examples to records. Agree on handling of confidential information before disclosure. A clear explanation of a supported claim is more useful than a long technical appendix whose relationship to the employee is never established. Prepare a confidential appendix only when needed, with a plain-language summary in the main explanation. The reviewer should be able to follow the claim without guessing.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.