Skip to content
Back to skills

Youth Work Incident Report

ASecurity

Respond to, record and learn from incidents involving young people and their communities in youth centres, schools and outreach settings. TRIGGERS - Use when a youth worker needs a incident reporting & response for young people and their communities in youth centres, schools and outreach settings.

  • 38 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 12, 2026
businessgorailsdocumentation

Works with

  • cli

Security analysis

A100/100

Scanned November 12, 2026

npx -y skills add lionelsimai/claude-skills-collection --skill youth-work-incident-report --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Youth Work Incident Report?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Youth Work Incident Report
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lionelsimai-youth-work-incident-report/badge)](https://www.skillsdirectory.com/skills/lionelsimai-youth-work-incident-report)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: youth-work-incident-report
description: |
  Respond to, record and learn from incidents involving young people and their communities in youth centres, schools and outreach settings.
  TRIGGERS - Use when a youth worker needs a incident reporting & response for young people and their communities in youth centres, schools and outreach settings.
category: Youth Work
license: MIT
version: 1.0
---
# Incident Reporting & Response — Youth Work

Respond to, record and learn from incidents involving young people and their communities in youth centres, schools and outreach settings. The deliverable is a factual incident report and a lessons-learned action list.
This skill is written for a youth worker working with young people and their communities in youth centres, schools and outreach settings.

## When to use
- You are a youth worker preparing, delivering or reviewing this part of your work in youth centres, schools and outreach settings.
- You need a defensible, repeatable approach that produces a factual incident report and a lessons-learned action list.
- A colleague, auditor or client asks how this was done and what evidence supports it.

## Key Concepts
| Term | Meaning |
|------|---------|
| Detached work | youth work delivered on streets and in public spaces |
| Outcome star | a visual tool tracking a young person's progress |
| Participation | young people's active involvement in decisions |

## Workflow
1. **Step 1** - Make the situation safe first; attend to people before paperwork, and escalate if safeguarding disclosures missed is still live
2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in session plans
3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in youth centres, schools and outreach settings
4. **Step 4** - Support those affected, including honest communication with young people and their communities about what happened and what happens next
5. **Step 5** - Analyse causes without blame, agree preventive actions with owners and dates, and track them to closure

## Profession-Specific Components
| Component | Details for Youth Work |
|-----------|-------------------------------|
| Core documentation | session plans; project records; safeguarding logs; outcome stars |
| Core tools & equipment | engagement tools; activity equipment; communication apps; recording systems |
| People involved | young people and their communities; the youth worker; colleagues and other services in youth centres, schools and outreach settings |
| Primary record | session plans — keep it current, dated and attributable |

## Output Format
**Context:** [Situation in youth centres, schools and outreach settings] | **Objective:** [What this must achieve] | **Audience:** [young people and their communities and other stakeholders]

The finished output is a factual incident report and a lessons-learned action list, structured as:
1. Summary of position and evidence
2. Detail, following the workflow above
3. Decisions, actions, owners and dates
4. Review point and escalation route

### Action Plan
1. **Immediate:** Confirm scope, consent and the evidence available in session plans.
2. **Short-term:** Complete the workflow steps and record outcomes against attendance and engagement.
3. **Medium-term:** Review results, close actions, and update local procedures in youth centres, schools and outreach settings.

## Success Metrics
| Metric | Target | Method |
|--------|--------|--------|
| attendance and engagement | Agree a local target and track the trend | Measured from session plans and reviewed on a set cycle |
| outcome progress | Agree a local target and track the trend | Measured from session plans and reviewed on a set cycle |
| young people's feedback | Agree a local target and track the trend | Measured from session plans and reviewed on a set cycle |
| session delivery rates | Agree a local target and track the trend | Measured from session plans and reviewed on a set cycle |

## Guardrails & Quality Checks
- Never let this happen: safeguarding disclosures missed.
- Never let this happen: unsafe activities.
- Never let this happen: young people disengaging.
- Work only within the competence and authority of a youth worker; escalate or refer anything beyond it.
- Record facts and observations, not speculation, and keep records confidential to youth centres, schools and outreach settings's rules.
- Verify names, dates, figures and measurements twice before anything is issued or signed off.
- Use only real, verified information from the case in hand — never invent results, credentials or evidence.

## Example (illustrative)
A youth worker in youth centres, schools and outreach settings applies this workflow for young people and their communities: they open
session plans, work through the five steps using engagement tools, and close by recording
the outcome against attendance and engagement and agreeing the next review date. (Illustrative example only —
replace with the real details of the case in hand.)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in business →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.