Online course assignments and a gradebook: a practical guide for creators

A video course can show someone how to write a sales page. Only an assignment can show you, and them, whether they can. Assignments turn passive watching into practice, and practice is what learners are paying for when they buy a skill.

They also create a relationship. A learner whose work you have read and commented on is more likely to finish the course, buy the next one and recommend you, because they have had a teacher, not just a library. For many creators that personal touch is the main thing separating a paid course from free videos.

A good assignment is specific, short and checkable. "Write a 150-word product description for one of your offers, using the three-part structure from this lesson" is all three. "Reflect on what you learned" is none of them: it is hard to do well and impossible to review consistently.

Place assignments where the course turns from understanding to doing, usually at the end of a module rather than every lesson. One or two per course is plenty for most creators. Each one should have a one-line success standard you could share with the learner: "Approved if it has a clear headline, one concrete benefit and a call to action."

A rule worth screenshotting: if you cannot write the success standard in one sentence, the assignment is not ready to set.

Batch it. Pick one or two fixed slots a week and review everything waiting, instead of answering each submission as it arrives. Learners can wait a few days for feedback if they know when it comes; say so in the assignment brief.

Use three outcomes, not a score out of 100. Approved means it meets the standard. Revision requested means it does not yet, with one or two specific changes. Reviewed means you have read it and commented, for work that is not pass or fail. Three outcomes are faster to decide and clearer to receive than a number.

Write feedback to the standard. Start with what meets it, then the single most important change. Long lists of edits are discouraging and rarely acted on. If you see the same mistake in many submissions, record a short video for everyone instead of writing it twenty times.

When volume grows, recruit help. Experienced members or graduates can review first drafts, or learners can swap work in a community thread before submitting. Keep the final approval with you, or with someone you trust, if it counts toward a certificate.

School gradebooks track weighted scores across many assessments for report cards. A creator rarely needs that. What you need is a view that answers four questions per learner: have they started, how far through are they, have they finished, and did they earn the certificate?

Add quiz results and assignment status, and you can spot the two learners who matter most: the one stuck at 60% for three weeks, who needs a nudge, and the one who submitted an assignment and is waiting on you, who needs feedback. A gradebook that shows both turns into a weekly to-do list.

Export matters too. If a client company, an employer or an accrediting body ever asks for completion records, you want a CSV, not screenshots.

Minutes 0-5: open the gradebook and note anyone stuck in the same place for two weeks. Minutes 5-40: work through every submission waiting for review, oldest first, using the three outcomes and the one-sentence standard. Minutes 40-50: send a short message to each stuck learner, naming the next lesson rather than asking how they are. Minutes 50-60: post one piece of general feedback in the community, based on the most common mistake you saw.

Run it on the same day each week and tell learners which day it is. Predictable feedback beats fast feedback, because learners plan around it instead of refreshing the page. If the routine starts taking more than an hour, that is the signal to cut an assignment, tighten a standard or bring in a second reviewer.

Skip them in very large, low-priced courses where you cannot realistically review everything. A quiz, a peer-feedback thread or a self-check against a model answer will serve learners better than an assignment you never get to.

Skip a formal gradebook if you run one short course and know every learner by name. And if you teach for a school that reports grades into a student information system, use the institution's LMS; a creator platform is built for a different job.

In HiveLearn, any lesson can carry an assignment with a written prompt and a due window. Learners submit their work as text in the lesson, which can include links to files, documents or portfolios. Instructors review submissions in one panel, filtered by status or lesson, and mark each one approved, reviewed or revision requested. Requesting a revision requires written feedback, and the learner can then resubmit.

The gradebook shows per-student progress across every course: not started, in progress or completed, with a progress bar and certificate status, and it exports to CSV. Assessment, enrollment and activity reports sit alongside it, and member health scores flag learners going quiet before they drop out.

Quizzes in the same course are graded on the server with six question types, so you can use quizzes for knowledge checks and keep assignments for the work that needs a person. Courses, community, events and payments are in one place; see the pricing page for which plan includes these features.