An Ownership Log for Recruiting Video File Transfers

A recruiting video file rarely stays in one place. The source match sits on a parent's phone after Saturday. A copy moves to a family laptop on Sunday. An editor receives a folder on Monday. A college coach receives a single link on Wednesday. Each move is quick, but after a month of movement the family often cannot answer a simple question: who can still open which file and under what permission.

An ownership log answers that question without adding heavy administration. It tracks the file, its owner, the permission granted for a specific transfer, and when that permission should expire.

Define the file and the owner at the moment of creation

Ownership begins at creation, not at sharing. For each source match, record five fields immediately after the file lands in the family archive.

That record lives in the family file index, not in the inbox. When a later transfer moves a copy, the index stays as the reference for what was transferred, rather than relying on the transfer email to describe the file.

A VA keeping the index can populate it after each match weekend by normalizing file names, confirming that each file plays and that its duration is recorded, and noting the owner verbatim. The owner field for a school or event feed should name that organization exactly, because permission to share that file may differ from permission to share a parent recorded file.

Two ownership mistakes create most later problems. One is to treat every file as if the family owns it, when a school feed or showcase operator controls redistribution. The other is to treat a file received from a teammate's parent as if it carries the same permission as the family's own recording. Both are solved by a literal owner field that names the actual source.

Record each transfer as a permission, not just a send

A send line says a file moved. A permission line says who is allowed to access or share it, for what purpose, and until when.

For each transfer, create a row with these columns.

The permission granted column uses plain access terms the platform actually offers. View only means the recipient can play or view but not download a new copy. View and download means the recipient can keep a copy for editing. The family should choose view only for routine coach evaluation and reserve view and download for editors who need to cut.

The expiration column turns a one way send into a bounded grant. Many file sharing tools allow an expiration date, and others allow manual revocation by turning off the link. The log should state which method applies and the intended end date, so the family can follow through.

A VA preparing a transfer can draft this row before sending, hold it for approval, and then complete the date sent and expiration fields immediately after the transfer succeeds. The VA should also test the link while signed out and note that test date beside the row.

Keep versions and links from diverging silently

Two objects diverge during a busy editing cycle: the files themselves and the links that point to them. Version naming and link labeling keep them aligned.

Version naming applies to the highlight reel that the family sends to many programs. Use a simple pattern such as First_Last_Position_v2_20260823 and keep a one line changelog per version. The changelog notes which source matches contributed, which clips moved or were replaced, and whether captions or identification markers changed.

Link labeling applies to the sharing links. A link that points to a folder labeled August sources v2 should not contain July matches mixed in. A link titled August reel v2 should not quietly be replaced by v3 while the same URL remains in several coach threads. When a version changes, create a new link labeled for the new version and update the transfer log accordingly. Keep the prior link's row with its expiration, so the family can see which programs still reference the older version.

The ownership log can help here by adding a version column to the file or set entry, and a link name column to the transfer row. That small addition lets the weekly review spot mismatches such as transfers of v1 still active after v2 is approved.

Review and expire on a schedule

A file transfer log that is created once and never revisited becomes a list of permissions that never end. A short review schedule keeps it accurate.

After each filming weekend, verify that new source files have owners recorded and that any temporary editor access was set to expire after the editing window.

Each week during active editing or outreach, scan the transfer table for any row where expiration has passed or where permission is blank. Expire any link that reached its date, update the log with the revocation date, and keep the row for history rather than deleting it.

At the end of a program's recruiting cycle, expire any remaining active links to that program and note the date. That step aligns with the broader transfer permission habit described for game film handling: scope each share narrowly and close it when its purpose is complete.

A VA can run the weekly scan as a ten minute task and bring any unclear permission to the family with a concrete choice: extend to a new date, revoke now, or request updated permission from the content owner. The family approves the decision, and the log records it.

Frequently Asked Questions

Does the family need to ask permission every time it moves its own recording?

When the file is clearly the family's own recording with the family's equipment, the permission question is internal. When the file came from the school, club, or event operator, or when a team policy limits distribution, the family should ask that content owner and record the response before sharing outside the team.

What if a college coach forwards the link beyond the program?

Choose view only for coach links to limit onward sharing, and treat any link as potentially forwardable. Keep the video itself free of unrelated personal data, and keep sensitive documents in a separate owner only location that is never linked in a film message.

Should the athlete or the parent be listed as the owner for a parent recorded file?

List the family archive as the owner for that file, with the recording dated and noted. The sharing purpose remains recruiting evaluation, and the athlete approves any transfer to a college program before it is sent.

How does this log relate to the broader transfer permission protocol?

The ownership log records who created and controls each video file. The transfer permission protocol records who is allowed to receive a specific copy for a specific task. Together they show both sides of the exchange: what can be shared and what was shared, with dates and permissions that the family can review without reopening every message.