Use an appropriate, accurate way to explain the relevant work while addressing legitimate confidentiality constraints.
Preserve the substance of the example
A generic statement that details cannot be shared may leave the knowledge claim unexplained. Review whether relevant records, permitted summaries or other support can establish the actual contribution without inventing facts.
Design documents, release notes, internal training material, project assignments and performance records that show the specialist's knowledge of the company's own system, together with a letter explaining why that knowledge is required at the U.S. site. Describe what the knowledge does and how it was acquired, and attach documents that prove existence and authorship — cover pages, version histories, training records — rather than the technical content itself. The design and test record with authorship identified, internal procedures and work instructions, training material, any patent or trade-secret registers, and payroll records that establish continuous employment. Evidence of specialized knowledge should identify the company product, process, or procedure involved and explain why the later employee’s understanding is advanced or special, rather than merely showing long industry experience. Sequence the evidence from pre-existing materials outward: internal manuals, version histories, training records, deployment tickets, customer requirements and declarations from knowledgeable supervisors. Add the training records showing how long an internal technologist takes to reach that level, because time-to-competence is the most concrete evidence that the knowledge is not readily available in the labour market.