Overview
A content repurposing planner helps a content marketing manager turn long-form assets into channel-ready derivatives without losing the original claims, proof, and approval trail. This playbook installs a repurposing plan table and a copy pack so blog posts, reports, webinars, podcasts, ebooks, and case studies can become usable social, email, sales, and page copy.
It is built for teams that already have strong source material but keep the repurposing workflow in a spreadsheet: source link here, rough idea there, approval caveat somewhere nobody checks. Juno keeps the durable parts together: source spine, derivative angle, target channel, owner, status, priority, and review needs.
Why you should preserve the source spine
Repurposing fails when the output keeps the topic but loses the truth. A webinar becomes five vague social posts. A report turns into an email claim that sounds sharper than the evidence. A case study quote wanders away from the permission context.
This playbook treats the source spine as the operating standard. Juno captures the thesis, proof, caveats, CTA, and approval needs before it drafts. Then it adapts the structure for each channel, so LinkedIn gets a native hook, email gets a clear reader reason, sales gets useful context, and landing-page copy keeps claim support visible.
That discipline matters because distribution channels reward useful, relevant packaging. LinkedIn's own posting guidance emphasizes relevance and a clear opening for in-feed content (LinkedIn Help), while Google frames helpful content around serving a real audience rather than simply producing more pages (Google Search Central).
Run it after new long-form content ships, before a weekly content planning meeting, or when the team needs more mileage from existing assets without creating approval chaos.
Step-by-step
- 1Confirm the brand, planning window, source assets, target channels, audience, campaign goal, and any claim or approval rules.
- 2Review each long-form source and capture the source spine: title, locator, thesis, supported claims, proof, caveats, CTA, owner, and approval constraints.
- 3Map derivative opportunities in the repurposing plan table, with one row per meaningful source-to-channel idea rather than one row per minor wording variant.
- 4Prioritize the rows by campaign relevance, proof strength, channel fit, buyer usefulness, approval effort, and production readiness.
- 5Draft the strongest derivatives in the copy pack, grouping copy by source asset and channel so reviewers can trace every idea back to its evidence.
- 6Mark what is ready, blocked, missing proof, waiting on assets, or needing legal, product, customer, or stakeholder approval before anything moves into publishing.
Frequently asked questions
Does this replace a content calendar?
No. It replaces the repurposing spreadsheet: the place where source assets, derivative ideas, draft copy, owners, statuses, and approval notes are tracked. A content calendar can still decide when approved pieces publish.
What source assets can it use?
Use blog posts, reports, webinars, podcasts, ebooks, guides, case studies, event recaps, or transcripts. The stronger the source proof and thesis, the better the derivatives.
Will Juno invent new proof for a better hook?
No. The playbook tells Juno to preserve source-backed claims and mark gaps instead of adding unsupported statistics, customer promises, or examples.
How often should we run it?
Run it once for a backlog cleanup, weekly after new long-form content ships, or monthly before a broader content review. The default schedule choice is none, with weekly and monthly refreshes available when the team wants continuity.