You are an expert in research ethics and do-no-harm protocol design. Draft a do-no-harm risk identification and mitigation protocol for "program or activity name" (from the material, if given) involving "population" (from the material, if given) in "context" (from the material, if given) using "data collection methods" (from the material, if given).
CONTEXT SENSITIVITIES TO ADDRESS: "context sensitivities" (from the material, if given)
Draft Requirements:
- Risk identification breadth. Identify physical, psychological, social, and economic risks separately for participants, communities, and data collection teams. Do not default to a single risk type.
- Context-specific risks. Name risks particular to the operating context (conflict, marginalization, surveillance, displacement) rather than relying on generic risk language.
- Mitigation specificity. For each identified risk, name a concrete mitigation step so the protocol is operationally usable.
- Escalation and response. Specify procedures for incident response and escalation, including who is contacted, on what timeline, and what immediate action is taken.
- Monitoring of risks. Build risk re-assessment into the activity timeline so emerging or changing risks are caught during implementation, not only at design.
Output Format:
Produce:
- A 1-paragraph context statement summarizing the activity and the highest-stakes risk categories.
- A risk register table: risk ID, risk type (physical/psychological/social/economic), affected party (participants/community/team), description, likelihood, severity, mitigation step, monitoring trigger, responsible person.
- An escalation and response protocol with named roles, contact procedures, and timelines for each incident type.
- A risk monitoring schedule tied to the activity timeline (pre-deployment, weekly during data collection, post-collection debrief).
- A 'stop-collection' decision rule identifying the conditions under which data collection is suspended.
Quality bar: The result must meet these criteria. It will be reviewed against them afterwards.
- Risk Identification Breadth: Whether physical, psychological, social, and economic risks are all considered rather than the protocol defaulting to a single risk type.
- Context-Specific Risks: Whether risks particular to the operating context (conflict, marginalization, surveillance, displacement) are named rather than left at the level of generic risk language.
- Mitigation Specificity: Whether a concrete mitigation step is named for each identified risk so that the protocol is operationally usable, not just a list of concerns.
- Escalation and Response: Whether procedures for incident response and escalation are specified, including who is contacted, on what timeline, and what immediate action is taken.
- Monitoring of Risks: Whether risk re-assessment is built into the activity timeline so that emerging or changing risks are caught during implementation, not only at design.
Where the material is silent, write "Not in the material" rather than guessing.
Source material: Attached, or pasted below. Base everything above on it and do not invent details that are not in it.