---
name: get-mentioned-in-publications
description: "Help the right readers learn from your real work."
category: Personal Branding
stage: —
definitive_article: GAP — to be written
status: needs-work
---

# Get mentioned in publications

Help the right readers learn from your real work. This guide turns a useful fact or story into a clear press pitch. Start with a source you can prove and a writer who covers that topic.

**The path:** Real story + proof → Relevant writer → Specific pitch → Checked coverage

**Start when:** The person has a verifiable story or expert contribution suitable for a publication.

## Inputs

- A source-backed story, useful data or expert response, with permission to share the material.
- A current press kit, accepted name and home site, and a verified publication/writer list.
- Submission rules, deadline and outreach owner; this task’s dedicated canonical article remains unmapped.

## Steps

1. Choose outlets and writers whose actual recent work covers the topic. Read the editorial focus and submission rules. A prestigious name alone does not make the story relevant, and a purchased placement is not independent earned coverage.
2. Build the pitch around a true new fact, useful lesson or timely perspective. Verify numbers, dates, qualifications and client permission. State what the source proves and what remains uncertain; do not create news by inventing a milestone.
3. Prepare a concise response or pitch with the reader value, specific angle, supporting sources and a relevant bio. Keep quotes attributable and in the person’s voice. Use [Article Guidelines](https://localservicespotlight.com/article-guidelines/) for plain context and proof, without turning the message into a company sales page.
4. Send through the writer’s real accepted channel only under existing authority. Track the exact message, recipient, deadline and reply. If a journalist asks a follow-up, verify the new facts before preparing an answer; speed does not substitute for accuracy.
5. Coordinate any interview or source material with the actual editorial terms, attribution and use rights. Paid promotion is a separate optional task; do not assume an ad can or should target an individual journalist before a pitch.
6. When coverage is reported, inspect the published source for the correct identity, exact quoted meaning, disclosure and link. Prepare a factual correction if needed and keep requested versus accepted changes distinct. A pitch or interview does not establish publication.
7. Add the verified source to the proof inventory with date, independence, permission and exact supported claim. Keep the missing canonical task article as a visible mapping gap; use the current personal-brand method hub for context without calling it this task’s finished recipe.

## Definition of done (QA checklist)

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

- [ ] The story and pitch are useful, supported and addressed to a relevant actual outlet.
- [ ] Every claimed published item is checked; pending or declined pitches remain honest.
- [ ] Proof, permission and attribution are recorded, and the dedicated article gap remains visible.
- [ ] The exact output, source revision, reviewer evidence and remaining owner action are saved.
- [ ] For any reader-facing output, the short grade-five opening states the reader’s useful outcome and supporting method or proof. The body delivers that promise; a useful authentic visual appears in the first screen. Retain exact text and quoted reviewer evidence.

## Example(s)

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

A fictional shop owner has measured a seasonal rise in one repair type. The team checks the date range and sample, then drafts a local trade story. The editor requests an interview but has not committed to publish. The record shows a real response and a pending interview, not a press mention or a new endorsement.

## Handoff and Content Factory context

[Check outside proof](https://local-service-spotlight.github.io/task-library/?task=build-third-party-validation#task-build-third-party-validation) receives only actual coverage. The task-library owner receives the existing unmapped article gap; the outreach owner retains the exact thread.

This task supports the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). Identity, proof, access or coordination can support several stages. Use the real inputs and receiving owner above; this task does not create unrelated transcripts, clips or ads merely because the diagram has four stages.

## Start with an agent

Give the [AI worker](https://blitzmetrics.com/build-agents/) this recipe, the real inputs, desired result and actions already authorized. Ask for the saved output, sources, checks and next owner. A [skill is a written recipe](https://localservicespotlight.com/plugin/); loading one does not prove account access or perform the task. Use the [installation guide](https://localservicespotlight.com/install/) if reusable setup is needed. A ZIP is a source snapshot, not an access grant or automatic update.

Use the app’s actual supported tools and verified file/account access. Keep a missing human verification step with its real owner. Recurring work needs its own configured job, trigger, timezone and observed result; this guide creates no schedule. Before any media playback, mute the player and set its volume to zero. If silence cannot be verified first, use captions, frames, metadata or another silent check.

## Record the real execution

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

Reuse the same execution ID for internal checks, revisions, retries and meta writing. A blocked run stays open with its dependency and owner, without an invented finish time. Dated public examples and distinct verified execution counts remain separate. Propose the smallest source-backed recipe improvement when the actual evidence reveals a defect.


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

- This task’s dedicated canonical article is not mapped. The [personal brand, the public record of your work](https://blitzmetrics.com/personal-brand/) supplies method context; resolve the missing recipe with its owner without creating a competing hub.
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=get-mentioned-in-publications#task-get-mentioned-in-publications)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records fit together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `needs-work`. It is preserved, not promoted by this rewrite. That label alone does not prove document readiness, account access, an actual execution or a client result.

The fictional example teaches the method and does not fill a real-run evidence gap. A named semantic reviewer must check the actual opening, full method, sources and handoff. Check the useful opening visual in the normal rendered guide at the current required desktop and mobile sizes, including 1280 × 800 and 390 × 844. Source readability checks do not prove public presentation or task execution.