The Glamies App
The real software behind every season.
Reviewers, adjudicators, chapter admins, and show directors all run their season through the same app — check-in, scoring, nominations, waivers, the calendar. This page shows exactly what’s live today, flow by flow, and is just as honest about what isn’t built yet.




































Built in the open
Real software, actively growing.
Every screenshot on this page is a real, driven action against live seed data — not a mockup. Click any screenshot to step through that flow. Where a flow isn't finished yet, we say so, the same way our own engineering tracker does.
7
Season flows
65
Steps built
103
Steps mapped
Chapter Onboarding
Standing up a brand-new chapter — the very first step before any season can exist. Almost entirely on the roadmap today.
On the roadmap
Create a chapter
The chapters table exists, but there’s no create-chapter service or admin UI yet. Chapters are seed-only today — a system admin can’t stand up a new organization from the app.
Define the chapter’s disciplines
There’s no discipline concept in the schema yet. Today the platform implicitly supports one discipline (full-length competition theater) — picking theater vs. choir vs. public speaking, each with its own default rubric set, is on the roadmap.
Invite the chapter admin by email
No invitation system yet. Every chapter-admin membership in the seed data is inserted directly, not through an invite flow.
Chapter admin accepts invite / creates their account
Sign-in itself works — but there’s no invite-acceptance flow that binds a brand-new account to a specific chapter and role yet.
Chapter admin configures feature toggles
Season-level policy toggles exist (voting thresholds, nomination windows). Chapter-level settings — auto-reminders, email notifications — don’t yet.
Chapter admin agrees to terms / acknowledgments
No terms/acknowledgment model exists yet — nothing records that a chapter admin accepted responsibility for handling sensitive student data.
Chapter admin can now create seasons
Chapter-admin permissions already gate the rest of the app correctly — but season creation itself is missing. See Season Setup below for what season management actually does today.
Season Setup
Standing up a competition year — calendar, schools, performances, and award categories & rubrics.
On the roadmap
Create a season
No create-season form exists yet — every season today comes from seed data, though the underlying table (with draft/active/completed/archived status) is ready for it.
Season tied to a discipline; rubrics auto-populate
Every season today implicitly means theater — a discipline picker with automatic rubric-set cloning is on the roadmap.
Create performances
Title, type, school, date, venue, playbill — the performances table supports all of it, but there’s no create/edit form yet. Every performance today is seeded.
Assign a show director to each performance
The backend service to assign roles exists, but no page currently has a role-assignment control wired up to it yet.
Activate the season
There’s a voting-day toggle, but no general draft-to-active transition yet — every season you see is already seeded as active.
Role Onboarding & Invites
Getting every participant an account, the right season role, and a signed waiver before training day.
On the roadmap
Invite season-wide roles by email
No invite system yet — role assignment requires an already-existing user account.
Bulk invite via spreadsheet
No CSV/spreadsheet import path exists to invite a whole roster in one pass.
Member self-selects a role; admin approves
Only admin-initiated role assignment exists — no member-facing request-a-role workflow yet.
Show director manages their own school’s team
Role assignment is chapter-admin-only today — a director’s read-only team view is built (see Performance Day), but not their own assign/edit control.
Floating members
A person can belong to a chapter with no season role in the data model, but there’s no in-app flow to add one outside of seeding.
Lead-reviewer designation
Not in the role model at all yet — there’s no signifier-only "lead reviewer" label.
Record the school liaison
No liaison field exists on a school’s profile yet.
Training Day
Meant to be a first-class, roster-taking event that gates who can review a show. Today it’s a line on the calendar — everything else is roadmap.
On the roadmap
Tag each training day by the role it trains
No field distinguishes a reviewer-training session from an adjudicator-training or makeup session yet.
Take a training-day roster
Attendance in the app today is tied to a performance, not a training day — the paper-sign-in-sheet replacement for training day itself is still on the roadmap.
Online training + external quiz → mark present later
No path exists yet for crediting a reviewer who completed training online or after the fact.
Multiple training days + makeup days
Follows directly from the missing roster/attendance model above.
Demo / sample show for practice scoring
No way yet to seed a practice show reviewers can score without it counting toward eligibility or awards.
Collect waivers at training
The waiver flow itself is real — see Role Onboarding & Invites — but training day has no waiver-specific UI of its own; it’s just the usual moment it gets collected.
Trace "was this person trained?" for late additions
With no training-attendance records yet, there’s nothing to verify a mid-season addition against.
Training completion gates show assignment
Reviewer and adjudicator assignment works regardless of training record today — no gate checks it yet.
Nomination Lifecycle
Nominee names, reviewed and approved through the season — feeding voting day’s slates and, eventually, the winners.
On the roadmap
Nomination slots auto-created per performance
Nothing creates a show’s nomination slots automatically at runtime today — every slot is seeded.
Show director submits nominee names
The intended design has the director submit their own show’s nominees first. That path doesn’t exist yet — today, names are only ever entered by an adjudicator or chapter admin.
Canonical accepted names recorded on approval
Approving a nomination updates the submitted name, but the "canonical accepted" spelling that voting day’s conflict-matching is meant to key off doesn’t exist yet.
Nominee and teacher told "you’re nominated"
Nothing surfaces a nomination to the student or their teacher anywhere in the product yet.
Approved slate feeds awards computation
No awards service exists yet — approved nominations don’t feed anything downstream. That’s part of Voting Day’s remaining roadmap.
Withdraw / resubmit a rejected nomination
No withdraw concept yet — a rejected nomination has no resubmission path back to the director.
Performance Day
The flagship flow — check-in to feedback, fully built and verified end to end. Every screenshot below is a real, driven action against live seed data.
Voting Day
Eligibility-gated scoring for the season’s final round. The phase gate and approval flow are built and shown live; slate and winner computation are next.
On the roadmap
Reviewer sees an eligibility snapshot
Eligibility is fully computed server-side, but it’s only exposed admin-side today — a reviewer has no dashboard card showing their own status ahead of time.
Compute top-5 nominations per category
Not built yet — the season-wide standings computation this depends on doesn’t exist.
Committee reviews slates and determines winners
No winners view or confirm-winner path yet — depends on the standings/slate computation above.
Reviewer award for perfect attendance
The raw attendance and grade data is tracked, but nothing computes a per-grade standing from it yet.
Results feed the gala
Out of scope until the standings/winners computation above exists — would just export its output.
See it yourself
Walk through the live system.
Everything on this page is running right now — click into the demo, or reach out and we'll walk your team through it directly.









