Define the release decision
A recommender must submit a final letter to a college or application platform while preserving confidentiality and avoiding an accidental draft upload.
Send the authorized final letter through the intended application channel without exposing unrelated applicant or recommender records.
Run the control sequence
- 01Verify the exact applicant, college, application service, deadline and recommender account before upload.
- 02Confirm the final authorized file without changing its content or metadata.
- 03Use the official submission route and avoid shared personal accounts or improvised forwarding.
- 04Record submission acknowledgement, date and destination without storing the letter text in the log.
- 05Remove temporary upload copies and revoke any short-lived access after confirmation.
Preserve enough evidence
Record the dataset identifier, application cycle, source device or system, export date, manifest, responsible custodian, authorized recommenders, key location, encryption environment, recovery result, retention rule and next review date. Do not put passwords, recovery secrets or unnecessary applicant values in the decision record.
Keep the manifest, custodian, approved recipient, key-separation decision, restore result and retention owner together without copying applicant values into the record.
Keep surrounding controls visible
Local encryption does not prove the recipient identity, satisfy a deadline, preserve a waiver or control copies after the provider receives the file.
Field conditions can create extra copies on tablets, laptops, removable media, synchronization folders and recipient devices. The archive owner must address those copies separately and verify the current software release before relying on product behavior.
Questions to ask
Should the access credential travel with the dataset?
Only when the approved research purpose requires linkage and the responsible owner has authorized the same recipient. Separation is a core risk control.
Does encryption make an export anonymous?
No. Encryption restricts file access; it does not remove identifiers or eliminate reidentification risk after decryption.
Primary references
References support specific controls and do not imply endorsement.