You are an expert in research ethics and do-no-harm protocol design. Score the do-no-harm or risk identification and mitigation protocol I have attached or pasted using the rubric below. The document may be a standalone safeguarding protocol or a do-no-harm section embedded in a methodology, inception report, or MEL plan.
SCORING RUBRIC - Do No Harm Protocol
Score each dimension 1-5 using these criteria:
DIMENSION 1: Risk Identification Breadth
| 5 | All four risk types are considered. Physical risks named (injury, exposure to violence, transport hazards, communicable disease, exhaustion). Psychological risks named (re-traumatization, distress from sensitive topics, stigma triggered by participation). Social risks named (community backlash, family conflict, loss of standing, retaliation from authorities or armed actors). Economic risks named (opportunity cost of time, loss of livelihood access, perceived favoritism that affects future aid). Risks named separately for participants, communities, and data collection teams. |
|---|---|
| 4 | At least three risk types considered. Participant-side coverage strong; team-side or community-side risks partial. |
| 3 | Two risk types addressed (commonly physical and psychological). Social or economic risks absent. |
| 2 | One risk type addressed in detail; others not named. |
| 1 | No risk identification across types. |
DIMENSION 2: Context-Specific Risks
| 5 | Risks particular to the operating context are named with specificity (active conflict, post-conflict transition, surveillance environments, refugee or IDP contexts, gender-based violence settings, repressive political environments, contested ethnic or religious settings). The protocol names how each context-specific risk applies to this activity. Local actors and dynamics that elevate risk are identified (armed groups, hostile authorities, gatekeepers, dominant clan or caste structures). Risks specific to marginalized identities in this context are addressed. |
|---|---|
| 4 | At least three context elements addressed. Conflict, marginalization, or surveillance considered; local actor mapping or identity-specific risks partial. |
| 3 | Context referenced but risks remain generic. Local actors not named. |
| 2 | Context mentioned in passing. No risk implications drawn. |
| 1 | No context-specific risk consideration. |
DIMENSION 3: Mitigation Specificity
| 5 | Each identified risk has a named mitigation step that is concrete and operational (not a principle). Mitigation is matched to risk severity and likelihood (greater risk receives stronger mitigation). Mitigation includes preventive measures (interviewer matching, neutral location, omission of high-risk questions) and reactive measures (referral pathway, support contact, withdrawal). Mitigation responsibilities are named (who does what). Mitigation steps are feasible given the team, budget, and context. |
|---|---|
| 4 | At least four elements present. Mitigation specific and matched to risk; responsibility assignment or feasibility partial. |
| 3 | Generic mitigation language. Some risks have a concrete step; others have a principle. |
| 2 | Mitigation listed as a principle ("we will minimize harm"). No concrete steps tied to risks. |
| 1 | No mitigation specified. |
DIMENSION 4: Escalation and Response
| 5 | Incident categories are defined (what counts as a safeguarding incident, a security incident, a participant distress event). For each category, escalation steps are specified (who is contacted, on what timeline, by what channel). Immediate-response steps are specified (what the team does in the first hour, before escalation completes). A confidential reporting channel exists (so that team members and participants can raise concerns without retaliation). Documentation of incidents is required, with named responsibility for follow-up. |
|---|---|
| 4 | At least four elements present. Escalation paths and immediate response clear; reporting channel or documentation partial. |
| 3 | Escalation mentioned but timelines or contacts unclear. Immediate response not specified. |
| 2 | General "report incidents to manager" language. No timelines, no immediate response, no confidential channel. |
| 1 | No escalation or response procedures. |
DIMENSION 5: Monitoring of Risks
| 5 | Risk re-assessment is scheduled at named points in the activity timeline (pre-fielding security check, mid-activity review, after-incident review, post-activity debrief). Triggers for ad-hoc re-assessment are named (security incident, contextual change, participant complaint). The team has a named role responsible for risk monitoring through the activity. Findings from re-assessment feed back into the protocol (the protocol is updated, not just reviewed). Risk monitoring is documented. |
|---|---|
| 4 | At least four elements present. Scheduled re-assessment and triggers in place; role assignment or documentation partial. |
| 3 | Risk monitoring stated as intention. No schedule, no triggers, no named role. |
| 2 | Risk treated as a one-time design step. No monitoring through implementation. |
| 1 | No risk monitoring. |
OUTPUT FORMAT:
Return your assessment as a table followed by a summary:
| Dimension | Score (1-5) | Evidence | Priority Revision |
|---|---|---|---|
| Risk Identification Breadth | |||
| Context-Specific Risks | |||
| Mitigation Specificity | |||
| Escalation and Response | |||
| Monitoring of Risks |
Total: X/25 Band: Strong (22-25) / Adequate (17-21) / Needs Revision (11-16) / Substantial Revision (5-10) Single Most Important Revision: [One specific sentence]
For any dimension scored 1 or 2, add a brief explanation and a concrete revision example.
PROTOCOL TO SCORE:
(See the attached or pasted document.)
Document to review: Attached, or pasted below. Base everything above on it and do not invent details that are not in it.