About Childmap
Why we built this
Every school gate still runs on the same outdated system: a paper logbook, a teacher or gateman manually recording names and times, and a parent at home simply hoping everything went fine. Most days, it does. But the moment something goes wrong a late pickup, a child who never made it into school, or confusion over who a student left with the logbook has little useful information to offer. By the time anyone checks it, it’s often too late to matter. Schools need more than a record of what happened. They need a system that knows when a child arrives, when they leave, who they leave with, and can instantly notify the right parent.
The problem we kept seeing
Parents want one simple thing: to know their child is safe, the moment it's true not at pickup time, not when someone remembers to call. Schools want the same thing from the other side: a reliable record of who's on campus right now, without a staff member re-typing a paper register into a spreadsheet every evening. Neither side was getting it. The gap between "my child left the house for school" and "my child is confirmed safe at school" was just silence.
What Childmap does about it
Childmap replaces the logbook with a gate scanner and a live dashboard. A student taps a card, enters a code, or is recognised by Face ID, and two things happen instantly: the school's dashboard updates, and the parent gets a message. Same at pickup. No end-of-day reconciliation, no guessing, no waiting just a record that's accurate the second it's created, for the people who actually need it.
Who it's for
We built Childmap for schools that take arrival and departure seriously but don't have the budget or the appetite for enterprise security software starting with schools here in Nigeria, where this gap is especially wide. Simple enough for gate staff to run without training, honest enough about pricing that a school can budget for it per term, and built so that every check-in actually reaches a parent's phone, not just a database.