Record what changes future action

Your relationship record should help a teammate understand how to work with a host. Useful notes include preferred topics, submission methods, guest requirements, recording constraints, and explicit instructions about future outreach. A transcript of every conversation is rarely the most usable summary.

Keep facts and interpretations separate. “Host asked for practical founder stories” is a direct preference. “Host probably dislikes academics” may be an unsupported interpretation of one declined pitch. Record what was actually said so later decisions do not become more certain than the evidence allows.

Connect the conversation to its outcome

Link notes to the relevant show, guest, and outreach thread. Record whether a host expressed interest, requested additional information, offered a recording slot, declined, or left the proposal unanswered. These are different states and should not collapse into a vague label such as “contacted.”

If a booking progresses, preserve the agreed topic and any boundaries. The next teammate should not need to reconstruct the promise from a chain of emails. Clear notes also help avoid sending a guest bio that contradicts the version the host already reviewed.

Keep personal information limited to what is appropriate and useful for the professional relationship. A host’s unrelated private circumstances do not need to become permanent team context simply because they appeared in a message. Focus on the information required to handle the work well.

Make the record part of the workflow

Relationship notes are only useful when people consult them before reaching out. Make the relationship check a required step in podcast research. If a show already has an owner or an active thread, route the new idea through that person instead of starting a parallel introduction.

Review stale notes when they affect a new decision. A host’s old preference may still be helpful, but it is not a permanent rule unless they made it one. Preserve the date and context so the team can judge whether a brief confirmation is appropriate.

  • Log the host’s actual preference in clear language.
  • Attach the note to the correct show and conversation.
  • Use distinct statuses for interest, booking, decline, and silence.
  • Assign an owner and a specific next action.
  • Check the record before every new pitch or follow-up.