The busiest five minutes of a preschool day are often the riskiest: children are excited, adults are rushing, and a last-minute message says an uncle will collect instead. A calm authorised-collection process protects children, gives staff a script and reassures parents that the school takes handover seriously.
Direct answer
Preschools and TASKA can manage child pickup safely by keeping an up-to-date authorised-collector list, verifying every unfamiliar collector against it, documenting last-minute changes through one agreed channel, and recording each handover. Staff should never release a child because an adult “looks familiar” or because a child says they know them.
Malaysia’s official TASKA information notes that centres must be registered under the Childcare Centre Act 1984 and frames registration around safety and quality standards. See Malaysia.gov.my’s TASKA overview. Your collection procedure should be part of a wider safeguarding and operating framework—not an isolated reception rule.
The collection record every child needs
At enrolment, ask each parent or legal guardian to provide:
- their own current contact details;
- each approved collector’s full name, relationship and contact number;
- a photo or agreed identity-verification method, if your policy supports it;
- collection permissions or restrictions that require an escalation path;
- an emergency-contact order; and
- consent for the school’s defined communication channel for collection changes.
Confirm that an approved collector is not automatically allowed to make other decisions about the child. Collecting a child, receiving invoices and changing enrolment details are different permissions.
A simple pickup SOP
| Step | Staff action | Record |
|---|---|---|
| 1. Prepare | Check expected absences, transport changes and collection notes before dismissal | Daily handover list |
| 2. Receive collector | Greet the adult; check identity if unfamiliar or when policy requires | Collector name |
| 3. Verify | Match against authorised list and any same-day change approval | Verification completed |
| 4. Handover | Confirm the correct child, belongings and any required message | Collection time and staff initials |
| 5. Escalate if uncertain | Keep child supervised; contact registered guardian and manager | Incident / decision note |
| 6. Close out | Review uncollected children and late pickups against escalation plan | Late-pickup record |
The person releasing the child needs permission to pause the queue. Make it explicit that no staff member will be penalised for taking time to verify an unfamiliar adult.
Write the last-minute-change rule before you need it
Parents will sometimes be delayed. Make the acceptable request specific: the parent contacts the school through the registered number or parent portal, gives the new collector’s full name and relationship, and receives acknowledgement from staff. The new collector brings the required identification.
Do not rely on a screenshot, a message forwarded by a relative or an adult calling from an unknown number. If the team cannot verify the change, the response is simple: “We understand this is inconvenient. To keep [child] safe, we need to confirm this with the registered guardian before release.”
An example of the basic expectation appears in MBPJ’s TASKA and Tadika rules: where a parent or guardian cannot collect a child, an authorisation is required; the page also asks families to call ahead for emergency pickup. Your setting may use a different method, but it should be documented and consistently applied.
Give staff a clear script for difficult moments
For an unlisted collector:
Thank you for coming. I need to confirm your collection authorisation with [child]’s registered guardian before I can release them. Please wait here while we make that check.
For a late parent:
[Child] is safely supervised. Our collection time ended at [time]. Please let us know your expected arrival time; our late-pickup procedure is [brief next step].
For a dispute or restriction, do not negotiate at the gate. Move the conversation away from children, involve the named manager and follow the school’s safeguarding and legal advice procedures.
Train for the edge cases
Role-play these situations at induction and once a term:
- a grandparent arrives for the first time;
- a collector has the same surname but is not on the list;
- a parent sends a last-minute WhatsApp while reception is busy;
- two children share a surname or first name;
- the authorised adult appears unwell, distressed or impaired; and
- a child has not been collected after closing.
For each scenario, staff should know who takes responsibility for the child, who calls the guardian, when to involve the principal, and how to record the decision. A policy that works only on a quiet day is not a working policy.
Review the list as part of everyday administration
Ask parents to verify authorised collectors at the start of each term, after a family-contact change and before holiday programmes. Reception should not have to interpret an old form while a child is waiting at the door. Keep the current list in the system staff actually use for dismissal, with access restricted to roles that need it.
How Oodlins can help
Oodlins can help schools maintain current student and guardian records, attendance and parent communications in connected workflows, making daily handover checks easier to manage. Explore school management, attendance and reports, and our guide to daily health and attendance records.