Run the learning platform
The work behind the count.
Inspect example learner records, with drafts, submitted versions and published reviews kept distinct.
Submitted work and review state
Selected learner records. These six examples are a sample of the 66-person fictional program.
| Learner | Classroom | Submitted versions | Reviewed | Latest work |
|---|---|---|---|---|
| Jordan Lee ↗ | Python Lab | 7 | 6 | Revision submitted |
| Liam Chen | Python Lab | 8 | 7 | Ready for review |
| Avery Morgan | Python Lab | 6 | 6 | Working on a draft |
| Noah Rivera | Web Studio | 8 | 8 | Feedback published |
| Riley Brooks | Web Studio | 7 | 5 | Ready for review |
| Alex Kim | Idea Lab | 5 | 5 | Revision requested |
- 01
Draft
Work in progress has its own state.
- 02
Submitted version
The learner commits a version for review.
- 03
Published feedback
The review remains associated with that submitted version.
- 04
Revision
A later submission adds history instead of erasing it.
What this part of Arc does
- Classroom and status filters; supported format tabs
- Grouped work with format-specific presentation
- CSV format exports and a full Excel export
- Version and review context is preserved separately
This is a browsable portfolio interpretation of Arc’s workflows with fictional examples. Navigation, filtering and theme previews work here; editing, execution and platform services belong to the original application.
Inside the original application.
Real Arc screens and recordings, captured locally with fictional people and work.
Feedback beside the original work
The instructor reads a student response and writes a concrete next step in the same review panel.
A clear reason to try again
The student receives the revision request alongside the previous version, with a direct path to improve the answer.
Watch this workflow in Arc
From a first idea to a stronger second version
A real student submission, an instructor’s revision request, and an improved answer - with both versions preserved.
Read the walkthrough
- Submit a first idea
A fictional student writes a first response and submits version 1 of the activity.
- Turn feedback into a clear next step
The instructor reads that response, publishes actionable feedback and requests a revision.
- Improve the work. Keep both versions.
The student reads the feedback and submits an improved version 2, preserving the first submission.
Source references & review notes
app/Platform/Portals/Admin/Controllers/AdminSubmissionsController.phpapp/Platform/Portals/Admin/ViewModels/AdminSubmissionsViewModel.phpapp/Platform/Portals/Admin/ViewModels/AdminSubmissionGroupPresenter.php
Source reviewed at development revision 5549bf96. Original captures have their own pinned revisions; the live platform has a separate release.