Summary
A fictional two-day stakeholder workshop on community safety coordination, attended by 34 participants across six sessions. This document records what was discussed, what was decided and what each party agreed to do. Names below are role descriptions rather than individuals.
| Title | Coordinating community safety responses at ward level |
|---|---|
| Dates | Two days |
| Participants | 34 across local administration, civil society, service providers and community representatives |
| Purpose | Agree a coordination mechanism and assign responsibilities |
| Prepared by | Rapporteur |
1. Opening and objectives
The convenor set out three objectives: to establish where responsibilities currently overlap, to agree a single coordination point, and to leave with assigned actions rather than a general commitment to cooperate. Participants were asked to raise disagreements in the room rather than afterwards.
2. Session summaries
Session 1: Mapping current responsibilities
Participants mapped who currently responds to which categories of safety concern. Three areas of overlap were identified where two or more bodies believed they held the lead. One area was identified where participants concluded nobody currently held it. The exercise took longer than scheduled and ran into the following session.
Session 2: Information sharing
Discussion centred on what information could be shared between parties and under what conditions. Several participants raised concerns about sharing anything containing personal details without a written basis. The session did not resolve this and it was carried forward as an action rather than recorded as agreement.
Session 3: Reporting routes for residents
Participants agreed that residents face too many separate reporting routes and that this suppresses reporting. Two options were debated: a single intake point, or a shared referral protocol between existing routes. The second was preferred on the grounds that it required no new structure.
Session 4: Resourcing
No new resources were identified. Participants agreed that the coordination mechanism must operate within existing commitments, and that any proposal requiring new funding would need to be developed separately.
Session 5: Drafting the coordination arrangement
A working text was drafted covering membership, meeting frequency, the standing agenda and how matters escalate. Two clauses were left in square brackets for later resolution, both relating to information sharing.
Session 6: Closing and action review
The draft actions were read back and confirmed by the parties named against them. Two were amended during this reading, which is the point of doing it.
3. Decisions
| Ref | Decision | Status |
|---|---|---|
| D1 | A ward-level coordination forum will be established, meeting monthly | Agreed |
| D2 | The forum will operate within existing resources | Agreed |
| D3 | A shared referral protocol is preferred over a single intake point | Agreed in principle |
| D4 | Information sharing involving personal data requires a written basis before any exchange | Agreed |
| D5 | Chairing arrangements for the forum | Not resolved, carried to A5 |
Recording a decision as unresolved is as important as recording agreement. A report that shows consensus where there was none creates a dispute later.
4. Action points
| Ref | Action | Owner | Due |
|---|---|---|---|
| A1 | Circulate the draft coordination text with bracketed clauses marked | Convenor | Week 1 |
| A2 | Seek written advice on the basis for sharing personal data | Legal focal point | Week 3 |
| A3 | Draft the referral protocol covering the three overlap areas | Working group of three members | Week 4 |
| A4 | Confirm which body takes the unassigned responsibility area | Local administration lead | Week 2 |
| A5 | Propose chairing arrangements for decision at the first meeting | Convenor | Week 3 |
| A6 | Confirm the date and venue of the first monthly meeting | Secretariat | Week 1 |
5. Matters carried forward
- The legal basis for information sharing, which blocks two clauses of the draft text.
- Chairing arrangements, deferred to the first meeting.
- Any proposal requiring new funding, to be developed outside this forum.
6. What a client receives
For a real assignment this would be delivered alongside the participant list as supplied by the organiser, the agenda as actually run including any departures from it, and the action table as a separate editable file so it can be tracked between meetings.