Building a Content Pipeline That Survives Graduation

The hardest media problem in FRC isn't a camera setting — it's continuity. Every June, your most skilled photographers and editors graduate. A pipeline is what keeps quality from resetting to zero each fall.

1. A season-long content calendar. Map the FRC season into content phases and pre-plan recurring posts:

• Preseason (fall): recruiting posts, mentor/sponsor spotlights, 'meet the team.'
• Build season (the roughly six-week period after January Kickoff): weekly build-progress updates, subsystem teasers, the CAD reveal.
• Competition season (spring): match-day recaps, highlight reels, award announcements.
• Offseason: thank-you posts, retrospective, demo events. A recurring template — like a 'Build Update Tuesday' graphic — means you're filling a slot, not inventing from scratch each week.

2. An organized asset library. A shared Google Drive with a strict, dated folder convention: /2026/Photos/[EventCode]/, /2026/Video/raw/, /Brand/logos/, /Brand/templates/. The brand folder holds vector logos, fonts, the brand sheet, and reusable Canva/DaVinci templates. When a project is 'find the file in 10 seconds,' people actually reuse and maintain it.

3. Defined roles, not a hero. Avoid the single-person-does-everything trap. Split into clear roles students can grow into: photographers, video editors, graphic designers, a social media scheduler, and a writer for press releases and the Impact Award. Pair each senior with a younger student all season so the skill transfers before the senior leaves.

4. Documentation as the real deliverable. The most valuable thing a graduating media lead leaves behind isn't their best video — it's a written playbook: the camera settings checklist, the export presets, the publish/consent checklist, login access (in a team password manager, never a personal account), and 'how we do match-day.' Store it where the project lives. Teams that document their processes are also the teams whose Impact Award narratives show sustainable, transferable structure — something judges explicitly look for.

5. Own your accounts. A classic failure: the only person with the Instagram password graduates and disappears. Fix: accounts belong to the team, with a mentor as recovery contact and credentials in a shared, secured vault. The same goes for the YouTube channel, Google Drive, and any scheduling tools.

6. A lightweight approval flow. Define who reviews a post before it's public — typically a mentor for anything involving minors, sponsors, or other teams. This isn't bureaucracy; it's the safety net that catches the consent and sponsor mistakes from the troubleshooting module before they're live.

The test of a good pipeline: a brand-new sophomore who has never touched the account can, with the documentation alone, produce and publish an on-brand match recap. Build toward that.