| Course | Title | Length | Dean | Program Manager | Assigned Instructor | Notes | Actions |
|---|
How this view works
Each row is one offering — a single term instance of a course, derived from the registrar's online rotation. 5-week slots (A/B/C) land in subterms 1A / 2B / 3C. 10-week courses (F = First, L = Last) appear in both of the subterms they span. Full-semester online courses (15W / 16W) are anchored to the 1A subterm for planning.
Fill in Program Manager and Assigned Instructor inline. The Dean is auto-assigned from the course's school and isn't editable. Set the deadline for this subterm once in the stats bar at the top — it applies to every section in the current subterm. Rows turn red when that deadline has passed and no instructor is assigned.
Click Submit to Registrar when a section is ready — the instructor is locked, the row is tagged SENT, and the button swaps to Request Change (which opens a Change Request for any post-submission edit). Click the + to the left of a course code to add another section of the same course (ACC 240 01, ACC 240 02, etc.). New rotation slots are pulled in automatically — use the Re-sync now button in the rotation banner above the page if you want to force an immediate refresh.
| Source | Course | Type of Change | Explanation | Submitter | Approver | Date Received | Action |
|---|
How this view works
This is the Registrar's queue — the only items that appear here are the ones requiring registrar action. Two sources feed in: section submissions from the Term Assignments page (a Dean clicked Submit to Registrar) and change requests that have been Approved & Sent. Everything else stays out of view.
Click Completed on a row when the Registrar has processed it. The row disappears from this page, the action is recorded in the Changelog, and (for change requests) the request transitions to Finalized.
Use the subterm chips to walk through Fall 1A → Spring 3C → Summer; counts on each chip show how many items still need attention.
| Submitter | Date | Level | Modality | Term | Subterm | Course | Change Type | Explanation | Rationale | Actions |
|---|
How the Change Request workflow works
This view mirrors the Schedule Change Google Sheet exactly. Each request captures the same 14 columns: Submitter, Date, Grad/Undergrad, Modality, Term, Subterm, Year, Prefix, Number, Type of Change, Explanation, Rationale, Approved By, Approval Notes. Status transitions add registrar-side fields (Sent date, Processed date, Registrar notes).
Lifecycle:
A Dean or Program Manager submits a request by clicking + New Request (or Request Change on a specific course row in the Rotation view). The Associate Provost then reviews — clicking Approve & Send routes the request directly to the Registrar Queue, or Reject closes it with a reason. The Registrar works from the Registrar Queue chip above the table and clicks Mark Finalized once processed (CRN, section #, etc.). Finalized requests expose an Apply to Rotation button that writes the change back to the course row. All actions are visible in this prototype (no role gating).
When a request reaches Finalized, click Apply to Rotation to write the change back onto the course row in the Rotation view (for add / remove / instructor / location changes).
| Type | Course | Change Requested | By | When (Central Time) |
|---|
How this view works
The Changelog is a chronological feed of every meaningful action that's happened in this scheduler. It pulls from two sources: each section's submission to the Registrar (with timestamp and the instructor that was locked in), and the per-request history entries on every Change Request (creation, approval, rejection, send to registrar, finalize, etc.).
Newest events appear first. Use the search box to find a course code or a person's name, the type filter to narrow to just submissions or just request lifecycle events, and the range filter to focus on recent activity.