Do Not Release a Child Without a Written Handover Protocol

Why child handover should be treated as a safeguarding decision

An NGO that works with children should never treat the release of a child as a casual administrative step. Whether the organisation runs a school, shelter, sports camp, child sponsorship programme, residential facility, rescue project, disability programme, religious activity or community learning centre, the moment it receives a child into its care it assumes a serious responsibility. That responsibility does not end well if a child is released to the wrong person, even where the staff member acted in good faith.

The recent High Court decision in Ruzindantaro v The School Management Committee Bishop Asili Memorial Nursery & Primary School, Civil Suit 36 of 2022, [2025] UGHC 409, reported on ULII with a judgment date of 11 June 2025, gives the issue real weight. The reported summary states that a school released a minor to a third person without parental consent, that the parent’s constitutional rights were violated, that the separation lasted five years, that emotional trauma resulted and that general damages were awarded. The case was about a school, but its lesson appears wider. Many NGOs work in spaces where children are received, transported, hosted, mentored, trained, sheltered or referred. In those settings, a child handover is not just logistics. It is a legal and safeguarding risk point.

In loco parentis does not erase the parent or guardian

When a school or child facing NGO has temporary responsibility for a child, it may be acting in loco parentis. That phrase can sound broad, and sometimes staff may assume it gives the organisation room to make quick decisions. It does not cancel the authority of a parent, lawful guardian or competent authority. The organisation may supervise the child for a period, but it does not acquire an open discretion to decide who should receive the child at the end of the day, at the gate, at a shelter, after a camp or during a referral.

This distinction matters in everyday situations. A relative may arrive and say the parent has agreed. A religious leader may insist that the child should be released for a family event. A community elder may claim to be resolving a domestic matter. A donor, sponsor or local official may appear influential. None of these facts should replace direct verification. The safest approach is to ask a simple question before release. Who legally authorised this handover, and can we prove it?

Written records matter more than staff memory

In a dispute, staff memory is rarely enough. People may remember events differently. A phone call may be denied. A rushed conversation at a gate may later become a contested story. If a complaint arises, the NGO will need documents showing who was authorised to receive the child, how consent was obtained, how identity was verified, what time the child left, who approved the release and whether the child showed any sign of fear, confusion or reluctance.

A written Child Handover and Release Protocol gives staff a practical rule to follow. It should apply whenever a child leaves the organisation’s custody or active supervision. That includes ordinary school pickup, camp departure, medical referral, rescue placement, reintegration, home tracing, transport drop off, field trip return, weekend release, boarding exit and handover to a relative, foster family, religious leader, community elder, sponsor, local authority or another service provider. The policy should be so clear that a new volunteer, driver or teacher understands that recognition, pressure, convenience or an undocumented phone call is not enough.

What the protocol should contain

A strong protocol should begin with an authorised receiver record. Parents or lawful guardians should identify, in advance, the people who may receive the child. The record should include names, relationship to the child, contact details and reliable identity information. It should be updated when family arrangements change. Where the child is in a protection case, the record may need additional restrictions or approvals from the safeguarding lead or competent authority.

The protocol should also require written consent before any unusual release. If the person collecting the child is not on the approved list, staff should not rely on a message passed through someone else. The parent, lawful guardian or competent authority should provide clear authorisation. In an emergency, an email, a recorded message, a signed note or a properly saved digital communication may be useful evidence, but it should still be reviewed carefully. The organisation should record why the release was allowed and who approved it.

Identity verification is equally important. A person may be known in the community, but that does not always prove authority to receive the child. Staff should verify identity using a national identity card, passport, refugee card, local council letter or another reliable document where appropriate. The point is not to turn every pickup into a hostile process. It is to make sure the organisation can explain, calmly and clearly, why it believed the handover was safe.

A second approval should be required for unusual or emergency handovers. This is especially important where the request comes suddenly, where parents or relatives are in conflict, where the child is being moved from a protection arrangement, where the adult is forceful, or where the child appears uncomfortable. A second staff member, preferably the safeguarding lead or project manager, may notice a risk that the first staff member missed.

The child’s voice should not be ignored

Child safeguarding is not only about adult paperwork. Staff should pay attention to the child’s response. If the child appears afraid, confused, reluctant or says they do not know the person, the handover should stop until the concern is reviewed. This does not mean every child’s hesitation proves danger. Children may be shy, tired or upset for unrelated reasons. Still, the hesitation is information. It should be recorded and treated seriously.

The same caution applies where an adult pressures staff, threatens to report the NGO or demands urgent release without documents. Pressure is not proof of unlawful intent, but it is a warning sign. A person who has authority to receive a child should usually be able to wait while the organisation verifies the facts. Where the request is disputed, suspicious or connected to family conflict, the matter should be treated as a safeguarding incident and escalated.

Why emotional harm must be taken seriously

One mistake in child handover may cause harm even without physical injury. The Ruzindantaro summary highlights prolonged separation and emotional trauma. That should make NGOs cautious. A child may suffer fear, confusion, disrupted schooling, loss of family contact and deep emotional distress where release is mishandled. A parent or guardian may also experience serious harm where a child is removed without proper consent.

This is why the organisation should not wait for a dramatic incident before improving its procedure. The better practice is to identify every point where children are received, transported, hosted or released. The NGO should then create or update the authorised receiver form, emergency consent form and release register. Staff, volunteers, drivers, teachers, coaches and community facilitators should be trained on the rule. After the first month of use, the organisation should audit the records and correct gaps before poor habits settle in.

A practical policy standard

A useful policy can be written simply. No child under the supervision or custody of the organisation should be released to any person unless that person is listed as an authorised receiver or the organisation has obtained clear consent from the parent, lawful guardian or competent authority. Staff should verify identity, record the time of release, record the reason for release and obtain approval from the safeguarding lead where the handover is unusual, urgent, disputed or requested by a person not previously authorised.

That wording may look strict, but it is fair to staff as well as children. It protects the driver who is being pressured at the gate. It protects the teacher who is unsure whether a relative is telling the truth. It protects the project officer who wants to help but needs a recorded decision. Most of all, it protects the child, whose safety should not depend on improvisation.

Source note. This article is based on Ruzindantaro v The School Management Committee Bishop Asili Memorial Nursery & Primary School, Civil Suit 36 of 2022, [2025] UGHC 409, and on the Children Act, Chapter 62, as consolidated on ULII, especially its concern with custody, protection from violence, abuse and neglect, and parental responsibility. It is a general compliance article and should be adapted to the facts of each child facing project.