Do No Harm Protocol

Plantillas de prompts de IA

Copie un prompt en Claude, ChatGPT o Gemini. Pegue su documento al final y ejecute.

Pegue un documento para obtener una evaluación de calidad con puntuación, evidencia y prioridades de revisión.

5,839 caracteres
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 will provide 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
- Score 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.
- Score 4: At least three risk types considered. Participant-side coverage strong; team-side or community-side risks partial.
- Score 3: Two risk types addressed (commonly physical and psychological). Social or economic risks absent.
- Score 2: One risk type addressed in detail; others not named.
- Score 1: No risk identification across types.

DIMENSION 2: Context-Specific Risks
- Score 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.
- Score 4: At least three context elements addressed. Conflict, marginalization, or surveillance considered; local actor mapping or identity-specific risks partial.
- Score 3: Context referenced but risks remain generic. Local actors not named.
- Score 2: Context mentioned in passing. No risk implications drawn.
- Score 1: No context-specific risk consideration.

DIMENSION 3: Mitigation Specificity
- Score 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.
- Score 4: At least four elements present. Mitigation specific and matched to risk; responsibility assignment or feasibility partial.
- Score 3: Generic mitigation language. Some risks have a concrete step; others have a principle.
- Score 2: Mitigation listed as a principle ("we will minimize harm"). No concrete steps tied to risks.
- Score 1: No mitigation specified.

DIMENSION 4: Escalation and Response
- Score 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.
- Score 4: At least four elements present. Escalation paths and immediate response clear; reporting channel or documentation partial.
- Score 3: Escalation mentioned but timelines or contacts unclear. Immediate response not specified.
- Score 2: General "report incidents to manager" language. No timelines, no immediate response, no confidential channel.
- Score 1: No escalation or response procedures.

DIMENSION 5: Monitoring of Risks
- Score 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.
- Score 4: At least four elements present. Scheduled re-assessment and triggers in place; role assignment or documentation partial.
- Score 3: Risk monitoring stated as intention. No schedule, no triggers, no named role.
- Score 2: Risk treated as a one-time design step. No monitoring through implementation.
- Score 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:
[Paste your do-no-harm protocol here]

Scoring Criteria

Risk Identification Breadth
5Excellent

Physical, psychological, social, and economic risks all considered. Participants, communities, and teams treated separately.

4Good

At least three risk types. Participant coverage strong; team or community partial.

3Adequate

Two risk types addressed. Social or economic absent.

2Needs Improvement

One risk type addressed. Others not named.

1Inadequate

No risk identification across types.

Context-Specific Risks
5Excellent

Context-specific risks named with specificity. Local actors identified. Identity-specific risks addressed.

4Good

At least three context elements. Conflict, marginalization, or surveillance covered; local actors or identity risks partial.

3Adequate

Context referenced but risks remain generic.

2Needs Improvement

Context mentioned in passing. No risk implications drawn.

1Inadequate

No context-specific risk consideration.

Mitigation Specificity
5Excellent

Each risk has a concrete mitigation step. Severity matched. Preventive and reactive measures present. Responsibility assigned. Feasible.

4Good

At least four elements. Mitigation specific; responsibility or feasibility partial.

3Adequate

Generic mitigation language. Some risks concrete; others principle-only.

2Needs Improvement

Mitigation listed as principle. No concrete steps.

1Inadequate

No mitigation specified.

Escalation and Response
5Excellent

Incident categories defined. Escalation steps with timelines. Immediate response specified. Confidential channel exists. Documentation required.

4Good

At least four elements. Escalation and immediate response clear; channel or documentation partial.

3Adequate

Escalation mentioned but timelines or contacts unclear.

2Needs Improvement

General report-to-manager language only. No timelines or immediate response.

1Inadequate

No escalation or response procedures.

Monitoring of Risks
5Excellent

Re-assessment scheduled. Triggers named. Role assigned. Feedback loop in place. Documented.

4Good

At least four elements. Scheduled re-assessment and triggers; role or documentation partial.

3Adequate

Monitoring stated as intention. No schedule or named role.

2Needs Improvement

Risk treated as one-time design step.

1Inadequate

No risk monitoring.

Score Interpretation

Total (out of 25)BandNext Step
22-25StrongDo-no-harm protocol is robust. Use as-is or with minor refinements before fielding.
17-21AdequateAddress flagged dimensions before fielding. Most likely fix: tighten mitigation specificity and add a risk monitoring schedule.
11-16Needs RevisionSubstantial revision required. Use the Revise prompt to identify and fix protocol gaps before any participant contact.
5-10Substantial RevisionProtocol fails the threshold for sensitive, conflict-affected, or vulnerable-population work. Rebuild with risk identification breadth and mitigation specificity as the foundation.