This article is for informational and educational purposes only and does not constitute legal advice.
A video approval process is not a list of everyone who might have an opinion. It is a decision system: the organization decides what needs review, who has the expertise to provide it, and who can make the final call.
Without that structure, routine videos can stall in broad email threads, with late feedback reopening decisions that were already made. A workable process keeps the review group small, brings in specialists only when their issue is present, and records who approved the finished work.
Start with roles, not job titles
For each approval gate, name one person with final authority. Shared final authority often creates delay because no one knows whose decision settles a disagreement. A useful plain-language model comes from the RACI framework: one role does the work, one is accountable for the decision and final approval, some are consulted before the decision, and others are informed after it. The role definitions are explained by Section508.gov; nonprofits can use this model for workflow clarity without treating its federal accessibility framework as a rule for their work.
For most videos, the communications lead can own the process, manage versions, and check brand and message consistency. A program lead can verify operational facts, participant context, impact statements, and whether a story reflects current practice. A senior leader with organizational authority can make the final decision. If the video supports fundraising, add a development reviewer to check the donation language, campaign name, donor references, and stewardship promises.
That is a starting team, not a fixed rule. A program with sensitive participants, a coalition campaign, or a contract with review requirements may need additional expertise. The question is whether a reviewer has a defined responsibility that the video actually raises.
Keep routine board review out of production
In staff-led organizations, board members usually should be informed about routine video work rather than added as production approvers. The National Council of Nonprofits describes board responsibilities in terms of governance, oversight, and strategic guidance, while paid staff manage day-to-day operations. That distinction supports a staff-led workflow for ordinary communications.
There can be exceptions. A board may need to review a strategically significant or publicly sensitive campaign, a video governed by a board-adopted policy, or material that the organization’s governing documents reserve for board action. The point is to define those exceptions early, not introduce board review after a near-final cut is circulating. See the National Council of Nonprofits’ board guidance for the governance context.
Use approval gates instead of one large final review
Divide the work into clear moments when a decision is needed. At the brief and concept gate, approve the audience, purpose, core message, budget assumptions, and final decision-maker. At the script or interview-plan gate, review proposed claims, questions, tone, and the stories the project intends to tell.
Before filming, hold a clearance gate. Confirm who will secure and store participant permissions, location permissions, partner approvals, and permissions or licenses for outside materials. Requirements vary by jurisdiction and situation, so a single universal release form is not a substitute for organization-specific review.
The rough cut should answer a narrow set of questions: Is the message accurate? Is important context missing? Does the participant story remain respectful and understandable? This is the time for substantive corrections, not a new creative direction.
At final cut, reviewers should check that agreed corrections were made. New strategic or creative requests should go to the final approver, who can decide whether the project must return to an earlier gate. The last gate is publication readiness: confirm captions, descriptions or transcripts as appropriate, links, calls to action, and channel-specific details.
Plan rights and accessibility before production
When an outside creator is involved, address ownership and intended uses in a written agreement before relying on the footage, edit, music, graphics, or project files. The U.S. Copyright Office explains that a specially commissioned work can be a work made for hire only in specified circumstances and with an express written agreement signed by the parties. Commissioning work alone does not establish that status. The Copyright Office’s work-made-for-hire guidance explains the limited rule.
Accessibility also belongs in planning, not as a last-minute publishing task. W3C guidance distinguishes needs based on whether media is prerecorded or live and whether meaningful information appears in audio or visuals. For prerecorded video with meaningful audio, captions are identified as a Level A WCAG item. When visual details are needed to understand the content, audio description or a descriptive transcript may be needed. W3C recommends captions and a separate transcript; applicable legal duties can vary with the organization, funding, service, platform, jurisdiction, and context. Review the W3C media-planning guidance when setting the publication checklist.
Bring in legal, privacy, or safeguarding review only when needed
Not every simple video needs legal or compliance review. Add that gate when the project involves clients, minors, health information, schools, research participants, restricted locations, partner obligations, licensed material, or a sensitive story. Consult qualified counsel or the organization’s compliance lead when the facts call for it.
HIPAA is one example of why this review must be conditional. HHS guidance addresses HIPAA covered providers and related circumstances; it does not automatically apply to every health-focused nonprofit. Where the rule applies, a covered provider generally cannot give media access to protected health information without the required authorization, and blurring in post-production does not cure unauthorized access. See the HHS guidance on filming and media access.
FERPA is similarly context-specific. Serving young people does not by itself trigger FERPA considerations. The Department of Education explains that photos or video can raise FERPA questions when maintained by an educational agency or institution, or a party acting for it, and directly related to a student. The assessment depends on the context described in the Department of Education’s FERPA photo and video FAQs.
Make review comments usable
Send every reviewer the same version, a deadline, and one written review question tied to that person’s role. Ask the program lead to identify factual or contextual problems, for example, while development checks fundraising language. Keep comments in one location so the communications lead can consolidate conflicts and escalate them to the named decision-maker.
Silence should not automatically count as approval where affirmative sign-off is required by a contract, policy, or material review need. Name a fallback decision-maker for absences instead. After final approval, retain the final version, date, approver, publication destinations, location of participant and rights records, accessibility files, and any partner or funder approvals. That small record makes later reuse, updates, and questions much easier to manage.
Sources / References
National Council of Nonprofits: Board Roles and Responsibilities
W3C Web Accessibility Initiative: Planning Audio and Video Media
U.S. Copyright Office: Work Made for Hire
U.S. Department of Health and Human Services: Film and Media Access in Treatment Areas
U.S. Department of Education: FAQs on Photos and Videos under FERPA