Start with synthetic records
Public product work uses made-up schools, students, clubs, and activity records so the workflow can be evaluated without real student information.
About Bellroll
Built from our experience with school clubs
We are students at a Connecticut public high school. Through the clubs we participate in, we’ve seen how difficult it can be to find one current source for meeting times, room details, and schedule changes.
What clubs need to keep current
- 01Meeting times
- 02Room details
- 03Schedule changes
Why this problem matters
Why clubs are different
Sports teams have practical systems for schedules, rosters, and communication, but clubs often do not.
At our school, club meeting times, room details, and updates can end up across paper, group chats, and separate spreadsheets. When those sources fall out of sync, students can be left unsure about when or where a club meets.
Bellroll grew from that problem. We’re building one workflow where students can find current information and the people organizing activities can keep schedules and club records aligned.
Our approach
How we are building
Experiencing that problem ourselves does not earn a school’s trust. The way we build Bellroll has to do that work.
Listen before defining a pilot
Administrators, advisors, district staff, parents, and students should help identify what the workflow gets right and what it misses.
Put school review before real data
No real-data pilot should begin before the school completes its required legal, privacy, security, accessibility, and procurement reviews.