Content Repurposing Planner

Choose the question your source can help someone answer

Start with a specific source and a specific reader problem. In this worked example, Harbor Kit Library has written an article about returning borrowed project equipment. New borrowers keep asking what to bring back, while volunteer coordinators want a consistent desk routine. Those are related questions, but they need different explanations. The article can support both without being copied in full into every channel. Write the source title as “Returning a Harbor Kit loan” and describe the shared objective as helping borrowers complete a clear return. These are invented planning details, not a claim about an existing organization or measured results.

Choose a derivative because it resolves one of those questions in a suitable form. A borrower might need a visual sequence showing the equipment case, its parts list, and the return desk. A volunteer coordinator might need an explanation of why the desk records missing accessories before shelving a case. A conversation could ask experienced borrowers which part of preparing a return needs clearer guidance. The same source supports three different editorial jobs. If two proposed briefs offer the same answer to the same person in the same way, reconsider the second brief before assigning production work to it.

This is the distinction between a repurposing plan and a calendar, caption worksheet, or script. The repurposing plan records which source supports which new piece and what a person must produce. A calendar can later organize release dates; a caption can express the finished message; a script can specify spoken delivery. None replaces the decision about what to retain, explain, or leave out. Keep that decision here first. The planner handles one source and up to twelve derivative briefs, so use separate saved projects when unrelated source documents would make the connection difficult for a reviewer to follow.

Enter the source you actually want the briefs to use

Give the project a recognizable working name, then enter the source type, source title, audience, and objective. Paste the article text into the source area, or supply a transcript or manually prepared notes for a recording. Selecting video, podcast, or webinar describes the source; it does not upload media or transcribe speech. For Harbor Kit, include the return sequence and the exceptions that affect it, rather than pasting only a promotional introduction. The derivative writer needs the part that explains the process. An audience such as “first-time borrowers returning a complete equipment kit” is more useful than “everyone interested in projects.”

An optional HTTPS reference helps a person find the original later. It is a reference only: the planner does not fetch the page, check whether it exists, inspect ownership, or keep the supplied text synchronized with it. If the article changes, you must review and update the source yourself. A timestamp or section name is also a note you provide, not a media selection. For a recording, “Return desk demonstration, around the parts check” can help the producer locate context, but it does not identify extracted footage or create a playable clip inside this tool.

Treat the source area as a deliberate working copy. Remove private borrower details, access credentials, and unrelated internal discussion before entering material or sharing a review export. The planner works in the browser without an account or an API connection for source processing. It has no autosave, so download editable JSON before leaving a session that you want to continue. Ordinary website resources may still load; browser-local planning is not a promise that the whole website runs offline. Keep your original article and any media in your own files because a saved project records supplied text and notes, not the underlying recording or photographs.

Select evidence without confusing a literal match with approval

Select an excerpt manually for each derivative. Suppose the supplied article contains the sentence “Use the case checklist to count accessories before returning the kit.” Copy that sentence exactly into the excerpt field and add “Preparing the case” as its source location. The planner can report that those characters occur in the supplied source. That is useful traceability: a reviewer can identify what prompted the brief. It does not establish that the instruction is accurate, that the article belongs to you, or that every derivative preserves the instruction’s meaning. Read the surrounding source before making any of those judgments.

Literal matching is deliberately narrower than editorial review. Changing “accessories” to “parts” can make a sensible paraphrase fail the substring check. Changing capitalization, punctuation, spacing, or line breaks can also prevent a match. A failed match is a reason to inspect what you selected, not proof of an inaccurate claim or copied material from elsewhere. Conversely, an exact sentence can be misleading when detached from the exception immediately after it. Keep the excerpt faithful for reference and put your adaptation in the angle, opening, and draft fields. Do not rewrite evidence merely to make it sound like finished post copy.

Read the possible excerpt states according to what was supplied. No excerpt means no excerpt was provided; an excerpt without source text has no source text to search. An exact match means literal presence, while not found means the supplied characters were not located. None is a content quality, originality, or plagiarism score. You can also leave the excerpt blank and supply a useful human-written source location when that better reflects incomplete notes. Make the limitation visible in the brief and ask the source owner to resolve it. A review declaration remains a separate human decision even when the matching state is favorable.

Build three derivatives that earn their own place

Create the first Harbor Kit brief for an Instagram carousel with the working title “Before you close the equipment case.” Its angle is a visual return check for first-time borrowers, not a summary of the whole article. Plan a sequence that shows the checklist, the accessories arranged beside the case, and the closed case at the return desk. Those scenes are editorial choices for this example, not fixed platform requirements. Write the opening yourself, explaining the immediate task without promising that every kit contains the same parts. The selected format provides a recipe and checklist, but it does not create slides, captions, or images.

Add a LinkedIn text brief titled “Why our return desk checks the small pieces first.” This one serves volunteer coordinators who need to explain a repeatable process to new helpers. Its angle is the handover between borrower and desk volunteer. Retain the article’s distinction between counting accessories and deciding what to do about a missing item. Do not invent claims that the process reduced losses or improved turnaround. If the source contains no outcome measurements, discuss the procedure and its purpose instead. The derivative should stand alone for a coordinator who has not read the borrower article or seen the carousel.

For the third brief, choose a Threads conversation about the hardest part of preparing a kit return. Include enough context for a reader to understand that the question concerns a borrowed equipment case, then ask one answerable question. Record a follow-up action for the author, such as gathering unclear instructions for the next source revision. This is not a disconnected promotional extract or an automatically generated thread. Use add, duplicate, reorder, and remove to shape the plan as needed. A duplicate is a starting copy with a new identifier and unreviewed declarations; it still needs a distinct purpose before you treat it as another production assignment.

Write the fields that turn an idea into a production task

Use the title to identify the deliverable and the angle to explain its promise. The opening is your proposed first line or first spoken thought. The draft field holds text you write, which may still be incomplete. Do not use the draft area as a claim that the tool generated a finished caption. For the carousel, an opening might be “Check the little pieces before the case closes.” The body can explain why the case checklist matters and where to ask about a missing accessory. Keep any unresolved instruction visible rather than silently replacing it with a confident rule you cannot support.

Asset instructions should tell a producer what exists and what still needs creating. Harbor Kit can specify an overhead photograph of the actual case checklist, a separate view of the matching accessories, and a desk scene without borrower details. State that those photographs must be taken if they do not exist. Pasting a source location does not supply an asset, and choosing a video format does not cut footage. Use the reader next-action field for the public invitation, such as “Ask the desk about an unmatched accessory.” Put internal requests to arrange a photograph or confirm a staged message in the asset and production instructions instead.

Assign an owner so the brief has someone responsible for moving it forward. Estimated production minutes are values you supply, not calculated predictions. If the carousel is estimated at 45 minutes, the text brief at 20, and the conversation remains unestimated, the known total is 65 minutes with one unknown estimate. That does not mean all work will take 65 minutes. A blank estimate is stored as null, not zero; enter zero only when you deliberately mean no estimated production minutes. Counts of briefs, platforms, and manual checks describe the plan’s administration. They do not rank the content or predict reach, usefulness, or publication success.

Review the source relationship and the adaptation separately

Source review asks whether the selected evidence and location fairly support the derivative. Adaptation review asks whether the new piece fits its intended audience, format, assets, and next action. Read the full brief against both questions. Harbor Kit’s carousel could quote the source exactly while showing accessories from a different kit; the literal match would still be present, but the visual adaptation would be wrong. Another brief might correctly explain the process while its source location points to an earlier paragraph. Keeping the declarations separate helps reviewers name the problem instead of treating one favorable indicator as blanket approval.

The review flags and the Ready status are declarations made by the user. The planner does not certify facts, permissions, brand approval, or production readiness. Source title, reference URL, or source text changes clear source review declarations across the project, because the reference basis changed. Editing a derivative’s excerpt or source location clears both of its declarations. Editing its angle, opening, draft, asset instructions, or next action clears adaptation review. These resets prompt another look at the affected decision; they do not inspect the change and determine whether the new version is right or wrong.

Changing a platform selects a compatible starting format and clears adaptation review, while changing the format also clears that declaration. Re-read the retained text because it may still describe the previous deliverable. Administrative changes to a title, owner, estimate, or status do not erase editorial review. That convenience does not remove your responsibility to notice a substantive change hidden in an administrative edit. Before declaring a brief ready, inspect the preview’s actual authored values and the relevant format checklist. The checklist is guidance for a human reviewer, not a platform compliance test or a guarantee that the destination will accept the eventual file.

Choose an export for the part of the plan you are handing over

Use current-brief TXT or clipboard output when one producer needs one assignment. The source title and the selected brief’s title and angle must be present; unfinished neighboring briefs do not block that current export. This minimum is not the same as an editorial approval gate. Draft text may still need work, and unchecked manual declarations remain visible. The brief output carries source metadata, the selected excerpt, your authored fields, owner, effort, status, recipe, and review declarations. Check that the recipient can distinguish a proposed line from approved wording and an asset request from an existing photograph before sending the text outside your team.

Whole-plan review, CSV, and PDF require a source title plus a title and angle for every derivative. If the Threads idea has neither, finish those planning fields or keep working in JSON rather than assuming the export will omit it. Missing draft text and unchecked declarations are not silently completed. CSV preserves source and derivative data for inspection in a spreadsheet; it is not a platform publishing file or an automatic import into another tool. Copied whole-plan review is appropriate when a reviewer needs the complete context, including the supplied source text, rather than only the currently selected assignment.

Editable JSON serves a different purpose: it can preserve unfinished, structurally valid drafts for reopening. Save it during exploration, not only after everything is ready. The PDF is a styled review made from raster page images: its visible text is not selectable, searchable, or accessibility-tagged. A full JSON attachment preserves the source and brief fields; keep the separate editable JSON too. Choose copied text, TXT, or CSV when usable text matters. The PDF has a twelve-page and twenty-megabyte ceiling, so a large plan may need another output. None contains produced slides or cut video. Whole-plan exports and attachments can expose internal source material that a public post would never include.

Move from a clear brief to production without skipping the work

Have the assigned producer read the brief before beginning. For Harbor Kit, ask whether the photographer knows which case to use, whether the writer understands the missing-accessory exception, and whether the conversation owner will review replies. A question at this stage is useful information about the brief, not evidence that another automatic generation step is needed. Update the relevant fields and repeat affected manual checks. Keep the finished artwork, recordings, and editorial approvals in your normal production files. The planner records their instructions and declared state; it does not store a media library or confirm that the producer completed each external task.

When production is understood, a separate Content Calendar Generator can help organize release planning, or the Caption Builder can support work on accompanying copy. For a visual sequence, the Carousel Maker addresses the different job of assembling slides. Transfer the relevant information yourself and check the receiving tool’s requirements. There is no automatic handoff between this planner and those tools. Keep the source connection intact as you work so a last-minute wording change can still be checked against the article rather than against another derivative that may already have shortened the context.

Consider account automation only after you know what has actually been produced and approved. SMTasker offers supported publishing on Instagram, TikTok, Threads, Facebook, and LinkedIn where the app supports the chosen format; that does not extend to every format described by this planner. It uses connected Android phones with a Windows or macOS local client and dashboard configuration. The five-day trial can help you evaluate a relevant account routine separately from editorial production. Planner exports do not import automatically into SMTasker or Skye. A clear brief prepares a human to make the content, while the separate app handles only its supported account actions.

Questions about planning repurposed content