---
name: step-5-write-article-from-transcript
description: "Turn your source into a useful article. Keep the real voice, facts, and story."
category: Content Factory — Process
stage: Process
definitive_article: https://localservicespotlight.com/article-guidelines/
status: complete
---

# Step 5: Write article from transcript

Your article should sound like the person in the video. This guide helps you turn their best points into clear, useful words. Start with the checked source and the plan for the reader.

**The path:** Checked outline → Source-led draft → Proof and voice check → Complete article.

**Use this when:** The GCT brief and timestamped outline are ready for a full source-grounded draft.

## Inputs
- The verified transcript, full source, timestamped outline and source-review gaps.
- The [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) brief, page role, intended site and real author/speaker relationship.
- Checked research and media rights, exact quotation/identity records, and maintained [Article Guidelines](https://localservicespotlight.com/article-guidelines/).
- A working document, existing canonical page if any, and named editor.

## First-run prompt

> Write the complete article from my checked outline, transcript and research. Preserve the real author’s voice, source limits and page role. Give the reader a clear answer with useful proof and owned term links. Keep every claim traceable and put unresolved evidence in review notes; do not invent stories, quotes, outcomes or keyword rules.

## Steps
1. Write into the outline one section at a time. Start with the answer or scene supported by the source. Do not ask a model to fill a topic with generic facts when the source does not support them.
2. Choose the correct voice. On a personal-brand page, write as that person in first person when the project supports that authorship. A company article may use third person. Do not make an interviewer’s experience become the named author’s first-person claim.
3. Keep useful concrete details and exact numbers with their source anchors. Paraphrase clearly when a sentence is not a verbatim quote. Add researched claims with their actual citation instead of placing them in the speaker’s mouth.
4. Show the moment, not the resume: lead with a specific scene, useful action or lesson before credentials. Names and awards can supply relevant context; avoid a trophy-name paragraph that substitutes famous names for the story. Make relationship language no stronger than the evidence.
5. Place compact proof near the point it supports: a real photo, exact quote, source video or primary record with known identity/context. Keep the internal verification process, private proof IDs, scoring and research notes in the working evidence map unless those systems are the actual topic.
6. Use praise only with an exact named source, relevant role/company or city, and applicable permission. A quote without verified identity, primary source or needed permission remains **HOLD** and stays out of the public draft. Domain or company attribution alone does not establish a named speaker. Narrow an unsupported relationship claim instead of adding defensive boilerplate about it.
7. Write short paragraphs and explain the first meaningful use of a specialist term with a maintained owned guide. State who, why, the first action and the useful outcome in the opening, using grade-5-or-lower language. This is the maintained opening rule for every document. Use the reader’s phrase naturally without forcing an exact keyword into an awkward first sentence.
8. Make each section fulfill its heading. A task recipe must describe the start, inputs/access, ordered work, measurable output, checks and next step. A story or reference page keeps its own role; do not invent completed work to make it look like a recipe.
9. Compare the whole draft with the GCT and source map. Remove unsupported statements, preserve needed legal disclosures, and mark remaining source gaps in review notes. Save the complete draft for titles and headings.

## Opening meaning review

Keep the opening to two or three short sentences at grade 5 or below. It must show the actual reader’s situation, why the subject matters, the useful result, and how this page helps. A source-backed moment or useful finding can lead. Keep its relevant visual in the first screen; check that the body delivers the opening’s promise.

Save the exact opening and artifact revision in the existing run receipt. Have the reviewer quote the words that establish the situation, reason to care, result and method. Record PASS, FAIL or UNKNOWN with reasons and a readability diagnostic. A grade score, keyword, generic audience label or unsupported conversion promise cannot approve meaning. Follow [Step 7: write and review the opening](https://local-service-spotlight.github.io/task-library/?task=step-7-write-hook-and-establish-context#task-step-7-write-hook-and-establish-context) and the [maintained opening standard](https://github.com/dennisyu/local-service-spotlight-skills/blob/main/standards/every-article-and-project-starts-with-specific-gct.md).

## Definition of done (QA checklist)

- [ ] Every factual claim and quote has a source; no invented scene, result or testimonial is present.
- [ ] Voice and relationship wording match the actual author and evidence.
- [ ] The opening is clear, sections answer the reader’s need, and the page’s role is preserved.
- [ ] Proof is useful and close to its claim; private internal evidence notes stay outside public prose.

## Example(s)

**Fictional teaching example — the shop and statement are invented.** In the sample recording, Maple Cycle’s mechanic says, “One photo helps us start, but I may need to see the bike.” A faithful draft is:

“A photo helps us prepare for your visit. Send one view of the whole bike and one close-up of the issue. I may still need to inspect it before I can give you a final quote.”

The draft rejects “Get an exact price in minutes,” because the sample source says no such thing. On the mechanic’s personal page, “I” can reflect their voice. A company summary can say “The mechanic may need to inspect the bike.” Neither version claims a real customer result.

## Handoff and Content Factory context

The article editor receives the draft and evidence map for [Step 6: write the title and headings](https://local-service-spotlight.github.io/task-library/?task=step-6-write-title-and-headings#task-step-6-write-title-and-headings).

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 requested article draft, with bounded revisions when a reviewer or source change identifies a real issue.

## 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:** 5/5 `●●●●●` — frequency 5, revenue 4, gating 3 (runs every factory cycle or weekly; creates the asset ads amplify)
- **Suggested previous station:** `create-quote-cards-from-strongest-statements`
- **Suggested next station:** `run-overnight-local-writer`
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 5: Write article from transcript](https://local-service-spotlight.github.io/task-library/?task=step-5-write-article-from-transcript#task-step-5-write-article-from-transcript)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Task recipe and publishing standard](https://blitzmetrics.com/definitive-article-guide/)
- [Entity linking: choose the right person, company or guide](https://blitzmetrics.com/entity-linking/)
- [Google’s title-link rules](https://developers.google.com/search/docs/appearance/title-link)

## 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 author voice, quote rights and source claims must be verified for the real article.