← All articles

Content strategy

Keep sources and corrections attached to every repurposed post

A one-file ledger that ties each repurposed post to the exact source sentence behind it, plus a real correction drill: one YouTube rule, five assets, a correction that was itself wrong, and a post we could not fix.

By Ferryman··6 min read

What the ledger records

Repurposing multiplies a claim. One sentence from a help page becomes a guide paragraph, a text post on five networks and a slide in a carousel. If the sentence turns out to be wrong, or the page changes, you need to find every copy. A ledger is a plain spreadsheet or text file with one row per asset. This is a manual template, not a Ferryman feature.

ColumnWhat to writeWhy it matters
Source IDA short ID for the primary source, such as YT-15424877Every derivative points back to one place
Source and date readThe URL of the page that actually states the fact, the date you read it, and the exact sentenceA summary or your own notes can drift from the page
Claim as usedThe sentence as it appears in this asset, word for wordSearching for the old wording finds every copy
Asset and destinationWhat it is (guide, text post, slide) and where it wentDifferent destinations allow different fixes
URL or scheduled IDThe live link, or the ID of the queued postQueued posts can still be replaced before they go out
RightsWho owns the media, music or quote, and where you may use itPermission for one platform is not permission for all
Status and correctionLive, scheduled, corrected or unresolved, with the date and what changedAn unresolved copy stays visible instead of forgotten

A real lineage: one YouTube rule, five assets

This is Ferryman's own ledger for one fact, as it stood on 2026-11-16. The source is the YouTube Help page "Understand three-minute YouTube Shorts". Read in full on 2026-11-16, it says a Short over one minute "with an active copyright claim of any type, including manual claims, will be blocked globally on YouTube", and in its FAQ that "Shorts longer than one minute that have an active Content ID claim, regardless of the policy, will be blocked on YouTube."

AssetDateClaim as usedWhat happened
Guide: how to turn one idea into a week of contentPublished 2026-10-16"blocked globally"Reworded on 2026-11-16 to quote the FAQ sentence. Both versions match the page.
Carousel on TikTok and Instagram, 4 slides on FacebookPosted 2026-11-14"blocks a Short over 1 minute that has an active copyright claim"Matches the page. No change.
Text post for X, Threads, Bluesky, Mastodon and TumblrScheduled for 2026-11-21"blocked worldwide"Cancelled on 2026-11-16 and booked again in the same slot quoting the FAQ sentence.
Guide: AI repurposing promptsPublished 2026-11-16Said the page does not say "worldwide"Wrong. Corrected the same day to quote both sentences.

What the correction drill taught us

The drill started with a re-read of the source. The first re-read found the FAQ sentence, which says "blocked on YouTube", and stopped. We concluded that "worldwide" had no source, cancelled the text post, reworded the guide and wrote that conclusion into a new guide. A full read later the same day found the other sentence, which does say "globally". The original wording had been supported all along.

The ledger made the first half of the drill fast: every asset recorded the sentence it used, so finding every copy was a search of one file, not a scroll through five networks. It also made the mistake easy to undo, because each change was logged with what it replaced. The lesson we took from it is the rule in the answer above: a correction is a new claim, and it needs the same full-page check as the claim it replaces.

Record the copies you cannot fix

On 2026-10-22 Ferryman's brand accounts posted a carousel on TikTok and Instagram about video length limits. Its caption said Bluesky takes videos up to 3 minutes. That number came from a summary table in our own website code, not from the primary source. The official Bluesky app's code sets a 10-minute, 300 MB video limit (checked 2026-11-16).

A corrected carousel is scheduled for 2026-11-21. The October post has not been edited or removed, so the ledger marks it unresolved, with the correct source and the date of the replacement. Writing that down is the point. An unresolved row keeps a known public error on the list until someone fixes the caption, posts a correction or takes it down, and tells anyone who asks which source to cite.

The same mistake has a second lesson: the ledger's source column should hold the page that states the fact, not a table or note that summarizes it. A summary is a derivative too, and it can be wrong.

Steps when a source fact changes

Use these steps whether the source changed or you found an error. Do them in order.

  1. Fix the source row first. Read the whole primary page, quote the exact sentence and record the date.
  2. Search the ledger for the source ID and for the old wording. Both searches matter: an asset may quote the fact without the ID.
  3. Replace every scheduled copy before it goes out, then record the new wording and the new scheduled ID.
  4. For each live copy, choose: edit it if the destination allows, post a correction, delete it, or leave it. Record the choice and the reason.
  5. Mark anything you leave as unresolved, with the date and the correct source, so it stays on the list.
  6. Have a second person, or a second full read, check the correction before it goes out.

Where Ferryman fits

Ferryman does not keep a source ledger for you. What it does help with is the scheduled part of the drill: you can cancel a queued post that carries an old claim and schedule the corrected text for the same time, which is how the 2026-11-21 text post above was replaced. In a team workspace, drafts, schedules and connected accounts stay with the team, and roles decide who can draft, schedule and publish.

FROM GUIDE TO WORKFLOW

Explore this workflow in Ferryman

  • Keep the people who correct posts in one workspace

    Workspace drafts, schedules, sync flows, posts and connected accounts stay with the team, and roles decide who can draft, schedule and publish, so a correction reaches whoever can change the queued copy.

Sources & further reading

Written by Ferryman. Sources checked Nov 16, 2026. Platform rules can change; consult the linked documentation for current requirements.