Syllabus week. Four PDFs landed in two days and you scrolled to the grading table on each one and closed it.

Here is the thing about those four documents. Every one of them was written as if it were the only class you take. Not because your instructors are careless. Because none of them can see the other three. I write syllabi. When I build mine I am looking at my course, my outcomes, my fourteen weeks. I have no idea who else is on your schedule.

So four people, working in good faith, in four different buildings, picked four sets of dates. Nobody stacked them.

The stack already exists. Somewhere in October there is a week holding three things, maybe four. It has been scheduled since before you arrived. The only reason it feels like a surprise in October is that the information was spread across four PDFs and nobody put them side by side.

Two things worth knowing before you look.

Your collision week is almost never the week you would guess. You guess from fear, so you predict the week your hardest course peaks. But a collision is not made by your hardest course. It is made by three ordinary courses landing in the same seven days. The class you are not worried about is the one that ruins the week.

And the move that fixes it expires. Taking one item out of that week and starting it early costs about two hours in August. It costs two hours you actually wanted in late September. In the collision week itself it costs nothing, because there is no early left.

The Collision Map is today's free working session. Every dated item from every syllabus onto one page, the collision weeks marked, and one decision written down. By hand, no account, nothing saved, nothing sent.

https://www.harvestkernel.com/the-collision-map/

Then tell me, because I actually want to know:

Which week on your calendar has three things in it? Month and week, one line. That is the whole question.