A Transfer Permission Protocol for Game Film With Personal Data

Game film moves constantly during recruiting. A parent sends a full match file to an editor. A club coach shares a tagged playlist with a family. A recruit forwards a link to a college staff member. Each move feels routine, but the file often carries more than game action. Scoreboards show school names, rosters list ages, team portals display contact details, and shared folders inherit permissions that linger after the season.

A transfer permission protocol gives that movement a deliberate pause before the file leaves its current location. It does not add heavy legal framing. It asks three practical questions every time: who is authorized to share this specific file, who actually needs it for the recruiting task, and what access setting matches that need without over sharing.

Clarify ownership before the first transfer

Two owners matter. The content owner is the person or organization that created the recording and controls its distribution. That is often the school athletic department, the club, or a tournament operator. The data owner is the family responsible for the athlete's personal information that appears in or alongside the film, such as roster data, academic references, or contact details stored in the same folder.

Both owners need to be named in a brief permission note before the first external transfer. For a typical high school match filmed by a parent from the stands, the parent may be the content creator and the family is the data owner, so the permission is essentially internal. For a club showcase filmed by the event operator, the club or operator may restrict redistribution, and the family needs explicit permission to share outside the team.

A support VA handling file organization can record that ownership decision in a transfer log with four columns: file identifier, content owner, permission source, and permission date. The identifier can be the file name plus recording date and opponent, for example 2026-08-12_Central_High_Varsity_Full_Match.mp4. That level of specificity prevents the common confusion where one good permission gets stretched to cover an entire season of unrelated files.

Where ownership is unclear, the default is to ask before sharing. A short note to the coach or event contact such as may we share the August 12 full match file outside the team for recruiting review, and if so through which method, usually produces a clear answer within a day. Keep the response beside the log entry with its date.

Match the sharing method to the actual recipient need

Not every recipient needs the same access. Matching the method to the need limits exposure while keeping the recruiting workflow smooth.

The distinction between view and download matters more than it appears. A view link serves a coach evaluation purpose and reduces further redistribution. A download copy is appropriate when an editor needs to cut footage, but it should be time limited where the platform allows. A folder link to an entire season is almost never needed by a college coach who asked for one match.

A VA preparing a transfer can set these defaults: each college thread gets a link to exactly the file or files that the message references, not to the family master archive. Each editor transfer gets a dated folder for that season's source files, with a note that the link expires on a specific date. Each transfer entry records the method used, the setting chosen, and the expiration if any.

Check every link while signed out before sending. Open the link in a private browser window and confirm that it shows only the intended file, that it plays without requiring a sign in where the coach is expected to view it, and that the preview does not surface a roster sheet or contact list stored in the same folder.

Write the transfer record so future review is easy

A strong transfer record answers four questions without opening the file.

First, what was shared. Use the file identifier, match date, opponent, and length if known. A title such as Highlight reel v2 with August 12 and 19 clips is more useful than final_edit3.

Second, when and through which channel. Include the send date, the platform or link provider, and whether the access was view or download.

Third, to whom and why for this recruiting task. Name the recipient role, not just the name where privacy suggests, and state the purpose in plain terms such as requested evaluation of outside hitter positioning.

Fourth, what permission supports the share. Reference the permission source from the ownership check, with its date.

A one row example reads like: August 12 full match, 64 minutes, shared August 23, 2026 via view link to college program for routine evaluation, permission from high school coach via message August 10. That row lives in a running transfer log sorted by date, separate from the inbox. It is not the sent email itself. It is the family's evidence that the share was intentional and authorized.

The VA can keep this log in a simple spreadsheet with filters by athlete, season, and opponent, so a later question about who received which match can be answered in seconds. The athlete should review any log entry that references a college program to confirm the purpose line matches the actual outreach intent.

Protect personal data that travels with film

Film rarely travels alone. The same folder often holds roster exports, grade reports used for eligibility checks, contact sheets, and medical clearance emails. Those documents should not ride along with a film transfer unless the recipient has a concrete need and the family has chosen to share that specific record.

Two habits prevent most over sharing.

First, keep film and sensitive documents in separate storage locations with separate sharing settings. A film source folder should contain only video files and a simple index sheet. A personal records folder should be owner only and never linked in a coach message. When a task truly requires both, create a short lived transfer packet that contains only the needed items, name them explicitly, and expire the link.

Second, check any film preview for visible personal information before sending. Scoreboards are expected. A grades tab visible in a screen share, a phone number on a whiteboard behind the huddle, or a roster sheet open on the same desktop as the video player are not. Close unrelated files, use a clean desktop for preview, and crop screen recordings to the game window only.

If a file was shared beyond its intended scope, handle the correction directly. Revoke or expire the link where possible, send a brief factual correction to the recipient noting the updated link and access scope, and record the correction with its date. Do not forward the larger personal record to another recipient to fix the first error. Fix scope where it started.

Routine maintenance that keeps the protocol alive

A protocol only matters if it survives the season. Three periodic checks help.

After each major filming weekend, confirm that new files are named consistently, ownership notes are complete for that weekend's files, and no transfer outside the agreed methods occurred during rushed post game sharing. After each month of outreach, review the transfer log for entries where permission is still pending or where a link was set without an expiration. After the recruiting cycle ends for a given program, expire any active links tied to that program and archive the log section.

A VA can own the first two checks as administrative tasks and bring any unresolved permission item to the family with a clear owner and due date. The athlete approves the recipient purpose line for any college thread. The family approves any sharing of personal records beyond film itself.

Frequently Asked Questions

Does the family need written permission for film a parent recorded from the stands?

When the recording is clearly created by the family with its own equipment at a public event, the family typically controls that file. When the recording comes from a school, club, or event operator, or when league rules restrict distribution, ask the content owner first and record the response.

What if a college coach asks for a full season folder rather than one match?

Share a view link to a limited set that matches the stated need, with a clear index that names each included file. If the request is open ended, offer one or two additional matches and ask which specific evaluation setting would be most helpful, rather than opening the entire archive.

How long should a transfer link remain active?

For a single coach review, a link that expires within a few weeks is usually sufficient. For an editor actively cutting highlights, extend the folder window to the named editing period, then expire it. Record the expiration date beside each entry and check it during the monthly review.

Where does this work sit inside recruiting support?

A VA can maintain the naming, indexing, permission notes, and transfer log, and can generate the sharing links with the correct access setting. The athlete and family own the decision about what to share with a college program and approve each transfer purpose before it moves.