Published October 12, 2026.
Start with the source promise
Repurposing should extend a source idea, not manufacture a new claim under the source’s authority. The brief should link the approved original, identify its primary audience and promise, and mark facts, quotes, examples, or caveats that must remain intact. If the source contains time-sensitive data, record its checked date. An assistant can adapt structure and emphasis for a channel, but should flag any proposed claim that the original does not support. This keeps a short post from becoming more certain than the long-form article it cites.
Judge the artifact in its own channel
A useful adaptation is not merely a shortened copy. A carousel needs a coherent sequence and readable frames. A newsletter excerpt needs enough context to stand alone and a destination that fulfills the click promise. A short video needs spoken clarity, captions, and visual pacing. Define character, dimension, duration, link, and accessibility requirements in the assignment. Preview the actual rendering where possible; text that fits in a document may truncate in a feed or disappear beneath interface controls.
Check fidelity and voice separately
First compare facts, names, numbers, qualifications, and calls to action against the approved source. Then review voice: does the adaptation sound like the brand without copying whole paragraphs? Remove unsupported superlatives, invented anecdotes, and urgency that was not approved. Confirm that quotations are exact and authorized. Check alt text, captions, contrast, link labels, and reading order. A separate factual pass helps reviewers avoid overlooking a changed meaning while concentrating on tone.
Leave a traceable handoff
Record the source version, adaptation owner, reviewer, approval time, channel, scheduled time, and final asset link. Name the campaign and UTM convention if traffic will be measured. Keep rejected drafts only when they are useful for audit or learning, and ensure the scheduler points to the approved file. After publishing, verify the live artifact and destination once. The acceptance checklist should make it possible to answer two questions quickly: what was approved, and which source evidence supports it?
