Roll call from the deck team's pocket.
Every class starts the same way. Someone prints the roll sheet and clips it to the board. Then they hope the wind doesn't take it.
The way it works today.
The sheet spends an hour at the pool edge, so it spends that hour getting wet. Names get missed, and nobody finds out until the parent at the gate says their kid was there.
At the end of term the sheets go in a folder. Everything the school needs next term (who missed what, and who's owed a makeup) stays trapped in handwriting. Nobody reads a folder, so next term starts on guesses.
What I'm building.
Roll Call lives on the phone already in the deck team's pocket. Open the class and tap who's here. Done. It takes seconds, poolside, by whoever is running the deck.
And every mark lands in the record log, where the rest of the school can use it. A missed class issues a Makeup Token under your school's own rules. (A token is a credit the family earns by missing with enough notice, and spends on a makeup.) The freed seat goes back on the board for the next family, so the term runs on the numbers the deck marked, every class, all term.
The engine underneath already runs and it's tested: a missed class issues the token, and the seat count updates. The deck-side screens are what we build next, with you.
I'm Matthew Bilo. I build software used by 10,000+ firms at Sitemate and LRQA. fathm gets the same engineering.
Build it with me.
Tell me how roll call works at your school, the parts you like too. (Yes, there are usually parts you like.) What you say decides what gets built:matthew@fathm.io