Describe the actual capability and support it with understandable work evidence. Public product information can provide background, while internal implementation records, process explanations and the employee’s contributions establish the specific knowledge claim.
Use a layered explanation
Begin with an accessible description, then attach selected technical material with annotations explaining relevance. Distinguish a standard vendor feature from the employer’s use of it and from the employee’s own knowledge. Avoid submitting a large vendor manual as if its length proves expertise.
Where advanced knowledge is claimed, explain the internal comparison as well. Build the explanation in layers so that a reader without technical background can follow it and a technical reader can verify it. The top layer is a plain statement of what the employee knows and why it matters to the business.
Beneath it sit short descriptions of specific work — a problem, what was done, what the outcome was. Beneath those sit the underlying records: procedures, configurations, incident logs, design notes, customer correspondence. Caption each so that its purpose is stated rather than inferred.
Where a colleague can attest to the employee's role in a piece of work, a specific account with dates carries more weight than a general endorsement. And prefer documents created at the time over material assembled for the petition, since the former are evidence and the latter are argument.