Content Repurposing Workflow: From Source to Review

8 steps to a reviewable result

1. 01

   Inspect the source asset

   Record the source URL or file, publication date, audience and reusable passages. For each claim, note the exact condition that makes it true and whether a visual or quotation can be reused.

   Result: A source record that prevents the plan from treating a sentence as a free-floating fact.

2. 02

   Choose destination jobs

   Pick two or three reader jobs first. For example, a newsletter can give subscribers a checklist, while a short clip can show one step. Skip a channel if you cannot name its reader job or review owner.

   Result: A short destination list with a reader job for each asset.

3. 03

   Create the asset map

   Copy the prompt and fill in the source passage, rights, destinations and team capacity. Reject any suggested asset that cannot point back to an approved passage.

   Result: A format plan that protects source context while giving creators concrete work to produce.

   Your prompt

   Copy prompt

   Create a content repurposing plan from the approved source asset.
   
   Source asset and context: {{source}}
   Approved claims, examples and limits: {{claim_boundary}}
   Destination channels and reader jobs: {{destinations}}
   Available owners and production limits: {{capacity}}
   
   Return no more than three rows. Use these columns: asset and reader job | source section or timestamp | format and draft angle | exact claim and condition to retain | rights or quote check | production owner | approval owner and next action. Mark a missing permission, source or fact as [NEEDS INPUT]. If an idea cannot be supported, put it in a separate rejected-ideas line with the reason. Do not turn a conditional source claim into a universal promise or invent a new result.

   Example input

   Fictional source: a 20-minute webinar about weekly client reporting. At minute 12, the presenter shows how to check missing dates before sending a report. The slide at minute 13 is approved for reuse. A customer example at minute 16 is not approved. Destinations: newsletter checklist, short clip, existing article update. Team: writer Ava, video editor Lee, approval owner Sam.

   Example output

   Illustrative asset map: Newsletter checklist | min 12–13 | help readers check a weekly report | Keep the scope “weekly client reports”; use the approved slide only | Ava drafts; Sam checks claim and slide rights. Short clip | min 12–13 | demonstrate the missing-date check | Preserve the presenter's explanation and captions; confirm recording/voice reuse | Lee edits; Sam approves the cut. Article update | min 12–13 | add a worked reporting step | Cite the webinar passage; do not imply a measured improvement | Ava updates; Sam checks the source link. Rejected: customer-results post from min 16. Customer example is not approved for reuse.

4. 04

   Draft the approved assets

   Draft only the rows that have a source passage, reader job and reuse permission. Adapt the opening, structure and call to action to each chosen channel using its current requirements. Keep the source location beside each draft; do not make an unsupported idea sound finished.

   Result: Up to three drafts, each tied to an approved row rather than copied across channels.

5. 05

   Check the claim drift

   Read the source passage beside every headline and draft. Check scope words such as “weekly”, the screenshot or quote permission, and whether a new audience needs context the source does not provide.

   Result: A plan that retains accuracy across formats.

6. 06

   Assign production and review

   Give each draft a production owner and an approval owner. Record approval or a hold with the reason; keep rejected ideas visible so they are not reused without new evidence or permission.

   Result: Each draft has a documented go, revision request or stop decision.

7. 07

   Publish or record the hold

   Release only approved assets through your normal publishing process. For each one, record the channel, final URL or location, date and owner. If a source, permission or review is still missing, leave the item on hold instead of assigning a fictional publication date.

   Result: A release record for approved assets and a visible hold for everything else.

8. 08

   Review one actual result

   After the chosen observation window, write down one measure that fits each reader job, such as qualified clicks for a link-led post or saves for a reference checklist. Compare it with your own prior work if you have a usable baseline; otherwise record the result without claiming the workflow caused it. Use that note when choosing the next source.

   Result: One observed result or a pending date per released asset, plus a decision for the next cycle.