This student dashboard template links each assignment to its instructions, file version, submission receipt and any redo request. It gives you a concrete next action while preserving unknown status instead of inventing a missing submission or grade.
Build a personal register with source references
Instructure's Canvas guide distinguishes submission-related activity from graded feedback and explains that a reassigned item marked Redo requires resubmission. Use that distinction for the personal register below; it is an original planning record rather than a copy of Canvas's dashboard or completion rules. Canvas List View Dashboard guide
Use the course and assignment IDs together so similarly named work in different courses stays distinct. Keep a snapshot date beside status. This fictional example is as of October 13, 2026, using date-only due dates.
| Course / assignment | Due date | File/submission evidence | New instruction | Personal review status |
|---|---|---|---|---|
| C01 / A01 | October 12 | v1 submitted October 11; receipt S01 | R01: redo requested October 13 | New submission pending; prior receipt retained |
| C01 / A02 | October 13 | Fixture explicitly says not yet submitted; no receipt supplied | Actual instructions need review | Due today; submission pending |
| C02 / A03 | October 14 | Draft file F03 only | Actual instructions need review | Future due date; draft is not submitted evidence |
| C02 / A04 | October 12 | Submission status unknown; no source export supplied | Actual status source needs checking | Unknown; do not infer failed or missing work |
These are four unique fictional assignments, not actual students or courses. No grades are supplied. Date-only comparisons support “due today,” “future date” and “past date” planning labels; they do not establish a time-zone cutoff, late penalty or instructor policy.
Keep the redo chain intact
For A01, preserve v1 → S01, October 11 and link the later R01, October 13 beside it. S01 supports the prior version's submission. It does not prove that the newly requested version has been prepared, submitted or accepted.
The next action is to confirm R01's requirements and redo deadline, then prepare the new version. The new deadline is TO CONFIRM; do not reuse October 12 as if it automatically governs the redo.
Add blank fields for revised file/version, actual new submission receipt, submission date/time and remaining instructor feedback. A new draft can fill the file field without filling the receipt field. Only record the new submission when its actual source evidence is available.
Give each row a useful next action
| Assignment | Proposed student-owned next action | Evidence to retain afterward |
|---|---|---|
| A01 | Check redo requirements/deadline, then prepare a new version. | R01 clarification, revised file and eventual new receipt |
| A02 | Check actual instructions and submit through the approved LMS route when ready. | Correct file/version and actual submission receipt |
| A03 | Finish F03 against the actual instructions. | Updated draft; later receipt only if actually submitted |
| A04 | Check the actual LMS/receipt source to determine submission status. | Retrieved status or receipt reference, or an unresolved question |
These are proposed actions, not completed transactions. Keep the actual outcome, source reference and follow-up blank until you act. An absent export for A04 means the register lacks evidence; it does not prove that you failed to submit.
Review files, receipts and feedback separately
Use a maintained record with fields for course/assignment, instruction reference, date-only due date, actual due time/zone if confirmed, current draft reference, submitted version, receipt, feedback/redo reference, next action and actual outcome.
Do not collapse those fields into a single “done” checkbox. A draft indicates work exists. A receipt supports a specific submission. A grading record, if supplied later, is another source. A redo request creates a new action even while the prior receipt remains valid history.
Before relying on a dashboard row, ask:
- Does this receipt match this assignment and file version?
- Is there newer instruction or feedback that changes the next action?
- Is the status explicitly supplied, or simply absent from this export?
- Have I confirmed the actual deadline and submission route?
Keep permitted course records in the systems your institution authorizes. This template has no actual LMS connection, automatic upload, reminders or saved submission status.
Copy this prompt for the personal dashboard
Prepare an original US-English personal cross-course assignment register, file/receipt/redo matrix and blank actual next-action form. Do not mimic an LMS interface, submit assignments or invent grades. Snapshot October 13, 2026; date-only deadlines do not establish late penalties, due-time zone or policy. Actual instructions/deadline windows/routes TO CONFIRM.
Four fictional rows:
C01/A01 due October 12, v1 submitted October 11 with receipt S01. Instructor R01 requests redo October 13. Preserve prior receipt; new submission pending. Confirm redo requirements and new deadline, then prepare revised version. No new file/receipt supplied.
C01/A02 due October 13, explicitly not yet submitted in fixture, no receipt. Due today/pending; check actual instructions and approved LMS submission route.
C02/A03 due October 14, draft F03 only; future due date, draft not receipt. Finish draft against instructions.
C02/A04 due October 12, status unknown because source/export absent; do not mark missing, failed or zero grade. Check actual receipt/status source.
Use unique course-plus-assignment identity. Link instruction, due date and confirmed time/zone, draft file, submitted version, receipt, feedback/redo, proposed next action, blank actual outcome and evidence. For A01 show v1/S01 history separately from R01 and blank revised file/new receipt. A prior receipt does not fulfill redo; draft does not prove submission; submission does not prove grading. Keep actual new actions/results blank. No actual student data, LMS integration, uploads, sends, notifications, persistence or automatic completion. Native maintained assignment and source records authoritative.
Review the next action beside the receipt
An optional prepared HTML review in NOS can put the four assignment rows beside their receipt, draft and redo references. NOS supports saving and rendering HTML. Keep the maintained register and actual course/LMS records authoritative; the review does not submit work or update the course system.
Explore NOS to present the prepared assignment review. Leave with the right next action for each version, including the row whose status still needs checking.