THE SYSTEM SEES INCIDENTS. COERCIVE CONTROL OPERATES ACROSS SYSTEMS.
Why Safeguarding Must Learn to Recognise Harm Across Technology, Criminal Justice, Risk Assessment, Housing, Family Systems and Everyday Dependencies
The Directive™ | SAFECHAIN™
There is a fundamental mismatch emerging between the way coercive control operates and the way institutions are organised to recognise it.
Coercive control does not respect institutional boundaries.
It does not remain neatly inside the relationship.
It does not restrict itself to physical violence.
It does not necessarily stop at separation.
And increasingly, it does not require the person exercising control to be physically present at all.
Control can move through a phone.
A banking application.
A shared account.
A location service.
A tenancy.
A child-arrangements dispute.
A digital platform.
A professional narrative.
A debt.
A benefits claim.
A family member.
A court process.
A housing decision.
An institutional record.
Each individual interaction may appear relatively small.
But the person experiencing them does not live them as separate administrative events.
They experience their cumulative effect.
And that creates one of the defining safeguarding challenges of our time:
The institution sees incidents. The survivor lived a system.
The strongest safeguarding signals emerging across technology, criminal justice, risk assessment, housing, family systems and everyday dependencies all point towards the same underlying problem.
Our systems remain fragmented while coercive control is becoming increasingly connected.
That is the governance gap.
And closing it requires much more than awareness.
It requires institutional capability.
Coercive Control Has Changed the Safeguarding Question
For years, domestic abuse systems were largely organised around visible incidents.
What happened?
Was somebody assaulted?
Was there an injury?
Was the police called?
Was there an identifiable threat?
Those questions remain important.
But coercive control requires another layer of analysis.
Not simply:
What happened?
But:
What is happening over time?
Who controls access?
Who controls information?
Who controls money?
Who determines mobility?
Who monitors communication?
Who imposes consequences for resistance?
What happens when the person says no?
What happens after separation?
And critically:
How do apparently separate behaviours interact to reduce another person's autonomy?
That is the difference between incident recognition and systems recognition.
The Control Ecosystem™
We need a more sophisticated way of understanding contemporary coercive control.
I call this the Control Ecosystem™.
The Control Ecosystem™ describes the interconnected technological, financial, relational, administrative, institutional and environmental mechanisms through which coercive power can be exercised, reinforced or extended over time.
Consider what that ecosystem can contain.
Technology
Location tracking.
Shared passwords.
Account access.
Smart-home systems.
Digital surveillance.
Cloud accounts.
Device monitoring.
Artificial intelligence.
Online impersonation.
Communication platforms.
Money
Bank accounts.
Credit.
Debt.
Benefits.
Mortgages.
Business interests.
Employment.
Financial information.
Subscriptions.
Everyday spending.
Housing
Tenancies.
Ownership.
Mortgage liability.
Access to the home.
Homelessness.
Temporary accommodation.
Utilities.
Addresses.
Possessions.
Family systems
Children.
Extended family.
Mutual friends.
Care responsibilities.
Schools.
Health services.
Social networks.
Institutions
Police.
Courts.
Local authorities.
Banks.
Employers.
Healthcare.
Housing providers.
Safeguarding services.
Legal professionals.
Individually, each may possess only one fragment.
Together, they may contain the architecture.
The Evidence Can Exist Everywhere While the Pattern Exists Nowhere
This is perhaps the most important safeguarding problem.
Imagine that:
the bank sees unusual financial behaviour;
the housing provider sees instability;
the GP sees deteriorating wellbeing;
the police see repeated incidents;
the court sees a dispute;
the school sees changes affecting the children;
a domestic abuse service sees controlling behaviour;
and digital evidence shows monitoring or repeated contact.
Each institution has information.
But who has the pattern?
Perhaps nobody.
That is the Connectivity Deficit™.
The evidence exists.
The records exist.
The warning signs exist.
The institutional contacts exist.
Yet the architecture remains invisible because the information is divided according to organisational responsibility.
The safeguarding failure does not necessarily arise because nobody possessed the evidence. It can arise because nobody connected it.
Technology Has Changed the Geography of Control
The home was once treated as the primary geography of domestic abuse.
Digital technology has fundamentally altered that assumption.
Control can now travel.
A person can leave the property without leaving the surveillance environment.
A former partner may potentially retain access to:
location data;
shared accounts;
photographs;
passwords;
cloud services;
smart devices;
financial applications;
family subscriptions;
communication histories;
or connected technologies inside the home.
Separation therefore does not necessarily create technological separation.
This is why Digital Safeguarding can no longer sit at the margins of domestic abuse policy.
It must become core safeguarding infrastructure.
Because:
A locked front door does not create safety if digital access remains open.
When Convenience Becomes Dependency
Many technologies are designed around convenience.
Automatic login.
Shared accounts.
Location sharing.
Connected homes.
Family subscriptions.
Cloud synchronisation.
Password recovery.
Joint calendars.
Shared financial tools.
These features can make ordinary life easier.
But safeguarding must ask a different question:
What happens when the relationship becomes unsafe?
Can access be revoked safely?
Will the other person be notified?
Can location sharing be stopped without escalation?
Can evidence be preserved?
Can account ownership be established?
Can somebody exit a shared digital ecosystem without losing essential information?
This is where Survivor Privacy by Design™, Quick Exit™, Stealth Mode™, Journal Lock™ and Digital Evidence Integrity™ become governance questions rather than optional product features.
Safe technology cannot merely work well during healthy relationships.
It must fail safely when relationships become unsafe.
Criminal Justice Has the Same Pattern Problem
Criminal justice faces a similar challenge.
Coercive control is inherently cumulative.
But justice systems frequently encounter behaviour as discrete events.
One message.
One argument.
One financial act.
One unwanted contact.
One allegation.
One breach.
One disclosure.
Each may appear insufficiently serious when examined alone.
The danger lies in treating the absence of a dramatic individual incident as evidence of the absence of a serious pattern.
This produces the Fragmentation Paradox™:
The more a patterned form of harm is divided into administratively manageable incidents, the harder the underlying pattern can become to recognise.
The institution sees A.
Then B.
Then C.
Then D.
But the survivor experienced:
A → B → C → D → reduced autonomy.
The arrows matter.
Sometimes:
The most important evidence is the relationship between the incidents.
Risk Assessment Must Move Beyond the Snapshot
Risk assessment presents another challenge.
Traditional assessments inevitably capture a moment.
But coercive control is dynamic.
Risk changes.
Separation changes risk.
Pregnancy can change risk.
Housing instability changes risk.
Financial loss changes risk.
Litigation can change risk.
Technology changes risk.
New relationships can change risk.
Children's arrangements can change risk.
Resistance itself can change risk.
A safeguarding system therefore cannot assume:
assessed once = understood permanently.
Risk must be capable of reassessment as the architecture changes.
This requires what SAFECHAIN™ describes as Safeguarding Continuity™:
The obligation to maintain meaningful recognition of vulnerability and changing risk across transitions, services and institutional boundaries rather than treating safeguarding as a single intervention.
Because:
Risk does not become static merely because somebody completed a risk-assessment form.
Housing Is Safeguarding Infrastructure
Housing is too often treated as a downstream consequence of domestic abuse.
It should be understood as part of the safeguarding architecture itself.
Housing determines:
physical security;
distance;
privacy;
financial stability;
children's routines;
access to employment;
access to support;
ability to store possessions;
and capacity to rebuild.
Housing insecurity can also dramatically reduce Exit Capacity™.
A person may theoretically be free to leave.
But where do they go?
Can they afford it?
Can they take the children?
What happens to the mortgage?
What happens to the tenancy?
What happens to possessions?
What happens to employment?
What happens tomorrow?
This is why:
The existence of an exit is not the same as the capacity to use it.
A safeguarding system that tells somebody to leave without considering whether leaving is practically survivable has not solved the problem.
It may simply have relocated it.
Economic Abuse Connects Almost Everything
Money is often the connective tissue between apparently separate systems.
Housing requires money.
Transport requires money.
Legal representation requires money.
Childcare requires money.
Technology requires money.
Safety frequently requires money.
Starting again requires money.
Economic abuse therefore cannot be treated as merely another category of domestic abuse.
It can determine whether every other safeguarding intervention is practically usable.
A person may have a legal right.
But no money to exercise it.
A safe place exists.
But no transport to reach it.
A housing option exists.
But no deposit.
A court process exists.
But no meaningful capacity to navigate it.
This is why Reduced Exit Capacity™ matters.
And why the question:
“Why didn't they leave?”
is often analytically inadequate.
The better question is:
“What resources remained available to make leaving realistically possible?”
Family Systems Can Carry Control
Control can also migrate through relationships surrounding the survivor.
Children.
Relatives.
Friends.
New partners.
Mutual acquaintances.
Professional networks.
This does not mean everybody who takes a side has been manipulated.
Nor does it mean seeking support is abusive.
But safeguarding must be capable of examining function.
Who originated the information?
Who independently witnessed events?
Who repeated what they were told?
Who began monitoring?
Who carried messages?
Who exerted pressure?
Who excluded?
Who reported?
Who generated consequences?
This is where Social Recruitment Effect™, Rescue Recruitment™ and Assertion Provenance™ become relevant.
Because:
Ten people repeating an assertion originating from one person do not necessarily constitute ten independent sources.
Social consensus is not automatically evidential corroboration.
Then the Narrative Reaches Institutions
This is where fragmented systems can inadvertently amplify private power.
A narrative enters a professional record.
Another professional reads it.
A lawyer refers to it.
An institution records it.
A later decision references the earlier record.
The assertion begins acquiring institutional familiarity.
But:
Familiarity is not verification.
And:
Professional repetition cannot transform an unverified proposition into an established fact.
That is why Evidence Integrity™ and Assertion Provenance™ are safeguarding issues.
Institutions must know:
where material information originated;
whether it was independently verified;
whether it remains disputed;
whether it represents allegation, evidence, inference or finding;
and whether later repetition has accidentally increased its apparent evidential weight.
Everyday Dependencies Are Where Control Can Hide
Some of the most consequential control does not look dramatic.
It looks ordinary.
Who has the password?
Who drives?
Who manages the bank account?
Who knows the mortgage details?
Who controls the phone contract?
Who keeps the documents?
Who speaks to the landlord?
Who manages benefits?
Who knows the children's schedules?
Who has access to the car?
Who understands the business finances?
Who has the login?
Who knows where everything is?
These are everyday dependencies.
In healthy relationships, they may simply represent division of labour.
In controlling relationships, however, concentrated knowledge can become concentrated power.
This is why safeguarding must ask not only:
Who owns what?
But:
Who knows what, who controls access to it, and what happens if the other person tries to become independent?
The Survivor Becomes the Integration Layer™
And here lies perhaps the most serious institutional failure.
When systems cannot connect the evidence, the survivor is often expected to do it.
They become:
the investigator;
the archivist;
the chronology builder;
the evidence manager;
the messenger between institutions;
the person correcting records;
the person remembering dates;
the person retrieving documents;
the person explaining why Event A matters to Event D.
In technological language, they become the integration layer between institutions that cannot communicate meaningfully with one another.
That is an extraordinary burden.
Especially where the same person may already be experiencing trauma, financial instability, housing insecurity or litigation.
The system fragments the evidence and then requires the survivor to reconstruct it.
That cannot be our long-term safeguarding model.
From Incident Management to Architecture Recognition™
What is required is a fundamental shift.
Safeguarding must move from:
Incident → Response → Closure
towards:
Signal → Context → Connection → Pattern → Verification → Risk → Intervention → Review
I call this Architecture Recognition™.
It does not mean automatically connecting every piece of information.
It does not mean abandoning privacy.
It does not mean creating unlimited institutional surveillance.
It does not mean treating pattern as proof.
And it certainly does not mean prejudging allegations.
It means designing systems capable of asking:
Could these apparently separate signals be meaningfully connected?
And where the answer may be yes:
What can lawfully and independently be verified?
Because:
Pattern recognition is not pattern conviction.
Recognition triggers inquiry.
Evidence determines conclusion.
Safeguarding Must Become Longitudinal
Perhaps the greatest conceptual change required is this:
Safeguarding must stop thinking only in episodes.
Coercive control unfolds across time.
That means safeguarding must become capable of understanding trajectories.
What changed?
What escalated?
What migrated?
What disappeared?
What happened after resistance?
What happened after separation?
What happened when housing changed?
What happened when financial access changed?
What happened when technology changed?
What happened when institutions became involved?
That is longitudinal safeguarding.
And without it, the system repeatedly encounters Chapter Seven and treats it as Chapter One.
The Cumulative Harm Model™
The consequence of fragmentation is not merely informational.
It affects harm itself.
One financial incident may be manageable.
One housing problem may be manageable.
One court process may be manageable.
One digital intrusion may be manageable.
One professional misunderstanding may be manageable.
One reputational attack may be manageable.
But combine them.
Economic Instability
Housing Insecurity
Digital Monitoring
Family Conflict
Administrative Burden
Institutional Proceedings
Social Isolation
Psychological Distress
and the cumulative impact may be radically different from the apparent seriousness of any individual component.
That is the purpose of The Cumulative Harm Model™.
The total harm cannot always be understood by adding up incidents individually. Their interaction may create an entirely different level of risk.
This Is a Governance Problem
It would be easy to describe all of this as a domestic abuse problem.
It is more than that.
It is a governance problem.
Because institutions determine:
what information is collected;
what information is connected;
what questions are asked;
how risk is assessed;
what gets recorded;
what gets escalated;
who owns the next action;
when a case is closed;
and whether somebody is required to start again when they encounter another service.
That is architecture.
And architecture produces outcomes.
Policies cannot compensate indefinitely for systems that lack the operational capability to recognise the harm those policies describe.
Recognition is not reform. Recognition must become capability.
THE DIRECTIVE™
Stop designing safeguarding around the assumption that harm arrives in one recognisable form.
Connect the architecture.
When technology is involved:
Ask what access survives separation.
When financial instability appears:
Ask what produced it.
When housing collapses:
Ask what happened beforehand.
When somebody appears unable to leave:
Assess Exit Capacity™, not merely physical opportunity.
When risk has already been assessed:
Ask what has changed since.
When several institutions hold different fragments:
Ask where responsibility for connection sits.
When the same assertion appears repeatedly:
Trace its provenance.
When social networks become involved:
Examine function, not merely affiliation.
When the survivor arrives with hundreds of documents:
Do not begin by asking why they have collected so much. Ask why they had to.
When incidents appear unrelated:
Test whether the relationship between them matters.
And when the system says:
“We dealt with our part.”
Ask the question safeguarding can no longer avoid:
Who was responsible for seeing the whole?
Because coercive control does not organise itself according to institutional departments.
It moves.
It adapts.
It migrates.
It exploits dependencies.
It can cross technological, financial, relational and institutional boundaries.
Our safeguarding systems must therefore become capable of doing something equally important:
connecting without assuming, sharing without prejudging, recognising without convicting, and intervening without waiting for cumulative harm to become catastrophe.
That is the next generation of safeguarding.
Not more forms.
Not more isolated procedures.
Not another policy sitting inside another institutional silo.
Connectivity.
Continuity.
Evidence integrity.
Pattern recognition.
Digital safeguarding.
Cumulative harm analysis.
Institutional capability.
Because the evidence can exist everywhere while the pattern exists nowhere.
And when that happens, the survivor becomes the only person carrying the whole architecture.
That is not safeguarding.
That is institutional fragmentation transferred onto the person already experiencing the harm.
THE DIRECTIVE™
Stop looking only at the incident. Examine the architecture.
The pattern is not proof—but neither is it noise. Test it.
The institution sees incidents. The survivor lived a system.
© 2026 Samantha Avril-Andreassen. All Rights Reserved.
SAFECHAIN™ | The Directive™
Copyright Notice
© 2026 Samantha Avril-Andreassen. All Rights Reserved.
SAFECHAIN™ | The Directive™ | The System Sees Incidents. Coercive Control Operates Across Systems.™ | Control Ecosystem™ | Connectivity Deficit™ | Fragmentation Paradox™ | Architecture Recognition™ | The Cumulative Harm Model™ | Safeguarding Continuity™ | Evidence Integrity™ | Reduced Exit Capacity™ | Survivor Privacy by Design™
This article, including its original written expression, analytical architecture, frameworks, models, terminology and proprietary concepts, is protected by copyright. No part may be reproduced, republished, adapted, distributed, transmitted or commercially exploited without prior written permission, except where permitted by law.
Control Ecosystem™, Connectivity Deficit™, Architecture Recognition™, Fragmentation Paradox™, The Cumulative Harm Model™, Safeguarding Continuity™, Evidence Integrity™, Reduced Exit Capacity™ and associated SAFECHAIN™ terminology are asserted as proprietary SAFECHAIN™ concepts and intellectual property.
Published by SAFECHAINN Ltd (Company No. 12038453).