PlaysbyMoat8
Back to the library
The workflow guideMarketing

Build a library of journalist outreach templates

Collect public examples of press outreach and turn useful structures into reusable draft templates.

5 implementation stepsIntermediate

How this works

A pitch-template library captures useful communication structures, not other peoples wording, private contact lists or claims. Identify how a public example establishes relevance, provides a newsworthy fact, offers evidence and makes a modest next-step request. Then write original templates for the team’s actual stories.

Separate template development from a particular outreach campaign. A polished structure is not proof that a journalist is interested, that an embargo is agreed or that a result can be promised. Tailor each draft using recent, relevant public editorial work and facts the organization can substantiate.

Before you start

Story brief

Identify the verified announcement or insight, its date, evidence and why it matters to a specific audience.

Example access

Use public or explicitly authorized examples. Do not collect private inbox correspondence without permission.

Editorial review

Identify a reviewer for factual claims and any timing, embargo or spokesperson commitments.

Prepare the inputs

public_examples
Required

Example IDs, dates, publication context and short structural notes

Do not assume an example caused coverage or copy its distinctive language.

company_brief
Required

Approved facts, claims, evidence and available spokesperson roles

Separate planned developments from completed announcements.

pitch_use_cases
Required

Announcement, expert commentary, data story or follow-up

Each template must have a clear reason to exist.

recipient_context
Optional / conditional

Relevant recent editorial topic and audience

Use only legitimate public professional context; optional until tailoring.

Implementation, step by step

  1. Select structurally useful examples

    • Choose a small set relevant to the intended story types, not simply famous or visually attractive pitches.
    • Record what each example demonstrates and any missing outcome evidence. Avoid claiming a successful outreach rate from anecdotes.

    Checkpoint: The example matrix supports specific structural lessons.

  2. Extract reusable mechanics

    • Identify the relevance hook, factual news element, supporting evidence, proposed access and next-step request.
    • Distinguish a reusable structure from distinctive wording or a claim belonging to the original sender.

    Checkpoint: A neutral pattern description can be used without copying the example.

  3. Write original templates

    • Create separate templates for the selected use cases using explicit fields for story fact, audience relevance, evidence and contact role.
    • Keep unsupported superlatives, assumed exclusivity and artificial urgency out. Make optional sections visibly conditional.

    Checkpoint: Each template is original and has a completion checklist.

  4. Tailor a sample pitch

    • Use the approved story and relevant public editorial context to fill a template. Explain relevance in a concrete sentence rather than flattering the recipient.
    • Verify that attachments, spokesperson access and dates actually exist. Leave unresolved facts as review questions rather than invented details.

    Checkpoint: The sample is a reviewable draft with evidence for its claims.

  5. Organize and evaluate the library

    • Index templates by story type, audience and required evidence. Preserve version and review date.
    • If outreach is separately authorized, record delivery and relevant responses distinctly from coverage; otherwise hand off drafts only.

    Checkpoint: The library has a clear selection rule and an evidence-based improvement loop.

Decisions along the way

An example includes an impressive result without support

Use its structure only and omit the borrowed result.

No recent relevant editorial topic is found

Keep the draft untailored and flag relevance as unresolved instead of inventing a connection.

A draft offers exclusivity or an embargo

Require the actual agreed terms and owner authorization before including the commitment.

What you will produce

pitch-template-library.md

Markdown

Original structures with explicit completion requirements.

Include: use_case · required_facts · subject_pattern · body_structure · review_checks

sample-pitch-review.csv

CSV

A factual and relevance checklist for sample drafts.

Include: draft_id · claim · evidence · recipient_relevance · open_question · review_status

Check the result

  • Check that template wording is original and borrowed evidence is not represented as the team’s result.
  • Verify every filled claim and offered asset against the approved brief.
  • Confirm that recipient relevance uses actual public editorial context.
  • Separate draft, sent, replied and covered states in any evaluation record.

When something goes wrong

The story has no verifiable news element

Produce a story-development question list instead of disguising promotion as news.

A source example disappears

Retain permissible structural notes and mark the source unavailable; do not claim current verification.

The requested contact or access is unavailable

Remove the offer and ask the owner for a feasible alternative.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Create a data-story pitch template and a sample from our approved research brief.

Inputs

Synthetic brief contains a survey of 80 respondents, not a representative national sample. A public example claims a nationwide trend, but the supplied study does not.

Expected result

Write an original sample about observations from the 80-person study, retain the sample limitation and offer the actual methods note. Do not borrow the nationwide claim or assume coverage.

Run a small pilot

Start small

Review a few templates against distinct real story briefs before expanding the library.

Record the baseline

Record current rewrite effort, factual corrections and relevance failures.

Agree success criteria

Judge draft readiness and reviewer corrections; evaluate responses only from an authorized, comparable outreach batch.

Stop or revise

Stop reuse when templates encourage unsupported claims or commitments the team cannot meet.

Keep the scope clear

  • Do not send outreach, scrape private contact data or promise media coverage as part of template preparation.
  • Keep internal spokesperson availability and confidential story details within their approved audience.

Check before using

Check factual claims and relevance to the journalist; review each draft before sending.

Business activities

  • Find and approach prospects
  • Create and publish content

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Public outreach examples · An accurate company brief

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗