Student Progress Update Draft
Student changes stay in progress until the workspace accepts the update.
Fields: requirement, phase, progress, note, and evidence.Workspace workflow guide
A public guide to the signed-in workflow for students, mentors, program teachers, and admins. It explains how private proof, review decisions, revision loops, dashboards, and protected activity fit together; real student records stay inside the Capstone Project Workspace.
Trusted progress state
The workspace separates student drafts, assigned-staff updates, status history, school totals, and refresh states so users know which information is ready to trust.
Student changes stay in progress until the workspace accepts the update.
Fields: requirement, phase, progress, note, and evidence.Mentors and teachers work only with the students assigned to their role.
Checks: account, program, assigned students, and reason.Every accepted change adds to the student record before dashboard counts update.
Records: progress, status history, and submission status.Dashboard totals are derived from saved rows by role and cohort.
Rules: totals link back to the student records a user can view.Out-of-date changes ask the user to refresh and keep the student record protected.
Activity: progress updates, status changes, and protected access reviews.Check the signed-in account and the submitted change.
Apply student, mentor, teacher, or admin boundaries.
Review status move, deadline, and evidence readiness.
Save progress and status history together.
Keep a safe activity trail for who changed what and why.
Refresh counts from saved records only.
Student workspace
The student view stays calm: current phase, one next action, feedback, evidence, and clear resubmission paths.
Problem, sources, quote, counterclaim, and draft saved.
Two uploads and one checked external link.
Proposal approval checkpoint.
Teacher feedback is ready for resubmission.
Teacher feedback asks for a stronger CTE connection, a verified third source, and a final student revision.
Workspace, program, cohort, and access created.
Teacher asked for clearer CTE evidence.
Two sections still need completion.
Unlocks after proposal approval.
Presentation outline opens in Phase 2B.
Submissions
Clarify CTE skill, testing plan, and final evidence.
Two required sections remain before submit.
3 artifacts mapped to proposal and research.
Unlocks after proposal resubmission.
Guided quality engine
Specific audience and project goal.
3 sources attached, one needs access check.
Quote saved; explanation needs revision.
Student started but not submitted.
Required before submit.
Locked while under review.
Feedback present, final revision missing.
Teacher feedback attached.
Needs stronger CTE program connection.
Private proof
Program teacher dashboard
The staff surface is denser: filters, review queue, evidence risks, student counts, revision loops, and direct actions.
Proposal or research challenge submitted.
Students with more than one request.
Missing sources or inaccessible links.
Ready for build-phase check-ins.
Top interventions
Review drawer
Mentor dashboard
Mentors see meeting status, presentation readiness, recent evidence, and comments for assigned students without broad cohort access.
Visible only for active mentor assignments.
Need scheduling or make-up notes.
Outline missing or slot unconfirmed.
Students with fresh evidence to discuss.
Meeting workflow
Mentors see assigned students only. Readiness viewers see explicitly granted dashboards only.
Student can retry, replace, or attach an external link without exposing a public file URL.
Draft fields lock while a reviewer is making a decision, with version history still visible.
Feedback routes back to the exact section that must change before the next submit.
Override requires a reason and records protected activity before state changes.
Empty states explain the missing action, filter, or assignment instead of showing a blank panel.
Admin overview
Admin tools focus on provisioning, assignments, exports, audit events, deadline pressure, and audited overrides.
Sample operational student records.
Assignment gaps before Phase 2B.
Accounts or roles need correction.
Final-file packages awaiting generation.
Program comparison
Evidence access checks
Costing and safety plans
Scope and source accuracy
Materials approval
Learner feedback evidence
Protected activity
Admin / Program teacher -> IT cohort
Program teacher / Assigned student only
Program teacher / Proposal v2
Admin / Student archive
System states
Mentors see assigned students only. Readiness viewers see explicitly granted dashboards only.
Student can retry, replace, or attach an external link without exposing a public file URL.
Draft fields lock while a reviewer is making a decision, with version history still visible.
Feedback routes back to the exact section that must change before the next submit.
Override requires a reason and records protected activity before state changes.
Empty states explain the missing action, filter, or assignment instead of showing a blank panel.
Workspace states
These examples show the kinds of status, access, and follow-up states a school user may see in the workspace.
Workspace boundary
This public guide explains the workflow. Student records, private work, reviews, mentor assignments, and closeout tasks belong in the signed-in Capstone Project Workspace.
School users should sign in from the workspace when they need to review real project information.
Separate account-check pages are reserved for approved workspace verification and are not part of public navigation.