Checklist: Is Your School Gate Ready for the Next Incident?

Most incidents at the school gate don't happen because the school doesn't care about safety. They happen because the process works well enough day-to-day that no one feels the urgency to review it — until the day it doesn't work.

This checklist was developed to help administrators see the gaps before they become problems. Answer honestly: not how you'd like the process to be, but how it actually operates today.

Block 1 — Authorized Pickup Registry

1. Does your school have an up-to-date photo registry of all individuals authorized to pick up each student? ☐ Yes, digital and current ☐ Yes, but on a spreadsheet or paper ☐ Partially ☐ No

2. Can guardians update authorizations without calling or visiting the school? ☐ Yes, through an app or system ☐ No — they need to contact the office

3. When a new student enrolls, is the authorized pickup registry completed before the first day of school? ☐ Always ☐ Most of the time ☐ Rarely, or no defined process

Block 2 — Gate Process

4. Can any staff member working the gate — including a substitute who has never been there before — verify who is authorized to pick up a specific student? ☐ Yes, the system allows this ☐ No — it depends on who's on duty

5. Does identity verification at pickup go beyond asking for a name? ☐ Yes, there is photo-based verification ☐ No — the guard asks for the name or recognizes the person

6. Is there a documented protocol for when an unknown person arrives to pick up a child? ☐ Yes, written and trained with the team ☐ Yes, but informal (each person handles it their own way) ☐ No

7. When the gate guard is unsure, what do they do? ☐ Follow a clear, documented protocol ☐ Use their best judgment ☐ There is no mapped process for uncertain situations

Block 3 — One-Time Authorizations

8. When a family needs to authorize a one-time pickup (grandma picking up just today, a driver, a neighbor), how does that reach the gate? ☐ Through a system with photo ID of the authorized person ☐ Via WhatsApp or a call to the office ☐ The person just shows up and the guard decides

9. Is there a record of who authorized each one-time pickup? ☐ Yes, automatic and traceable ☐ Sometimes, when someone remembers to write it down ☐ No

Block 4 — Records and Audit Trail

10. Does each student dismissal generate a record with date, time, guardian identity, and the staff member who approved the release? ☐ Yes, automatically ☐ Sometimes, manually ☐ No

11. If a guardian contested that their child left with an unauthorized person, could your school present traceable evidence? ☐ Yes, we have an auditable digital record ☐ Maybe, depending on what was written down ☐ No

12. Is the data collected at the gate stored securely, in compliance with Brazil's LGPD? ☐ Yes, in a secure system with controlled access ☐ On a spreadsheet or paper, with no access control ☐ I don't know

Block 5 — Process Resilience

13. If the regular gate guard called in sick tomorrow without notice, could a substitute operate at the same level of security? ☐ Yes ☐ No

14. Has your school experienced any situation of doubt or tension at the gate related to student pickup in the past 12 months? ☐ No ☐ Yes, but it was resolved without major consequences ☐ Yes, and it was a real problem

15. If an attorney requested the record of the last 30 dismissals for a specific student — including who picked them up each time — could you produce that in under 5 minutes? ☐ Yes ☐ No

How to Interpret Your Results

Mostly first-option answers: Your gate operates with an adequate level of security and traceability. Review the isolated points where your answer differed — those are your vulnerability windows.

Mixed answers: Your process depends on specific individuals and favorable conditions to work. You don't have one problem — you have multiple risks that haven't materialized yet. The time to act is now.

Mostly non-first-option answers: Your school is operating with real legal exposure. A gate incident — however minor — can have disproportionate consequences because there is no documented process to back you up.

What to Do Now

Regardless of your result, the next step is the same: identify the points where the process depends on human memory, goodwill, or luck — and replace them with a documented, traceable flow.

Kidsflow was built to transform exactly this scenario. In less than a week of implementation, any school can operate the gate with photo verification, an auditable record of every dismissal, and one-time authorizations via QR code — without depending on who's on duty.

Want to see how it would work at your school? Schedule a 20-minute demo and leave with a personalized assessment of your current process.

Frequently Asked Questions

Why is a manual gate process considered risky if it has worked for years? The manual process works while favorable conditions hold — the regular guard present, families recognized, no disputed incidents. The risk isn't in the smooth day-to-day, but in the exception scenarios: guard on vacation, unfamiliar family, authorization disputed in court. In those moments, the school needs records and protocol — not memory or goodwill. The problem is those scenarios don't announce when they'll happen.

How often should a school review its dismissal and authorization process? Ideally, the process should be reviewed at the start of each school year — when enrollments renew, new students arrive, and gate staff may change. Beyond that, any incident or near-incident should trigger an immediate review. Schools with a digital system have the advantage of the process updating continuously as families update their own registrations, without depending on periodic manual reviews.

What should a school do if a child is not picked up on time? The school needs a clear protocol for this scenario: attempt contact with all registered guardians, in a pre-defined priority order; log the time of each attempt; and, if no contact is made after a set time, notify the relevant authorities. This protocol must be documented, trained with staff, and accessible at the gate — not just in someone's memory.

Is a shared spreadsheet an acceptable alternative to a digital system? A shared spreadsheet is better than a printed list, but still has critical flaws: it doesn't offer photo-based verification, doesn't auto-generate a dismissal record with time and guardian, doesn't have adequate access control for LGPD compliance, and requires constant manual updates. For day-to-day gate operations — especially during peak hours — a spreadsheet creates friction that a specialized system eliminates.

Does the school need parental consent to photograph authorized individuals in the registry? Yes. Registering photos of authorized individuals involves collecting biometric and image data, which requires an adequate legal basis under the LGPD. The most common basis is the explicit consent of the data subject — in this case, the authorized person themselves — or the school's legitimate interest in protecting the child, properly documented. Systems like Kidsflow are built with LGPD compliance incorporated, including the necessary consent workflows.

How do you train gate staff to follow the protocol consistently? Training should cover three scenarios: standard dismissal with a registered guardian, dismissal with a one-time authorization, and dismissal with a situation of doubt or an unauthorized person. Each scenario needs a documented flow with clear steps, leaving no room for individual interpretation. Training must be repeated with every new staff member before their first day at the gate — not after. Digital systems make this training easier because the system itself guides the operator through the correct flow.