PBP pattern-recognition resource

How to organise a history of coercive control

A practical, non-legal structure for organising rough notes, messages and events into behaviour, repetition, consequence, adaptation and effect.

Direct answer

The short version

Organise a coercive-control history by preserving the raw material, building a simple chronology, grouping repeated behaviours and writing a short pattern statement that connects behaviour, consequence, adaptation and effect. Do not wait for a perfect timeline before seeking urgent help.

Keep the raw history and build a second, usable layer

Do not destroy or rewrite original messages, screenshots, documents or notes. Keep them safely where appropriate. The organised layer is an index: it helps another person understand what to look for without replacing the source material.

Start rough. A date, approximate period, route, observable behaviour and effect are enough for the first pass. Mark uncertainty rather than filling gaps from memory.

Use five columns that give each event a job

A spreadsheet is optional. Paper or a document can work. The useful part is the relationship between the fields.

  • When: date or approximate period
  • Behaviour: what happened in observable language
  • Trigger or context: what occurred immediately before it
  • Consequence: what followed resistance, delay or refusal
  • Effect or adaptation: what you or the children changed afterwards

Group repetition after the chronology exists

Tag events by recurring route—children, money, messages, surveillance, isolation, threats, systems or another relevant category. Then ask whether the method shifts when one route closes. This preserves time order while making the architecture visible.

Write a two- or three-sentence opening that states the repeated method and its effect. Follow it with a small number of representative examples, then keep the full chronology available. The opening is a map, not a substitute for the terrain.

Protect privacy and safety

Store material where the other person cannot access it. Consider device, cloud-account and location safety. Remove unnecessary identifying information before sharing with a service that does not need it. For legal evidence, risk assessment or court use, obtain qualified advice about collection, storage and relevance.

Sources and further reading

This page provides general education and pattern-recognition language. It is not legal advice, clinical advice, crisis support or an individual risk assessment.