This article is for informational and educational purposes only and does not constitute legal advice.
Raw footage is not simply the unused material left after a video is published. For a nonprofit, it can include original camera files, audio recordings, still photographs, transcripts, captions, editing project files, proxy files, interview logs, releases, consent notes, and exported versions. Years later, those materials may support a fundraising campaign, document program history, answer a rights question, or create risk if they are shared without review.
A raw-footage access and retention plan gives the organization a simple record of what it has, who is responsible for it, who can use it, and when it should be reviewed or deleted. Create the plan before filming when possible, or before a producer, freelancer, or staff member hands files to the organization.
Start by defining the project record
Begin with an inventory. Identify the files that belong to the project and the places they are stored. Include materials that explain what the footage shows and what limits apply to it, not just the video clips themselves. A file is much more useful when a future staff member can tell who appears in it, when it was recorded, whether releases exist, and whether there are limits on reuse.
This emphasis on inventories and metadata aligns with the NIST Cybersecurity Framework 2.0, which addresses managing data and metadata throughout their life cycles. The Library of Congress also notes that continuing access to digital material depends on preservation planning and descriptive information.
A compact project record can include the project name, file location, custodian, date, description, people and locations depicted, release or consent status, copyright status, sensitivity level, approved users, retention trigger, preservation-copy location, deletion method, and last review date. This is a decision record, not merely a naming convention for folders.
Confirm rights before assuming reuse is permitted
Paying a freelance videographer does not automatically mean the nonprofit owns all raw footage or may reuse it without limits. Under U.S. copyright law, copyright generally begins with the author. A transfer of copyright ownership generally requires a signed writing. A specially commissioned audiovisual work can qualify as a work made for hire only when statutory conditions are met, including a signed written agreement.
Before accepting files, review the agreement in plain language. It should address who owns the footage, whether raw files will be delivered, whether the nonprofit may edit or license material later, whether the creator may keep a portfolio copy, what third-party materials are included, and when return or deletion is required. The Copyright Office’s ownership and transfer provisions explain these rules. Have qualified counsel or the appropriate compliance lead review agreements that raise questions for your organization.
Ownership and access are separate decisions. Even if the nonprofit owns a recording, broad internal access may not be appropriate because of the people, locations, or information shown in it.
Classify sensitivity and assign access by role
A short classification system is easier to use than a complicated security policy. For example, standard internal footage may include ordinary event material. Restricted footage may need communications-lead approval before it is shared. Highly restricted footage may require approval from a program leader and a specific delivery method.
Give each classification a written restriction. A label such as “confidential” does not tell staff what they may do. Record instructions such as “fundraising use only,” “no social posting,” “blur identity before external use,” “requires program director approval,” or “expires after this campaign.” Footage involving clients, children, health-related services, domestic violence survivors, immigration status, legal matters, shelter locations, or other identifying details warrants heightened review before access or reuse.
Then create an access matrix based on named roles: the project team, communications leadership, an archive administrator, an outside editor, a partner organization, or an interviewee requesting a clip. For each role, state whether that person may view, download, copy, edit, share externally, or only request material. Give people the minimum access needed for their task, review permissions periodically, remove access when a contractor’s work ends, and document exceptions. These are practical uses of NIST’s least-privilege guidance.
Set retention by purpose and trigger
There is no universal retention period for all nonprofit raw footage. Start with why a category is being kept: future storytelling, historical documentation, final grant reporting, a contractual storage obligation, or temporary editing. Then set a trigger and review date, such as the end of a campaign, completion of reporting, expiration of an approved consent term, or an annual archive review.
Check relevant contracts, releases, grant terms, insurance requirements, state-law obligations, and any litigation, audit, investigation, or records hold before deleting material. The IRS requires exempt organizations to maintain books and records needed to show tax compliance and document activities, income, and expenses. That requirement does not automatically mean every raw file must be retained. Instead, assess whether footage or related project documentation is needed to substantiate a reported activity or expense, using the IRS recordkeeping guidance as a reference.
Preserve useful masters and dispose of sensitive material intentionally
When long-term retention is justified, preserve a protected master separately from editing copies. Keep the accompanying rights-and-restrictions record with it. Maintain backups and periodically test whether staff can locate and open preserved files, as recommended by NIST’s lifecycle and backup practices. Retain final captions, transcripts, and accessible final deliverables when the organization needs those assets for future use.
Deletion should be a documented stage of the plan. Ordinary deletion of a working copy is different from sanitizing media that contains sensitive information. The NIST media-sanitization guidance describes sanitization as making access to target data infeasible at an appropriate level of effort, based on the information’s sensitivity and whether storage media will be reused or disposed of.
At the end of the approved period, record what was deleted, what preservation copy remains, and whether contractor-held copies or shared-folder copies were addressed. A modest operating rhythm helps: document decisions at project intake, review access at file delivery and publication, review the archive annually, and record final disposal. That discipline preserves future storytelling options without treating every file as something that must remain forever.
Sources / References
IRS — Recordkeeping Requirements for Exempt Organizations
U.S. Copyright Office — Chapter 2: Copyright Ownership and Transfer
NIST — The Cybersecurity Framework 2.0