How to produce video for the public sector

Why public-sector video carries a different production load

Public-sector video runs into three gates that do not apply in the commercial sector. Procurement: the agency cannot simply hire a production company; the vendor has to hold a relevant contract vehicle or win a competitive solicitation. Accessibility: Section 508 (US federal), WCAG 2.1 AA (state and local), EN 301 549 (EU) require captions, transcripts, audio description, contrast standards on every asset that reaches citizens. Security: controlled unclassified information (CUI), FOUO footage, citizen-identifiable material all need controlled-access workspaces, defensible audit trails and storage that survives FOIA or sunshine-law inspection.

Most agencies underestimate the structural impact. They start treating government video like commercial corporate video, then run into procurement timelines that stretch to 6 to 9 months, accessibility rework that drives 30 to 50 percent of post-production cost, and security gaps that surface during inspection. The structural shift: design the video program around the three gates from day one. Choose a partner already on the relevant contract vehicle. Bake Section 508 into the standard delivery, not as a finishing step. Treat sensitive footage like sensitive data. This post is a guide to building or evaluating a video program that handles the public-sector specifics properly.

The three gates

Gate 1: Procurement

The single largest difference from commercial production. Federal agencies typically procure through GSA Schedule (MAS), category management vehicles like 8(a) STARS III or OASIS+, agency-specific IDIQs, or sole-source justifications. State agencies use NASPO ValuePoint where the state has participating-addendum coverage, state master agreements, or competitive RFPs. Local agencies use municipal procurement code, often with SBE/MBE/WBE set-asides.

Vendors not already on the relevant vehicle face 60 to 120 days of procurement runway before the first shoot. Agencies that select vendors already holding the vehicle skip that delay. For agencies running a video program at scale, the choice of contract vehicle is the single highest-leverage decision.

Gate 2: Accessibility

US federal: Section 508 of the Rehabilitation Act. State and local: typically WCAG 2.1 AA via state digital accessibility law or municipal policy. EU: EN 301 549 transposed from the Web Accessibility Directive. International: varies by jurisdiction (DDA in Australia, ACA in Canada, JIS X 8341 in Japan).

For video, the minimum accessibility deliverables are open captions or closed captions with controllable display, a transcript, audio description for non-text content where required, sufficient contrast in on-screen text, and keyboard-accessible video players where embedded. Multi-language deliverables apply to many citizen-facing programs under agency language access plans. The accessibility load is often the largest single difference in post-production cost between commercial and public-sector video.

Gate 3: Security and data handling

CUI (controlled unclassified information), FOUO (for official use only) and citizen-identifiable material require controlled-access workspaces and defensible audit trails. FedRAMP-authorised storage for federal CUI workflows. CJIS-compliant handling for law enforcement footage. State and local agencies have their own classification frameworks. International public-sector adds local data residency and GDPR-equivalent regimes.

Standard public-sector video practice: secure ingestion path, restricted-access editorial workspace, controlled distribution to approved channels only, encrypted archival, defensible audit log of every access and approval. The partner must handle the data correctly because the agency cannot accept the risk of public release of restricted material.

Get a Free Consultation

The four content surfaces

Surface 1: Citizen-facing service video

Service explainers, program eligibility walkthroughs, how-to-apply videos for benefits and licences, public health and safety communications. The most accessibility-loaded category because the audience includes the full citizen population. Volume: 20 to 60 finished pieces per year for most agency video programs. Cost: $5K to $15K per finished piece. Multi-language delivery typical (2 to 12 languages under most language access plans).

Surface 2: Workforce training

Onboarding for new federal, state and local employees. Compliance training (cybersecurity, ethics, anti-harassment). Policy update communications. Recertification modules. Highest volume surface for most agencies because the workforce training catalogue compounds. Volume: 40 to 120 finished pieces per year typical. Cost: $3K to $8K per piece. Internal security tier; Section 508 still required because the workforce includes employees with disabilities.

Surface 3: Recruitment and workforce branding

Mission story video, role profiles, benefits explainers, day-in-the-life content for federal civilian roles, state agency hiring, local government recruiting. Volume: 8 to 24 finished pieces per year. Cost: $8K to $20K per piece. Distribution across USAJOBS, state hiring portals, social media, partner job boards.

Surface 4: Leadership communications

Agency head updates, programme launch announcements, policy explainers, internal town hall video, anniversary and milestone content. Volume: 12 to 30 finished pieces per year. Cost: $4K to $10K per piece. Cycle time 2 to 6 weeks depending on policy complexity.

The procurement vehicles that cut time-to-first-shoot

US federal

GSA Multiple Award Schedule (formerly GSA Schedule 70 and 541) is the broadest commercial-acquisition vehicle. Agencies can place orders directly without re-competing the underlying contract, which removes the 60 to 120 day procurement runway. Category management vehicles (8(a) STARS III, OASIS+, Polaris, Alliant 2) cover specific socioeconomic or task-area categories. Sole-source justification under FAR 6.302 is theoretically available but rarely succeeds for video production where commercial competition exists.

US state

NASPO ValuePoint cooperative purchasing covers state agencies in participating states; check the state-specific addendum for activation. State master service agreements cover state-specific procurement. Competitive RFP is the default; expect 90 to 150 day cycles.

US local and municipal

Local procurement code varies widely. Many jurisdictions piggyback on state cooperative vehicles. Small purchase thresholds (typically $50K to $250K) allow simpler procurement; larger contracts require formal RFP. SBE/MBE/WBE set-asides often dictate eligible vendors.

International public sector

Frameworks vary substantially: G-Cloud and DOS in the UK, EU framework agreements, BuyAndSell.gc.ca in Canada, AusTender in Australia. Most require local-incorporated vendor or formal framework registration. Always confirm vendor registration status before scoping.

The accessibility workflow that holds at volume

Bake accessibility into the brief

Section 508 / WCAG 2.1 AA requirements specified at brief stage. On-screen text contrast, caption style, transcript format, audio description requirements all locked before production starts. The teams that struggle treat accessibility as a finishing step; the teams that ship cleanly bake it into the brief.

Standard delivery package

Every public-sector video ships with open captions, closed-caption file (WebVTT or SRT), full transcript, audio description track where required, alt-text for thumbnails, accessible player embed code. This is the standard delivery, not the premium delivery. Pricing reflects accessibility as a default.

Multi-language pipeline

Translation, dub, regional caption files for languages required under the agency language access plan. Typical federal citizen-facing video ships in 3 to 6 languages; New York, California and Texas state programs often require 8 to 12 languages. Multi-language pipeline efficiency is where high-volume citizen-facing programs find the most leverage.

Accessibility review gate

Pre-delivery review against Section 508 / WCAG checklist by a reviewer trained on accessibility, not just on video. Catches contrast misses, caption-timing drift, audio-description gaps before the agency stakeholder review. The accessibility review is where the highest-quality public-sector video programs invest because catching issues at this gate is 10x cheaper than catching them at agency review or, worse, at publication.

The security workflow that holds at inspection

Restricted-access workspace

Editorial workspace with controlled access lists, audit logging of every file access, no public cloud sharing of footage. For CUI workflows, FedRAMP-authorised cloud storage and FIPS-validated encryption. For CJIS-relevant footage, CJIS-compliant access controls. The partner's workspace pattern is one of the highest-stakes decisions in vendor selection.

Audit trail per asset

Every access, every approval, every distribution decision logged with user, timestamp, and reason. The log defends the agency against FOIA, sunshine law, ombudsman and inspector general requests. Retained per the agency's records schedule (often 3 to 7 years for video, longer for records that may surface in litigation).

Controlled distribution

Published video distributes only through approved channels with appropriate accessibility delivery. No partner-side promotional re-use of agency content without explicit authorisation. Standard public-sector vendor agreements include strict re-use restrictions and break clauses for non-compliance.

What changes for the production team working on public-sector content

Three practical shifts.

Shift 1: Accessibility-fluent editing

Editors, producers and graphics teams who understand Section 508 / WCAG 2.1 AA in detail. On-screen text contrast, caption timing, audio description gap placement, accessible motion design. We covered the broader accessibility model in how to make enterprise video accessible; public-sector adds the regulator-enforcement layer.

Shift 2: Procurement-aware production scoping

Scopes of work that align to the procurement vehicle: contract type, performance work statement, deliverable structure, government property handling. The producer briefing the agency contracting officer should be fluent in the contract vehicle the work is being done under.

Shift 3: Defensive data handling

Same security discipline as defence or healthcare work. Restricted workspaces. Controlled access lists. Audit trails. No casual file-sharing through commercial cloud. We covered the broader contract pattern in video production contracts: what to look for; public-sector contracts add data-handling and audit-trail clauses.

Practical questions enterprise public-sector teams ask

How long does the procurement cycle actually take?

Partner already on a relevant vehicle (GSA, NASPO with addendum, agency IDIQ): 2 to 6 weeks from selection to first shoot. Partner requires competitive RFP: 90 to 150 days. Sole-source: 60 to 120 days with no guarantee of success. The procurement vehicle choice is often the single largest scheduling variable.

What is the accessibility cost premium?

For agencies new to Section 508 / WCAG 2.1 AA delivery: 25 to 40 percent above equivalent commercial production. For agencies and partners with mature accessibility workflows: 8 to 15 percent. The cost premium drops sharply once the workflow is in place because most accessibility delivery becomes standardised rather than per-asset bespoke.

How do we handle multi-language requirements?

Standard pattern: master content produced in primary language, regional caption translation and dub derived from the master. For agencies with formal language access plans covering 6+ languages, dedicated translation pipeline drops per-language cost 40 to 60 percent against ad-hoc translation. Most large federal citizen-facing programs invest in this pipeline.

What about footage with citizen-identifiable material?

Same consent and handling standards as healthcare patient testimonials. Documented consent at recording, additional consent for distribution, retention per agency records schedule. Production workflow tags every citizen-identifiable asset and routes through consent-verification before publication.

How do we handle FOIA and sunshine law requests?

Production audit trail captures who created what, when, with which approvals. Final assets and supporting documentation retained per the agency records schedule. The partner's audit log is the agency's first defence against FOIA challenges to video content. Choose partners who treat the audit log as a primary deliverable, not an afterthought.

Where to go next

For the broader accessibility framework that public-sector video extends, read how to make enterprise video accessible. For the contract patterns that govern public-sector vendor agreements, read video production contracts: what to look for. For the global production pattern that handles multi-jurisdiction public sector, read how to scale video across global offices.

To scope a public-sector video program with procurement, accessibility and security gates handled correctly, book a free consultation.