Content Repurposing Workflow Template
Two documents and three sheets that map every derivative output before the source ships, not after.
Free download · No account needed
Asset Map
Source asset, mapped before it ships
One row per planned derivative output.
| Format | Channel | Owner | Target date |
|---|---|---|---|
A row with no owner is the row that does not get made.
Content Marketing Institute's 2025 B2B benchmarks found that content repurposing is a challenge for 37% of the marketers it surveyed, introduced that year as a new response option rather than a repeated one. The usual plan is to publish the long-form report or the recording, then figure out the social posts, the email, the blog cuts once things calm down. Calm rarely comes, and by the next sprint the source asset is old news competing with whatever shipped since.
This pack maps the derivative outputs before the source exists, as a required field on its own commissioning record rather than a follow-up task. Every row gets a format, a channel, an owner and a target date, sized to how much the source actually contains rather than to a round number. The Publishing Calendar generates from those dates, so a slipped source visibly drags what depends on it instead of orphaning it.
On the pack's own worked example, five source assets mapped this way produced 8.8 published outputs each within sixty days. Seven left to get planned later, including a recorded customer panel and a launch webinar, produced 1.6 each: the same kind of material, planned at a different time. That gap holds even though nothing about the unmapped material was harder to repurpose. Pair it with the editorial calendar that schedules everything else, and a voice guide so every cut still sounds like one writer.
What's in the pack
Repurposing Playbook
The method and the worked before-and-after: 8.8 published outputs per mapped source asset against 1.6 for unmapped ones.
Channel Guidance
What to pull for each output format, and the one failure mode per format, so rules stop getting relitigated.
Asset Map
One row per planned output: format, channel, owner and target date, required before the source is allowed to ship.
Publishing Calendar
Generated from the map's own dates, so a slipped source visibly drags every output that depends on it.
Performance by Format
What the last batch showed by format, fed back into which formats the next Asset Map weights up or down.
How it works
- 1
Map it before it ships
Send the next report or recording you're about to commission. The map gets sized to what it contains, not to a quota.
- 2
Assign owner and date per row
Every planned output gets a format from Channel Guidance, a channel, an owner and a target date relative to the ship date.
- 3
Publish against the calendar
The Publishing Calendar generates from the map, spaced so no two outputs from the same source collide on one week.
- 4
Log results, feed the next map
Performance by Format shows which formats earned their place after sixty days, before the next source asset is mapped.
Frequently asked questions
Is this template free?
Yes, the Word and CSV download needs no account or card. Edit with AI installs this pack in River and sizes the Asset Map to your next report or recording. For the source assets themselves, an article from a transcript turns a recording into the piece worth repurposing.
How is this different from a repurposing checklist or content atomization guide?
A checklist lists formats to consider after a piece is already live, which is exactly the timing this pack argues against. Content Marketing Institute's own 2025 research found repurposing a challenge for 37% of B2B marketers surveyed; the Asset Map is a required field on the source's commissioning record, not an afterthought checklist.
How many derivative outputs should one source asset actually produce?
As many as the material genuinely supports, tested against Channel Guidance's per-format pulls rather than a round number. On the worked example a dense research report or recording supported ten; a single blog post usually supports two or three. Padding the count with rows the source cannot support produces thin outputs, not more reach.
What if a planned output turns out not to be worth making?
It gets marked declined on the Asset Map with a reason, and the row stays rather than getting deleted. A declined row and a deleted row look the same from the outside; only one of them was actually considered and can be carried to the next source asset instead of forgotten.
Does this replace an event-specific repurposing workflow?
No. Event content repurposing reads session recordings against a timestamped question log, which is specific to what happens at an event. This pack is the general commissioning-time map for any long-form report or recording, event or not.
Will repurposed cuts still sound consistent across every format?
That depends on whether a voice guide exists yet. The style guide and voice pack gives every owner on the Asset Map the same checkable patterns, so a social post and a sales one-pager pulled from the same report do not read like two different writers.
Map the outputs before the source ships
Send the next report or recording you're about to commission, and River sizes the Asset Map to what it actually contains.
Edit with AI