reach-outreach-log

Keeps a private outreach log with one row per person you wrote to, holding the date, channel, the reason you used, whether a warm path existed, reply or none, first call or none, open promises and any

SKILL.md

GitHub

Outreach Log

When To Use

You cannot say who you wrote to last month or what you promised. This is the plain record behind everything else. It answers: who have I written to, by what route, what came back, and what do I still owe?

When Not To Use

If you only need what is due this week, use the Follow-Up Tracker; it is rebuilt weekly and this is the record behind it. Notes on what someone is like, how warm they seemed or how likely they are to buy are not kept here or anywhere in this guide.

Inputs

  • Your Run of Ten Plans, Reply Triage results and Call Recaps, or your own notes of who you wrote to.
  • The existing log, if you have one.
  • Where it lives: a private Project (beta) or your own private file. Never a shared space. If you have none of this, I start from what you remember of the last run and mark the rows "from memory".

Approach

A private contact log with data kept to the minimum. The UK Information Commissioner's Office describes data minimisation as holding the least personal data you need for your purpose; here the purpose is knowing who you wrote to and what you promised, so the log holds exactly that. How data protection rules apply to your records is a question for you: check with a qualified adviser. Notes about people slide into profiles unless the columns stop them, so there is no column for one. The failure it prevents: writing a "first" message to someone you already wrote to in spring, who asked you not to.

Workflow

  1. Ask at most three questions: which runs to enter, where the log lives, and whether anyone has asked not to be contacted.
  2. Write one row per person: date first written, channel, the reason you used, warm path yes or no, reply or none, first call or none, promises open, do not contact yes or no.
  3. Enter do not contact first. A person marked yes stays in the log as a name and that flag only, so they are never written to again by mistake.
  4. Pull every open promise into a list, yours first, each with a date. "Soon" is replaced with a date you set.
  5. Strip everything that is not a fact about your contact or a promise: ratings, impressions, guesses about interest, personal details, anything said in confidence. I list the kind of line removed, not its content.
  6. Check where the log lives. If it sits anywhere shared, move it before adding more.
  7. Say what the review will be able to count from these columns, and what it will not.

Output Format

# Outreach Log
Kept in: [your private Project or file] | Last updated: [date] | Rows: [number]
## Open promises
| Who | What was promised | By whom | By when |
|---|---|---|---|
| [name] | [reply, document, introduction] | [you / them] | [date] |
## People written to
| Person | First written | Channel | Reason used | Warm path | Reply | First call | Do not contact |
|---|---|---|---|---|---|---|---|
| [name] | [date] | [email / platform message / call / introduction] | [share / congratulate / introduce / suggest a conversation] | [yes / no] | [date, or none] | [date, or none] | [no / yes, since date] |
## Removed from the log
- [kind of line removed: rating, impression, personal detail]
## Decision
[Your name] decides by [date] which open promise to keep first, and how long a row stays in the log before it is deleted.

Done When

  • Every person written to has one row with all eight columns filled.
  • Every promise has an owner and a date.
  • Do not contact flags are entered and match your Reply Triage results.
  • No rating, impression or personal detail remains, and the log sits in a private place.

Quality Bar

  • Facts and promises only; message text is never pasted in.
  • There is no column for warmth, value, likelihood or priority of a person.
  • The research coverage label is not carried into the log.
  • You set how long rows are kept; old rows are deleted, not archived forever.
  • A private record of your own actions, with nobody rated; you keep it and you decide what stays.

Next

Run reach-outreach-review (Outreach Review) after a few runs to see what your own counts say.

About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).