Bellroll Talk to us

Student-built in Connecticut

We’re building Bellroll for life after the bell.

We’re involved in clubs at our school, and we’ve seen how hard it can be to find reliable meeting times, room details, and other basic information when everything is spread across paper, group chats, and separate spreadsheets.

See how it works
Bellroll synthetic Student home showing a made-up Robotics Club meeting and sample club memberships
Synthetic demoSample school and student records only.

Different needs, centralized records

Bellroll gives people involved in clubs the tools they need.

  1. Students

    Find clubs, see when and where they meet, request to join, and keep upcoming meetings in one place.

  2. Club leaders & advisors

    Keep rosters current, take meeting attendance, and explore illustrative form tracking in the demo.

  3. Administrator

    See which clubs are active, where they are meeting, which adult is supervising, and which students are participating.

See the workflow without sharing student data

The Bellroll demo uses a made-up school, made-up students, and resettable sample records. It is separate from any authenticated school environment, so you can explore the workflow without entering information from a real school.

  • Rosters
  • Meeting attendance
  • Permission forms
  • Advisor coverage

Three connected synthetic views

  1. Before the meeting

    Student checks the Robotics schedule

    Synthetic Student view showing the next Robotics Club meeting in Room 114 with Ms. Alvarez

  2. During the meeting

    Club leader records Robotics attendance

    Synthetic Club Leader view showing five visible Robotics students, with three selected, in a five-student excerpt under advisor supervision

  3. Advisor oversight

    Across clubs: status and roster sign-off

    Synthetic Advisor summary showing three pending approvals, four confirmed clubs, and two of four forms submitted

    Illustrative demo-only form tracking. Local form tracking is being tested for authenticated school use. External form delivery, electronic signatures, and guardian verification are disabled.

    Synthetic Advisor review item asking for Photography Club roster confirmation
Assembled from synthetic demo views. Sample school and student records only. Values shown are synthetic demo state, not customer outcomes.

From club setup to schoolwide reporting

What Bellroll is being built to manage

In a school-approved pilot, Bellroll would bring the records associated with clubs into one convenient place for everyone involved.

Clubs and rosters

Keep each club’s purpose, leaders, advisor, meeting details, and current membership organized.

Schedules and rooms

Set meeting times and locations, and confirm advisor participation.

Meeting attendance

Select a specific meeting, record attendance, and keep the room and adult advisor attached to the record.

Permission forms

The demo illustrates advisors checking off submitted forms. Local form tracking is being tested for authenticated school use; external delivery, electronic signatures, and guardian verification are disabled.

Participation reporting

The illustrated dashboard compares sample enrollment with club rosters. The current authenticated candidate provides self, club, and school counts; it does not provide this roster-membership percentage.

Make club information easier to find

We’ve seen how difficult it can be for students to find current meeting times, room details, and schedule updates when that information is scattered across different places.

Bellroll would bring schedules, enrollment, and roster information into the same workflow so administrators can see which clubs are active and where organization needs attention. The dashboard below uses aggregate sample data. It is not a customer result and does not expose a student-level list. Student roster detail belongs in the administrator workflow, not the public student view.

Illustrative Bellroll Admin dashboard showing 83 percent sample roster membership labeled participation and a 141-student aggregate outside club rosters, without student names

What the sample dashboard shows

Participation: 83%
The illustrated share of sample enrolled students listed on at least one club roster. The public demo’s participation measure instead counts distinct students who attended a finalized meeting in its reporting period.
Active clubs: 42
The sample clubs currently listed as active.
Meetings this month: 118
The sample club meetings recorded during the current month.
Forms submitted: 2 of 4
Two of four sample forms are marked complete in this illustration. The pictured form totals are illustrative; local form tracking is being tested for authenticated school use.
Front-office approval
A sample room request is waiting for an administrator’s decision.
Advisor confirmation
A sample club roster still needs its advisor’s confirmation.
Silent for 30+ days
A sample alert marks a club with no recent recorded activity.
Zero-activity aggregate
A schoolwide sample count of 141 students not listed on a club roster.
Named zero-activity export
Student names are not available from this aggregate view.
Illustrative view: sample data. The values shown are authored examples, not customer outcomes.

Student data deserves more than a promise; it deserves a written, reviewable plan.

Before Bellroll uses real student data, a school would need to decide whether the product, contract, and operating plan meet its requirements.

Before any real student data is used, the school would review and approve the legal agreement, data scope, access model, security plan, accessibility requirements, subprocessors, retention rules, and exit process.

Synthetic public experience

No real student records are needed to evaluate the workflow.

The public imagery uses a made-up school, made-up students, and resettable sample records. The marketing site does not request or accept student data.

Role and scope review

Access would be defined before a pilot starts.

A school would document which students, club leaders, advisors, and administrators can access each type of record, along with which data fields are in scope.

Data lifecycle

Schools set the data timeline.

Before a pilot begins, the school and Bellroll would agree how long data is kept, how corrections and exports work, and when pilot data is deleted.

School approval comes first

A school decides whether a pilot can use real data.

Before that happens, the school reviews the agreement, security and incident plans, service providers, accessibility, purchasing requirements, and how data will be removed at the end.

  • No ads. Advertising is not part of the product being built.
  • No student profiling. Student records are not being built for behavioral advertising or commercial profiles.
  • Never sold. Student data will never be sold. It will only be shared with school-authorized users and necessary service providers.

Follow along

A clearer view of what’s next

We’re keeping a record of the work behind Bellroll, with availability stated for every update.

Read the patch notes
In development

The next chapter for school clubs

School setup, meeting updates, and better membership and attendance workflows are the focus of our next development work.

These product updates are not yet available for school use.

About Bellroll

Built from our experience with school clubs

We’re 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.

Read our story

Students should not have to guess when or where a club meets.

Tell us how clubs work at your school

We’ll show you the synthetic demo, listen for what we got wrong, and explain what Bellroll can and cannot do today.

Talk to us at contact@bellroll.app