Volunteer shift signup with waitlists, built by Claude Code on Elements

Volunteer shift signup with waitlists, built by Claude Code on Elements

Volunteers pick up shifts with live spots left, waitlists and day-before reminders; coordinators set weekly shifts, check people in and export hours.

View the code on GitHub →

How it's built

Rostergrove needed shifts with spots that count down as volunteers sign up, waitlists that move people up, day-before reminders, check-in and an hours report for the coordinator. Each of those is a part of Elements, so the agent spent its 18 minutes on the food bank's roster itself.

  • Live spots and rosters. Shifts, signups and the coordinator's roster are LiveTables. Spots left change the moment someone signs up, and the roster fills in and checks off as people arrive.
  • Waitlists that move people up. Signing up locks the shift first, so the last spot goes to exactly one volunteer and a full shift puts the next one on the waitlist. When someone with a spot leaves, whoever has waited longest is confirmed.
  • Day-before reminders. A one-line cron schedule runs a job every hour that emails each confirmed volunteer the day before their shift, in the food bank's time zone, and marks each one as sent.
  • Weekly shifts and hours. A coordinator adds a shift once or every week for a set number of weeks, and downloads each volunteer's checked-in hours for the year as a CSV.
  • Server calls as function calls. Signing up, leaving, check-in and cancelling a shift call server functions straight from the page with @rpc.
  • Data and roles from SQL. Migrations define the roster and seed one coordinator, fifteen volunteers, sixteen weeks of past shifts with hours served and two weeks of upcoming shifts with signups. Sessions and roles give coordinators check-in and the admin pages.

Why Elements

Elements is the integrated stack for building apps with AI: a TypeScript project server, build system, app framework and deployment system, engineered from the ground up as one. Your editor, tools and one or many agents all connect to the same always-on project server, which runs type checking, program analysis, migrations and tests as the agent builds. Built-in guardrails keep the app structured correctly and secure as it grows from prototype to production.

Run it yourself

Paste this into a terminal. It installs Elements, creates your copy of this app and starts it.

curl -fsSL 'https://elements.dev/install?create=rostergrove&scaffold=demo-rostergrove' | sh
View script