---
name: step-11-proofread-with-grammarly-or-chatgpt
description: "Check the whole draft for clear words and true facts. Fix mistakes while keeping the real voice."
category: Content Factory — Process
stage: Process
definitive_article: https://localservicespotlight.com/article-guidelines/
status: complete
---

# Step 11: Proofread with Grammarly or ChatGPT

Small errors can make a good article hard to trust. This guide helps you fix the words and check the facts before the next step. Start with the full draft and the source it came from.

**The path:** Complete draft → Suggested fixes → Source and voice check → Ready draft or clear gaps.

**Use this when:** The article has its planned text, links, visuals and source player and needs the final Process proofreading pass.

## Inputs
- The complete versioned draft, [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) brief, verified transcript and source proof.
- The actual spelling/identity list for this project, not a generic list of unrelated client names.
- An approved proofreading tool or manual workflow, with permission to send the draft’s data to that tool.
- The title/headings/search fields, link and media evidence, and next publisher.

## First-run prompt

> Proofread this full draft against the supplied source and project spelling list. Propose small fixes, review each for meaning and voice, and check facts separately. Keep media and text-to-speech silent. Return the corrected revision, key decisions and any unresolved evidence; do not call the article ready from a grammar score alone.

## Steps
1. Save the current draft so each change can be reviewed. If using Grammarly or ChatGPT, request suggestions for grammar, clarity and consistency only. Do not upload private content to an unapproved service or ask for fabricated expansion.
2. Review changes individually. Accept a typo fix or shorter clear sentence; reject a rewrite that changes voice, certainty, chronology, attribution or the actual lesson. Do not bulk-accept every suggestion.
3. Check every name, number, quote and material factual claim against the source or cited primary research. A fluent rewrite is not a fact check. Preserve unresolved claims as explicit editorial gaps rather than guessing.
4. Compare several representative passages with the source voice, including the opening and a direct quote. Ensure personal first person belongs to the real author and company/reference voice remains appropriate.
5. Read the full text in order, including captions, headings and link anchors. Check for repeated words, missing context, abrupt transitions and broken formatting. Use a silent read; do not start text-to-speech through the user’s speakers.
6. Recheck the specific GCT opening and plain first-use term explanations. Use a readability screen to find long sentences, then judge clarity. Keep the meaningful lead visual and page-role requirements intact.
7. Verify that title and description still match the final body and headings remain logical. Google does not impose hard 60/160-character rules, and an exact keyword in the first paragraph is not this proofreading pass’s universal acceptance test.
8. Review the whole-page checklist state. Mark Process ready only for the checked revision and completed applicable work. Keep an unavailable caption/source fact or unresolved rights issue as a specific handoff gap.
9. Save the corrected draft, change notes and evidence references. Hand it to the publisher with the actual scope: draft placement, update or publication already authorized for that job.

## Definition of done (QA checklist)

- [ ] Each accepted change preserves meaning, attribution and real voice.
- [ ] Material facts and proper names are source-checked or clearly unresolved.
- [ ] The full draft, captions/headings and first-use terms have been read.
- [ ] The exact final revision and applicable ready/pending checks are recorded without invented SEO or audio guarantees.

## Example(s)

**Fictional teaching example — no actual draft was reviewed.** A proofreading tool changes “The photo helps us prepare” to “The photo lets us diagnose the fault.” The editor rejects it because the sample source requires an inspection.

The editor accepts “bring you bike” → “bring your bike.” They retain the mechanic’s plain phrase “show us what happens” instead of “provide a comprehensive operational demonstration.” The review note lists those decisions and keeps an unclear source term at 02:18 pending. Better grammar does not erase that evidence gap.

## Handoff and Content Factory context

The assigned publisher receives the exact checked revision for [Step 12: place the article in WordPress](https://local-service-spotlight.github.io/task-library/?task=step-12-post-article-on-wordpress#task-step-12-post-article-on-wordpress). Outstanding checks remain attached to that handoff.

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

One proofreading pass per completed draft, with targeted rechecks after later substantive edits.

## 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 3, gating 3 (runs every factory cycle or weekly)
- **Suggested previous station:** `step-10-embed-source-video`
- **Suggested next station:** `grade-article-using-jennifer`
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 11: Proofread with Grammarly or ChatGPT](https://local-service-spotlight.github.io/task-library/?task=step-11-proofread-with-grammarly-or-chatgpt#task-step-11-proofread-with-grammarly-or-chatgpt)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Task recipe and publishing standard](https://blitzmetrics.com/definitive-article-guide/)
- [Google’s title-link rules](https://developers.google.com/search/docs/appearance/title-link)
- [Google’s snippet rules](https://developers.google.com/search/docs/appearance/snippet)

## 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.
- The real source, tool data scope and final revision need actual checking; this proposal does not certify a published article.