Build a Reusable Beat Library for Teach Campaigns
Catalog teach beats by intent, visual type, and on-screen proof so recurring explainer campaigns stop rewriting the same modules every week.
Build a Reusable Beat Library for Teach Campaigns
Stop rewriting the same teach beats from scratch every week. A reusable beat library turns recurring explainer campaigns into composition work: pick locked modules, swap campaign-specific proof, ship.
Content ops and product marketing teams that batch AI explainer Reels feel the pain first. Hooks, definition cards, step demos, and soft next-steps repeat across launches—but without a catalog, every sprint reopens blank boards. Pair a library with batch production from one approved style lock so visual language and beat modules stay aligned.
What counts as a reusable beat
A beat is reusable only when three fields stay stable across campaigns:
- Intent — the viewer job (define, contrast, prove, warn, next step)
- Visual type — still card, UI crop, metaphor, host CU, transition wipe
- On-screen proof shape — what evidence appears (label, before/after pair, numbered step, citation chip)
If any of those three must change for a new campaign, treat the beat as a template with placeholders—not as a locked module. Reuse the structure; regenerate the filled frame.
| Beat class | Typical duration | Reuse signal | Usually campaign-specific |
|---|---|---|---|
| Definition card | 3–5s | Same term family | Product name / UI skin |
| Problem stakes | 4–6s | Same failure mode | Logo, competitor vibe |
| Method step | 5–8s | Same rule | Screenshot date |
| Proof still | 3–5s | Same proof type | Metric, client |
| Soft CTA | 2–4s | Same ask shape | Offer / URL |
| Transition bridge | 1–2s | Same motion language | Scene content |
Do not catalog “pretty frames.” Catalog jobs the viewer must complete. A beautiful metaphor that only works for one launch is campaign art, not a library module.
Intent verbs worth standardizing
Pick a short controlled vocabulary so search inside the library works:
- Define · Contrast · Show failure · Teach step · Prove · Warn · Transition · Soft ask
If two modules share a verb but differ in visual type, keep both—and name them clearly (DEF-CARD-FLAT vs DEF-HOST-CU).
Catalog fields that keep modules findable
Minimum fields for each library entry:
- Beat ID — stable code (
DEF-QUEUE,PROOF-BEFORE-AFTER) - Intent verb — from the controlled list
- Visual type — still | motion | hybrid
- Mute-safe caption — the line that must work without VO (mute-first sound notes still apply)
- Safe-zone notes — top/bottom UI clearance for 9:16
- Proof placeholder — what must be swapped per campaign
- Approval status — draft / brand-approved / legal-cleared
- Last used — campaign + date (retire stale skins, keep structure)
Optional but useful: aspect-ratio variants, language tags, owner, and a “do not combine with” list so incompatible metaphors stay apart.
Example library row
STEP-FILTER-RULE · intent: teach step · visual: UI crop still + caption · mute caption: “Filter first, then export” · proof placeholder: product UI skin · approved · used in Q3 onboarding series.
Operators composing a new Reel pull three to six IDs, fill placeholders, and only regenerate what changed. That composition list is the first draft of the storyboard.
Filled mini example: onboarding week
Campaign intent: “Invite a teammate without duplicate seats.”
| Order | Beat ID | Placeholder fill |
|---|---|---|
| 1 | HOOK-FAIL-DUPE | “Double invite = double chaos” |
| 2 | DEF-SEAT | Seat vs viewer role card |
| 3 | STEP-INVITE-FLOW | Current invite UI crop |
| 4 | WARN-BILLING | One billing caution chip |
| 5 | CTA-SOFT-DOCS | Link to invite help article |
Four of five IDs were evergreen. Only UI crops and the billing chip needed campaign refresh. Without a library, that week would have been five new boards.
When a beat must stay campaign-specific
Force a new board (do not pull from library) when:
- Claims, regulated disclaimers, or proof numbers change (pre-board claims checklist)
- The teach intent itself is new (new micro-intent ≠ new skin)
- Host identity, brand palette, or metaphor system changes mid-series
- Performance kill criteria retired the old module’s framing
Campaign-specific beats often include launch pricing, named customers, and dated changelog UI. Keep those out of the “evergreen” shelf. If you must reuse a campaign proof shape, store it as a template with empty proof fields—not as an approved finished still.
Operating the library week to week
- Intake — after each campaign, promote any beat used twice into the catalog with a clean ID
- Compose — new boards start as ordered ID lists, then fill placeholders
- QA — check that proof placeholders were replaced and captions still match intent
- Retire — mark modules that confuse viewers or fail completion; do not silently regenerate
- Version — bump IDs when the teach rule changes (
STEP-FILTER-RULE-v2), keep v1 for analytics continuity
A library without retirement becomes a junk drawer. Treat modules like code: version, deprecate, delete.
Review rituals for non-design stakeholders work better when they approve modules, not every finished Reel—see storyboard review rituals for non-design stakeholders. Annotating boards so non-designers give useful feedback (annotation guide) pairs well with ID-based reviews: stakeholders comment on WARN-BILLING, not on “frame 7 feels off.”
Soft production tip
Approve library stills and boards once, then compose new Reels from locked modules. Storyboard-first tools (including Scro) fit this pattern: lock the beat map and style, regenerate only campaign skins. The win is editorial reuse, not more blank prompts.
Quick start checklist
- Define beat classes for your next four-week series
- Add the eight catalog fields above to a shared sheet or board library
- Promote two repeated beats from last month into IDs
- Mark at least one beat as campaign-only (claims/proof)
- Compose next Reel as an ordered ID list before any render
- Schedule a monthly retirement pass for low-performing modules
Reusable beats cut rewrite time; they also raise consistency so viewers recognize your teach grammar across a campaign.