Intake
Student submits placement details and uploads offer letter
Architecture · How it works
From six scattered forms to one pipeline.
The program runs on six Microsoft Forms today, scattered across five faculty inboxes, plus one manual eligibility step the program coordinator runs by hand on every offer letter. The OS unifies those into a single intake-to-close-out pipeline visible to every faculty seat, with the classifier inline.
Section 1 · The change
How this connects
Today · Six Microsoft Forms scattered across email
CurrentEach form lives in a separate email thread, scattered across five faculty inboxes. The coordinator tracks status by reading inboxes and copying data into a master spreadsheet. The eligibility classification runs manually on every offer letter. Other faculty have to ask to see status.
Form 1 · Intake
Internship Contact and Information
Email thread to student
Form 2 · Agreement
Student Internship Agreement
Email thread to student
Form 3 · Agreement
Site Supervisor Internship Agreement
Email thread to supervisor
Form 4 · Active
Hours Log
Email thread to student
Form 5 · Close
Final Internship Evaluation
Email thread to supervisor
Form 6 · Close
Exiting Intern Information Form
Email thread to student
Plus one manual step
The program coordinator classifies every offer letter by hand. Reads the duties description, judges whether it lifts above pre-internship-level, asks for revisions when it does not. Mackenzie required two revisions before approval. Marcus is on the second revision and still stuck. None of the other four faculty can see the judgment without asking.
With NextStage OS · One intake-to-close-out pipeline
ProposedAll six forms become one pipeline visible to every faculty seat. The classifier runs automatically at the right gate. The coordinator reviews AI-generated verdicts instead of authoring them by hand. Status is visible at every step, on every screen, for every cohort member, to every faculty member.
1
AI
Eligibility Classifier
Two-gate engine reads offer plus duties, returns verdict with evidence
2
Agreements
Student and supervisor sign in sequence, both routed through the same pipeline
3
Active
Hours Log opens automatically, pacing monitor runs against the 250-hour gate
4
Evaluation
Final Internship Evaluation routed to supervisor at Week 11
5
Close-out
Exiting Intern Information Form routed to student at Week 12, archive complete
What changes for the faculty team. Email-thread tracking goes to zero across all five faculty inboxes. The AI eligibility classifier produces a draft verdict the coordinator approves or redirects in front of the team. Pacing flags fire automatically. The 47 minutes the coordinator spends per intern on data movement today returns to the week, and the other four faculty stop asking for status updates because they can see them.
Section 2 · The five phases
Phase picker
Every intern moves through these five phases in order. Each phase has known forms, known signers, and known triggers. The OS handles the routing; people handle the substance.
Phase 3 · Active Internship
Hours Log open · pacing monitor running
The Active phase is the longest stretch of the internship. The student logs hours, the pacing monitor watches against the 250-hour course gate, and the system raises a flag if a student trails the expected pace. This is the phase where Lauren Beckett currently sits, behind pace at 95 of 250 by Week 7.
Forms in this phase
1
Hours Log
Signed weekly by the student, countersigned by the site supervisor
Automated touchpoints
2
Pacing monitor
Runs weekly against expected hours pace
3
Supervisor check-in nudge
Sent to supervisor at Week 4 and Week 8
4
Faculty Console queue surface
Every faculty member sees pacing flags in the Red Flag queues without searching
Next phase
Phase 4 · Evaluation
How This Connects + Phase Picker V1 · Hybrid Substrate · Sample data · Em-dash zero · WCAG 2.2 AA
BUILD V1