---
name: step-3-watch-video-and-identify-gct
description: "Choose who the article helps and what it should do. Base the plan on the real video."
category: Content Factory — Process
stage: Process
definitive_article: https://localservicespotlight.com/article-guidelines/
status: complete
---

# Step 3: Watch video and identify GCT

A video can cover more than one point. This guide helps you choose the point your reader needs and the result you want. Start by reviewing the full source and the goal for this job.

**The path:** Whole source → Business goal → Supported content → Specific reader.

**Use this when:** A source recording and checked transcript are ready to guide an article or related assets.

## Inputs
- The full source, transcript, speaker map and any unverified intervals from Step 2.
- The project’s actual business goal and desired reader action. A current 90-day plan is useful if it exists; do not invent one or require a separate program by default.
- The source’s [Topic Wheel](https://blitzmetrics.com/topic-wheel/) entry and existing topic owner, if known.
- The article working document and tracker, with the person responsible for scope decisions.

## First-run prompt

> Review the supplied source and real project goal. Write three plain lines for Goal, Content and Targeting, with source timestamps and a clear article role. Identify the reader’s question and any unsupported promise. State review gaps instead of claiming a full watch from transcript-only evidence.

## Steps
1. Review the whole source for the story, tone, demonstrations and limits. Read captions alongside frames and use authorized speech evidence. Record portions not actually reviewed; a transcript skim cannot be marked “watched in full.”
2. Write the Goal first: the practical result this piece should help the business achieve. Prefer an actual reader action or need, such as helping a customer bring the right information, over an unmeasured promise to rank first.
3. Write Content second: the specific answer, scene or method the recording actually supplies. Attach useful timestamps. Separate a supported lesson from a proposed topic the speaker never covered.
4. Write Targeting third: who needs this answer, their situation, and the words they use for the question. If a funnel stage is useful, explain it plainly as learning, engaging or ready to act; do not make labels substitute for a real audience.
5. Read these three lines together using [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/). If the source does not serve the requested goal, adjust the article scope or flag the need for new source material. Do not force the transcript into a desired claim.
6. Choose the article role: a repeatable task guide, a broader explanation, a source story, or a record of one run. Only a task recipe needs a complete operational contract; a story should not be mislabeled definitive to fill a checklist.
7. Note the main reader question and candidate search phrase naturally. Search intent helps wording; it does not establish search volume or business performance without measured data.
8. Save the three lines, source anchors, role, scope decisions and open questions. Hand the brief to outlining so every section has a clear purpose.

## Definition of done (QA checklist)

- [ ] Goal, Content and Targeting are three specific, connected statements.
- [ ] The content line is supported by source moments; missing source review is stated.
- [ ] The goal comes from the project and has no invented performance promise.
- [ ] Audience, article role and main question are clear enough to guide the outline.

## Example(s)

**Fictional teaching example — no client plan was made.** A six-minute Maple Cycle video shows which bike photos help a repair shop prepare.

- **Goal:** Help new riders send useful details before a shop visit.
- **Content:** The mechanic shows a full-bike photo, a close-up of the issue, and a short note on when it happens.
- **Targeting:** Riders who want a repair quote but do not know what to send.

“Get a guaranteed final price from a photo” fails because the sample speaker says the shop may need an inspection. The reader’s question, “What photos help with a bike repair quote?”, fits the actual content. The article can teach that preparation task without claiming more leads or rankings.

## Handoff and Content Factory context

The outline writer receives the GCT brief, article role and timestamp evidence for [Step 4: research and outline](https://local-service-spotlight.github.io/task-library/?task=step-4-research-edit-add-timestamps-and-outline#task-step-4-research-edit-add-timestamps-and-outline).

Produce supplies the real source. **Process**, this stage of the [Content Factory](https://blitzmetrics.com/content-factory/), turns it into useful finished assets. Post saves or publishes them on the agreed channels. Promote tests and distributes suitable work within its own scope. The handoff above names this task’s actual next step; catalog neighbors alone are not prerequisites.

## When this runs

Once per article brief; revisit when its goal, audience or source changes. This is not an automatic recurring strategy review.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


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

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

- **Phase:** Process
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 3, gating 2 (runs every factory cycle or weekly)
- **Suggested previous station:** `use-descript-underlord-to-remove-filler-words`
- **Suggested next station:** `step-4-research-edit-add-timestamps-and-outline`
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

- Canonical article: https://localservicespotlight.com/article-guidelines/
- Exact task: [Step 3: Watch video and identify GCT](https://local-service-spotlight.github.io/task-library/?task=step-3-watch-video-and-identify-gct#task-step-3-watch-video-and-identify-gct)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Task recipe and publishing standard](https://blitzmetrics.com/definitive-article-guide/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Actual project goal, full-source coverage and scope decisions need supplied evidence.