7 Signs You’re Being Gaslighted (And How to Document Each One)
01 — What gaslighting actually is
Definition: Gaslighting is a pattern of manipulation where someone undermines your perception of reality so you doubt your memory, judgment, or sanity.
Gaslighting vs normal disagreement
- Disagreement: “I remember it differently.”
- Gaslighting: “That never happened. You’re making it up.”
- Disagreement: “I didn’t mean it that way.”
- Gaslighting: “You’re too sensitive. You’re crazy for reacting.”
Why it works (and why you need records)
- It’s repetitive, not a one-off.
- It targets memory and confidence, not just feelings.
- It escalates: denial → attack → “you’re the problem.”
Documentation anchor
Full article expansion: show how to record “objective facts first” (date, quote, context, evidence) so the gaslighting can’t be re-labeled as “miscommunication.”
Sign 1: Denying things you know happened
Pattern stub: They deny a statement, promise, or event that you remember clearly, especially when accountability is required.
What it sounds like
- “I never said that.”
- “You’re imagining it.”
- “You always twist things.”
How to document it (specific)
- Record the exact denial quote.
- Reference the original proof (text/email/calendar).
- Note their response when shown evidence (attack, deflect, change topic).
Example incident entry (stub)
Date/Time:
Trigger:
Claim denied:
Exact denial quote:
Proof that exists (file/link):
Response after proof shown:
Tag(s): Denial, Gaslighting
Impact:Sign 2: Trivializing your feelings
Pattern stub: They reduce your reaction to a flaw in you instead of addressing what happened. The goal is to make your response look irrational.
What it sounds like
- “You’re too sensitive.”
- “It’s not a big deal.”
- “You’re overreacting.”
How to document it (specific)
- Log what happened (the factual event).
- Log their minimization quote.
- Note if your boundary/request was ignored entirely.
Full article expansion: show how to track minimization frequency as a “pattern metric” (e.g., 12/30 conversations end with “overreacting”).
Sign 3: Shifting blame
Pattern stub: The issue never stays the issue. It turns into your tone, your timing, your personality, your “issues.”
What it looks like
- You ask about a specific event.
- They attack your character.
- You end up apologizing.
How to document it (specific)
- Write the original topic in one sentence.
- Write the pivot point (exact phrase).
- Record the outcome (who apologized, who “won,” what got avoided).
Conversation map template (stub)
Topic I raised:
Their first response:
Pivot line (exact quote):
New accusation against me:
Outcome / resolution (if any):
Tag(s): Blame shift, DARVOSign 4: Rewriting history
Pattern stub: They change what was agreed, promised, or stated after the fact, especially when the consequences show up.
What it sounds like
- “That’s not what I meant.”
- “You misunderstood.”
- “We never agreed to that.”
How to document it (specific)
- Capture the original agreement (text/email note).
- Capture the rewrite statement.
- Log the consequence (what you lost / what changed).
Full article expansion: show “version control” basics: keep screenshots of original messages, file naming rules, and a timeline row linking both statements.
Sign 5: Isolating you from support
Pattern stub: They discourage or punish outside support: friends, family, coworkers, therapy, groups, anyone who might validate you.
What it sounds like
- “Your friends are a bad influence.”
- “Why do you need to tell people our business?”
- “If you talk to them, we’re done.”
How to document it (specific)
- Log the restriction (what they demanded).
- Log the consequence threatened or applied.
- Log what changed (reduced contact, canceled plans, etc.).
Sign 6: Using love as a weapon
Pattern stub: Affection becomes leverage. Love is offered or removed to force compliance.
What it looks like
- Affection after you give in
- Coldness when you assert a boundary
- “If you loved me, you would…”
How to document it (specific)
- Log the demand attached to affection.
- Log the withdrawal moment (what changed).
- Tag cycles (push/pull) to see repetition.
Full article expansion: include a cycle tracker (date, trigger, demand, compliance/refusal, aftermath) to reveal conditioning patterns.
Sign 7: Making you feel crazy
Pattern stub: They frame your reaction as evidence that you’re unstable, irrational, or untrustworthy, especially when you ask for accountability.
What it sounds like
- “You need help.”
- “You’re delusional.”
- “No one will believe you.”
How to document it (specific)
- Record the exact wording (don’t paraphrase).
- Record what you raised right before the attack (topic + request).
- Record what happened after (withdrawal, intimidation, punishment).
Impact log prompt (stub)
After this, I questioned:
I changed my behavior by:
I avoided bringing up:
Physical symptoms (sleep, appetite, panic):
Work/social impacts:09 — How to document each sign
System stub: One format, every time. Consistency makes your records usable.
Minimum fields (fast logging)
- Date/time (approx ok)
- Location / who was present
- Trigger/topic (1 sentence)
- Exact quote(s)
- Sign tag (1–2)
- Evidence saved (file name)
- Impact (1–2 lines)
Quality rules (keep it credible)
- Facts first, interpretations second.
- Use direct quotes when possible.
- Don’t diagnose; label behaviors.
- Keep entries short and repeatable.
One-page incident report template (stub)
Incident ID:
Date/Time:
Sign(s) (1-2):
Trigger/topic:
Exact quote(s):
My response (brief):
Their response (brief):
Evidence saved:
Outcome:
Impact:
Safety concern (Y/N):Full article expansion: include completed sample entries for each sign + a “what to screenshot” checklist.
10 — Tools that help
Fast capture
- Voice-to-text notes
- Phone shortcut to a logging form
- Template pinned in notes app
System + search
- Airtable base (tags, filters, exports)
- Notion database (quick search + views)
- Google Form → Sheet (auto timestamp)
Recommended structure (stub)
01_Incident_Reports/ (entries)
02_Timeline/ (master table)
03_Evidence/ (screenshots, audio refs, emails)
04_Exports/ (clean PDFs for sharing)Full article expansion: show step-by-step setup for one tool path (Form → Sheet) and one “power” path (Airtable) with suggested field names and tags.
Related Toolkit
Gaslighting Incident Report Kit
Name it. Log it. Stop doubting yourself.
$27
Stub: In the full article, each sign links to a matching page in the kit (pre-tagged fields + examples), so readers can log incidents in under 2 minutes.
Leave a Reply