1. What This Criterion Is For
Ownership assesses whether the people responsible for using or supporting a control see it as their responsibility and act accordingly.
Controls often fail not because they are unclear or unsupported, but because the people involved do not believe it is their role to follow through. Ownership gives a control its traction — it turns expectations into action.
This criterion addresses:
- Whether responsibility is clearly assigned and accepted
- Whether people feel connected to the purpose of the control
- Whether follow-through is internalized, not just monitored
2. How to Use It
Use the Ownership criterion when:
- A control is not being consistently applied despite training and awareness
- Staff describe safeguarding responsibilities as someone else’s domain
- There’s a gap between intention and execution, especially at individual or team level
Ownership is particularly important for controls that depend on initiative, relational judgment, or frontline vigilance.
3. Examples Across Controls
| Control Type | Example of How Ownership Applies |
|---|---|
| Behavior Expectations | Do staff feel personally accountable for maintaining boundaries and setting tone? |
| Intake | Do staff see screening and onboarding as part of their role in prevention, or just HR’s job? |
| Incident Response | Are individuals prepared to initiate a response, or do they wait for someone else to act? |
| Record-Keeping | Do staff complete documentation because they believe it matters, not just because it’s required? |
| Team Mandate | Do leaders take visible responsibility for the success of risk-related controls in their area? |
4. What Strong, Fragile, and Failing Look Like
| Level | Indicators |
|---|---|
| Strong | People speak about the control as part of their role. They act proactively. Ownership is culturally supported and modeled. |
| Fragile | Some staff own the control, but others defer. People may say “it depends” or wait for direction. |
| Failing | No one claims responsibility. The control is ignored or left incomplete. Follow-up only happens when externally triggered. |
5. Common Pitfalls
- Assuming role = responsibility (without buy-in or modeling)
- Delegating ownership without clarity or reinforcement
- Undermining ownership through punitive culture or unclear expectations
- Fragmented systems where multiple people assume someone else is responsible
6. Design Prompts
When designing or reviewing a control:
- Who feels responsible for this control being carried out well?
- Is that person (or team) clear, visible, and supported?
- Does the organization’s culture encourage ownership — or avoidance?
- Are consequences (positive or negative) aligned with ownership behavior?
- How do new team members come to understand their role in this control?
Ownership turns systems from something imposed into something lived. When people internalize their role in protection, the system gains strength, flexibility, and resilience from within.