Choose a relevant sequence and explain the record links, the applicant’s decision and the operational consequence. Remove unnecessary identifiers without removing the logic of the example.
Avoid an unexplained export of the entire database
A large data file can conceal the issue. Provide enough context to distinguish the employee’s process judgment from a routine search result and identify work performed by others.
Explain which U.S. duties would use that knowledge and why the supporting examples are relevant. Narrate the investigative path the applicant actually followed, including what was checked first and what was ruled out along the way, rather than presenting only the final finding as though it were obvious from the outset. A short before-and-after comparison showing the system's condition prior to the applicant's intervention and afterward can make the applicant's specific contribution easier to follow than a single end-state screenshot. Where records must be redacted, preserve the structural logic of the trace, such as the sequence of steps and the relationships between them, so the redaction removes identifying detail without erasing the reasoning it was meant to illustrate. Keep the example proportioned to what a reader needs to follow the applicant's judgment, since padding it with unrelated detail can bury the actual point in the same way an unexplained bulk export does, regardless of how much raw material either one actually contains.