Education & TrainingFree
Student Workload Calculator for Courses
Send the reading list, the assignments and the week-by-week plan, and get estimated student hours against the credit hour expectation.
Every student workload calculator for a course does the same division. Total pages over a reading speed, plus assignment hours, over the number of weeks. It produces an average, the average looks defensible, and the syllabus goes to the committee. The problem is that no student experiences an average. They experience week six, and a calculator that reports a semester mean cannot tell you that week six is more than twice the budget.
HIST 342 is a three-credit, fifteen-week course. The federal definition of a credit hour is one hour of instruction plus a minimum of two hours of out-of-class student work each week, so the out-of-class budget is six hours a week and 90.0 hours across the term. The reading list is 480 textbook pages at 20 pages an hour, 300 monograph pages at 12, and 90 pages of journal articles at 6, which is 64.0 hours. Assignments add 35.0.
That is 99.0 hours against 90.0, or 1.10 times the budget. Ten percent over is the kind of number that passes review. Week by week it reads 4.0, 5.0, 5.5, 5.5, 6.0, 13.5, 4.5, 9.0, 4.5, 5.0, 5.5, 5.5, 14.0, 4.5, 7.0. The median week is 5.5 hours, comfortably under the cap. Week 13 is 14.0 hours, which is 2.33 times the weekly budget, and four of the fifteen weeks sit above it. The average was never the constraint.
Nineteen and a half hours of excess against ten and a half hours of slack
Once the weeks are separate the fix stops being a matter of moving things. Add up how far the four heavy weeks sit above the six-hour cap and the excess is 19.5 hours. Add up the unused room in the eleven light weeks and the slack is 10.5 hours. Redistribution can absorb 10.5 of the 19.5, and the remaining 9.0 hours have to come out of the course rather than move around inside it. That 9.0 is exactly the amount the semester total was over.
The three heaviest weeks carry 36.5 of the 99.0 hours, which is 36.87 percent of the term in three weeks out of fifteen. Two of those weeks stack a paper deadline on top of a reading block that was already the densest in the course. Neither of them is visible in a total, a mean or a page count, and both are the weeks students describe on an evaluation without being able to say which week it was.
Reading rates are the input the whole estimate turns on, so the output prints them rather than burying them. Twenty pages an hour for a textbook, twelve for a monograph and six for dense primary material are assumptions, and reading the monograph two pages an hour faster moves the term total by 3.57 hours. Institutions vary here, and where the calendar itself is unusual the minimum of 30 weeks of instructional time in an academic year is the outer frame the credit hour sits inside.
How it works
Send the syllabus
The reading list and assignments with the week each one is assigned or falls due.
Set the rates
A reading rate per genre of material, stated explicitly rather than averaged into one figure.
Build the weeks
Hours attributed to the week the student does the work, not the week it is listed.
Compare to the cap
Every week against the credit hour expectation, with excess and slack totalled separately.
What you get
- Estimated student hours for every week of the term, not a semester average
- Every single week measured against your own institution's published credit hour expectation
- The reading rate used for each genre of material, printed as an assumption
- The overload weeks named, with what stacked in each one to cause it
- Excess above the weekly cap against available slack, so you know what must be cut
- A change list that levels the term, with the hours each change actually saves
Common questions
Is a reading rate not too crude to build an estimate on?
It is crude, which is why the output prints the rate it used on every line rather than hiding it in a total. One rate for all material is what makes an estimate useless. Twenty pages an hour of textbook and six of dense primary source differ by a factor of more than three, and a course that mixes them is misestimated by any single number.
Why does the weekly view change the answer so much?
Because the constraint is weekly and the total is not. HIST 342 is 1.10 times its budget on the term and 2.33 times on week 13. A student can absorb a ten percent overrun spread evenly. What they cannot absorb is 14.0 hours in the week two other courses also set deadlines, and that week is invisible in every average.
Does this tell me what to cut?
It tells you how much has to come out and where the room is, then proposes a change list with the hours each change saves. Which reading matters is your judgement and your discipline's. The syllabus template is where the resulting schedule gets written down, and the outcomes it serves stay fixed while the hours move.
What if my institution publishes a different expectation?
Then it is the one used, and the output says which figure it applied. Some institutions publish three hours of out-of-class work per credit hour, some express it as total hours per term, and some vary it by level. The federal two-hour minimum is the default only when nothing else is supplied.
Does it work for an online or asynchronous course?
Yes, and it matters more there, because there is no timetabled contact hour anchoring the estimate. Everything becomes out-of-class work, so video, discussion posts and quizzes all need hours attributed to a week. Converting a course to online delivery is the companion when the structure itself is changing rather than the load.
How does this relate to designing the course in the first place?
Workload is a constraint on design rather than an output of it. The course design pack carries the alignment from outcomes through activities to assessment, and this is the check that the resulting plan fits in a week. Running it before the syllabus is published is considerably cheaper than running it after.
Can it account for students taking three courses at once?
Only if you send the other courses' calendars, and then it stacks the weeks and reports the combined figure. Programme-level clashes are the most common cause of a week nobody planned. Without that data it reports this course alone and says so, rather than guessing at a cohort's total load.
Student Workload Calculator for Courses
Fill in the form and your workspace opens with the work already underway.