Our University Switched to Week-Based Scheduling — Half the Students Showed Up on the Wrong Day

Three years ago, my university decided to modernize course scheduling. Instead of listing calendar dates on every syllabus — "October 7, October 14, October 21" — they'd use semester week numbers. "Presentations: Week 4." "Midterm: Week 8." Everything clean, everything standardized.

I was a teaching assistant for a cross-department course. Half the students were from the engineering school. Half from the business school. Same syllabus. Same schedule. Same LMS page.

On the Tuesday of what I thought was Week 4, I walked into the lecture hall at 9 a.m., ready to grade 28 team presentations. The room was set up. Projector was on. Grading rubric was printed.

Five students showed up. None of them were presenting that day. They were just there to watch.

I stood at the front of an empty theater for fifteen minutes, refreshing my email, wondering if I had gotten the date wrong. I hadn't. The date was right. The week number was wrong — for half the class.

The Week 0 problem nobody thought to clarify

Here's what happened. The business school's academic calendar treated orientation week as Week 0. Teaching started in Week 1. Under their system, "Week 4" was the fourth week of actual classes — seven days later than what the engineering school thought.

The engineering school counted differently. Their calendar started with Week 1 on the first day of the semester — orientation and all. No Week 0. So their "Week 4" fell seven days earlier.

Both departments had used week numbers for years internally. It had never been a problem because they rarely shared courses. But this one course — this one syllabus that said "Presentations: Week 4" — exposed a gap nobody knew existed.

Half the business students had already presented their projects. To an empty room. They filmed themselves on their phones and sent me the videos, confused and annoyed. The other half — the engineering students — were still a week away from what they thought was their deadline, calmly polishing slides while half their classmates had already finished.

"The syllabus said 'Presentations: Week 4.' Two departments had two different Week 4s. Nobody noticed until the room was empty."

This happens more than anyone admits

After that disaster, I started asking around. I talked to TAs in other departments, program coordinators, even people at other universities. Turns out, academic week numbering is a quiet mess, and almost nobody talks about it.

Here's what I found:

Some schools start counting from the first day of classes. Week 1 is when teaching actually begins. Orientation, reading days, and administrative periods don't count.

Other schools start from the official semester start date — the Monday the university declares as "semester begins," even if no classes happen until Wednesday. That three-day offset cascades across all 16 weeks.

Then there are the LMS platforms. Canvas, Moodle, Blackboard — they each have their own week-numbering logic. Canvas starts counting from the course start date you set. Moodle counts from the first Monday of the course. If the registrar's Week 1 and the LMS Week 1 disagree — and they often do — students see one number on the syllabus and a different number on their dashboard.

And if you have international exchange students? The confusion compounds. A German student's internal sense of "Week 41" is ISO 8601. An American student's is the US standard. An Indian student might be used to yet another system. Then you layer on top of that a semester-week offset — "this is Week 4 of the fall term" — and you've got three layers of potential misalignment before anyone even opens the syllabus.

What the registrar told me (that I still think about)

I went to the registrar's office the day after the empty lecture hall. Sat down with someone who'd been there 20 years. I explained the whole thing — the two departments, the orientation week, the split class.

She listened, nodded, and then said something I've never forgotten: "We switched to week numbers to reduce confusion. We created about three new kinds of confusion in the process."

She wasn't defensive about it. She was just honest. The old system — listing every date — was tedious and error-prone when manually typed. But it had one advantage: a date is unambiguous. March 7th is March 7th in every department, every country, every system. "Week 4" is not.

What I started doing after that semester

For the rest of that term, I added one thing to every announcement and every syllabus update: the actual calendar date range, in parentheses, next to every week number.

"Presentations — Week 5 (Oct 3–7)"

"Midterm review — Week 8 (Oct 24–28)"

"Final project due — Week 15 (Dec 12–16)"

It felt redundant. It was redundant. That was the point. Everyone owns a calendar. Not everyone agrees on what "Week 5" means. The redundancy was a bridge between two systems that didn't talk to each other.

We eventually got the department to add a line to the standard syllabus template: all week numbers must be accompanied by the Monday–Friday date range. It took three semesters of bringing it up at curriculum committee meetings, but they did it.

I also started using a week number calculator when building course schedules. I'd look up the ISO week numbers for the semester dates, write those into the master timeline, and cross-reference against what the LMS was displaying. More than once, I caught a mismatch before the first day of class.

The real lesson: week numbers need a date anchor

Here's what I've come to believe after all of this: week numbers are useful. They make schedules easier to read, easier to plan, easier to scan. "Chapter 4 due Week 6" is cleaner than "Chapter 4 due October 14." I get why universities use them.

But a week number without a date anchor is a trap. It assumes a shared definition that, in practice, almost never exists across departments, platforms, or countries.

These days, when I see a syllabus that just says "Week 8" with no date, I know with certainty: someone is going to miss something. They always do.