A coercive control evidence log that makes the pattern visible.
Coercive control is hard to prove because no single incident is dramatic on its own. It is the accumulation — monitoring, isolation, financial control, the slow rewriting of your reality — that makes it abuse. A structured log is what turns that accumulation into something a court, a therapist, or an investigator can read.
The abuse hides in the pattern. So does the proof.
A single hostile text looks like a bad day. Ninety of them across a year, categorized by tactic, tagged with the same recurring themes — monitoring, degradation, weaponizing the children — is a documented pattern of coercive control. Judges, DCFS caseworkers, and custody evaluators are increasingly trained to recognize it, but only when it is presented as a pattern.
How to do it right
- 01
Categorize by tactic, not by feeling
Use recognized coercive-control categories: monitoring & surveillance, isolation, financial control, weaponizing children, degradation, threats, gaslighting. Every log entry should carry a category tag. This lets you show volume within each tactic.
- 02
Log the incident, not your reaction
Write what happened in neutral, factual language. 'He checked my location three times between 9pm and midnight' — not 'he was obsessive again.' Save your reaction for a private journal; the log is a legal document.
- 03
Preserve the source material
Every entry should link to the underlying evidence: the message, the location-tracking screenshot, the bank statement, the recording. A log without source material is testimony; a log with sources is evidence.
- 04
Track escalation over time
Coercive control almost always escalates when the target tries to leave, files for custody, or gets a protective order. A dated log lets you show 'incidents doubled in the 60 days after I filed for divorce' — which is legally significant.
What we built for exactly this problem
Pre-built coercive control taxonomy
Chronica ships with the recognized coercive-control categories used by researchers, judges, and DV specialists. Every log entry is one dropdown selection away from being properly categorized.
Pattern recognition across your record
The Harm Engine surfaces category frequency, escalation curves, and repeated behaviors automatically. You do not have to hand-count 90 incidents to say 'monitoring occurred at least twice a week for a year.'
Court-neutral export language
The one-page pattern summary uses court-neutral phrasing — no 'narcissist,' no diagnostic labels. Designed for evaluators and judges who are wary of pop-psychology framing.
Questions people ask
Is coercive control legally recognized?
In several US states, in the UK, and in Ireland, coercive control is a named offense or a specific factor in custody law. Even where it is not codified, a documented pattern of coercive control is admissible as evidence of domestic abuse in almost every family court.
What is the difference between coercive control and 'high conflict'?
'High conflict' is symmetrical — both parents contribute. Coercive control is asymmetric — one parent uses systematic tactics to dominate the other. Courts increasingly recognize this distinction, but only when the pattern is documented.
Can I use my log in a protective order hearing?
Yes. A dated, source-linked log is one of the strongest forms of evidence in a protective order hearing, particularly when the abuse is non-physical.
Keep going
How to document custody violations
A practical guide to documenting custody order violations — what to capture, how to timestamp it, and how to turn it into evidence a judge will read.
ReadHow to document parental alienation
Parental alienation is contested in family court. Here is how to document alienating behaviors in a way that avoids the diagnostic trap and shows a pattern.
ReadCustody evidence documentation
Chronica is built for Utah custody, DCFS, and protective order cases. Timeline documentation mapped to Utah code — § 81-9, § 76-5-106.5, § 62A-4a.
Read