1. What This Criterion Is For
Supervision & Oversight assesses whether a control is supported, visible, and guided by someone in a position to intervene, reinforce, or improve it.
In abuse prevention, the presence of a control is never enough. Controls become fragile when no one is responsible for monitoring how they’re used, ensuring they’re followed, or coaching people when they drift.
This criterion helps teams identify whether:
- A control is being monitored in real time
- There is structured support for its application
- There is accountability for its quality or outcome
2. How to Use It
Use the Supervision & Oversight criterion when:
- Reviewing a control that is inconsistently applied or drifting over time
- Exploring near misses or unexpected outcomes
- Designing new controls that require real-time visibility or reinforcement
This criterion often reveals where a control is functionally unmonitored, or where there is no mechanism to catch deviation until something goes wrong.
3. Examples Across Controls
| Control Type | Examples of Supervision & Oversight |
|---|---|
| Behaviors | Are staff conduct and boundary practices observed, reinforced, and supported? |
| Training | Is training quality reviewed? Are staff supported to integrate learning into daily practice? |
| Security | Are access controls or technology systems actively monitored? Is someone checking logs? |
| Events | Is there clear leadership, zone supervision, or mobile oversight during high-risk moments? |
| Intake | Are application decisions or screening outcomes reviewed or double-checked? |
| Reporting | Is someone responsible for reviewing incoming reports and following through? |
4. What Strong, Fragile, and Failing Look Like
| Level | Indicators |
| Strong | Oversight exists, but it is inconsistently practiced or relies heavily on a single individual. Corrections may happen only after something goes wrong. |
| Fragile | Oversight exists but is inconsistently practiced or relies heavily on one individual. Corrections may happen only after something goes wrong. |
| Failing | No one monitors the control. It is left to individual discretion. Gaps are only noticed during crises or audits. |
5. Common Pitfalls
- Assuming oversight is happening because someone is “in charge”
- No distinction between presence and engagement (e.g., second adult present but inattentive)
- Overloading one person with supervisory roles
- Failure to define what supervision looks like across different programs or settings
6. Design Prompts
When designing or reviewing a control:
- Who is responsible for supporting or monitoring this in real time?
- Is that role visible to others?
- Do they have the skills, authority, and time to do it?
- What happens if someone starts drifting or missing the mark?
- Is there a way to observe patterns over time (not just one-off issues)?
Supervision & Oversight is often assumed rather than built. A control may appear complete, but if no one is watching, guiding, or learning from how it operates, it is likely to degrade over time.