We hire a protection team and let everyone else off the hook. Safety and dignity are not one department’s specialism. They are a thread that runs through every distribution, every clinic, every line we make people stand in.
Most organisations now have protection on the org chart somewhere. There is a specialist, a team, perhaps a whole unit, and they hold real expertise that matters. But watch how the rest of the organisation behaves around them, and a quiet abdication appears. The logistics team treats the safety of a distribution as the protection team’s concern. The health team designs a clinic without asking who might be put at risk by where the queue forms. The water engineer places a tap without considering the walk to reach it after dark. Each assumes that keeping people safe is the job of the people with protection in their title. We have turned a thread that should run through all of our work into a box that belongs to a few.
This is not the same conversation as safeguarding our own conduct, important as that is. This is about whether the way we deliver aid, in its everyday design, keeps people safe from harm and treats them with dignity, or quietly exposes them to risk. A food distribution can feed people and endanger them at the same time, if the route to it is unsafe or the wait humiliating. A registration process can record people and expose them, if the data is held carelessly. Protection in this sense is not a service we deliver alongside the others. It is a quality every service either has or lacks, and it depends on everyone who designs and runs the work.
The honest cause is that specialisation, which serves us well in most things, works against us here. When we create a dedicated unit for something, the rest of the organisation reasonably concludes the something is now handled, and stops holding it. The very act of building expertise in one place relieves every other place of the duty to think about it. There is a second reason, rooted in how we plan and measure. The technical sectors, food, water, health, shelter, each have their own targets and their own definition of a job well done, and protection rarely appears inside those definitions. So a team can hit every target it owns and still have designed a service that exposes people to harm, because the harm was nobody’s indicator. What sits between the sectors, as protection does, belongs to no one’s scorecard and slips through.
The cost is paid by the people least able to absorb it. A response that delivers its goods but ignores the safety and dignity of how it delivers them can leave people worse off than before, exposed at the distribution point, endangered on the journey, or put at risk by the information we collected. We counted the aid we provided. We did not count the harm the manner of providing it created, because that harm lived between our departments where no measure could see it.
The fix is to make protection a thread that runs through all of our work rather than a unit that holds it alone. The specialist expertise still matters. The point is that it should inform every team’s choices, not absolve every team of the duty to make safe ones.
Make safety and dignity a question every team asks of its own work. When designing any service, the team running it should ask how the way they deliver it could expose people to harm, and adjust accordingly. The specialist helps them ask the question well. They do not get to ask it instead of the team. A thread is woven by everyone or it is not woven at all.
Put the specialists upstream, in the design, not downstream, in the cleanup. A protection team consulted after a distribution goes wrong is being used as a repair crew. The same expertise placed at the design stage prevents the harm rather than documenting it.
Build protection into the measures each sector owns. As long as a team’s definition of success leaves out the safety and dignity of how it works, that part will keep falling between the cracks. Folding a simple test of do no harm into each sector’s standards makes protection part of doing the job well, rather than a concern competing with the job.
Name protection as a shared duty, with funders alongside. Part of why it sits in a silo is that it is funded as a separate specialism rather than a quality of all programming. Making the case to funders that it belongs inside every sector helps move it from a box a few people own to a thread everyone carries.
A food distribution can feed people and endanger them at the same time. Protection is not what one team delivers. It is a quality every service either has or lacks.
None of this diminishes the specialists or pretends protection expertise is something anyone can improvise. It asks only that the expertise inform everyone rather than excuse everyone. The measure of protection is not whether we have a unit for it. It is whether the engineer placing the tap and the clerk recording the name each made a choice that kept people safe, and that is a thread we can begin weaving now.