Skip to content

Submission

Element · All elements
Evidence · 11 claims (5 for, 5 mixed, 1 against) · 14 studies (4 review, 3 associational, 3 theoretical, 2 causal, 1 qualitative, 1 design), q1–q3 · 1 of 14 report an effect size · 8 claims rest on one study

Description

Submission is the act of learners delivering completed or in-progress work for evaluation, feedback, or peer review. It functions as a structured checkpoint that makes learning visible to instructors and to learners themselves, converting private effort into an assessable artifact.

Design Implications

Submission creates the accountability structure that makes practice productive: work that must be completed and shown is worked on more deliberately than work that is optional [~M]. Its learning value depends less on the act of handing work in than on what follows — timely, specific feedback and opportunities to act on it. Frequent low-stakes submissions outperform infrequent high-stakes ones, because regular checkpoints support self-monitoring and error correction before misconceptions consolidate Self-monitoring improves self-regulated learning outcomes. [+M].

Context

Requirements

  • Clear criteria or rubrics so learners know what "good" looks like before submitting (Assessment aligned to goals)
  • A feedback loop: submission must be followed by Feedback the learner can act on, ideally with a revision opportunity
  • Deadlines and cadence that match the pacing of the learning tasks — frequent enough to catch problems, spaced enough to allow substantive work
  • Low stakes early, higher stakes later, so early submissions invite risk-taking rather than defensive minimalism

Constraints

  • Submission without timely feedback becomes a bureaucratic ritual; work handed in and returned weeks later produces little learning [-M]
  • High-stakes single submissions promote procrastination and surface compliance rather than mastery; learners optimize for the grade, not the learning [~M]
  • Overly frequent submissions can crowd out time for deep work and increase anxiety, particularly for novice learners still building confidence [~W]
  • In large-enrollment settings, feedback capacity often cannot keep pace with submission volume, degrading the entire cycle

Target Learners

Target Learning Goals

  • Competency demonstration: producing evidence that a skill or standard has been met
  • Self-regulation: deadline-driven planning, monitoring, and revision cycles
  • Quality improvement: iterative refinement of work through feedback and resubmission

Affordances

  • Assessment for Learning — submission is the mechanism by which assessment becomes formative: the artifact gives both teacher and learner something concrete to evaluate against criteria, closing the gap between current and target performance
  • Competency-Based Assessment — submissions serve as the evidence base for competency decisions; learners submit when ready rather than on a fixed schedule, and resubmit until the standard is met
  • Active Learning — a submission requirement converts passive consumption into production; learners must generate an artifact, not just attend or read
  • Mastery Learning — paired with resubmission policies, submission enables the mastery cycle of attempt, feedback, correction, and re-attempt until proficiency is demonstrated

Claims

The evidence by question

  • Assessment — the evaluative frame that gives submission its criteria and stakes
  • Feedback — the response that makes submission worth doing; submission without feedback is bookkeeping
  • Revision — the follow-on action that converts feedback into learning
  • Check-ins — lightweight, low-stakes submissions that surface progress and problems early
  • Coaching — the human support that interprets feedback and guides revision
  • Student-made glossary assignment for MATLAB syntax

Patterns That Use This Element

Examples

GitHub — Pull requests are submissions in a professional context: work is submitted for review, receives line-level feedback, and is revised before merging. The model has been widely adopted in computing education.

Canvas / Moodle assignment workflows — LMS submission points with rubrics, due dates, and resubmission settings operationalize the submit–feedback–revise cycle at scale.

Writing process portfolios — National Writing Project approaches use staged submissions (draft, peer review, revision, final) so that submission is a checkpoint in a process rather than a terminal event. - Iterative post-teaching analysis with rubric-aligned written feedback and revise-and-resubmit cycles - Using Mathspace workflows to provide timely, mastery-oriented feedback on student work - Assess process over product using staged, connected tasks with iterative evidence - Develop papers through successive preliminary presentations to gather peer feedback before journal submission

Key Sources

  • Black, P., & Wiliam, D. (1998). Assessment and classroom learning. Assessment in Education: Principles, Policy & Practice, 5(1), 7–74. doi:10.1080/0969595980050102
  • Hattie, J., & Timperley, H. (2007). The power of feedback. Review of Educational Research, 77(1), 81–112. doi:10.3102/003465430298487
  • Guskey, T. R. (2007). Closing achievement gaps: Revisiting Benjamin S. Bloom's "Learning for Mastery." Journal of Advanced Academics, 19(1), 8–31. doi:10.4219/jaa-2007-704
  • Zimmerman, B. J. (2002). Becoming a self-regulated learner: An overview. Theory Into Practice, 41(2), 64–70. doi:10.1207/s15430421tip4102_2
Page metadata
Field Value
type element
id submission
title Submission
description Learners submit work for assessment, feedback, or peer review at structured checkpoints.
status review
canonical True
generated by claude/unspecified on 2026-08-29
trust unverified — no one has confirmed this page's content

Frontmatter is the page's machine-readable record — see the Schema & Guide.