A syllabus gets treated as a reading list — a document to highlight once in week 1 and forget until finals. But the objectives page is the contract: it's the professor's public list of what you'll be asked to do, written in verbs. "Discuss ethical limits of A/B tests" isn't a topic to read about; it's an operation to perform, and the exam will score the performance.

The conversion is to a mastery map. List every objective, then rewrite each as a stem you could fail — a concrete prompt where a wrong answer is possible, not a topic heading. Group them by week, attach re-test dates, and work backward from the exam so every objective gets at least two retrievals. The map is done when every objective has evidence attached — a stem that produced an answer — not when the PDF is highlighted.

Why highlighting the syllabus fails

Highlighting the syllabus PDF is a week-1 ritual that produces a decorated document — the objectives get read, marked, and never touched again because the highlighting is the only interaction they get. The map that should be built from them never is: by finals week the syllabus is a list of things seen once, not a checklist of things proven. Familiarity with the document substitutes for mastery of the objectives.

Mastery is performance you can show again later — the definition that makes the re-test dates the point, not decoration. An objective is mastered when a stem derived from it produced a correct answer on two spaced attempts, which is evidence; a highlighted line is a claim. The syllabus-to-map conversion turns "topics I've seen" into "operations I've proven," which is the only list that predicts the exam.

The syllabus-to-map workflow

List every objective, then rewrite each as a failable stem. "Discuss ethical limits of A/B tests" becomes "A company ships a pricing test to 5% of users without notice — using the three-limit test, is this allowed?" The stem is concrete enough to be wrong: it demands the operation the objective names, not the topic it gestures at. An objective that can't become a failable stem is too vague to study — sharpen the verb first.

Group the stems by week, then attach dates. The week grouping matters less than the spacing: each stem gets a first attempt and a re-test 3–7 days later, on a calendar that works backward from the exam date. Late-term objectives get flagged specially — they're the ones that get read once and never retrieved, because they arrive too close to finals for a second pass unless the map schedules it.

Work backward from the exam, not forward from week 1. The syllabus's week order is a teaching order, not a study order. The map starts at the exam date and lays retrieval events backward — which is why the last weeks' objectives, the ones everyone leaves unread, get two scheduled retrievals instead of a panicked first read the night before.

A stem with an answer is evidence; a stem without one is a gap. The map's state is visible: which objectives have produced correct answers, which produced misses still on the re-test schedule, which never got attempted. That visibility is what makes it a map instead of a list — the coverage is checked, not assumed.

A 40-minute session on the clock

The weak answer leaves the objective as reading — "the night before" is the leftover-treatment that week-11 topics always get, one exposure with no retrieval. The strong answer does both conversions: the objective becomes a concrete, failable stem (a scenario demanding the three-limit test), and the stem gets two spaced dates that still fit inside the 21 days. The late-term objective that would have been leftover reading becomes evidence with a schedule.

Why the last weeks are always the weakest

Week 1 material gets months of ambient review — it comes up in office hours, in later lectures, in the reading you do for later topics. Week 11 material gets nothing: it arrives last, is freshest in lecture memory, and gets skipped in favor of "the stuff I haven't looked at." The result is a predictable collapse — strong on the early objectives, blank on the late ones, which is backwards from where the exam's hardest synthesis questions live.

The map fixes this by making the schedule visible rather than assumed. When every objective has a stem and two dates, the week-11 objectives can't silently become leftover reading — they're on the calendar with the same status as week 1. The backward-from-the-exam layout is what protects them: the spacing requirement means the last material gets scheduled first, not last.