The Fresher's First 30 Days: A Starter Study Plan for New University Students

<p>University reading is not the same as reading, and most students lose whole terms to the difference.</p> <p><strong>Reading for information.</strong> You want the shape of an argument: what the author claims, what evidence they use, what they assume. Speed matters more than detail. Skim first — abstract, introduction, headings, conclusion — then read the sections that look load-bearing.</p> <p><strong>Reading for argument.</strong> You are reconstructing a claim you could defend or attack in a tutorial. You need the evidence, not just the conclusion, and you should write as you read.</p> <p><strong>Reading for reference.</strong> One specific thing — a definition, a theorem, a date. That is what reference books and search tools are for.</p> <p>Most assigned reading is the first kind. Some is the second. Almost none is the third, yet students spend hours on reference material because it feels like studying.</p> <h3>The lecture-to-review-time ratio</h3> <p>A rough, tested rule: <strong>for every hour of lecture, plan two hours of independent work.</strong> One hour preparing the next lecture, one hour reviewing the last. If a module has 10 lecture hours a week, that is 20 hours of independent work — which sounds brutal until you realise reading is not the same as sitting at a desk staring at a wall.</p> <table><thead><tr> <th>Situation</th><th>Lecture hours</th><th>Independent hours</th><th>Weekly total</th><th>Realistic?</th> </tr></thead><tbody> <tr><td>Reading-heavy humanities module</td><td>10</td><td>25–30</td><td>35–40</td><td>Yes, if you read on paper and take notes actively</td></tr> <tr><td>Stem module with problem sets</td><td>12</td><td>24–30</td><td>36–42</td><td>Yes, if problem sets are done weekly, not in a rush</td></tr> <tr><td>Assessment-heavy final-year module</td><td>8</td><td>30–40</td><td>38–48</td><td>Yes, but term-time pressure rises</td></tr> <tr><td>Group project module</td><td>6</td><td>20–25</td><td>26–31</td><td>Yes, plus meeting time you cannot control</td></tr> <tr><td>Part-time or employed</td><td>5</td><td>12–15</td><td>17–20</td><td>Yes — cut lecture replay, keep reading</td></tr> <tr><td>Week 11, revision term</td><td>6</td><td>35–50</td><td>41–56</td><td>Only if the term started on time</td></tr> </tbody></table> <p>The ratio is not about precision. It is that students under-budget independent work, then blame themselves at the end. Budget it up front.</p> <h3>The three ways a week can go</h3> <p>Every week goes one of three ways, and the difference is almost always whether you read <strong>before</strong> the session that needed it.</p> <p><strong>Week type A: prepared.</strong> You read before the lecture. The lecture confirms what you already half-know, the tutorial feels like a conversation, and you end with notes you will actually use. Cost: 2–3 hours of reading per module per week.</p> <p><strong>Week type B: reactive.</strong> You did not read. The lecture introduces new material at speed, you understand perhaps 40 per cent in the room, the tutorial asks questions you cannot answer, and you spend Sunday reconstructing the lecture from slides. Cost: 8–10 hours, and you still understand less.</p> <p><strong>Week type C: detached.</strong> You did not read, the lecture went over your head, you avoided the tutorial, and you have decided this week will be reclaimed later. It will not be. Cost: 2 hours of avoidance now, then 15 hours of catch-up in week seven plus guilt.</p> <blockquote><p>You do not need to understand everything. You need to understand enough to ask a useful question.</p></blockquote> <p>The rule is unglamorous: <strong>read before the session, always, even if the reading is only twenty minutes.</strong> Pre-reading converts a type B week into a type A week more reliably than any note-taking technique.</p> <h3>How to read a chapter in 30 minutes</h3> <ul> <li><strong>Read the abstract, introduction and conclusion (5 minutes).</strong> Write the single sentence that says what this chapter argues.</li> <li><strong>Scan the headings (2 minutes).</strong> Turn them into questions: "Why does the author say this here?"</li> <li><strong>Read the section that matters most (15 minutes).</strong> Slow down. Underline only what you would want to quote in an essay.</li> <li><strong>Write three lines of your own (5 minutes).</strong> Your words, not the author's. If you cannot write three lines, you have not understood it.</li> <li><strong>Note one question (3 minutes).</strong> For the tutorial or the next lecture. This is the highest-return habit in this guide: <strong>one question per session, 8–10 per week.</strong></li> </ul> <p>That is 30 minutes per chapter. Three modules and two readings each is 3 hours a week. It fits.</p> <h3>Managing the readings you will not finish</h3> <p>You will not finish everything. Every student does not finish everything. The design problem is deciding what to skip without getting caught.</p> <ul> <li><strong>Always do:</strong> the section the lecture covers, the extract quoted in the reading list, anything the lecturer has singled out.</li> <li><strong>Do if you can:</strong> the recommended primary text, in order.</li> <li><strong>Skip if you must:</strong> supplementary and "further reading" items — genuinely optional until essay-writing week.</li> <li><strong>Never skip:</strong> the assignment instructions, the mark-up of the assessment criteria, the week-1 and week-2 slides.</li> </ul> <h3>What to do in the 10 minutes after a lecture</h3> <ul> <li>One line: what today's session was about.</li> <li>Three keywords or terms you did not understand.</li> <li>One question to bring to the next session.</li> </ul> <p>Three lines is enough. Anything more and you will stop doing it.</p> <blockquote><p>Notes are not a transcript. Notes are a set of handles you can use to pull the full idea back later.</p></blockquote>