Toolkits · Free

Civic Action Map (Free)

A general next-step map for what to do after publishing: set a minimum defensible claim, choose public vs private evidence, publish with a correction path, and schedule review dates. Education only — not legal advice.

What this is (and what it is not)

  • For: general publishing discipline after you post something in the public interest (non-case, non-tailored).
  • Not for: case strategy, legal guidance, emergency response, or outcome services.
  • Privacy-first: do not publish or send sensitive personal data; reduce identifying details by default.

Why this exists

After publishing, people often either do too much (over-claim, over-share, escalate without clarity) or do nothing (no review date, no corrections plan). This map keeps actions proportional: claim → evidence → limits → corrections route → review cadence.

Common failure modes (quick scan)

  • No “minimum defensible claim” (the post implies more than it proves).
  • No limits statement (readers assume certainty where there is none).
  • Publishing raw material that increases privacy risk.
  • No corrections route (updates become silent edits or confusion).
  • No review date (stale claims stay live after facts change).
  • Mixing support with influence expectations (support must never buy coverage or outcomes).

Minimum standard (5 minutes)

If you do nothing else, complete these six items before taking any next step.

  • Claim: write the minimum defensible claim in 1 sentence.
  • Evidence split: list what is publishable vs what remains private.
  • Limits: write what is unknown / unproven (1–2 lines).
  • Privacy risk: identify the biggest identification risk and reduce it.
  • Corrections route: decide how you will publish corrections/updates.
  • Review date: set a date to revisit, update, retract, or clarify.

Decision steps (simple map)

  • Define the claim you are making (1 sentence).
  • List the evidence you can publish safely (and what must stay private).
  • Write limits (what is unknown, uncertain, or not provable).
  • Publish with a correction path and a changelog (no silent edits).
  • Archive sources privately (two backups; keep a simple index).
  • Set a review date to update, retract, or clarify if facts change.

Copy checklist (free template)

Paste into Notes / Google Docs / Notion.
See all toolkits
Pro version adds a fuller map, additional checklists, and reusable scripts for updates/corrections and review cycles. It remains general education (not case handling).

Worked example (before → after)

Before (too broad):

“This program is corrupt and the public should be angry. Everyone knows it.”

After (disciplined and correction-ready):

  • Public goal: “Clarify what the program states vs what is observed.”
  • Minimum claim: “Public information and observed outcomes appear inconsistent in these specific ways.”
  • Publishable evidence: “Public pages, published reports, de-identified summaries.”
  • Private evidence: “Sensitive records retained privately (not published).”
  • Limits: “This does not prove intent; it describes discrepancies and documents sources.”
  • Corrections route: “If new information changes the claim, publish a dated update and what changed.”
  • Review date: “Re-check in 30 days for updates, retractions, or clarifications.”

Upgrade path (choose the right next step)

  • Stay free: use the template when you publish occasionally.
  • Buy Pro ($29): if you want a fuller map, scripts, and printable checklists you can reuse.
  • Training: if you want repeatable discipline across sourcing, limits, privacy, and corrections.
  • Support (no influence): tips help keep the project running, but never buy coverage or outcomes.

Purchases are digital goods for general education. They do not buy coverage, influence, or outcomes.

FAQ

Is this legal advice?

No. Education only — not legal advice.

Will WitnessBC review my case or tell me what to do?

No. No case review, no case handling, and no outcome services. This is a general workflow map.

Should I publish all evidence publicly?

Not necessarily. Publish what is safe and necessary; keep sensitive material private and reduce identifying details.

What does “corrections route” mean?

A simple plan for how updates will be published visibly (date + what changed + why), rather than silently editing.

Does buying Pro or tipping buy coverage or influence?

No. Support does not buy coverage or outcomes.

What if I am dealing with urgent risk?

This is not an emergency service. Publish less if unsure, prioritize safety, and seek appropriate professional help.

Internal links (pick by intent)

Boundaries: Education only. Not legal advice. Not an emergency service. Do not send sensitive personal data. No case review. No guarantees. Support does not buy coverage or outcomes.