---
name: process-through-content-factory
description: "Make the files you need from a thank-you clip. Use this when the clip is checked and you know who should see it."
category: Thank You Machine
stage: Process
definitive_article: /thank-you-machine
status: complete
---

# Process the Thank-You Clip

One thank-you clip can be used in more than one place. This guide helps your team make the files you need without changing the story. Start with the checked clip. Finish with clear files and a list of where each may go.

**The path:** Checked clip → useful versions → reviewed files and next owner.

**Use this when:** the original clip is checked and you know who should see it.

## Inputs

- The original clip, checked transcript and source note.
- The agreed channels, audience and sharing rights; planned formats must serve a real use.
- Access only to the file store and editing tools needed for the chosen outputs.

## First-run prompt

> Use this thank-you clip to make the agreed files. Keep the facts and tone. Fix captions, label each version and prepare the right post or private-message copy. Show which files are checked and what comes next.

## Steps

1. Open the original and source note; confirm that this is the checked take. Preserve the original rather than overwriting it.
2. Choose the needed outputs, such as the full clip, a short cut, captions or a brief text post. Do not force five formats if the audience only needs one.
3. Edit for clarity and remove dead space without changing the reason for thanks. Keep enough context for a stranger to understand the deed. Do not use an edit to make the recipient appear to endorse your business.
4. Correct names and words in the transcript, then time captions to the clip. Choose framing and text size for each agreed channel; verify current platform requirements when exporting.
5. Write a short caption naming the deed and why it mattered. Attribute any real quote accurately. A thank-you you recorded is not a customer testimonial; do not label it as their recommendation.
6. Review each export visually and inspect its duration, dimensions, file size and caption timing. Keep agent playback silent. Open the saved export, not only the editor preview.
7. Create an output list with file link, format, audience, permission limits, checked state and next owner. Prepare post drafts or the private-message draft. Publish or send only when that action is already authorized, and record its actual result separately.

## Definition of done (QA checklist)

- [ ] The original is preserved and each chosen export opens.
- [ ] Facts, names, attribution and tone match the source.
- [ ] Captions and visible text are readable for the intended channel.
- [ ] Every output has a purpose and sharing scope; no fabricated testimonial was created.
- [ ] Draft, exported, posted and delivered states are distinguished in the handoff.

## Example(s)

**Fictional teaching example — no client result or completed run.** The agreed use is a private video plus one team post. The editor saves the full clip with corrected captions and a short post draft. No testimonial, public blog post or ad is created just to fill a quota.

## Handoff and Content Factory context

Pass an approved public post to [Tag the Right Person in a Thank-You Post](https://local-service-spotlight.github.io/task-library/?task=tag-the-person-on-social-media#task-tag-the-person-on-social-media). If this stays private, hand off the exact message and destination to the authorized sender. A suitable posted clip can later enter [Test a Thank-You Post With a Small Ad](https://local-service-spotlight.github.io/task-library/?task=boost-with-dollar-a-day#task-boost-with-dollar-a-day).

This fits the [Content Factory](https://blitzmetrics.com/content-factory/): Produce a true story, Process it into useful files, Post only in the agreed places, and Promote a suitable post when its test has a budget. Each stage passes its checked files and next owner forward.

## When this runs

Run after a checked clip arrives. Use the agreed output list rather than a fixed number of posts or an assumed automatic distribution job.

## First-run setup and continuity

Use the files and accounts this task actually needs. A skill is a written recipe; the [AI worker](https://blitzmetrics.com/build-agents/) needs suitable tools and access to follow it. This file does not install an app, connect an account or start a timer. Follow the [setup guide](https://localservicespotlight.com/install/) for the chosen app. Carry out work already covered by the user's instructions; ask only for an exact missing item or a new action outside that scope.

Save the source, current state, checked result and next owner in the project files. Check that record before retrying or handing work to another person. Configure a repeat only when requested, with its time zone, actual runtime and first successful firing. An app or model name does not prove persistence, memory or a schedule.

Keep every agent media check muted with volume zero before playback. If that cannot be verified, use captions, metadata or still frames and record the limit. Do not play sound through the user's speakers without their current request.

## Write up the real run

For each real attempt, [write the meta article](https://blitzmetrics.com/meta-article-prompt/): its task and source revision, starting point, work done, evidence, measured result, gaps and next handoff. Save one execution ID across retries and edits. Partial, blocked and failed work also gets a record. A saved draft satisfies writing while any public release is pending. Writing does not grant publication authority.

A teaching example is not a real execution. Do not count it, a repeated check or a revision as another run. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains the link between reusable instructions and actual work.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Process
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Process-stage artifact examples include `transcript.md`, `gct.md`, `article.html` (or a staged draft), `clips/`, or `04-Promote-Creatives/`. These are examples, not requirements for every task. Follow this task's actual Inputs and Handoff sections for the required output, evidence, and next owner. Pass the files or records, not one vendor's memory.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Exact task: [Process the Thank-You Clip](https://local-service-spotlight.github.io/task-library/?task=process-through-content-factory#task-process-through-content-factory)
- [One-minute video guide](https://blitzmetrics.com/one-minute-video-guide/) — how to record one clear point.
- [Content Factory](https://blitzmetrics.com/content-factory/) — how the source becomes checked posts.
- [Dollar-a-Day guide](https://blitzmetrics.com/dollar-a-day/) — the paid test method; current platform controls still need checking.

## Review and evidence still needed

The original contributor state is preserved. Instruction review, article certification, account access and completed work are separate states.

- Source mapping needs repair: on September 6, 2026, the recorded /thank-you-machine/ hub redirected to /face-socks/, a gift-ordering guide. That live gift recipe does not certify this video workflow. Keep the task ID and contributor state; use the relevant video and process guides below until the owner resolves the canonical video hub.
- Add a dated, real execution record with the actual checked output. The example below does not fill that gap.