---
name: gct-goals-content-targeting
description: "Make sure your team knows what its work should achieve and who it should help."
category: Strategy & Measurement
stage: —
definitive_article: /9-triangles-framework-scalable-home-service-businesses/
status: complete
---

# GCT (Goals, Content, Targeting)

Make sure your team knows what its work should achieve and who it should help. This guide puts the goal, proof and people on one page. Start with one clear result you want, then choose the content and its audience.

**The path:** Goal → Content that supports it → People to reach → Checked brief

**Start when:** A page, project or campaign needs a clear brief before production or launch.

## Inputs

- The business or reader need, scope and desired result.
- Real source material: customer questions, records, photos, videos and proof.
- [Goals, Content, Targeting: the result, proof and people for this work](https://blitzmetrics.com/gct-business-strategy/) source guide, current audience knowledge and delivery constraints.

## Steps

1. Write Goals first: the intended change, who benefits and the time or completion condition. For an ad, name a relevant numeric target and period. For a task guide, name an observable reader result; do not invent a revenue target for every page.
2. Write Content next: exactly which sources and messages support that result. Prefer relevant proven work; verify claims, dates, attribution and use rights. A promise with no proof becomes a source gap.
3. Write Targeting last: identify the people, problem, geography and exclusions that matter. A paid audience is one implementation; an article can target a reader need and search intent without an ad audience.
4. Read the three parts together: achieve this result by showing this content to these people. Check whether the message and proof serve those people and whether the proposed next action can produce the desired result.
5. For the opening of any document, explain who it helps, why it matters and what to do first in two or three sentences at grade five or below. Define jargon on first use and use an owned explainer link; follow the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).
6. Save the agreed brief with date, source links, owner and the current recipe/page. Resolve material unknowns before dependent work. Keep its original target so later [Metrics, Analysis, Action: what happened, why and what to do](https://blitzmetrics.com/maa/) compares results to the real starting intent.
7. Hand the brief to the relevant production or campaign task. If the goal changes, record who changed it and why; do not rewrite history to make a missed result appear successful.

## 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/).

- [ ] Goal, Content and Targeting are specific, supported and in that order.
- [ ] The result has a measurable or observable pass rule appropriate to the work.
- [ ] The brief and grade-five context are saved with the actual next task and owner.

## Example(s)

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

A fictional repair shop wants readers to know when to stop using a leaking heater and call for help. Its content uses the technician’s checked steps and real photos. The audience is local homeowners with that problem. The guide passes when a reviewer can follow the safety and booking steps; no sales figure is invented.

## Handoff and Content Factory context

[Plan the next recording session](https://local-service-spotlight.github.io/task-library/?task=use-for-content-planning-and-video-topics#task-use-for-content-planning-and-video-topics) or the assigned article/campaign task receives the brief. [Write the agreed weekly report](https://local-service-spotlight.github.io/task-library/?task=submit-weekly-maa-report-every-friday#task-submit-weekly-maa-report-every-friday) later checks the result against it.

This work supports the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/) across its relevant stages. It uses the actual inputs and next owner above; a strategy or measurement guide does not manufacture transcripts, clips or other unrelated stage outputs.

## 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/9-triangles-framework-scalable-home-service-businesses/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=gct-goals-content-targeting#task-gct-goals-content-targeting)
- [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.