Common Content Repurposing Questions: Decision Record

What decision should I record before making another version?

Give every derivative its own decision record before production starts. A format idea becomes a workable assignment only when it names the source owner, rights, audience job and intended result, rather than treating repurposing as a choice of shape alone.

Questions about content repurposing often begin with formats, but the record redirects attention to ownership, purpose and evidence. Use one row per derivative, not a campaign-wide row, so separate versions do not inherit assumptions about rights, audience need or review.

Which seven details belong in the record?

Use seven fields for every version: source owner, rights status, audience job, format, named owner, review date and metric.

Write down the audience task before editing begins, rather than letting a format define it. That makes the row concrete enough for a reviewer to approve or return and gives the team a defined decision to check when the work is reviewed.

Route evidence into content marketing analytics, so performance can be traced to a named choice rather than a general impression. A decision record is useful only if its metric shows whether that derivative did its stated job, not merely whether the campaign generated activity overall.

What would a completed record say?

A 20-minute webinar on invoice reconciliation can be captured in two short records, one for each derivative.

Separate metrics show whether each derivative does its own job: checklist downloads that lead to a demo request track the checklist’s business action, while clip viewers who report matching a payment track the clip’s audience task. The named owner is accountable for reviewing each record on its review date, especially if reviewer approval is built into the workflow.

When should I give a derivative a separate URL?

Decide whether it needs its own URL by defining the audience task and added value first; then request technical review of overlapping URLs, redirects, canonical signals and localization.

A near-copy that serves the same task adds nothing the reader needs, so it does not justify another page. Content marketing strategy places this choice within a wider plan, while the task-and-value test keeps the page decision tied to user need.

What rights must I verify for each version?

Check rights for each derivative: approval of the source does not automatically extend to its reuse. The U.S. Copyright Office's Circular 14 states that only the owner of copyright has the right to prepare, or to authorize someone else to create, an adaptation of a work.

Before adaptation, confirm copyright, contract, quotation and platform rights. If permission is limited to internal reuse, state that restriction in the row, as in the webinar example; source approval alone is not enough to authorize every derivative or every destination.

Which access version should the format field name?

Name the access alternative needed for the media, not just its file type. Section508.gov guidance on captions and transcripts says captions describe dialogue, music and sound effects in videos, while transcripts describe audio-only and video-only content such as podcasts.

W3C guidance distinguishes basic transcripts of speech and meaningful non-speech audio from descriptive transcripts that also convey visual information. Which alternative fits depends on the media and user need. A recorded webinar with slides may need a descriptive transcript, while a simple audio interview may need a basic one.

A raw transcript does not automatically make a useful article. It still needs accurate meaning, useful structure, context, editing, accessibility, rights and an audience-specific purpose; recording it as a format without those checks leaves the original audience need unresolved for the derivative.

How many derivatives should I produce in one batch?

There is no universal count: make only versions tied to distinct audience and channel jobs that the team can review, distribute, measure and maintain.

If a row cannot name both a channel and a distinct job, leave that version out of the batch. Decide the content distribution route before production, so each version has a clear destination as well as a purpose the team can support.

What should I compare to judge performance?

Compare each derivative with its source over a matched period, not with site averages; use the primary task metric to report the difference.

Track completion rate, time on page, scroll depth, click-through to the next action, assisted conversions and unique users. Use bounce rate and exit rate as negative signals, and collect the data with Google Analytics 4 or Looker Studio for each derivative and its source.

Use a matched window such as the first 28 days after publication, then report the difference in the primary task metric. Combined reach does not prove new value: exposure may overlap across channels and is described under platform definitions, so also judge the distinct audience job and cost.

What extra details apply when data is collected?

When a derivative collects data, add privacy fields to its record, including the legal basis, data collected, retention period and access controls.

For each derivative, record the legal basis, data fields collected, retention period and access controls. The W3C Privacy Principles statement is not a local privacy policy; check the governing law and the actual configuration of the tools in use before relying on the record.

What should I do first?

Start with one candidate derivative and complete its row before production; use the record to settle permission, purpose and measurement before anyone creates the version.