Your syllabus is the most information-dense document you’ll receive all semester. It contains every deadline, every grade weight, and the full shape of a course — yet most students read it once during the first week and never look at it again. The smarter move is to treat it as raw data and process it systematically. Here’s the workflow.
Step 1: Extract the Raw Information
Open your syllabus PDF and run it through a text extraction tool. If the PDF has selectable text, you can paste it directly into a plain-text editor or a tool like ChatGPT, Claude, or Notion AI. If it’s a scanned image, run it through an OCR tool first — Adobe Acrobat’s free web version or Smallpdf both handle this cleanly.
Once you have the raw text, you’re looking for three categories of information:
- Dates and deadlines — every assignment due date, exam date, and drop date
- Grade weights — the percentage each component contributes to your final mark
- Topic clusters — the lecture topics or module themes listed in the weekly schedule
Paste the text into a language model and prompt it explicitly: “Extract all deadlines with their dates, all assessments with their grade weights, and all weekly topics. Format each as a separate list.” A well-structured prompt takes thirty seconds to write and saves you from manually hunting through fifteen pages of policy text.
The output won’t be perfect, but it will be fast. You’ll catch any errors in the next step.
Step 2: Build a Priority-Weighted Timeline
Now you have three lists. The next move is to combine them into a single timeline ordered by date, with grade weight attached to each assessment. This is where the study plan actually forms.
Open a spreadsheet — Google Sheets works fine — and create four columns: Date, Task, Weight (%), and Status. Populate it from your extracted lists. Once everything is in one view, a few things become immediately obvious:
- Which weeks are collision weeks, where multiple assessments land at the same time
- Which assignments carry the most grade weight and deserve proportionally more preparation time
- Where the light weeks are — those are your catch-up and review windows
A midterm worth 35% sitting three days before a group project submission is a different problem than those two things being three weeks apart. The timeline makes the compression visible before you’re inside it.
For topic clusters, map them against the assessment dates. If week six covers the material tested in the week-eight midterm, you know your deep review window is weeks five and six. If the final exam is cumulative, flag every major topic from the weekly schedule as a potential exam item and note the first time it appears.
At this point you have something most students never build: a document that shows you not just when things are due, but how much each thing matters and which content underlies each assessment.
Step 3: Convert the Timeline into a Weekly Study Blocks Plan
A timeline is passive. A blocks plan is actionable. The difference is that a blocks plan tells you what to do each day, not just what’s coming.
Take your priority-weighted timeline and work backwards from each assessment. For a midterm in week eight worth 35%, you might allocate:
- Week five: first read of relevant lecture notes
- Week six: practice problems or past papers
- Week seven: review gaps, consolidate notes
- Week eight, day before: light review only
The exact split depends on the subject and your baseline familiarity, but the structure is the same for everything. High-weight assessments get longer runways. Low-weight quizzes get a single preparation block the day before.
For recurring tasks — weekly readings, problem sets, participation — block a fixed slot each week so they don’t accumulate. The goal is to make each week’s workload visible on Sunday night, not discoverable on Wednesday morning.
If you use a calendar app, create events for the study blocks, not just the deadlines. Deadlines without preparation blocks are wishes. Blocks on a calendar are commitments.
One practical note: build in a fifteen-minute buffer at the end of each week to review the plan and adjust. Syllabi change, professors add readings, group project timelines slip. A plan you update weekly is still a plan. A plan you abandon after the first change is just a document.
Selene takes exactly this structured output — the extracted dates, weights, and topic clusters — and uses it to generate personalized study schedules and content explanations timed to your actual assessment calendar. Hand it your syllabus data and it builds the runway for each assessment automatically, so you can spend your time studying instead of planning.