---
name: stage-3-content-endorsements-why-video-3x3-grid-library
description: "Give your team real stories and proof to share."
category: Strategy & Measurement
stage: —
definitive_article: /social-amplification
status: complete
---

# Stage 3: Content (endorsements, WHY video, 3×3 grid, library)

Give your team real stories and proof to share. This guide gathers the files and plans the clips you still need. Start with the goal, the offer and the work the business has done.

**The path:** Goal + real proof → WHY story + grid → Usable library → Processing

**Start when:** The accepted goals brief is ready and the engine needs a usable set of source content.

## Inputs

- [The accepted goal and offer brief](https://local-service-spotlight.github.io/task-library/?task=stage-2-goals-mission-90-day-goals-cpa-roas-budget#task-stage-2-goals-mission-90-day-goals-cpa-roas-budget).
- [Topic Wheel, the map of your offer, topics and real stories](https://blitzmetrics.com/topic-wheel/) with WHAT center, HOW middle and WHY outer; current source library and page map.
- Real customer stories, endorsements and event or work media, with attribution and permission; a recording owner and editor.

## Steps

1. Inventory existing relevant sources before asking for more. Record file, topic, person, date, claim supported, permission and usable state. Do not treat an authority’s photograph as their endorsement.
2. Prepare a real WHY story using [Create a three-minute WHY video](https://local-service-spotlight.github.io/task-library/?task=create-a-3-minute-why-video#task-create-a-3-minute-why-video). The owner tells a specific moment and useful reason behind the work; the target length is guidance, not license to invent a story.
3. Build the agreed nine-cell plan through [Create a 3×3 video grid](https://local-service-spotlight.github.io/task-library/?task=create-a-3x3-video-grid#task-create-a-3x3-video-grid). Name its variant: three topic rows by story/WHY, teaching/HOW and offer/proof/WHAT purpose columns. These purposes are not the Topic Wheel’s physical ring positions.
4. Use actual questions and proof for each prompt. If a proof cell lacks evidence, leave the gap and agree a truthful offer explanation; never fill it with a made-up customer win.
5. Record and inspect the selected takes. Count nine distinct usable files only when they exist and the editor can access them. An agent uses muted frames, captions and metadata unless silent playback is verified; it cannot claim it heard sound from a silent check.
6. Store raw files and selected takes through [Set up the Content Library](https://local-service-spotlight.github.io/task-library/?task=set-up-content-library#task-set-up-content-library). Keep names, versions, source links, rights and the grid IDs aligned.
7. Hand the best supported sources to Process with the intended outputs. The editor selects useful derivatives; every source need not become every format. Mark unmet content inputs explicitly before the engine’s next gate.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the result against its agreed requirements; see the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] WHY story and agreed grid cells have real sources and usable selected takes, or specific gaps.
- [ ] Topic Wheel labels and the chosen grid variant are correct and distinct.
- [ ] The editor can open the library and knows the supported claims, rights and intended outputs.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional shop plans a nine-cell grid but has only eight usable takes. The ninth was meant to claim a customer result without a source. The team replaces that prompt with a true offer explanation and still marks its recording pending. Eight files are handed over as eight, not a complete nine-video set.

## Handoff and Content Factory context

[Upload the sources for processing](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript) receives files and brief. [Plan targeting](https://local-service-spotlight.github.io/task-library/?task=stage-4-targeting-custom-audiences-lookalikes-remarketing#task-stage-4-targeting-custom-audiences-lookalikes-remarketing) receives the actual available content and gaps.

This work supports Produce in the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). The selected sources pass to Process, approved outputs go to Post, and useful proven work can enter Promote. The real inputs and handoff above set this task’s scope.

## Start with an agent

Give the AI worker this recipe, the real Inputs, the desired result and the actions already authorized. Ask for the saved output, source evidence, passed and failed checks, and the next owner. A skill is a set of instructions. Loading it does not prove access, install a scheduled job or complete the work. Use the [current installation guide](https://localservicespotlight.com/install/) only if reusable setup is needed; a ZIP contains instructions and is not an access grant.

Use the actual supported app and verified source access. A model name is not a promise of browser control, memory or unattended work. For recurring work, inspect the real job’s trigger, owner, timezone and observed firing; this recipe creates no schedule. Before any media playback, mute the player and set volume to zero. A silent review does not prove sound was heard.

## Record the real execution

Open the run record when work begins. Keep one execution ID, the exact starting recipe revision, input sources and actual state. Write a [meta article, the record of one real execution](https://blitzmetrics.com/meta-article-prompt/) with results, checks, failures and next owner. Link it to this task in the [Task Library](https://local-service-spotlight.github.io/task-library/). Writing is required; public release follows existing authority.

Reuse the same execution ID for internal reviews, meta writing, revisions and retries. A blocked run stays open with its dependency and owner, without an invented finish time. Keep historical public examples as dated evidence; article counts alone are not verified execution frequency. Use supported findings to propose and verify a recipe improvement.


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

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

- **Phase:** —
- **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:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## 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

- [Maintained source guide](https://blitzmetrics.com/social-amplification/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=stage-3-content-endorsements-why-video-3x3-grid-library#task-stage-3-content-endorsements-why-video-3x3-grid-library)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records work together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `complete`. It is preserved, not promoted by this rewrite. That label alone does not verify document readiness, account access, an actual execution or a client outcome.

A relevant real execution, source evidence, independent reviewer and accepted handoff remain to be recorded. The fictional example teaches the method and does not fill a real-run evidence gap. The opening and full method need a named semantic reviewer; the task-specific path is source guidance, with visible desktop/mobile presentation still to check.