Mid-Year Demo · V1

NextStage Internship Experience

A working demo of the operating system the Hospitality Management faculty team would use to run the internship program end to end. Five working screens for the day-to-day. One BookFlip overview the team can carry into a meeting. One feedback form so each faculty member tells the coordinator directly what landed.

You are looking at a demo, not a production system. All student data is sample (no real UARK records touch the demo). Mackenzie Noffz is the one real name, used as the canonical case the program coordinator approved this term. Open the BookFlip first for the guided tour. Open Eligibility Engine to feel the live AI classifier. Open Feedback at the end and tell the program coordinator what landed.

Start here if it is your first time

Walk the BookFlip Overview first. It is the guided tour.

The BookFlip is built as a page-turner book. Eight to ten pages summarizing the five demo screens, the canonical Mackenzie case, and what the OS replaces in the current six-form pipeline. Click the cover to open, then drag the right edge or use the arrow keys to turn pages.

Open the BookFlip Overview →

The five working screens

Screen 1 · Student view

Student Cockpit

What an intern sees. Their requirements, their eligibility verdict, their hours-logged status, what they need to do next. Mackenzie Noffz is the canonical case · revised duties, internship-level after the second pass.

Screen 2 · Faculty view

Faculty Console

The shared workspace for the faculty team. KPI tiles, full 12-intern grid, three red queues (eligibility gate, classifier hold, hours-log pacing behind), two watches, and a pivot view. Wyatt, Marcus, and Lauren each surface as a separate queue, visible to every faculty member instead of buried in one inbox.

Screen 3 · Classifier

Eligibility Engine

The two-gate engine. Paste an offer letter and a duties description, classify the position. Returns internship-level vs pre-internship-level, evidence chips, hours-gate state, and an Approve / Request Revision recommendation. Falls back to a sample answer if the live LLM is offline.

Screen 4 · The pitch

How This Connects + Phase Picker

The "Today vs OS" frame. Side-by-side comparison: today's six scattered forms vs the single OS pipeline. Five-phase picker lets you click into any phase (Intake, Agreements, Active, Hours, Close-out, Exit) and see what changes.

Companion · Hand-out

BookFlip Overview

The page-turner summary of the whole demo in book form. Built as a hand-out the faculty team can carry into a meeting or read offline. Drag the right edge or use the arrow keys to turn pages. Click the cover to open.

Last stop · Tell us

Feedback Capture

Eight questions after you walk the demo. Five Likert, two multiple choice, one optional comment. Roughly three minutes. Answers stay on your device (localStorage) so each faculty member tells the program coordinator directly what landed and what missed.

Notes for the faculty team

The OS replaces the current six-form pipeline (Internship Contact and Information, Student Agreement, Site Supervisor Agreement, Hours Log, Final Evaluation, Exiting Intern). Same intent. Different mechanics. Same five faculty seats; one shared workspace instead of five separate inboxes.
The eligibility classifier is the manual offer-letter review the program coordinator runs today on every placement. The OS produces a draft verdict the coordinator approves or redirects, in front of the whole faculty team. The audit trail stays visible to everyone with a faculty seat.
The Eligibility Engine is wired to a Cloudflare Worker that calls Claude Haiku 4.5 with a classification rubric matching the program coordinator's manual process. If the live LLM is offline, the screen falls back to a built-in sample response so the demo never goes blank.
The sample cohort has 12 interns, three with intentional red flags so the Faculty Console surfaces them as distinct queues. Mackenzie Noffz is the one real name; everyone else is fictional with 479-555 phone numbers.
Nothing here is graded. Nothing here is final. Tell the program coordinator what landed, what missed, what you would build differently before the faculty team commits to building this for real.