SAFETYPLANINTEGRITY-001™
The SAFECHAIN™ Safety Planning, Feasibility & Protective Action Integrity Framework™
Framework Reference: SAFETYPLANINTEGRITY-001™
Framework Type: Safeguarding Governance, Safety Planning, Protective Feasibility, Survivor Capacity, Institutional Responsibility, Risk Management, Implementation Integrity, Contingency Planning, Verification & Systems Reform
Framework Series: SAFECHAIN™ Safeguarding, Coercive Control & Institutional Integrity Series™
Parent Architecture: SAFECHAIN™ Governance Architecture™
Version: 1.0
Year: 2026
1. Framework Purpose
SAFETYPLANINTEGRITY-001™ — The SAFECHAIN™ Safety Planning, Feasibility & Protective Action Integrity Framework™ establishes a governance methodology for testing whether a safety plan is actually capable of being implemented within the survivor's circumstances and whether institutional responsibility for protection has been appropriately retained.
The framework addresses a central safeguarding weakness:
A safety plan may appear complete on paper while remaining impossible, unsafe, unaffordable, inaccessible or unsustainable in practice.
It therefore moves safety planning beyond the production of recommendations and asks whether the person has the practical conditions required to carry them out.
2. Core Question
Is the safety plan genuinely executable within the person's circumstances, or does it transfer an unrealistic burden of protection onto the survivor?
3. Core Architecture
Risk → Safety Need → Proposed Action → Feasibility → Dependency → Survivor Capacity → Institutional Support → Implementation → Failure Contingency → Verification
Expanded:
Risk Recognition → Protective Objective → Safety Requirement → Proposed Measure → Survivor Intelligence → Feasibility Assessment → Constraint Assessment → Dependency Assessment → Responsibility Allocation → Institutional Support → Implementation → Monitoring → Failure / Breach → Contingency → Reassessment → Protective Outcome → Verification
4. Governing Proposition
A safety plan should be judged not by the quality of the advice it contains, but by whether the required protective actions are realistically achievable, sufficiently supported, safe to implement and capable of producing protection in practice.
5. Safety Plan Integrity™
Defined as:
The extent to which a safety plan is risk-linked, feasible, adequately supported, appropriately owned, implementable, resilient to failure and verified for protective effectiveness.
6. Safety Plan™
Defined as:
A structured set of actions, arrangements, controls or contingencies intended to reduce exposure to an identified safeguarding risk.
7. Plan–Protection Distinction™
Safety Plan Exists ≠ Safety Achieved
8. Advice–Implementation Distinction™
Advice Given ≠ Advice Implementable
9. Feasibility–Availability Distinction™
Option Available ≠ Option Feasible
10. Survivor Participation–Survivor Responsibility Distinction™
Survivor Involved in Planning ≠ Survivor Responsible for Making Protection Work
11. Safety Planning Architecture™
SPA1 — Risk
SPA2 — Protective Objective
SPA3 — Proposed Measure
SPA4 — Survivor Intelligence
SPA5 — Feasibility
SPA6 — Constraint
SPA7 — Dependency
SPA8 — Responsibility
SPA9 — Institutional Support
SPA10 — Implementation
SPA11 — Monitoring
SPA12 — Contingency
SPA13 — Reassessment
SPA14 — Protective Outcome
SPA15 — Verification
12. Risk Linkage™
Every element of the safety plan should correspond to an identified risk mechanism.
13. Risk-to-Action Trace™
Risk → Protective Objective → Action → Owner → Outcome
14. Protective Objective™
Defined as:
The specific risk reduction the safety measure is intended to achieve.
15. Protective Objective Integrity™
Ask:
What risk is this action intended to reduce, and how?
16. Generic Safety Planning Risk™
Defined as:
Use of standardised safety advice without sufficient adaptation to the person's actual risk architecture.
17. Generic-Plan Fallacy™
Standard Advice ≠ Individualised Protection
18. Individualised Safety Plan™
A plan should consider, where relevant:
perpetrator behaviour;
pattern;
escalation;
children;
finances;
housing;
digital exposure;
mobility;
health;
employment;
transport;
social network;
institutional constraints.
19. PATTERNINTEGRITY-001™ Integration
Safety planning should respond to the pattern, not merely isolated incidents.
20. CUMULATIVEHARM-001™ Integration
Plans should consider the cumulative effect of repeated exposure and repeated institutional demands.
21. Survivor Intelligence™
Survivor knowledge should inform whether proposed actions are realistic and safe.
22. SURVIVORINTELLIGENCE-001™ Integration
Safety planning should distinguish between:
professional recommendation;
survivor intelligence;
objective evidence;
uncertainty.
23. Protective Feasibility Intelligence™
Defined as:
Survivor knowledge concerning whether a proposed protective action can actually be carried out safely and effectively.
24. Survivor Feasibility Test™
Ask:
What does the survivor identify as the reason this action may not work?
25. Feasibility Integrity™
Defined as:
The extent to which proposed protective actions are realistically executable within the person's circumstances.
26. Feasibility Domains™
FD1 — Financial
FD2 — Housing
FD3 — Digital
FD4 — Transport
FD5 — Child / Dependant
FD6 — Health / Disability
FD7 — Employment
FD8 — Immigration / Documentation
FD9 — Communication
FD10 — Geographic
FD11 — Institutional
FD12 — Emotional / Cognitive Capacity
27. Feasibility Classification™
F1 — Not Feasible
F2 — Highly Constrained
F3 — Conditional
F4 — Feasible
F5 — Verified Feasible
28. Feasibility Gap™
Defined as:
Difference between what the safety plan requires and what the survivor is practically capable of doing.
29. Plan–Capacity Gap™
Required Action > Available Capacity = Protective Failure Risk
30. Constraint Integrity™
Constraints should be explicitly assessed rather than treated as non-compliance.
31. Safety Plan Constraint™
Defined as:
A condition materially limiting the survivor's ability to carry out a proposed protective action.
32. Constraint Categories™
SC1 — Financial
SC2 — Housing
SC3 — Digital
SC4 — Transport
SC5 — Family
SC6 — Disability
SC7 — Health
SC8 — Employment
SC9 — Immigration
SC10 — Institutional
SC11 — Communication
SC12 — Geographic
SC13 — Legal
SC14 — Safety
SC15 — Dependency
33. ESCAPECAPACITY-001™ Integration
Safety planning should incorporate the person's actual exit and separation capacity.
34. Constraint Density™
Defined as:
The number and interaction of materially significant barriers affecting plan implementation.
35. Constraint Interaction™
Two moderate constraints may create one serious implementation barrier.
36. Constraint Multiplication™
Constraint A + Constraint B ≠ Merely Two Separate Problems
Their interaction may make an action unworkable.
37. Constraint Cascade™
Defined as:
A sequence in which one unresolved constraint creates or intensifies others.
38. Example Constraint Cascade™
No Transport → Missed Appointment → No Housing Access → Continued Exposure
39. Option Reality Test™
Ask:
Could this person realistically use this option today?
40. False Safety Option™
Defined as:
A formally available protective option that cannot practically be used within the survivor's circumstances.
41. False Choice Risk™
Safety planning should not present theoretically available options as genuine choices where material constraints make them unusable.
42. Domestic Manufactured Choice™ Integration
A safety plan should consider whether the survivor's apparent decision is made within a constrained choice environment.
43. Dependency Integrity™
Safety planning should identify what each protective action depends upon.
44. Safety Plan Dependency™
Defined as:
A person, service, resource, technology or institution whose continued availability is necessary for the plan to function.
45. Dependency Categories™
SD1 — Person Dependency
SD2 — Service Dependency
SD3 — Housing Dependency
SD4 — Financial Dependency
SD5 — Technology Dependency
SD6 — Transport Dependency
SD7 — Legal Dependency
SD8 — Childcare Dependency
SD9 — Healthcare Dependency
SD10 — Institutional Dependency
46. Dependency Mapping™
Action → Dependency → Failure Risk → Backup
47. PROTECTIVEDEPENDENCY-001™ Integration
Critical dependencies should be tested for single points of failure.
48. Single-Point Safety Failure™
Defined as:
A dependency whose failure materially collapses the protective plan.
49. Dependency Fragility™
Assess whether required support is:
temporary;
uncertain;
discretionary;
inaccessible;
unstable;
unverified.
50. Dependency Replacement™
Critical dependencies should have alternatives where reasonably possible.
51. Survivor Capacity™
Defined as:
The practical ability of the survivor to perform the actions expected within the safety plan.
52. Capacity Domains™
Assess:
physical capacity;
emotional capacity;
cognitive load;
financial capacity;
digital capacity;
administrative capacity;
mobility;
communication;
time.
53. Capacity-Sensitive Planning™
Safety planning should adapt requirements to the person's capacity rather than treating difficulty implementing the plan as unwillingness.
54. Capacity–Compliance Distinction™
Unable to Implement ≠ Unwilling to Protect Oneself
55. Implementation Burden™
Defined as:
The total workload required of the survivor to make a safety plan operational.
56. Implementation Burden Components™
May include:
phone calls;
appointments;
evidence collection;
password changes;
relocation;
childcare;
benefit applications;
housing applications;
legal applications;
transport;
repeated disclosure.
57. Burden Accumulation™
Multiple individually reasonable tasks may become collectively unmanageable.
58. Safety Plan Burden Index™
Assess:
Number of Tasks × Complexity × Urgency × Capacity Requirement × Consequence of Failure
59. Survivor Protective Burden™
Defined as:
The proportion of safeguarding work transferred to the person requiring protection.
60. Protective Burden Transfer™
Defined as:
Institutional reliance on the survivor to perform actions that should reasonably be supported, coordinated or undertaken by institutional actors.
61. Institutional Burden–Survivor Burden Balance™
Ask:
Who is doing the work required to make this plan protective?
62. No-Survivor-as-Safety-System Principle™
A safety plan should not make the survivor the principal infrastructure through which institutional protection operates.
63. Institutional Responsibility™
The plan should identify which protective functions remain institutional.
64. RESPONSIBILITYCHAIN-001™ Integration
Every material protective action should have an identifiable owner.
65. Responsibility Allocation Map™
Action → Survivor Role → Institutional Role → Owner → Support Required
66. Survivor Action™
Defined as:
A protective action reasonably expected of the survivor within their capacity and circumstances.
67. Institutional Action™
Defined as:
A protective action requiring service, agency, professional or organisational responsibility.
68. Shared Action™
Defined as:
An action requiring coordinated survivor and institutional participation.
69. Action Allocation Integrity™
Responsibility should be assigned according to:
authority;
capability;
access;
risk;
feasibility.
70. No-Advice-Equals-Discharge Principle™
Giving the survivor advice does not automatically discharge institutional safeguarding responsibility.
71. Institutional Support™
Defined as:
The resources, actions and coordination necessary to make the safety plan practically executable.
72. Support Sufficiency™
Assess whether support is:
available;
accessible;
timely;
adequate;
sustainable.
73. Support Gap™
Defined as:
Difference between support required for plan implementation and support actually available.
74. Support Dependency Gap™
An action may technically be feasible only if an unconfirmed service becomes available.
75. No-Service-Exists-Equals-Service-Accessible Principle™
The existence of a service does not establish that the survivor can access it in time or on appropriate terms.
76. Access Integrity™
Protective options should be tested against real accessibility.
77. ACCESSFAILURE-001™ Integration
Barriers to services should be incorporated into safety-plan feasibility.
78. Timing Integrity™
Safety measures should occur while they can still reduce risk.
79. Protective Timing™
Defined as:
The relationship between when an intervention is delivered and when protection is required.
80. Timing Feasibility Test™
Ask:
Can this action be completed before the relevant risk window closes?
81. Late Protection Risk™
Defined as:
A measure that may be substantively appropriate but becomes ineffective because it is delivered too late.
82. Protective Window™
Defined as:
The period during which a safeguarding action can materially reduce foreseeable harm.
83. Implementation Timing Gap™
Action Available Eventually ≠ Protection Available When Needed
84. Urgency Classification™
U1 — Routine
U2 — Time-Sensitive
U3 — Urgent
U4 — Immediate
U5 — Critical
85. IMPLEMENTATIONGAP-001™ Integration
Safety planning should trace decisions through actual implementation.
86. Implementation Integrity™
Defined as:
The extent to which agreed protective measures are actually put into operation.
87. Implementation Status™
IS1 — Not Started
IS2 — Initiated
IS3 — Partially Implemented
IS4 — Implemented
IS5 — Verified Operational
88. Planned–Implemented Gap™
Plan Agreed ≠ Plan Operational
89. Partial Implementation Risk™
Some measures may fail if dependent actions remain incomplete.
90. Critical Action™
Defined as:
An action whose non-completion materially weakens the entire safety plan.
91. Critical Action Register™
Record:
Action → Owner → Deadline → Dependency → Failure Consequence → Backup
92. Implementation Verification™
Check whether:
action occurred;
control operates;
survivor can use it;
relevant institutions know their role;
dependencies are active.
93. Monitoring™
Safety plans should be capable of detecting when assumptions change.
94. Plan Monitoring Integrity™
Monitor:
new risk;
failed actions;
new constraints;
service withdrawal;
breach;
digital change;
housing change;
survivor capacity.
95. Monitoring Ownership™
A safety plan should identify who reviews continuing effectiveness.
96. No-Plan-Issued-Equals-Plan-Monitored Principle™
Producing a safety plan does not establish continuing oversight.
97. Safety Plan Drift™
Defined as:
Progressive mismatch between the original plan and the survivor's current circumstances or risk.
98. Plan Obsolescence™
Defined as:
A plan becoming materially outdated because circumstances, risk or available resources have changed.
99. Dynamic Planning Principle™
Safety planning should be capable of changing when the risk environment changes.
100. Reassessment Trigger™
Potential triggers:
new threat;
breach;
separation;
release;
relocation;
digital compromise;
loss of housing;
child-related change;
service withdrawal;
survivor report of plan failure.
101. Plan Reassessment™
Ask:
Does this safety plan still match the current risk architecture?
102. REVIEW-001™ Integration
Material change should trigger reassessment.
103. Failure Contingency™
Defined as:
The predetermined response when a critical safety measure cannot be implemented or fails.
104. No-Perfect-Plan Principle™
A credible safety plan should assume that some protective actions may fail.
105. Contingency Integrity™
For each critical measure identify:
Failure → Detection → Immediate Alternative → Owner → Escalation
106. Contingency Gap™
Defined as:
Absence of a viable response when a critical plan element fails.
107. Contingency Levels™
C1 — Routine Alternative
C2 — Enhanced Support
C3 — Escalated Protection
C4 — Emergency Response
C5 — Critical Safeguarding Intervention
108. PROTECTIVEDEPENDENCY-001™ Resilience Integration
Critical plan elements should have redundancy where proportionate.
109. Failure Detection™
The system should identify when the plan is not functioning.
110. Survivor Failure Report™
A survivor reporting that a plan is not working should be treated as material protective intelligence.
111. No-Plan-Noncompliance-Equals-Survivor-Failure Principle™
Failure to implement a plan should trigger examination of feasibility, constraints and support before being interpreted as survivor non-engagement.
112. Plan Failure™
Defined as:
Failure of the safety architecture to produce the intended protective effect.
113. Plan Failure Classification™
PF1 — Design Failure
PF2 — Feasibility Failure
PF3 — Constraint Failure
PF4 — Dependency Failure
PF5 — Support Failure
PF6 — Implementation Failure
PF7 — Monitoring Failure
PF8 — Contingency Failure
PF9 — Reassessment Failure
PF10 — Verification Failure
114. Plan Failure Severity™
PFS1 — Limited
PFS2 — Moderate
PFS3 — Material
PFS4 — Serious
PFS5 — Critical
115. Plan Failure Attribution Integrity™
Ask:
Did the plan fail because of survivor choice, institutional failure, structural constraint, third-party conduct, control circumvention or a combination?
116. No-Automatic-Survivor-Attribution Principle™
The person requiring protection should not automatically be treated as responsible for the failure of a plan they lacked practical capacity to implement.
117. Breach Integration™
Safety plans should anticipate protective-control breaches where relevant.
118. BREACHINTEGRITY-001™ Integration
Breach → Pattern → Reclassification → Escalation → Plan Reassessment
119. Breach Response Plan™
Record:
Expected Breach → Detection → Immediate Action → Institutional Owner → Survivor Action → Escalation
120. Protective Measure Integrity™
Formal controls should be tested for practical effectiveness.
121. PROTECTIONGAP-001™ Integration
Protective Measure ≠ Protective Outcome
122. Paper Safety™
Defined as:
A documented safety plan lacking sufficient practical capacity to change risk exposure.
123. Paper Safety Risk™
A plan may score well administratively while failing operationally.
124. Checklist Compliance–Safety Integrity Distinction™
Checklist Complete ≠ Safety Plan Effective
125. Documentation Bias™
Institutional confidence should not arise merely because a plan has been written and signed.
126. Signed Plan Fallacy™
Signed by Survivor ≠ Feasible, Voluntary or Protective
127. Consent Integrity™ Integration
Agreement with a plan should be appropriately informed and should not obscure constraints.
128. Plan Agreement–Plan Capacity Distinction™
Agreement ≠ Ability
129. Safety Plan Choice Integrity™
Assess whether the survivor had meaningful alternatives.
130. Manufactured Safety Choice™
Defined as:
Apparent agreement to a protective option because no viable alternative is available.
131. Exit-Dependent Planning™
Some safety plans rely implicitly on separation.
132. Exit Feasibility Test™
Ask:
Does this plan require the survivor to leave, and if so, does the person actually possess the capacity to do so safely?
133. ESCAPECAPACITY-001™ Full Integration
Opportunity to Leave ≠ Capacity to Leave ≠ Capacity to Remain Separated
134. Housing Feasibility™
Assess:
availability;
location;
affordability;
accessibility;
security;
suitability for dependants.
135. Housing Option Fallacy™
Accommodation Exists ≠ Safe Housing Exists
136. Financial Feasibility™
Assess:
immediate funds;
benefits;
bank access;
debt;
transport;
emergency costs.
137. Money Entitlement–Liquidity Distinction™
Entitled to Funds ≠ Funds Available Now
138. Digital Feasibility™
Safety advice concerning devices or accounts should consider:
discovery risk;
evidence preservation;
shared accounts;
device access;
connected technology;
technical capability.
139. DIGITALEXIT-001™ Integration
Digital separation should be safely sequenced.
140. Digital Safety Action Risk™
Some apparently protective digital changes may alert an abusive person.
141. No-Password-Change-Equals-Digital-Safety Principle™
Digital safety planning requires analysis of the wider access architecture, not only credential changes.
142. Child and Dependant Feasibility™
Plans should assess responsibility for:
children;
disabled dependants;
older relatives;
pets;
other caring duties.
143. Dependant Safety Integrity™
Safety planning should not create protection for one person by leaving a dependant unmanaged.
144. Childcare Dependency Risk™
A plan requiring appointments, relocation or work absence may fail without childcare.
145. Transport Feasibility™
Assess:
vehicle access;
public transport;
disability;
distance;
cost;
timing.
146. Geographic Feasibility™
Services should be realistically reachable.
147. Health Feasibility™
Safety planning should adapt to physical and psychological health needs.
148. Disability-Adjusted Planning™
The plan should account for mobility, sensory, communication and cognitive requirements.
149. Employment Feasibility™
Assess consequences for:
work attendance;
income;
workplace exposure;
disclosure;
job security.
150. Immigration / Documentation Feasibility™
Where relevant assess:
document access;
legal status dependencies;
passport control;
immigration advice;
eligibility constraints.
151. Social Feasibility™
Do not assume safe family or friends are available.
152. Social Support Assumption Risk™
Known Contact ≠ Safe Support Network
153. Institutional Feasibility™
Assess how many institutions the survivor is required to navigate.
154. Service Navigation Burden™
Defined as:
The workload required to locate, contact, explain circumstances to and coordinate multiple services.
155. Fragmented Safety Planning™
Defined as:
Different institutions creating separate protective requirements without assessing their combined burden or compatibility.
156. Cross-Plan Conflict™
One institutional safety requirement may conflict with another.
157. Plan Compatibility Test™
Ask:
Can all institutional requirements realistically be followed at the same time?
158. Multi-Agency Safety Plan Integrity™
Multiple agencies should understand the combined protective architecture.
159. HANDOVERINTEGRITY-001™ Integration
Safety-plan responsibilities should survive referrals and transfers.
160. CHAININTEGRITY-001™ Integration
Risk → Plan → Ownership → Implementation → Monitoring → Escalation → Verification
161. Safety Chain Break™
Defined as:
A failure point at which an identified risk no longer remains connected to an implementable protective action.
162. Safety Chain Break Classification™
SCB1 — Risk Break
SCB2 — Objective Break
SCB3 — Feasibility Break
SCB4 — Ownership Break
SCB5 — Support Break
SCB6 — Implementation Break
SCB7 — Monitoring Break
SCB8 — Contingency Break
SCB9 — Reassessment Break
SCB10 — Verification Break
163. Safety Plan Verification™
Defined as:
Testing whether the plan has actually changed the person's protective conditions.
164. Verification Questions™
Were agreed actions implemented?
Can the survivor use them?
Are critical dependencies functioning?
Has risk changed?
Have breaches occurred?
Are institutional responsibilities active?
Does the survivor report increased practical safety?
Does the plan remain sustainable?
165. Protective Outcome™
Defined as:
A demonstrable improvement in the person's protection, risk exposure or ability to respond safely.
166. Outcome–Activity Distinction™
Services Delivered ≠ Protective Outcome
167. Outcome Verification Integrity™
The institution should distinguish:
action completed;
service delivered;
protection improved;
risk reduced.
168. Survivor Outcome Intelligence™
The survivor's lived experience should inform—but not exclusively determine—verification.
169. Plan Sustainability™
Defined as:
The ability of the safety plan to remain operational beyond the immediate crisis period.
170. Short-Term–Long-Term Safety Distinction™
Emergency Protection ≠ Sustainable Safety
171. Sustainability Test™
Ask:
Can the survivor maintain this plan next week, next month and after temporary support ends?
172. Support Cliff™
Defined as:
A sudden reduction in protective capacity when temporary support ends.
173. Safety Plan Cliff Risk™
A plan may initially succeed but collapse when:
emergency accommodation ends;
funding ends;
supervision ends;
temporary transport ends;
advocate involvement ends.
174. Stabilisation Integration™
Safety planning should move from emergency protection toward sustainable stability.
175. Safety Plan Resilience™
Defined as:
The ability of the protective architecture to continue functioning when circumstances change or one measure fails.
176. Resilience Classification™
SR1 — Brittle
SR2 — Fragile
SR3 — Functional
SR4 — Resilient
SR5 — Verified Resilient
177. Resilience Test™
Ask:
If the most important support disappeared tomorrow, would the plan still protect the survivor?
178. Worst-Credible Safety Scenario™
Assess the most serious reasonably foreseeable combination of:
plan failure;
support withdrawal;
breach;
digital exposure;
housing instability;
institutional delay.
179. Compound Safety Failure™
Defined as:
Simultaneous or cascading failure of multiple protective plan components.
180. Compound Failure Test™
Ask:
What happens if two or more critical measures fail at the same time?
181. Safety Plan Stress Test™
Scenario A — Survivor Has No Immediate Money
Can the plan still work?
Scenario B — Emergency Housing Is Unavailable
What is the alternative?
Scenario C — Phone Is Monitored
Can the survivor safely contact services?
Scenario D — Childcare Falls Through
Can required appointments still happen?
Scenario E — Perpetrator Breaches a Restriction
Does the plan automatically escalate?
Scenario F — Survivor Has Limited Mobility
Are relocation and transport recommendations realistic?
Scenario G — Temporary Support Ends
Does the plan remain sustainable?
Scenario H — Three Agencies Give Different Instructions
Which plan governs?
Scenario I — Survivor Cannot Complete the Administrative Tasks
Does institutional support increase?
Scenario J — Every Recommended Action Is Completed but Risk Remains
Is the plan reassessed?
182. Whole-Plan Stress Test™
Ask:
If every action in this plan were carried out exactly as written, would the survivor actually be safer?
183. Survivor Burden Stress Test™
Ask:
Could a person experiencing the identified level of risk realistically perform everything this plan requires without additional institutional support?
184. Safety Plan Counterfactual™
Ask:
Would the protective outcome have been materially different if the feasibility constraints had been identified earlier?
185. Institutional Support Counterfactual™
Ask:
Would the plan have succeeded if more of the protective workload had been carried by institutions rather than transferred to the survivor?
186. Safety Plan Root-Cause Analysis™
Plan Failure → Immediate Cause → Constraint / Dependency → Responsibility → System Cause → Protective Consequence → Redesign
187. Root-Cause Categories™
SRC1 — Risk Misidentification
SRC2 — Poor Individualisation
SRC3 — Feasibility Failure
SRC4 — Constraint Failure
SRC5 — Dependency Failure
SRC6 — Responsibility Failure
SRC7 — Support Failure
SRC8 — Implementation Failure
SRC9 — Monitoring Failure
SRC10 — Contingency Failure
SRC11 — Timing Failure
SRC12 — System Design Failure
188. Safety Plan Register™
Record:
Risk → Objective → Action → Feasibility → Owner → Dependency → Deadline → Status → Outcome
189. Feasibility Register™
Record:
Action → Feasibility Domain → Constraint → Severity → Required Support
190. Constraint Register™
Record all barriers to plan implementation.
191. Dependency Register™
Record critical plan dependencies and backups.
192. Responsibility Register™
Record survivor and institutional roles.
193. Critical Action Register™
Track high-impact actions.
194. Safety Plan Failure Register™
Record PF1–PF10 failures.
195. Contingency Register™
Record:
Failure Scenario → Backup → Owner → Trigger → Escalation
196. Reassessment Register™
Record material changes and resulting plan revisions.
197. Safety Plan Verification Register™
Record:
Action → Implemented → Protective Effect → Evidence → Verified By
198. Safety Plan Dashboard™
Monitor:
infeasible actions;
unsupported actions;
unresolved constraints;
single-point dependencies;
overdue actions;
institutional ownership gaps;
failed plan components;
reassessment triggers;
verification failures.
199. Safety Plan Metrics™
Potential measures include:
Plan Individualisation Rate™
Feasibility Assessment Rate™
Constraint Resolution Rate™
Institutional Support Coverage Rate™
Critical Action Completion Rate™
Safety Plan Implementation Rate™
Plan Reassessment Rate™
Contingency Coverage Rate™
Protective Outcome Verification Rate™
Survivor Burden Ratio™
Plan Sustainability Rate™
200. Plan Individualisation Rate™
Measures safety plans tailored to identified risk and circumstances.
201. Feasibility Assessment Rate™
Measures proposed actions receiving explicit feasibility analysis.
202. Constraint Resolution Rate™
Measures identified critical constraints resolved or mitigated.
203. Institutional Support Coverage Rate™
Measures actions requiring institutional support that receive it.
204. Critical Action Completion Rate™
Measures critical protective actions completed within required timescales.
205. Safety Plan Implementation Rate™
Measures agreed plan actions actually operational.
206. Plan Reassessment Rate™
Measures materially changed cases receiving plan review.
207. Contingency Coverage Rate™
Measures critical actions with viable backup arrangements.
208. Protective Outcome Verification Rate™
Measures plans assessed for real-world protective effect.
209. Survivor Burden Ratio™
Measures the proportion of plan implementation dependent primarily upon survivor action.
210. Plan Sustainability Rate™
Measures plans remaining protective after temporary support ends.
211. Safety Plan Integrity Classification™
SPI1 — Paper-Based
Plan exists with little feasibility testing.
SPI2 — Partially Feasible
Some constraints are recognised but implementation remains fragile.
SPI3 — Functional
Plan is largely feasible, owned and implementable.
SPI4 — Integrated
Risk, feasibility, ownership, support and contingencies are systematically connected.
SPI5 — Verified
Plan implementation, resilience and protective outcome are demonstrated.
212. Systemic Safety Planning Failure™
Defined as:
A recurring organisational pattern in which safety planning produces recommendations without sufficient feasibility, support, implementation or outcome verification.
213. Systemic Burden Transfer™
Defined as:
Recurring institutional dependence upon survivors to implement most of the safeguarding work required for protection.
214. Systemic Feasibility Failure™
Defined as:
Repeated recommendation of actions that are formally available but practically unusable.
215. Systemic Paper Safety™
Defined as:
Institutional reliance on completed safety plans as evidence of protection without adequate implementation or outcome assurance.
216. Safety Planning Learning Loop™
Risk → Plan → Implementation → Outcome → Failure / Success → Learning → Redesign
217. Redesign Trigger™
Trigger where:
plans repeatedly fail for the same reason;
survivor burden remains excessive;
the same constraints remain unresolved;
support cliffs recur;
protective outcomes remain weak;
standardised plans repeatedly prove infeasible.
218. Governance Review Trigger™
Senior review should be considered where:
PFS5 failures occur;
plan failure precedes serious harm;
critical safety actions remain unsupported;
institutional burden is systematically transferred;
multiple safety plans fail at the same dependency;
paper safety is used as assurance.
219. Risk Gate™
Verify:
✓ risk identified
✓ pattern considered
✓ protective objective explicit
✓ risk-to-action link established
220. Survivor Intelligence Gate™
Verify:
✓ survivor knowledge considered
✓ protective feasibility discussed
✓ relevant concerns preserved
✓ disagreement documented where necessary
221. Feasibility Gate™
Verify:
✓ FD1–FD12 domains considered
✓ critical constraints identified
✓ proposed options are practically usable
✓ feasibility classification assigned
222. Constraint Gate™
Verify:
✓ implementation barriers mapped
✓ interactions considered
✓ critical constraints mitigated
✓ false options excluded
223. Dependency Gate™
Verify:
✓ critical dependencies identified
✓ single points of failure tested
✓ backups considered
✓ dependency fragility assessed
224. Capacity Gate™
Verify:
✓ survivor capacity assessed
✓ implementation burden calculated proportionately
✓ disability and health considered
✓ inability distinguished from unwillingness
225. Responsibility Gate™
Verify:
✓ survivor actions explicit
✓ institutional actions explicit
✓ action owners assigned
✓ burden transfer reviewed
226. Support Gate™
Verify:
✓ required support available
✓ accessibility checked
✓ timing adequate
✓ service assumptions verified
227. Implementation Gate™
Verify:
✓ critical actions operational
✓ deadlines tracked
✓ partial implementation assessed
✓ evidence of completion retained
228. Monitoring Gate™
Verify:
✓ plan effectiveness reviewed
✓ changes detected
✓ ownership of monitoring clear
✓ drift identified
229. Contingency Gate™
Verify:
✓ failure scenarios considered
✓ backup actions defined
✓ emergency escalation route identified
✓ survivor knows relevant options where appropriate
230. Reassessment Gate™
Verify:
✓ changed risk triggers review
✓ failed plan components reassessed
✓ survivor intelligence updated
✓ obsolete measures removed
231. Verification Gate™
Verify:
✓ implementation confirmed
✓ protective effect assessed
✓ residual risk considered
✓ survivor outcome intelligence considered
232. Closure Gate™
Before closing the safety-planning process verify:
✓ critical actions completed or transferred
✓ unresolved constraints recorded
✓ residual risk assessed
✓ sustainable protection considered
✓ reopening triggers established
233. No-Plan-Equals-Protection Principle™
The existence of a safety plan does not establish safety.
234. No-Advice-Equals-Feasibility Principle™
The fact that advice is reasonable in theory does not establish that the survivor can implement it in practice.
235. No-Option-Equals-Choice Principle™
An option that cannot practically be used should not be treated as a genuine protective choice.
236. No-Agreement-Equals-Capacity Principle™
Agreement with a safety plan does not establish practical ability to carry it out.
237. No-Referral-Equals-Support Principle™
Referral to a service does not establish that support is available or accessible.
238. No-Action-Completed-Equals-Protection Principle™
Completion of a protective task does not itself establish reduction of risk.
239. No-Survivor-Noncompliance-Equals-Unwillingness Principle™
Failure to implement a plan should first be tested against feasibility, capacity, constraint and support.
240. No-Temporary-Safety-Equals-Sustainable-Safety Principle™
A crisis intervention should not be treated as durable protection without sustainability assessment.
241. No-Signed-Plan-Equals-Informed-Choice Principle™
Signature or agreement should not substitute for analysis of feasibility, constraints and meaningful alternatives.
242. No-Institutional-Advice-Equals-Institutional-Discharge Principle™
An institution should not treat advice to the survivor as completion of responsibilities that remain institutionally owned.
243. SAFETYPLANINTEGRITY-001™ Integrity Test
An institution applying SAFETYPLANINTEGRITY-001™ should be able to demonstrate that:
Safety Plan Integrity™ is defined.
safety planning is distinguished from protection.
advice is distinguished from implementation.
availability is distinguished from feasibility.
participation is distinguished from responsibility.
SPA1–SPA15 architecture operates.
every action links to an identified risk.
Protective Objectives™ are explicit.
Generic Safety Planning Risk™ is assessed.
plans are appropriately individualised.
PATTERNINTEGRITY-001™ is integrated.
CUMULATIVEHARM-001™ is integrated.
survivor intelligence informs planning.
SURVIVORINTELLIGENCE-001™ is integrated.
Protective Feasibility Intelligence™ is considered.
Survivor Feasibility Test™ operates.
Feasibility Integrity™ is assessed.
FD1–FD12 domains operate.
F1–F5 feasibility classification operates.
Feasibility Gaps™ are identified.
Plan–Capacity Gaps™ are identified.
constraints are not automatically interpreted as non-compliance.
Safety Plan Constraints™ are identified.
SC1–SC15 constraint categories operate.
ESCAPECAPACITY-001™ is integrated.
Constraint Density™ is assessed.
Constraint Interaction™ is assessed.
Constraint Multiplication™ is recognised.
Constraint Cascades™ are identified.
Option Reality Test™ operates.
False Safety Options™ are identified.
False Choice Risk™ is assessed.
Domestic Manufactured Choice™ is integrated.
plan dependencies are identified.
Safety Plan Dependencies™ are defined.
SD1–SD10 dependency categories operate.
Dependency Maps™ are produced.
PROTECTIVEDEPENDENCY-001™ is integrated.
Single-Point Safety Failures™ are identified.
Dependency Fragility™ is assessed.
dependency replacements are considered.
Survivor Capacity™ is assessed.
capacity domains are considered.
Capacity-Sensitive Planning™ operates.
inability is distinguished from unwillingness.
Implementation Burden™ is assessed.
implementation burden components are identified.
Burden Accumulation™ is assessed.
Safety Plan Burden Index™ can be applied.
Survivor Protective Burden™ is assessed.
Protective Burden Transfer™ is identified.
institutional and survivor burden are compared.
No-Survivor-as-Safety-System Principle™ operates.
institutional responsibilities are identified.
RESPONSIBILITYCHAIN-001™ is integrated.
Responsibility Allocation Maps™ are produced.
survivor actions are defined.
institutional actions are defined.
shared actions are defined.
Action Allocation Integrity™ is assessed.
No-Advice-Equals-Discharge Principle™ operates.
Institutional Support™ is defined.
Support Sufficiency™ is assessed.
Support Gaps™ are identified.
Support Dependency Gaps™ are identified.
service existence is not equated with accessibility.
Access Integrity™ is assessed.
ACCESSFAILURE-001™ is integrated.
timing integrity is assessed.
Protective Timing™ is recognised.
Timing Feasibility Test™ operates.
Late Protection Risk™ is identified.
Protective Windows™ are identified.
implementation timing gaps are assessed.
U1–U5 urgency classification operates.
IMPLEMENTATIONGAP-001™ is integrated.
Implementation Integrity™ is assessed.
IS1–IS5 status classification operates.
Planned–Implemented Gaps™ are identified.
Partial Implementation Risk™ is assessed.
Critical Actions™ are identified.
Critical Action Registers™ operate.
implementation is verified.
plan monitoring exists.
Plan Monitoring Integrity™ is assessed.
monitoring ownership is explicit.
plan issuance is not equated with monitoring.
Safety Plan Drift™ is identified.
Plan Obsolescence™ is identified.
Dynamic Planning Principle™ operates.
reassessment triggers exist.
Plan Reassessment™ occurs.
REVIEW-001™ is integrated.
Failure Contingency™ is defined.
No-Perfect-Plan Principle™ operates.
Contingency Integrity™ is assessed.
Contingency Gaps™ are identified.
C1–C5 contingency levels operate.
PROTECTIVEDEPENDENCY-001™ resilience principles are integrated.
failure detection exists.
survivor failure reports are treated as material intelligence.
plan non-compliance is not automatically attributed to the survivor.
Plan Failure™ is defined.
PF1–PF10 classification operates.
PFS1–PFS5 severity classification operates.
Plan Failure Attribution Integrity™ is assessed.
No-Automatic-Survivor-Attribution Principle™ operates.
breach integration exists.
BREACHINTEGRITY-001™ is integrated.
Breach Response Plans™ can be created.
protective measure integrity is assessed.
PROTECTIONGAP-001™ is integrated.
Paper Safety™ is identified.
Paper Safety Risk™ is assessed.
checklist completion is distinguished from effectiveness.
Documentation Bias™ is controlled.
Signed Plan Fallacy™ is recognised.
Consent Integrity™ is integrated.
agreement is distinguished from capacity.
Safety Plan Choice Integrity™ is assessed.
Manufactured Safety Choice™ is identified.
exit-dependent planning is identified.
Exit Feasibility Test™ operates.
ESCAPECAPACITY-001™ is fully integrated.
housing feasibility is assessed.
accommodation is distinguished from safe housing.
financial feasibility is assessed.
entitlement is distinguished from immediate liquidity.
digital feasibility is assessed.
DIGITALEXIT-001™ is integrated.
digital safety action risks are considered.
password change is not equated with digital safety.
child and dependant feasibility is assessed.
Dependant Safety Integrity™ is assessed.
childcare dependency is assessed.
transport feasibility is assessed.
geographic feasibility is assessed.
health feasibility is assessed.
disability-adjusted planning occurs.
employment feasibility is assessed.
immigration and documentation feasibility are assessed where relevant.
social feasibility is assessed.
social support is not assumed.
institutional feasibility is assessed.
Service Navigation Burden™ is assessed.
Fragmented Safety Planning™ is identified.
Cross-Plan Conflicts™ are identified.
Plan Compatibility Test™ operates.
Multi-Agency Safety Plan Integrity™ is assessed.
HANDOVERINTEGRITY-001™ is integrated.
CHAININTEGRITY-001™ is integrated.
Safety Chain Breaks™ are identifiable.
SCB1–SCB10 classification operates.
Safety Plan Verification™ occurs.
verification questions are answered.
Protective Outcomes™ are identified.
activity and outcome are distinguished.
Outcome Verification Integrity™ is assessed.
survivor outcome intelligence is considered.
Plan Sustainability™ is assessed.
short-term and long-term safety are distinguished.
Sustainability Test™ operates.
Support Cliffs™ are identified.
Safety Plan Cliff Risk™ is assessed.
stabilisation is considered.
Safety Plan Resilience™ is assessed.
SR1–SR5 resilience classification operates.
Resilience Test™ operates.
worst-credible scenarios are assessed.
Compound Safety Failures™ are assessed.
Compound Failure Test™ operates.
Safety Plan Stress Test™ operates.
Whole-Plan Stress Test™ operates.
Survivor Burden Stress Test™ operates.
Safety Plan Counterfactual™ operates.
Institutional Support Counterfactual™ operates.
Safety Plan Root-Cause Analysis™ operates.
SRC1–SRC12 root-cause categories operate.
Safety Plan Register™ operates.
Feasibility Register™ operates.
Constraint Register™ operates.
Dependency Register™ operates.
Responsibility Register™ operates.
Critical Action Register™ operates.
Safety Plan Failure Register™ operates.
Contingency Register™ operates.
Reassessment Register™ operates.
Safety Plan Verification Register™ operates.
Safety Plan Dashboard™ operates.
Plan Individualisation Rate™ can be measured.
Feasibility Assessment Rate™ can be measured.
Constraint Resolution Rate™ can be measured.
Institutional Support Coverage Rate™ can be measured.
Critical Action Completion Rate™ can be measured.
Safety Plan Implementation Rate™ can be measured.
Plan Reassessment Rate™ can be measured.
Contingency Coverage Rate™ can be measured.
Protective Outcome Verification Rate™ can be measured.
Survivor Burden Ratio™ can be measured.
Plan Sustainability Rate™ can be measured.
SPI1–SPI5 integrity classification operates.
Systemic Safety Planning Failure™ can be identified.
Systemic Burden Transfer™ can be identified.
Systemic Feasibility Failure™ can be identified.
Systemic Paper Safety™ can be identified.
Safety Planning Learning Loop™ operates.
redesign triggers operate.
governance review triggers exist.
Risk Gate™ operates.
Survivor Intelligence Gate™ operates.
Feasibility Gate™ operates.
Constraint Gate™ operates.
Dependency Gate™ operates.
Capacity Gate™ operates.
Responsibility Gate™ operates.
Support Gate™ operates.
Implementation Gate™ operates.
Monitoring Gate™ operates.
Contingency Gate™ operates.
Reassessment Gate™ operates.
Verification Gate™ operates.
Closure Gate™ operates.
a plan is not equated with protection.
advice is not equated with feasibility.
an option is not automatically equated with choice.
agreement is not equated with capacity.
referral is not equated with support.
action completion is not equated with protection.
non-implementation is not automatically equated with unwillingness.
temporary safety is not equated with sustainable safety.
signature is not automatically equated with informed choice.
institutional advice is not automatically equated with institutional discharge.
And ultimately:
Can the institution demonstrate not merely that a safety plan was written, but that every material action was linked to an identified risk, genuinely feasible within the survivor's circumstances, supported by sufficient institutional action, resilient to foreseeable failure, capable of implementation within the relevant protective window and verified for actual protective effect?
244. Framework Outcomes
Implementation establishes:
✓ Safety Plan Integrity™
✓ Plan–Protection Distinction™
✓ Advice–Implementation Distinction™
✓ Feasibility–Availability Distinction™
✓ Survivor Participation–Survivor Responsibility Distinction™
✓ Safety Planning Architecture™
✓ Risk-to-Action Trace™
✓ Protective Objective™
✓ Generic Safety Planning Risk™
✓ Individualised Safety Plan™
✓ Protective Feasibility Intelligence™
✓ Survivor Feasibility Test™
✓ Feasibility Integrity™
✓ Feasibility Domains™
✓ Feasibility Classification™
✓ Feasibility Gap™
✓ Plan–Capacity Gap™
✓ Safety Plan Constraint™
✓ Constraint Density™
✓ Constraint Interaction™
✓ Constraint Multiplication™
✓ Constraint Cascade™
✓ Option Reality Test™
✓ False Safety Option™
✓ False Choice Risk™
✓ Safety Plan Dependency™
✓ Dependency Mapping™
✓ Single-Point Safety Failure™
✓ Dependency Fragility™
✓ Survivor Capacity™
✓ Capacity-Sensitive Planning™
✓ Implementation Burden™
✓ Safety Plan Burden Index™
✓ Survivor Protective Burden™
✓ Protective Burden Transfer™
✓ No-Survivor-as-Safety-System Principle™
✓ Responsibility Allocation Map™
✓ Institutional Support™
✓ Support Sufficiency™
✓ Support Gap™
✓ Protective Timing™
✓ Late Protection Risk™
✓ Protective Window™
✓ Implementation Timing Gap™
✓ Implementation Integrity™
✓ Planned–Implemented Gap™
✓ Critical Action™
✓ Plan Monitoring Integrity™
✓ Safety Plan Drift™
✓ Plan Obsolescence™
✓ Dynamic Planning Principle™
✓ Failure Contingency™
✓ Contingency Integrity™
✓ Contingency Gap™
✓ Plan Failure™
✓ Plan Failure Classification™
✓ Plan Failure Attribution Integrity™
✓ Paper Safety™
✓ Manufactured Safety Choice™
✓ Exit Feasibility Test™
✓ Housing Feasibility™
✓ Financial Feasibility™
✓ Digital Feasibility™
✓ Child & Dependant Feasibility™
✓ Transport Feasibility™
✓ Disability-Adjusted Planning™
✓ Institutional Feasibility™
✓ Service Navigation Burden™
✓ Fragmented Safety Planning™
✓ Cross-Plan Conflict™
✓ Plan Compatibility Test™
✓ Safety Chain Break™
✓ Safety Plan Verification™
✓ Protective Outcome™
✓ Plan Sustainability™
✓ Support Cliff™
✓ Safety Plan Resilience™
✓ Compound Safety Failure™
✓ Safety Plan Stress Test™
✓ Whole-Plan Stress Test™
✓ Survivor Burden Stress Test™
✓ Safety Plan Counterfactual™
✓ Safety Plan Root-Cause Analysis™
✓ Safety Plan Register™
✓ Feasibility Register™
✓ Constraint Register™
✓ Dependency Register™
✓ Critical Action Register™
✓ Safety Plan Failure Register™
✓ Contingency Register™
✓ Safety Plan Verification Register™
✓ Safety Plan Dashboard™
✓ Safety Plan Metrics™
✓ Systemic Safety Planning Failure™
✓ Systemic Burden Transfer™
✓ Systemic Feasibility Failure™
✓ Systemic Paper Safety™
✓ Safety Planning Learning Loop™
✓ SAFETYPLANINTEGRITY-001™ Integrity Test™
245. Cross-Framework Integration
SAFETYPLANINTEGRITY-001™ integrates with:
ESCAPECAPACITY-001™ — practical capacity to leave and remain safely separated.
SURVIVORINTELLIGENCE-001™ — survivor knowledge of risk and protective feasibility.
RESPONSIBILITYCHAIN-001™ — ownership of protective actions.
PROTECTIONGAP-001™ — distinction between formal measures and practical protection.
PROTECTIVEDEPENDENCY-001™ — safety-plan dependency and resilience.
HANDOVERINTEGRITY-001™ — continuity of responsibilities between services.
CHAININTEGRITY-001™ — continuous risk-to-protection pathway.
IMPLEMENTATIONGAP-001™ — translation of safety decisions into action.
ACCESSFAILURE-001™ — barriers preventing use of protective options.
PATTERNINTEGRITY-001™ — plans informed by behavioural patterns.
CUMULATIVEHARM-001™ — cumulative burden and harm.
BREACHINTEGRITY-001™ — response to breached protective measures.
REVIEW-001™ — plan reassessment following material change.
DIGITALEXIT-001™ — digital-separation safety and safe sequencing.
PROTECTIVEDEPENDENCY-001™ — critical plan dependencies and failure resilience.
Consent Integrity™ — meaningful plan agreement.
Domestic Manufactured Choice™ — constrained protective choices.
Reduced Exit Capacity™ — practical limitation of available options.
Architecture of Entrapment™ — interaction between constraints and dependencies.
246. Framework Statement
A safety plan is not protective merely because it has been written, agreed or placed on a case file. Its integrity depends upon whether the actions it requires can actually be carried out within the person's financial, housing, digital, health, family, transport, employment, institutional and dependency circumstances. SAFETYPLANINTEGRITY-001™ establishes the SAFECHAIN™ architecture for testing that reality. It requires every protective action to be linked to a specific risk, assessed for feasibility, supported by adequate institutional responsibility, tested against constraints and dependencies, implemented within the relevant protective window, supported by contingency arrangements and verified for actual protective effect. The framework rejects the assumption that advice equals protection, that an available option is necessarily a usable option, that survivor agreement proves capacity, or that failure to implement a plan proves unwillingness to protect oneself. Its governing proposition is that safeguarding must not become a list of instructions handed to a person whose circumstances make those instructions impossible to follow. A credible safety plan therefore distributes responsibility according to authority and capacity, reduces rather than increases survivor burden and remains capable of functioning when circumstances change or individual measures fail.
247. Copyright & Intellectual Property Notice
© 2026 Samantha Avril-Andreassen. All Rights Reserved.
SAFETYPLANINTEGRITY-001™ — The SAFECHAIN™ Safety Planning, Feasibility & Protective Action Integrity Framework™ is an original safeguarding-governance, safety-planning, feasibility, protective-action and systems-reform framework developed and authored by Samantha Avril-Andreassen, LLB (Hons), LLM, LPC, FRSA, Founder of SAFECHAIN™.
The original expression, selection, arrangement and combination of its architecture, terminology, classifications, tests, registers, metrics, governance gates and analytical methodology constitute proprietary intellectual property to the extent protected by applicable law.
Protected elements include, where original to this framework, terminology and architecture associated with Safety Plan Integrity™, Plan–Protection Distinction™, Protective Feasibility Intelligence™, Feasibility Integrity™, Feasibility Gap™, Plan–Capacity Gap™, Constraint Density™, Constraint Multiplication™, Constraint Cascade™, Option Reality Test™, False Safety Option™, Safety Plan Dependency™, Single-Point Safety Failure™, Capacity-Sensitive Planning™, Safety Plan Burden Index™, Survivor Protective Burden™, Protective Burden Transfer™, No-Survivor-as-Safety-System Principle™, Responsibility Allocation Map™, Support Gap™, Protective Timing™, Late Protection Risk™, Protective Window™, Implementation Timing Gap™, Planned–Implemented Gap™, Safety Plan Drift™, Plan Obsolescence™, Failure Contingency™, Contingency Integrity™, Contingency Gap™, Plan Failure Attribution Integrity™, Paper Safety™, Manufactured Safety Choice™, Exit Feasibility Test™, Service Navigation Burden™, Fragmented Safety Planning™, Cross-Plan Conflict™, Plan Compatibility Test™, Safety Chain Break™, Plan Sustainability™, Support Cliff™, Safety Plan Resilience™, Compound Safety Failure™, Whole-Plan Stress Test™, Survivor Burden Stress Test™, Safety Plan Counterfactual™, Safety Plan Root-Cause Analysis™, Safety Plan Register™, Feasibility Register™, Safety Plan Failure Register™, Safety Plan Dashboard™, Systemic Safety Planning Failure™, Systemic Burden Transfer™, Systemic Feasibility Failure™, Systemic Paper Safety™, Safety Planning Learning Loop™ and the SAFETYPLANINTEGRITY-001™ Integrity Test™, together with associated implementation materials.
No claim is made to ownership of general concepts concerning safety planning, domestic-abuse safety plans, safeguarding, risk assessment, housing, financial support, referrals or protective measures. Proprietary claims relate to original SAFECHAIN™ expression, terminology, selection, arrangement, combination and methodology to the extent protected by applicable law.
SAFETYPLANINTEGRITY-001™ is an analytical and safeguarding-governance framework. A framework finding does not itself establish negligence, civil liability, professional misconduct, statutory breach, regulatory breach, criminal conduct or other unlawful conduct. Any such determination requires analysis under the applicable factual, legal, evidential and professional standards.
Author and Framework Developer:
Samantha Avril-Andreassen, LLB (Hons), LLM, LPC, FRSA
Founder — SAFECHAIN™
Framework Reference: SAFETYPLANINTEGRITY-001™
Version: 1.0
Year: 2026
© 2026 Samantha Avril-Andreassen. All Rights Reserved.