Designing scored and non-scored learning activities with clearer completion logic

Completion is not the same as achievement

Opening a PDF, watching a video, submitting an essay and passing an exam represent different kinds of progress. Treating all of them as a generic complete state creates misleading records and confusing learner experiences.

A sound model separates engagement, submission, review, score and approval.

• Viewed or engaged
• Submitted for review
• Awaiting scoring
• Graded or approved
• Passed, incomplete or requires revision

When manual completion is appropriate

Manual completion works for non-scored activities where the learner is confirming engagement, such as reading a note or completing an optional reflection.

It should not allow a learner to override a required score, educator decision or approval rule.

Submission should create a protected state

After a learner submits an essay, project or assignment, the activity should move to submitted or awaiting scoring. A second final submission should only be available when revisions or resubmission are explicitly allowed.

Keeping the submitted version stable protects the assessment record and gives educators a reliable queue for marking.

Grades belong to authorised roles

Learners may view grades and feedback but should not be able to write or alter scoring fields. Educators need clear marking tools and an audit trail for significant changes.

Automated assistance may prepare suggestions, but the authorised human remains responsible for the final score where policy requires it.

Use status language consistently

Define a small status vocabulary and apply it across cards, detail pages, dashboards and notifications.

Test every transition: assigned, started, submitted, awaiting scoring, graded, revision and final approval. The workflow is clear only when every state has an appropriate next action.

• Document allowed transitions
• Test learner and educator accounts
• Lock final submissions appropriately
• Show the next authorised action