The Narcissistic Abuse Cycle: How to Track It in Real Time
Love-bombing, devaluation, discard, hoover. The cycle is predictable — but only if you’re tracking it. Here’s how.
The four phases of narcissistic abuse
Core point: The “cycle” is a repeating sequence of behaviors that tends to follow the same rhythm: intense pull-in, gradual destabilization, sudden drop, and return attempt. You don’t need labels to track it. You need timestamps.
Phase map (behavior-based)
- Love-bombing: fast intensity, promises, focus, urgency
- Devaluation: criticism, contempt, moving goalposts, instability
- Discard: withdrawal, replacement, humiliation, disappearance
- Hoover: re-entry attempt, apologies without change, bait
Tracking rule
- One incident means nothing.
- Repeated sequences mean everything.
- Track behaviors + outcomes, not theories.
Tools that make this systematic
- Phase tag system (LB / DV / DC / HV) added to every log entry
- Cycle timeline (one row per incident, filterable by phase)
- Baseline snapshot (what “stable” looked like before the cycle intensified)
Love-bombing: what it looks like
What to track (observable)
- Rapid escalation (commitment talk early)
- Excessive messaging/calls, especially at odd hours
- Future promises (“we’ll move in,” “I’ll take care of you”)
- Pressure to merge lives quickly (time, money, access)
How to log it
- Capture exact promise language (quotes).
- Log “speed markers” (how fast each step happened).
- Record any pressure attached (“if you loved me…”).
Love-bombing entry template
Date/Time:
What happened (facts):
Exact quote(s):
Escalation marker (commitment/finances/access/urgency):
Pressure applied (Y/N) + how:
Evidence saved (file name):
Tag(s): Phase-LB
Full article expansion: include 3–4 completed examples (promise-bombing, gift-bombing, access requests, urgency threats) and how to tag each.
Devaluation: the shift
Pattern: The tone changes. Approval becomes conditional. You start working for “normal” again. The rules shift and your reactions become the “problem.”
What to track
- Criticism disguised as “help”
- Moving goalposts (you can’t win)
- Public vs private personality split
- Blame shifting / DARVO patterns
- Withholding affection as leverage
How to log it
- Log the “before” statement and the “after” standard.
- Capture exact contempt/insult language.
- Track frequency (counts per week).
Goalpost tracker
Date:
Original expectation (quote/summary):
New expectation (quote/summary):
What changed:
Outcome (you apologized? you complied? conflict?):
Tag(s): Phase-DV
Discard: the drop
Pattern: Contact drops. Empathy drops. Accountability disappears. The relationship is treated like it’s disposable, often with coldness or humiliation.
What to track
- Sudden silence / blocked access
- Abandonment during conflict or crisis
- Public humiliation or smear attempts
- Replacement signals (new “best friend,” sudden secrecy)
How to log it
- Track last normal contact → drop point (timestamps).
- Log what triggered the drop (your boundary? question? request?).
- Record any “exit lines” used (“you’re too much,” “you’re unstable”).
Drop-point timeline template
Date:
Last normal interaction (time + context):
Drop behavior (ghosting/blocking/coldness):
Trigger before drop:
Any statements made (exact quotes):
Impact (work/sleep/safety):
Tag(s): Phase-DC
Hoover: the return
Pattern: They come back to reset access: affection, apologies, emergencies, nostalgia, guilt, or “closure.” The goal is re-entry, not change.
Common re-entry tactics to track
- Apology with no specifics
- Emergency crisis bait (“I need you right now”)
- Gift/gesture spikes after harm
- Guilt pressure (“after everything I’ve done for you”)
- “Closure” meetings that become blame shifts
How to log it
- Record the re-entry message verbatim.
- Tag the hook type (apology/emergency/guilt/nostalgia).
- Track whether boundaries were respected afterward (yes/no).
Hoover attempt log
Date/Time:
Re-entry method (text/call/in-person/third party):
Hook type (apology/emergency/guilt/nostalgia/closure):
Exact quote(s):
Boundary requested:
Boundary respected? (Y/N):
Outcome:
Tag(s): Phase-HV
How to track the cycle
System: The simplest working system is: (1) one intake template, (2) phase tags, (3) weekly rollups, (4) evidence vault naming rules. Consistency beats complexity.
Minimum fields (fast capture)
- Date/time + context
- Phase tag (LB/DV/DC/HV)
- What happened (facts only)
- Exact quote(s)
- What you did next
- Impact (objective: sleep/work/social)
- Evidence reference (file name)
Cycle detection rules
- Track phase changes (when did DV begin?)
- Track “reset attempts” (HV after DC)
- Track escalation markers (frequency, threats, monitoring)
- Track time between phases (shortening intervals = escalation)
Cycle timeline table
| Date | Phase | Incident summary (facts) | Exact quote (short) | Evidence file | Impact | Tags |
|---|---|---|---|---|---|---|
| YYYY-MM-DD | LB/DV/DC/HV | 1–2 lines | “…” | YYYY-MM-DD_…png | Objective outcome | goalposts / denial / guilt / etc |
Tools that make this fast
- Google Form → Sheet for standardized entries (auto timestamp)
- Airtable for tags, filters, phase views, exports
- Notion database for quick capture + “phase” views
- Phone shortcut to log an incident in one tap
Breaking the pattern
Core point: Tracking is step one. Breaking the pattern requires changing access and reducing exposure to the cycle triggers. Documentation supports decision-making and boundary enforcement because it stops “maybe it wasn’t that bad” rewriting.
Practical outputs from your logs
- Your “top 10 repeated behaviors” list
- Your escalation markers list
- Your phase timeline (how fast the cycle repeats)
- Your boundary outcomes (what happens when you say no)
Decision tools
- Boundary tracker (request → response → consequence)
- No-contact breach log (attempts + methods + hooks)
- Safety checklist (digital + physical)
- Support escalation plan (who to contact, what to share)
Boundary outcome tracker
Date:
Boundary stated (exact):
Their response (exact):
Outcome:
Retaliation or compliance:
Tag(s): Boundary, Phase-*
Related Toolkit
Narcissistic Pattern Index
Index the chaos. Find the pattern.
$23
Note: The full article will link each phase to matching index pages inside the toolkit (phase tags, hook types, goalpost tracker, hoover attempt log, and export-ready timeline packet).
Leave a Reply