IMPLEMENTATIONGAP-001™
The SAFECHAIN™ Decision-to-Action, Implementation Failure & Delivery Integrity Framework™
Framework Reference: IMPLEMENTATIONGAP-001™
Framework Type: Institutional Governance, Decision Implementation, Delivery Integrity, Operational Accountability, Assurance, Safeguarding & Systems Reform
Framework Series: SAFECHAIN™ Justice & Institutional Integrity Series™
Parent Architecture: SAFECHAIN™ Governance Architecture™
Version: 1.0
Year: 2026
1. Framework Purpose
IMPLEMENTATIONGAP-001™ establishes a structured governance methodology for determining whether an institutional decision, recommendation, safeguarding action, corrective measure, review outcome or formal commitment has actually been translated into the action required by that decision.
Institutions frequently possess sophisticated mechanisms for:
making decisions;
approving recommendations;
recording actions;
assigning responsibilities;
producing action plans;
issuing instructions;
accepting audit findings;
agreeing remediation;
responding to complaints;
creating safeguarding plans;
announcing reforms.
Yet institutional failure can occur after all of those stages.
A decision may be correct.
A recommendation may be accepted.
A safeguard may be approved.
An action may be assigned.
A deadline may be recorded.
A system may then report the matter as “in progress” or “complete”.
But the required action may never have occurred—or may have occurred only partially, late, incorrectly, symbolically or in a form materially different from what was authorised.
IMPLEMENTATIONGAP-001™ therefore examines the critical governance space between:
What the institution decided should happen
and
What actually happened.
Its key question is:
Was the institutional decision actually translated into the action it required?
2. Implementation Gap™
SAFECHAIN™ defines an Implementation Gap™ as:
The material difference between an institutional decision, instruction, commitment, recommendation, safeguard or corrective requirement and the action actually delivered in response to it.
3. Delivery Integrity™
Defined as:
The extent to which required institutional action is assigned, delivered, evidenced, completed and verified in accordance with the meaning, scope, standard and timeframe of the originating decision.
4. Implementation Failure™
Defined as:
The failure to translate an authorised institutional requirement into sufficient operational action.
Implementation failure may include:
no action;
incomplete action;
incorrect action;
delayed action;
substituted action;
unowned action;
unsupported closure;
unverified completion.
5. Key Question
Was the institutional decision actually translated into the action it required?
6. Core Architecture
Decision → Required Action → Assignment → Delivery → Implementation Gap → Correction → Verification
Expanded:
Decision → Decision Requirement → Action Specification → Ownership → Assignment → Resource → Delivery → Evidence → Completion Assessment → Implementation Gap → Correction → Retest → Verification
7. Core Principle
An institutional decision has not been implemented merely because an action was assigned, attempted, recorded or marked complete. Implementation requires evidence that the action actually delivered the substance, scope, standard and outcome required by the originating decision.
8. SAFECHAIN™ Implementation Integrity Architecture™
IIA1 — Decision
Identify the authoritative decision.
IIA2 — Required Action
Translate the decision into identifiable operational requirements.
IIA3 — Assignment
Assign each requirement to an accountable owner.
IIA4 — Capability
Confirm authority, competence and resources.
IIA5 — Delivery
Perform the required action.
IIA6 — Evidence
Retain evidence demonstrating delivery.
IIA7 — Gap Assessment
Compare required action with actual delivery.
IIA8 — Correction
Address implementation deficiencies.
IIA9 — Retest
Determine whether corrective action resolved the gap.
IIA10 — Verification
Confirm that implementation is complete and effective.
9. Decision-to-Action Integrity™
Defined as:
The preservation of an institutional decision's substantive meaning as it is converted into operational action.
10. Decision-to-Action Test™
Ask:
What exactly had to happen for this decision to be considered implemented?
If the institution cannot answer this clearly, reliable implementation cannot easily be demonstrated.
11. Decision–Implementation Distinction™
SAFECHAIN™ distinguishes:
Decision Made
from
Decision Implemented
A decision may exist without producing any operational consequence.
12. Decision Completion Fallacy™
Defined as:
The assumption that institutional responsibility is substantially discharged once a decision has been made, despite the action required by that decision remaining incomplete.
13. Required Action™
Every material decision should be capable of translation into identifiable action.
14. Action Specification™
Required action should establish:
What → Who → By When → To What Standard → With What Evidence → Subject to What Verification
15. Action Specification Test™
Ask:
Could an independent reviewer determine objectively whether this action had been completed?
16. Ambiguous Action Risk™
Instructions such as:
“address concerns”;
“consider improvements”;
“review processes”;
“take appropriate action”;
“ensure lessons are learned”;
may be too vague to establish meaningful accountability.
17. Action Precision Principle™
The greater the institutional risk, the greater the need for implementation requirements to be specific, attributable and verifiable.
18. Action Decomposition™
Complex decisions should be divided into individual implementation requirements.
Example:
Decision → Action A + Action B + Action C + Action D
19. Composite Implementation Risk™
Defined as:
The risk that an institution treats a multi-part decision as complete despite one or more required components remaining outstanding.
20. Whole-Decision Completion Test™
Ask:
Have all material components of the decision been implemented?
21. Partial Implementation™
Defined as:
Delivery of some, but not all, substantive requirements arising from a decision.
22. Partial Implementation Concealment™
Occurs where the completed portion of an action creates the appearance that the whole requirement has been fulfilled.
23. Partial Implementation Test™
Compare:
Total Requirements → Completed Requirements → Outstanding Requirements
24. Implementation Coverage™
Defined as:
The proportion and materiality of required action actually delivered.
25. Coverage Integrity Test™
Completion percentages should account for the importance of outstanding actions.
Nine minor actions completed and one critical safeguard outstanding should not automatically equal 90% effective implementation.
26. Critical Action Weighting™
Actions should therefore be classified according to materiality.
CA1 — Routine
CA2 — Relevant
CA3 — Material
CA4 — Critical
CA5 — Safety / Integrity Critical
27. Critical Action Rule™
A decision should not ordinarily be classified as fully implemented while a CA4 or CA5 requirement remains materially incomplete.
28. Action Ownership™
Every required action should have an identifiable accountable owner.
29. Ownership Integrity Test™
Ask:
Who is personally or functionally accountable for ensuring this action reaches verified completion?
30. Unowned Action™
Defined as:
A required institutional action for which no identifiable person, team or governance function holds clear responsibility for completion.
31. Collective Ownership Failure™
Where responsibility is assigned broadly to:
“the team”;
“management”;
“the service”;
“relevant departments”;
there is a risk that responsibility becomes diffuse.
32. Ownership Diffusion™
Defined as:
The weakening of implementation accountability caused by distributing responsibility without identifying a sufficiently clear completion owner.
33. Named Ownership Principle™
Material actions should identify:
Accountable Owner → Delivery Owner → Verification Owner
where appropriate.
34. Ownership Transfer™
Implementation responsibilities may move between people or teams.
35. Transfer Integrity Test™
Before transfer verify:
✓ outstanding action identified
✓ deadline preserved
✓ decision context transferred
✓ evidence transferred
✓ new owner accepts responsibility
✓ escalation status preserved
36. Orphaned Action™
Defined as:
An implementation requirement that loses active ownership during organisational transfer, staff change, restructuring or handover.
37. Orphaned Action Alert™
Triggered where:
owner leaves;
team restructures;
case transfers;
action remains open;
replacement owner is absent.
38. CONTINUITY-001™ Integration
Implementation responsibility must survive institutional transitions.
39. Assignment Integrity™
Assignment itself should be:
explicit;
acknowledged;
achievable;
time-bound;
appropriately authorised.
40. Assignment Acceptance™
The receiving owner should know:
what is required;
why;
by when;
what evidence is needed;
what happens if delivery becomes impossible.
41. Silent Assignment Failure™
Defined as:
The recording of responsibility against an individual or team without reliable confirmation that the responsible party received, understood or accepted the requirement.
42. Assignment Verification Test™
Ask:
Can the institution demonstrate that the implementation owner knew the action had been assigned?
43. Capability-to-Deliver Test™
Before assignment, assess whether the owner possesses:
authority;
competence;
information;
time;
systems;
resources.
44. SAFEGUARDCAPACITY-001™ Integration
An action cannot reliably be implemented where required operational capability is absent.
45. Impossible Assignment™
Defined as:
An action assigned to an owner who lacks sufficient authority, resources, information or capability to deliver it.
46. Responsibility Without Capability™
Institutions should not mistake assignment of responsibility for provision of capacity.
47. Resource-to-Action Integrity™
Required resources should be identified before implementation deadlines are imposed.
48. Unresourced Action™
Defined as:
An approved action for which the institution has not provided sufficient resources to permit reliable implementation.
49. Delivery™
Delivery means performance of the required action—not merely administrative processing surrounding it.
50. Activity–Implementation Distinction™
SAFECHAIN™ distinguishes:
Activity Occurred
from
Required Action Was Implemented
51. Activity Substitution™
Defined as:
The replacement of the substantive action required by a decision with an activity that is easier to demonstrate but does not fulfil the original requirement.
52. Activity Substitution Examples™
Examples may include:
Required: redesign unsafe process
Delivered: staff reminder
Required: investigate systemic failure
Delivered: team discussion
Required: implement safeguard
Delivered: update policy
Required: verify correction
Delivered: receive management assurance
53. Implementation Substitution™
Defined as:
The delivery of an alternative action in place of the action originally required without adequate assessment that the substitute achieves an equivalent outcome.
54. Substitution Integrity Test™
Ask:
Does the substituted action achieve the substantive purpose of the original requirement?
55. Unauthorised Substitution™
Material implementation requirements should not be replaced without:
justification;
authority;
equivalence assessment;
documented approval.
56. Delivery Fidelity™
Defined as:
The extent to which actual implementation corresponds to the action authorised by the originating decision.
57. Delivery Fidelity Test™
Compare:
Required Action ↔ Actual Action
across:
scope;
substance;
quality;
timing;
population;
location;
duration;
intended outcome.
58. Implementation Drift™
Implementation may diverge from the originating decision over time.
59. DECISIONDRIFT-001™ Integration
DECISIONDRIFT-001™ asks whether the meaning of the decision has changed.
IMPLEMENTATIONGAP-001™ asks whether the action required by that decision was actually delivered.
Together:
Decision Fidelity → Implementation Fidelity → Outcome Integrity
60. Delivery Standard™
Completion should specify not only whether an action occurred but whether it met the required standard.
61. Minimum Delivery Standard™
Defined as:
The minimum substantive level of implementation required before an action may legitimately be classified as completed.
62. Delivery Quality Test™
Ask:
Was the action merely performed, or was it performed to the standard required?
63. Procedural Completion–Substantive Completion Distinction™
An action may be procedurally complete while substantively incomplete.
64. Procedural Completion™
Examples:
form submitted;
meeting held;
policy issued;
referral sent;
training delivered.
65. Substantive Completion™
Requires evidence that the purpose underlying the action has actually been delivered.
66. Completion Integrity Test™
Ask:
What changed because this action was completed?
67. Completion Evidence™
Completion should be supported by evidence proportionate to action materiality.
68. Evidence of Implementation™
Possible evidence includes:
completed records;
system changes;
communications;
revised processes;
signed approvals;
service delivery records;
audit evidence;
outcome data;
user confirmation;
independent testing.
69. Evidence Sufficiency Test™
Ask:
Does the evidence prove implementation—or merely prove that implementation was discussed or intended?
70. Intent–Delivery Distinction™
Intention ≠ Implementation
Planning ≠ Implementation
Assignment ≠ Implementation
Activity ≠ Implementation
Reporting ≠ Implementation
Closure ≠ Implementation
71. Completion-by-Assertion™
Defined as:
An implementation status based primarily upon an unsupported statement that the required action has been completed.
72. Self-Certified Completion™
Defined as:
Completion confirmed solely by the individual or function responsible for delivering the action without proportionate independent verification.
73. Self-Certification Risk™
Risk increases where:
action is high impact;
failure previously occurred;
completion is contested;
safeguarding is involved;
regulatory requirements apply;
recurring failure exists.
74. ASSURANCEGAP-001™ Integration
Implementation assurance should distinguish:
Declared Completion → Evidenced Completion → Verified Completion
75. Completion Confidence Classification™
IC1 — Claimed
Completion asserted without sufficient evidence.
IC2 — Documented
Some supporting evidence exists.
IC3 — Evidenced
Substantive implementation evidence exists.
IC4 — Tested
Implementation has been tested.
IC5 — Independently Verified
Implementation and effectiveness have been independently confirmed.
76. Completion Status Integrity™
Recommended statuses:
IS1 — Not Started
IS2 — Assigned
IS3 — In Progress
IS4 — Delivered Pending Verification
IS5 — Verified Complete
IS6 — Failed / Reopened
77. No-Binary-Closure Principle™
Complex institutional implementation should not be reduced prematurely to Open / Closed where material verification remains outstanding.
78. Premature Completion™
Defined as:
The classification of an action as complete before sufficient evidence exists that the substantive requirement has been fulfilled.
79. Premature Closure Alert™
Triggered where:
evidence missing;
verification incomplete;
critical component outstanding;
outcome untested;
affected party disputes delivery;
recurrence occurs.
80. Administrative Completion™
Defined as:
Closure of an action within the tracking system irrespective of whether substantive implementation has been verified.
81. Administrative Completion Fallacy™
A closed action record does not itself establish completed implementation.
82. Closure Evidence Test™
Ask:
What evidence justified changing this action from open to complete?
83. Closure Authority™
High-risk implementation should identify who is authorised to approve final closure.
84. Delivery Delay™
Implementation integrity includes timeliness.
85. Implementation Delay™
Defined as:
The failure to deliver required action within the timeframe necessary to preserve the purpose, safety or effectiveness of the originating decision.
86. Delay Materiality Test™
Assess whether delay affects:
safety;
rights;
access;
risk;
financial consequences;
service continuity;
evidence;
effectiveness;
trust.
87. Delay Classification™
ID1 — Minor
ID2 — Manageable
ID3 — Material
ID4 — Serious
ID5 — Outcome-Defeating
88. Outcome-Defeating Delay™
Defined as:
Delay so significant that subsequent implementation can no longer reasonably achieve the purpose of the original decision.
89. Time-Sensitive Implementation™
Some actions lose value if delayed.
90. Time-to-Implementation™
Measure:
Decision Date → Assignment Date → Action Start → Delivery Date → Verification Date
91. Delay Attribution™
Where delay occurs identify whether caused by:
ownership;
resource;
approval;
system;
external dependency;
competence;
communication;
deliberate reprioritisation;
unresolved ambiguity.
92. Deadline Extension Integrity™
Extensions should require:
reason;
risk assessment;
approval;
revised deadline;
interim safeguard.
93. Silent Deadline Drift™
Defined as:
Repeated movement or non-enforcement of implementation deadlines without formal reassessment of the consequences of delay.
94. Deadline Integrity Test™
Ask:
Was the deadline changed because risk changed—or because delivery became inconvenient?
95. Dependency-Based Implementation™
Many actions depend upon other actions.
96. Implementation Dependency Chain™
Action A → Action B → Action C → Outcome
97. Dependency Failure™
If Action A fails, downstream actions may become impossible or ineffective.
98. Dependency Mapping™
Identify:
prerequisite actions;
external dependencies;
approvals;
information;
technology;
resource;
sequencing.
99. Critical Path Integrity™
High-impact implementation should identify actions whose failure would prevent overall completion.
100. External Delivery Dependency™
Institutions may rely upon third parties to implement part of a decision.
101. External Dependency Principle™
Delegating delivery does not automatically remove institutional responsibility for verifying whether the required action occurred.
102. External Delivery Verification™
Ask:
What evidence confirms that the external party delivered what was required?
103. Referral–Implementation Distinction™
A referral is not necessarily the implementation of the safeguard or remedy the referral was intended to secure.
104. Referral Completion Fallacy™
Defined as:
The assumption that institutional responsibility ends when a referral has been sent, regardless of whether the receiving service accepted, acted upon or completed the required intervention.
105. Referral Outcome Test™
Track:
Referral → Receipt → Acceptance → Action → Outcome
106. Implementation Handoff™
Where delivery transfers between teams:
Sender → Requirement → Recipient → Acceptance → Delivery → Confirmation
107. Handoff Failure™
Defined as:
Loss, delay, distortion or abandonment of implementation responsibility during transfer between actors.
108. INTERFACE-001™ Integration
Implementation gaps frequently arise at:
team interfaces;
agency interfaces;
digital interfaces;
operational handoffs.
109. FLOW-001™ Integration
Required action should remain traceable throughout institutional workflow.
110. Implementation Traceability™
Defined as:
The ability to trace a required action continuously from originating decision to verified completion.
111. Decision-to-Delivery Trace™
Decision → Requirement → Owner → Action → Evidence → Verification
112. Traceability Failure™
Exists where any material stage cannot be reconstructed.
113. Implementation Provenance™
Records should establish:
originating decision;
authority;
action requirement;
owner;
delivery evidence;
changes;
closure authority;
verification.
114. Implementation Gap Classification™
IG1 — Negligible Gap
Minor administrative discrepancy with no material delivery effect.
IG2 — Limited Gap
Some deficiency but substantive purpose largely achieved.
IG3 — Material Gap
Required implementation materially incomplete, delayed or altered.
IG4 — Serious Gap
Significant safeguarding, rights, operational or governance consequence.
IG5 — Critical Implementation Failure
The required institutional action has not been delivered sufficiently and material risk, harm or accountability consequences remain.
115. Implementation Failure Types™
IF1 — Non-Implementation
Required action never occurred.
IF2 — Partial Implementation
Only part occurred.
IF3 — Delayed Implementation
Action occurred too late.
IF4 — Incorrect Implementation
Action materially failed to follow requirement.
IF5 — Substituted Implementation
Different action delivered.
IF6 — Unowned Implementation
No accountable owner.
IF7 — Unverified Implementation
Completion asserted without adequate evidence.
IF8 — Unsustained Implementation
Action occurred but did not persist.
116. Implementation Gap Materiality Test™
Ask:
Could the gap materially affect safety, rights, risk, institutional integrity, access, service quality, accountability or the intended outcome?
117. Implementation Impact™
Implementation gaps should be assessed by consequence, not merely administrative status.
118. Outcome Integrity™
The ultimate question is whether implementation produced the intended institutional effect.
119. Action–Outcome Distinction™
Even technically correct implementation may fail to produce the intended outcome.
120. Outcome Effectiveness Test™
Compare:
Required Outcome → Delivered Action → Actual Outcome
121. REMEDYINTEGRITY Interface™
IMPLEMENTATIONGAP-001™ determines whether the remedy was delivered.
REMEDYINTEGRITY-001™ can determine whether the delivered remedy was actually effective.
122. Implementation Effectiveness™
Defined as:
The extent to which delivered action achieves the substantive purpose of the originating decision.
123. Output–Outcome Distinction™
Output: action performed.
Outcome: intended change achieved.
Both may require assessment.
124. Symbolic Implementation™
Defined as:
Action that demonstrates visible institutional activity without materially delivering the substantive change required.
125. Symbolic Implementation Test™
Ask:
Did this action materially change the condition that required intervention?
126. Performative Completion Risk™
Occurs where implementation primarily demonstrates organisational responsiveness rather than solving the identified problem.
127. Paper Implementation™
Defined as:
Implementation existing primarily in policies, plans, records or reporting while operational practice remains materially unchanged.
128. Paper-to-Practice Test™
Compare:
Documented Change ↔ Operational Reality
129. ASSURANCEGAP-001™ Operational Integration
Paper implementation should trigger testing of the gap between declared and verified operational reality.
130. Safeguarding Implementation Gap™
Defined as:
The difference between an authorised safeguarding action and the protective intervention actually delivered.
131. Safeguarding Delivery Test™
Ask:
Did the person or population actually receive the safeguard that the decision required?
132. Safeguarding Completion Risk™
A safeguarding action should not be closed merely because:
referral sent;
meeting held;
note added;
advice issued;
policy followed.
Protective outcome requires examination.
133. Safeguarding Implementation Gate™
Before closure verify:
✓ protective action delivered
✓ delivery timely
✓ required recipient reached
✓ residual risk assessed
✓ outstanding action identified
✓ outcome verified
134. ACCESSFAILURE-001™ Integration
A formally implemented remedy may remain inaccessible to the person intended to benefit from it.
135. User-Experienced Implementation™
Institutional records should be capable of comparison with the experience of those receiving the action.
136. Delivery Experience Gap™
Defined as:
The difference between institutional records of implementation and the implementation actually experienced by the intended recipient.
137. Experience Verification Test™
Ask:
Would the intended recipient recognise the institution's description of what was delivered?
138. Complaint-as-Implementation Signal™
Complaints following claimed completion may indicate:
non-delivery;
partial delivery;
ineffective delivery;
inaccessible delivery;
recurrence.
139. FEEDBACK-001™ Integration
Feedback should be capable of reopening assumptions about successful implementation.
140. Recurring Implementation Gap™
Repeated failure to implement similar decisions indicates a structural problem.
141. RECURRINGFAILURE-001™ Integration
Repeated implementation failure should trigger:
Recurrence → Structural Analysis → Escalation → Redesign → Retesting
142. Implementation Recurrence Trigger™
Trigger where:
same action repeatedly missed;
same deadline repeatedly extended;
same team repeatedly fails;
same safeguard repeatedly not delivered;
same recommendation reappears.
143. Repeated Recommendation Paradox™
Defined as:
The condition in which substantially the same recommendation appears across successive reviews because previous recommendations were accepted but never effectively implemented.
144. Recommendation Recurrence Test™
Ask:
Why is the institution being asked again to do something it previously agreed to do?
145. Implementation Debt™
Defined as:
The accumulated burden created by unresolved, partially delivered or repeatedly deferred institutional actions.
146. Implementation Debt Risk™
Accumulated actions may:
overwhelm capacity;
obscure priorities;
create stale commitments;
weaken accountability;
increase systemic risk.
147. Implementation Debt Register™
Record:
overdue action;
original decision;
materiality;
age;
consequence;
owner;
recovery plan.
148. Implementation Age™
Institutions should know how long significant actions remain incomplete.
149. Ageing Action Alert™
Escalate where high-materiality actions exceed expected implementation periods.
150. Implementation Backlog™
Backlogs should be risk-ranked rather than managed only by age.
151. Risk-Based Implementation Priority™
Priority should consider:
Risk × Harm × Urgency × Dependency × Consequence of Delay
152. Implementation Priority Classification™
IP1 — Routine
IP2 — Standard
IP3 — Priority
IP4 — Urgent
IP5 — Critical
153. Escalation of Implementation Failure™
Material implementation gaps should not remain indefinitely within routine action-management processes.
154. ESCALATION-001™ Integration
IG4–IG5 implementation gaps should trigger proportionate governance escalation.
155. Implementation Failure Escalation Trigger™
Potential triggers include:
missed critical safeguard;
repeated delay;
failed corrective action;
unowned action;
disputed completion;
material external dependency failure;
recurrence.
156. Leadership Visibility™
Senior leadership should be able to see material implementation gaps.
157. Hidden Implementation Failure™
Defined as:
A material implementation deficit that remains invisible to governance because reporting focuses on activity, percentages or closure counts rather than substantive delivery.
158. Green Action-Plan Illusion™
An action plan may appear predominantly green while critical implementation weaknesses remain.
159. Dashboard Integrity Test™
Ask:
Would the dashboard remain green if completion required verified substantive delivery rather than reported status?
160. Metric Gaming Risk™
Completion metrics may create incentives to:
redefine action;
lower standards;
extend deadlines;
close prematurely;
classify partial action as complete.
161. Completion Metric Integrity™
Metrics should distinguish:
claimed;
delivered;
evidenced;
tested;
verified.
162. No-Percentage-Equals-Integrity Principle™
A high action-completion percentage does not establish implementation integrity where the materiality and effectiveness of outstanding actions are unknown.
163. Implementation Correction™
Where a gap is identified:
Gap → Cause → Risk → Corrective Action → Owner → Deadline → Retest
164. Correction Integrity™
Corrective action should address the cause of the implementation gap rather than simply completing overdue paperwork.
165. Implementation Root-Cause Analysis™
Potential causes:
ambiguous instruction;
ownership failure;
inadequate resources;
insufficient authority;
capability deficit;
poor handoff;
weak monitoring;
system failure;
dependency failure;
deadline weakness;
cultural resistance;
competing priorities.
166. Root-Cause Test™
Ask:
Why did a valid institutional decision fail to become operational reality?
167. Correction–Completion Distinction™
Correcting an implementation gap may require more than belatedly performing the original action.
The delay itself may have created additional consequences.
168. Consequence Correction™
Assess:
Original Gap → Consequences Created → Additional Remedy Required
169. REVIEW-001™ Integration
Material implementation failure may require reconsideration of the originating decision where circumstances have changed during the delay.
170. Correction Propagation™
If implementation failure affected downstream actions:
Identify → Correct → Notify → Reassess → Verify
171. DECISIONDRIFT-001™ Correction Integration
Correction should ensure the implementation requirement still corresponds to the authoritative decision.
172. Implementation Retest™
Completion after correction should be retested.
173. Retest Integrity Test™
Ask:
Has the institution demonstrated that the corrected implementation now functions as required?
174. Verification Independence™
The greater the action's significance, the stronger the case for verification separate from delivery.
175. Delivery–Verification Separation™
Where proportionate:
Person Who Delivers ≠ Person Who Verifies
176. Verification Proportionality™
Verification intensity should reflect:
risk;
materiality;
prior failure;
recurrence;
safeguarding significance;
consequence.
177. Independent Verification Trigger™
Enhanced independence may be required where:
IG4–IG5 gap;
previous false completion;
repeated failure;
contested delivery;
high safeguarding risk;
serious governance consequence.
178. Verification Failure™
Defined as:
Failure to obtain sufficient evidence that required implementation actually occurred and achieved the necessary standard.
179. Verification Evidence Hierarchy™
From weaker to stronger:
Assertion → Document → Operational Evidence → Testing → Independent Verification
180. Verification Currency™
Implementation evidence should remain sufficiently current where ongoing controls are involved.
181. One-Time Implementation–Sustained Implementation Distinction™
Some actions require continued operation rather than single completion.
182. Sustained Implementation™
Defined as:
Continued operation of the implemented action over the period necessary to achieve and preserve its intended effect.
183. Sustainability Test™
Ask:
Is the action still operating as intended after initial implementation?
184. Implementation Regression™
Defined as:
The deterioration or abandonment of an action after it was previously implemented successfully.
185. Regression Trigger™
Indicators include:
recurrence;
declining compliance;
staff turnover;
policy drift;
resource reduction;
system change;
monitoring failure.
186. Sustainability Verification™
High-impact reforms should be reviewed after implementation.
Potential checkpoints:
30 Days → 90 Days → 6 Months → 12 Months
depending upon context and risk.
187. Implementation Resilience™
Implemented controls should survive foreseeable organisational change.
188. RESILIENCE-001™ Integration
Stress test implementation under:
staff absence;
leadership change;
demand increase;
technology failure;
restructuring;
resource pressure.
189. SYSTEMCHECK-001™ Integration
System-level implementation should be tested beyond isolated action completion.
190. Implementation Stress Test™
Scenario A — Owner Leaves
Does the action continue?
Scenario B — Resources Reduce
Does the safeguard remain?
Scenario C — Demand Increases
Does implementation still function?
Scenario D — System Changes
Is the requirement preserved?
Scenario E — Complaint Challenges Completion
Can evidence prove delivery?
Scenario F — Failure Recurs
Does the institution reopen implementation?
Scenario G — Independent Reviewer Tests It
Does the claimed change exist operationally?
191. Implementation Counterfactual™
Ask:
If this action had not been recorded as complete, what evidence would we require before believing it had actually happened?
192. Reality-of-Delivery Test™
Ask:
What exists in operational reality today that did not exist before the decision was implemented?
193. Recipient Reality Test™
Where relevant:
What changed for the person, service or population the action was intended to affect?
194. Decision Survival Test™
Ask:
Can the originating decision be traced intact through assignment, delivery and verification?
195. Implementation Audit Trail™
Maintain:
Decision → Action → Owner → Deadline → Evidence → Changes → Completion → Verification → Outcome
196. Implementation Action Register™
Record:
decision reference;
required action;
CA materiality;
IP priority;
owner;
deadline;
status;
evidence;
verification status.
197. Implementation Gap Register™
Record:
implementation gap;
IG severity;
IF failure type;
consequence;
root cause;
corrective action;
escalation;
retest.
198. Implementation Verification Register™
Record:
action;
completion claim;
evidence;
verifier;
verification method;
IC confidence;
outcome.
199. Overdue Critical Action Register™
Track all CA4–CA5 actions exceeding required delivery periods.
200. Substitution Register™
Record:
original action;
substituted action;
reason;
equivalence assessment;
approval;
verification.
201. SAFECHAIN™ Implementation Integrity Dashboard™
Monitor:
IG3–IG5 gaps;
IF1–IF8 failures;
CA4–CA5 incomplete actions;
overdue critical actions;
unowned actions;
orphaned actions;
implementation debt;
substituted actions;
claimed vs verified completion;
recurring recommendations;
implementation regression.
202. Dashboard Measures™
Potential measures include:
Verified Completion Rate™
Critical Action Delivery Rate™
Implementation Gap Rate™
Overdue Critical Action Rate™
False Completion Rate™
Reopened Implementation Rate™
Implementation Recurrence Rate™
203. Verified Completion Rate™
Defined as:
The proportion of implementation actions supported by sufficient evidence and verification rather than status assertion alone.
204. False Completion Rate™
Defined as:
The proportion of actions previously recorded as complete that subsequently require reopening because substantive implementation was absent, deficient or ineffective.
205. Implementation Recurrence Rate™
Measures how frequently substantially similar failures reappear after claimed corrective implementation.
206. Implementation Governance Review™
Governance should periodically ask:
what remains incomplete?
what is overdue?
what is unverified?
what has been substituted?
what has reopened?
what keeps recurring?
which critical actions remain exposed?
207. Implementation Challenge Function™
Independent challenge should test whether reported progress reflects operational reality.
208. Challenge Question™
Show the evidence—not simply the status.
209. Implementation Transparency™
Material implementation gaps should be visible to appropriate governance bodies rather than hidden through aggregate reporting.
210. Implementation Risk Statement™
Where significant action remains incomplete, reporting should identify:
What Remains Undelivered → Why → Consequence → Interim Control → Owner → Revised Deadline
211. Interim Safeguard™
Where implementation cannot occur immediately, temporary safeguards may be required.
212. Interim Safeguard Integrity Test™
Ask:
What protects against the identified risk while permanent implementation remains incomplete?
213. Interim Measure Permanence Risk™
Temporary measures should not become indefinite substitutes for permanent correction without review.
214. Temporary-to-Permanent Drift™
Defined as:
The institutional normalisation of an interim workaround because permanent implementation remains unresolved.
215. Workaround Dependency™
Implementation gaps may become hidden where staff develop informal workarounds.
216. Workaround Integrity Test™
Ask:
Is the system functioning because the required solution was implemented—or because individuals are compensating for its absence?
217. No-Workaround-Equals-Remediation Principle™
An informal workaround does not establish that the underlying implementation requirement has been fulfilled.
218. Implementation Culture™
Reliable delivery requires an institutional culture in which actions are owned through to verified completion.
219. Decision-to-Delivery Accountability™
Decision-makers should understand how implementation will be monitored after approval.
220. Approval Without Follow-Through Risk™
Defined as:
The governance risk created when institutional oversight focuses heavily on approving action while giving insufficient attention to whether approved action subsequently occurs.
221. Follow-Through Integrity Test™
Ask:
Who checks what happened after the meeting, decision, recommendation or action plan?
222. Implementation Accountability Chain™
Decision Authority → Action Owner → Delivery Owner → Verification Owner → Governance Oversight
223. Accountability Break™
Defined as:
Any point at which responsibility for progressing, delivering, checking or escalating implementation becomes unclear.
224. ACCOUNTABILITY-001™ Integration
Implementation accountability should remain identifiable from decision through final verification.
225. REMEDIATION-001™ Integration
Corrective action is not complete until remediation has been implemented and verified.
226. VALIDATION-001™ Integration
Material implementation claims may require validation against defined criteria.
227. METRICS-001™ Integration
Implementation metrics should measure meaningful delivery rather than administrative activity alone.
228. Implementation Integrity Gate™
Before implementation begins verify:
✓ authoritative decision identified
✓ required action specified
✓ materiality classified
✓ owner identified
✓ capability confirmed
✓ deadline established
✓ evidence requirement defined
✓ verification method identified
229. Assignment Gate™
Before assigning action verify:
✓ owner understands requirement
✓ owner possesses authority
✓ resources available
✓ dependencies identified
✓ deadline achievable
✓ escalation route understood
230. Delivery Gate™
Before declaring delivery verify:
✓ substantive action occurred
✓ required scope covered
✓ required standard met
✓ timing acceptable
✓ substitution authorised if applicable
✓ evidence retained
231. Completion Gate™
Before marking complete verify:
✓ all material components delivered
✓ CA4–CA5 actions complete
✓ evidence sufficient
✓ outcome assessed where required
✓ residual gaps documented
✓ verifier identified
232. Verification Gate™
Before final closure verify:
✓ delivery independently checked where proportionate
✓ implementation gap resolved
✓ downstream consequences addressed
✓ recurrence risk assessed
✓ sustainability considered
✓ audit trail complete
233. Reopening Gate™
Reopen implementation where:
✓ completion evidence disproved
✓ recurrence occurs
✓ material component discovered incomplete
✓ substituted action ineffective
✓ recipient evidence materially contradicts institutional record
✓ verification fails
234. No-Decision-Equals-Delivery Principle™
Making the decision does not deliver the decision.
235. No-Assignment-Equals-Implementation Principle™
Assigning responsibility does not prove that the required action occurred.
236. No-Activity-Equals-Implementation Principle™
Institutional activity is not evidence of implementation unless it fulfils the substantive requirement.
237. No-Documentation-Equals-Delivery Principle™
A record stating that action occurred does not by itself prove operational delivery.
238. No-Closure-Equals-Completion Principle™
Closing an action does not establish that implementation was complete.
239. No-Completion-Equals-Effectiveness Principle™
An implemented action may still require testing to determine whether it achieved its intended purpose.
240. No-Delegation-Equals-Discharge Principle™
Passing an action to another person or organisation does not itself establish that the originating responsibility has been discharged.
241. No-Delay-Equals-Neutrality Principle™
Implementation delay can itself alter risk, harm, access and the effectiveness of the eventual response.
242. No-Green-Equals-Delivered Principle™
A green status is an assurance claim requiring evidence, not proof in itself.
243. IMPLEMENTATIONGAP-001™ Integrity Test
An institution should be able to demonstrate that:
Implementation Gap™ is defined.
Delivery Integrity™ is understood.
Implementation Failure™ is identifiable.
decision-making is distinguished from implementation.
required actions are specified.
actions are sufficiently precise.
complex decisions are decomposed.
composite implementation risk is assessed.
partial implementation is identified.
implementation coverage is measured.
critical actions are weighted appropriately.
CA1–CA5 classification operates.
action ownership is identifiable.
Unowned Actions™ are detected.
Ownership Diffusion™ is controlled.
accountable ownership is preserved.
ownership transfers are controlled.
Orphaned Actions™ are detected.
assignment is explicit.
assignment receipt is verified.
Silent Assignment Failure™ is prevented.
capability is assessed before assignment.
impossible assignments are identified.
resources are aligned with required action.
activity is distinguished from implementation.
Activity Substitution™ is detected.
Implementation Substitution™ is controlled.
substitute actions are assessed for equivalence.
unauthorised substitution is prevented.
Delivery Fidelity™ is assessed.
implementation drift is identified.
delivery standards are defined.
minimum delivery standards exist where appropriate.
procedural completion is distinguished from substantive completion.
completion evidence is required.
Evidence Sufficiency Test™ operates.
intention is distinguished from delivery.
Completion-by-Assertion™ is challenged.
Self-Certified Completion™ is risk-assessed.
claimed completion is distinguished from verified completion.
IC1–IC5 confidence classification operates.
IS1–IS6 status classification operates.
binary closure is avoided where inappropriate.
Premature Completion™ is detected.
premature closure alerts operate.
administrative completion is distinguished from substantive implementation.
closure evidence is retained.
closure authority is identified.
implementation delay is measured.
delay materiality is assessed.
ID1–ID5 delay classification operates.
Outcome-Defeating Delay™ is identified.
Time-to-Implementation™ is measured.
causes of delay are attributable.
deadline extensions are governed.
Silent Deadline Drift™ is identified.
implementation dependencies are mapped.
critical paths are understood.
external delivery dependencies are verified.
referrals are not automatically treated as completed interventions.
referral outcomes are tracked.
handoffs are controlled.
Handoff Failure™ is identified.
implementation is traceable.
Decision-to-Delivery Trace™ exists.
Implementation Provenance™ is preserved.
IG1–IG5 gap classification operates.
IF1–IF8 failure classification operates.
materiality is assessed.
outcome integrity is considered.
action is distinguished from outcome.
implementation effectiveness is tested where appropriate.
output is distinguished from outcome.
Symbolic Implementation™ is identified.
performative completion risk is considered.
Paper Implementation™ is tested against operational reality.
safeguarding implementation gaps are identifiable.
safeguarding delivery is verified.
user-experienced implementation is considered where appropriate.
Delivery Experience Gaps™ are assessed.
complaints can trigger implementation review.
recurring implementation gaps are escalated.
repeated recommendations are investigated.
Implementation Debt™ is measured.
ageing critical actions are visible.
backlogs are risk-ranked.
IP1–IP5 priority classification operates.
material implementation failure triggers escalation.
leadership can see critical gaps.
Hidden Implementation Failure™ is challenged.
dashboard reporting reflects materiality.
metric gaming risk is assessed.
claimed and verified completion are separated.
correction addresses root cause.
implementation root-cause analysis occurs.
consequences created by implementation failure are assessed.
decisions are reviewed where delay materially changes circumstances.
correction propagates downstream.
corrected implementation is retested.
verification independence is proportionate.
Delivery–Verification Separation™ operates where required.
verification failures are identifiable.
verification evidence is proportionate.
sustained implementation is assessed where necessary.
implementation regression is monitored.
sustainability is verified.
implementation resilience is tested.
implementation stress testing occurs.
Implementation Counterfactual™ is used.
Reality-of-Delivery Test™ operates.
Recipient Reality Test™ operates where appropriate.
Decision Survival Test™ operates.
implementation audit trails exist.
Implementation Action Register™ exists.
Implementation Gap Register™ exists.
Implementation Verification Register™ exists.
critical overdue actions are tracked.
substitutions are recorded.
Implementation Integrity Dashboard™ operates.
Verified Completion Rate™ is measured where appropriate.
False Completion Rate™ is monitored.
recurrence is measured.
governance reviews implementation.
independent challenge is possible.
material implementation gaps are transparent.
interim safeguards are used where necessary.
interim measures are reviewed.
Temporary-to-Permanent Drift™ is identified.
workaround dependency is assessed.
approval is followed through to delivery.
Decision-to-Delivery Accountability™ is maintained.
Accountability Breaks™ are detected.
Implementation Integrity Gate™ operates.
Assignment Gate™ operates.
Delivery Gate™ operates.
Completion Gate™ operates.
Verification Gate™ operates.
Reopening Gate™ operates.
And ultimately:
Can the institution prove—not merely assert—that what it decided should happen was actually delivered, to the required standard, within the required timeframe, and with sufficient evidence to justify treating the action as complete?
244. Framework Outcomes
Implementation establishes:
✓ Implementation Gap™
✓ Delivery Integrity™
✓ Implementation Failure™
✓ SAFECHAIN™ Implementation Integrity Architecture™
✓ Decision-to-Action Integrity™
✓ Decision Completion Fallacy™
✓ Action Specification™
✓ Action Precision Principle™
✓ Composite Implementation Risk™
✓ Partial Implementation™
✓ Partial Implementation Concealment™
✓ Implementation Coverage™
✓ Critical Action Weighting™
✓ CA1–CA5 Critical Action Classification™
✓ Action Ownership™
✓ Unowned Action™
✓ Ownership Diffusion™
✓ Orphaned Action™
✓ Assignment Integrity™
✓ Silent Assignment Failure™
✓ Capability-to-Deliver Test™
✓ Impossible Assignment™
✓ Unresourced Action™
✓ Activity–Implementation Distinction™
✓ Activity Substitution™
✓ Implementation Substitution™
✓ Delivery Fidelity™
✓ Minimum Delivery Standard™
✓ Procedural Completion–Substantive Completion Distinction™
✓ Completion Integrity Test™
✓ Evidence of Implementation™
✓ Completion-by-Assertion™
✓ Self-Certified Completion™
✓ IC1–IC5 Completion Confidence Classification™
✓ IS1–IS6 Completion Status Classification™
✓ Premature Completion™
✓ Administrative Completion™
✓ Implementation Delay™
✓ ID1–ID5 Delay Classification™
✓ Outcome-Defeating Delay™
✓ Time-to-Implementation™
✓ Silent Deadline Drift™
✓ Implementation Dependency Chain™
✓ Critical Path Integrity™
✓ External Delivery Verification™
✓ Referral Completion Fallacy™
✓ Implementation Handoff™
✓ Handoff Failure™
✓ Implementation Traceability™
✓ Decision-to-Delivery Trace™
✓ Implementation Provenance™
✓ IG1–IG5 Implementation Gap Classification™
✓ IF1–IF8 Implementation Failure Types™
✓ Implementation Effectiveness™
✓ Output–Outcome Distinction™
✓ Symbolic Implementation™
✓ Performative Completion Risk™
✓ Paper Implementation™
✓ Safeguarding Implementation Gap™
✓ Delivery Experience Gap™
✓ Repeated Recommendation Paradox™
✓ Implementation Debt™
✓ Implementation Debt Register™
✓ Risk-Based Implementation Priority™
✓ IP1–IP5 Implementation Priority Classification™
✓ Hidden Implementation Failure™
✓ Green Action-Plan Illusion™
✓ Implementation Correction™
✓ Implementation Root-Cause Analysis™
✓ Consequence Correction™
✓ Implementation Retest™
✓ Delivery–Verification Separation™
✓ Verification Failure™
✓ Sustained Implementation™
✓ Implementation Regression™
✓ Implementation Resilience™
✓ Implementation Stress Test™
✓ Implementation Counterfactual™
✓ Reality-of-Delivery Test™
✓ Recipient Reality Test™
✓ Decision Survival Test™
✓ Implementation Audit Trail™
✓ Implementation Action Register™
✓ Implementation Gap Register™
✓ Implementation Verification Register™
✓ Overdue Critical Action Register™
✓ Substitution Register™
✓ SAFECHAIN™ Implementation Integrity Dashboard™
✓ Verified Completion Rate™
✓ False Completion Rate™
✓ Implementation Recurrence Rate™
✓ Implementation Challenge Function™
✓ Interim Safeguard™
✓ Temporary-to-Permanent Drift™
✓ Workaround Dependency™
✓ Decision-to-Delivery Accountability™
✓ Implementation Accountability Chain™
✓ Accountability Break™
✓ Implementation Integrity Gate™
✓ Assignment Gate™
✓ Delivery Gate™
✓ Completion Gate™
✓ Verification Gate™
✓ Reopening Gate™
✓ IMPLEMENTATIONGAP-001™ Integrity Test™
245. Cross-Framework Integration
IMPLEMENTATIONGAP-001™ should operate alongside:
DECISION-001™ — integrity of the originating decision.
REASONING-001™ — preservation of the reasoning supporting that decision.
DECISIONDRIFT-001™ — preservation of decision meaning during transmission and implementation.
REVIEW-001™ — reassessment where failed implementation changes circumstances.
ASSURANCEGAP-001™ — testing declared implementation against operational evidence.
ACCESSFAILURE-001™ — determining whether delivered actions are practically accessible.
SAFEGUARDCAPACITY-001™ — determining whether sufficient capability exists to implement safeguards.
ESCALATION-001™ — escalation of material implementation failure.
CONTINUITY-001™ — preservation of implementation ownership across transitions.
CUMULATIVEHARM-001™ — assessment of accumulated consequences of repeated implementation failure.
RECURRINGFAILURE-001™ — structural response where implementation failure recurs.
DEPENDENCYRISK-001™ — risks created where implementation depends upon fragile institutional relationships.
INTERFACE-001™ — implementation failure at institutional interfaces.
FLOW-001™ — preservation of action through workflows.
SYSTEMCHECK-001™ — testing whether implemented changes function systemically.
RESILIENCE-001™ — sustainability under disruption.
FEEDBACK-001™ — feedback capable of challenging implementation claims.
REMEDIATION-001™ — implementation of corrective action.
VALIDATION-001™ — validation of material implementation claims.
METRICS-001™ — meaningful measurement of delivery.
ACCOUNTABILITY-001™ — continuous ownership and accountability.
246. Framework Statement
Institutions frequently devote considerable attention to making decisions, accepting recommendations, approving safeguards and producing action plans. But institutional integrity is ultimately tested by what happens next. A decision that is never implemented cannot protect anyone. A recommendation that is repeatedly accepted but never delivered cannot produce reform. A safeguard recorded as complete without reaching the person it was intended to protect cannot be treated as effective. And an action plan filled with green statuses cannot demonstrate improvement unless those statuses are supported by evidence of operational change. IMPLEMENTATIONGAP-001™ establishes the SAFECHAIN™ architecture for tracing decisions into action, converting requirements into accountable assignments, distinguishing activity from implementation, detecting partial, delayed, substituted and unverified delivery, preventing premature closure, correcting implementation failure and verifying that what an institution decided should happen actually happened in practice.
247. Copyright & Intellectual Property Notice
© 2026 Samantha Avril-Andreassen. All Rights Reserved.
IMPLEMENTATIONGAP-001™ — The SAFECHAIN™ Decision-to-Action, Implementation Failure & Delivery Integrity Framework™ is an original institutional-governance, implementation-integrity, operational-accountability, safeguarding, assurance and systems-reform framework developed and authored by Samantha Avril-Andreassen, LLB (Hons), LLM, LPC, FRSA, Founder of SAFECHAIN™.
IMPLEMENTATIONGAP-001™ forms part of the SAFECHAIN™ Justice & Institutional Integrity Series™ and wider SAFECHAIN™ Governance Architecture™.
The original expression, selection, arrangement and combination of the framework's architecture, terminology, classifications, tests, registers, implementation controls, accountability mechanisms, verification methodology and governance gates constitute proprietary intellectual property to the extent protected by applicable law.
Protected elements include, where original to the framework, Implementation Gap™, Delivery Integrity™, SAFECHAIN™ Implementation Integrity Architecture™, Decision-to-Action Integrity™, Decision Completion Fallacy™, Action Precision Principle™, Composite Implementation Risk™, Partial Implementation Concealment™, Implementation Coverage™, Critical Action Weighting™, Unowned Action™, Ownership Diffusion™, Orphaned Action™, Silent Assignment Failure™, Activity Substitution™, Implementation Substitution™, Delivery Fidelity™, Minimum Delivery Standard™, Procedural Completion–Substantive Completion Distinction™, Completion-by-Assertion™, Completion Confidence Classification™, Completion Status Integrity™, Premature Completion™, Administrative Completion Fallacy™, Outcome-Defeating Delay™, Silent Deadline Drift™, Implementation Dependency Chain™, Referral Completion Fallacy™, Implementation Handoff™, Implementation Traceability™, Decision-to-Delivery Trace™, Implementation Provenance™, Implementation Gap Classification™, Implementation Failure Types™, Symbolic Implementation™, Paper Implementation™, Safeguarding Implementation Gap™, Delivery Experience Gap™, Repeated Recommendation Paradox™, Implementation Debt™, Risk-Based Implementation Priority™, Hidden Implementation Failure™, Green Action-Plan Illusion™, Implementation Correction™, Implementation Root-Cause Analysis™, Implementation Retest™, Delivery–Verification Separation™, Sustained Implementation™, Implementation Regression™, Implementation Counterfactual™, Reality-of-Delivery Test™, Recipient Reality Test™, Implementation Action Register™, Implementation Gap Register™, Implementation Verification Register™, SAFECHAIN™ Implementation Integrity Dashboard™, Verified Completion Rate™, False Completion Rate™, Implementation Recurrence Rate™, Temporary-to-Permanent Drift™, Decision-to-Delivery Accountability™, Implementation Accountability Chain™, Implementation Integrity Gate™, Assignment Gate™, Delivery Gate™, Completion Gate™, Verification Gate™, Reopening Gate™ and IMPLEMENTATIONGAP-001™ Integrity Test™, together with associated implementation materials.
No part of this framework may be reproduced, republished, substantially adapted, distributed, commercially exploited or incorporated into another proprietary governance, safeguarding, assurance, audit, implementation, remediation, accreditation, certification, consultancy, artificial-intelligence, analytics, training or software methodology without prior written permission from the applicable rights holder, except as permitted by applicable law.
Publication or citation does not transfer ownership of SAFECHAIN™ intellectual property or confer authority to issue SAFECHAIN™ assessments, classifications, certifications, accreditations, validations or institutional findings.
References to generally established concepts concerning implementation, action planning, project delivery, operational management, assurance, auditing, accountability, safeguarding, monitoring, evaluation and governance do not constitute claims of ownership over those underlying concepts. Proprietary claims relate to original SAFECHAIN™ expression, terminology, architecture, selection, arrangement and methodology to the extent protected by applicable law.
IMPLEMENTATIONGAP-001™ is an analytical and governance framework. Identification of an implementation gap does not itself establish legal liability, negligence, regulatory breach, professional misconduct, safeguarding breach or other unlawful conduct. Any such conclusion requires assessment under the applicable legal, regulatory, contractual or professional framework and relevant evidence.
Author and Framework Developer:
Samantha Avril-Andreassen, LLB (Hons), LLM, LPC, FRSA
Founder — SAFECHAIN™
Framework Reference: IMPLEMENTATIONGAP-001™
Version: 1.0
Year: 2026
© 2026 Samantha Avril-Andreassen. All Rights Reserved.