Source Log Template (Free)

What this is (and what it is not)

• For: creators who want a clean, repeatable sourcing workflow (source IDs, dates, limits, correction-ready notes).
• Not for: case handling, case review, outcome services, or emergency/legal guidance.
• Privacy-first: don’t put sensitive personal data into public drafts or forms.

Why this exists

Credibility usually fails because the workflow fails: sources get scattered, links lose context, and claims expand beyond what the evidence supports. This template forces a simple discipline: Claim → Evidence → Limits → Correction path.

Common failure modes (quick scan)

• Writing conclusions first, then searching for “support” after.
• No source IDs or access dates (links change; context disappears).
• Mixing notes, interpretations, and evidence in one paragraph.
• Publishing claims without stating limits (readers assume you proved more than you did).
• Sharing raw material publicly that introduces privacy risk.
• No corrections path (updates turn into silent edits or confusion).

Minimum standard checklist (5 minutes)

If you only do one thing: run this before publishing any claim set.

• Each claim is a single sentence (not a paragraph).
• Each claim links to at least one source (URL or file reference) with a Source ID.
• Every source has a date accessed.
• You wrote one “Limits” line per claim (what you cannot prove).
• You separated evidence from interpretation (label your interpretation explicitly).
• You included a privacy note (what should not be public).
• You included a correction path (how updates will be noted).

Copy template (must-keep)

Worked example (before → after)

Before (too vague / over-claimed):

“They changed the policy and lied about it. I saw messages and everyone knows it.”

After (publishable structure):

• Claim 1: “A policy change was communicated to staff.”
• Evidence: S-001 (summary of message content; stored privately), S-002 (public web page; date accessed).
• Limits: “I cannot confirm who approved the change or the internal timeline.”
• Publishing note: “Details are summarized to reduce privacy risk; originals retained privately.”
• Correction path: “If the public page changes, I will note the date and what changed.”

Why this matters:

• Readers can see what is supported, and what is not.
• “Limits” prevents accidental over-claiming.
• Privacy-first: you can keep sensitive originals private.

Upgrade path (choose the right next step)

• Stay free: use this page as your starter template when you publish occasionally.
• Upgrade to Pro ($19): if you publish repeatedly and want formatted, printable, repeat-use sheets. See Toolkits
• Take Training ($79): if you want habit-building discipline (claims, limits, correction-ready writing). See Training

Reminder: purchases are for general education materials. They do not buy coverage, influence, or outcomes.

FAQ

Internal links (pick by intent)

• Buy / compare: Toolkits hub
• Learn: Training
• Standards: Principles
• Support (no influence): Send a tip