A syllabus may describe instruction without explaining operational responsibilities or supervision.
Add the missing work account
Provide relevant assignment and worksite records. Distinguish the employee’s own contribution from a course the organization offers generally.
Internal material the employer owns: the platform documentation, recipe and protocol libraries, training records showing how the knowledge is acquired and by how few, development history and investment, and a statement of how many staff worldwide hold it. Dated artifacts from the company's own systems: version-control histories, design specifications, patent or invention records, validated procedures, training materials and internal staffing data. Use whatever contemporaneous evidence exists — internal notes, project files, correspondence, or third-party records — to document how the knowledge was developed and applied. More detailed exhibits may describe training modules, project phases, system architecture, quality controls, or implementation decisions without publishing sensitive source code or customer data. Gather dated internal manuals, controlled revisions, training records, project assignments, supervisor declarations grounded in examples, and work products that can be disclosed lawfully. Attach the table of contents, the sections the employee authored with their revision history, and any passage that expressly leaves a decision to a qualified operator, together with a short statement explaining what each attachment proves. 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.