How to Think About a Term as a System, Not a To-Do List
How to Think About a Term as a System, Not a To-Do List
There's a moment, usually around week six, where the term gets ahead of you. You meant to keep up with reading. You meant to start the paper early. Now you've got a midterm on Friday, a problem set due Wednesday, and the syllabus you skimmed in week one feels like it was written for a different person.
Most students respond to this with a to-do list. Sometimes a really nice one — color-coded, in three apps, with a Sunday-night planning ritual on YouTube. The list helps for about a week. Then a deadline shifts, a topic takes longer than expected, and the list ceases to reflect reality.
The problem isn't your list-making. It's that a term isn't a list. A term is a system: courses connected to assessments, assessments connected to dates, topics that build on each other, energy that has to be allocated. Treating it like a to-do list is like trying to fly a plane by reading off a checklist of altitudes — technically related to flying, but missing the part where everything affects everything else.
Here's how to think about the system. And, since this is the Fennie blog, here's where most of the work gets done for you.
The four objects that actually matter
Forget productivity frameworks. The mental model for a term has four pieces, in this order:
The syllabus. This is the truth source. Every assessment, every weight, every topic, every deadline traces back to it. Most students never reread the syllabus after week one, which is why they're surprised in week eleven when the final paper is worth 40%.
The calendar. Every assessment from every syllabus, on one surface, sized by weight. A 5% quiz and a 30% midterm shouldn't take up the same square. They almost always do, in students' heads.
The topic map. Each course breaks down into roughly 8–14 topics. Some are foundational (everything later depends on them). Some are isolated. Some are heavy. Knowing which is which is the difference between studying smart and studying long.
Your memory. What you actually know, distinguished from what you've seen. The honest version of this is uncomfortable. Most students never produce one.
A term goes well when these four are in sync. It goes badly when one is missing. The number-one cause of bad finals weeks isn't laziness — it's a missing or stale topic map. You can't decide what to study tonight if you don't have a clear picture of what the term contains.
Sunday evenings, before they get sad
The single highest-leverage habit in academic life is the Sunday evening planning session. Twenty minutes. Lukewarm coffee. The week ahead.
Done well, it looks like this:
- What's due this week? What's looming next week?
- Where am I weakest right now, by topic, by course?
- What's the one thing that, if I don't do it this week, will hurt me most in two weeks?
- What do I cut?
That last question is the one most students skip. Every term has more material than time. The strategic question isn't "how do I get it all done." It's "what gets less of me this week so the important thing gets more."
A pre-med studying for the MCAT in the spring while taking biochem and physics II shouldn't be running both courses at full intensity in the weeks before a practice exam. The MCAT is the assessment that matters most for their next twelve months. Biochem can run at maintenance for ten days. Physics maybe at maintenance for five. This is a strategic choice, and it requires sitting down on Sunday and making it.
This is one of the things Fennie's calendar layer is doing in the background. You drop in the MCAT date, the biochem midterm, the physics problem sets — Fennie weights the upcoming days. Mon–Wed before the Friday biochem midterm get heavier on biochem. The MCAT looms larger as it approaches. The daily plan reflects this. You don't have to redo the math every week.
But — and this matters — you should still do the Sunday review. The system can rebalance the schedule. It can't tell you what your goals for the term are. That's still your job, and it takes twenty minutes.
Three students, three campaigns
Strategy looks different depending on what you're studying. Three caricatures, all real:
The law student
A 1L's term is dominated by one event per course: the final. Most law schools weight finals at 90–100% of the grade. Everything before is rehearsal.
The strategic implication is unintuitive: front-load understanding, back-load synthesis. The first ten weeks should be about building a clean conceptual map of each subject — not memorizing rules yet, but understanding why the rules exist and how they relate. The last four weeks are about turning that map into outlines and practice essays under timed conditions.
A law student using Fennie well will spend the first half of the term in chat-as-tutor mode, working through hypotheticals where Fennie pushes back rather than answering. Notes get built up week over week. As finals approach, the daily plan tilts toward retrieval — quizzes generated from her own notes, flashcards on the elements of common law claims, IRAC-style essays where Fennie won't write the argument for her but will tell her where her analysis is thin.
She is not making a Notion outline of the federal rules of civil procedure on a Saturday in week three. That's busywork dressed as preparation.
The engineering undergrad
Multiple courses, frequent problem sets, a midterm somewhere around week seven, projects in week twelve. The grade is built incrementally, which is a blessing and a curse: a blessing because no single thing kills you, a curse because it's easy to coast.
The strategic move here is mastery cadence. Each week's material has to actually land before the next week's material arrives, or the foundation rots and the second midterm is a disaster. This is the cohort that benefits most from the daily-plan loop, because the discipline of "what should I be doing right now to stay caught up" is exactly what's hard to self-impose at 9pm on a Tuesday when you've got three problem sets going.
Fennie's interleaving — mixing courses in a single day's plan — matters here too. Engineering students naturally batch (one full evening of E&M, the next of fluids), and batching is what the research says doesn't work for retention. The daily plan does the unintuitive thing automatically.
The MCAT prepper
Not a term in the traditional sense. A campaign. Six months, one exam, no quizzes along the way to tell you how you're doing.
The strategic challenge is self-assessment. The MCAT prepper needs an honest, frequently-updated picture of what they know and what they don't. The biggest failure mode is over-studying material you've already mastered because it feels comfortable, while under-studying material you haven't touched because it feels bad.
This is where Memory — the eighth, quiet object in Fennie's system — earns its keep. Mastery tracking by topic. Patterns of what you skip. The plan steers you toward the discomfort, calmly, every day. No one else is going to do this for you.
What Memory actually changes
I want to spend a paragraph on this because it's the part of Fennie that's least visible and most consequential.
Every other study app treats your sessions as transactions. You took a quiz. You made a flashcard. They go into a list. They don't talk to each other.
Memory is the layer that connects everything. When you struggle on a quiz on enzyme kinetics, that fact informs tomorrow's plan. When you skip a flashcard set three days running, the system notices. When your notes show you've rephrased the second law of thermodynamics in your own words confidently, your retrieval load on that topic drops.
The result is a study plan that stops feeling generic. The first week with Fennie, the plan looks like a reasonable guess. By week three, it's started to know that you tend to drift on Tuesdays, that your weakest organic chem topic is reaction mechanisms (not synthesis, even though you think it is), that your retention on Spanish vocab cards drops faster than the default schedule assumes.
You can't build this in a Notion database. You can't build it with ChatGPT. It only works if the same system sees your courses, your calendar, your notes, your quiz performance, and your flashcards together.
The strategy of ramping
Most students study at a flat intensity until panic kicks in. The smarter pattern is a deliberate ramp.
Two weeks before a major assessment, intensity should already be climbing. The week before, you're doing more retrieval than reading. The 48 hours before, you're almost entirely on practice — exam-like questions, timed, with review of misses. The night before, you sleep.
This sounds obvious. Almost no one does it. The default is to read the textbook the night before, panic, and pull an all-nighter that wrecks the next day.
If you've put your assessments in Fennie's calendar, the ramp builds itself into the daily plan. The plan starts incorporating retrieval-heavy items 14 days out. Quizzes get harder. Flashcards from that course's deck show up more often. By 48 hours out, the plan is essentially a pre-exam taper.
You don't need Fennie to do this — you need a plan that does this. Fennie is one such plan.
What to do this week
If you take nothing else from this:
- Reread your syllabi. All of them. Block 30 minutes.
- Put every assessment, every deadline, every weight on a single calendar.
- Identify the one course where you're behind. Decide whether to catch up this week or accept the loss and protect the others.
- Schedule a recurring 20-minute Sunday session. This is the meta-habit.
Do those four things this Sunday and you'll be ahead of most of your cohort by Tuesday.
If you want the calendar, the topic map, the daily plan, and the memory layer to run on their own, that's what Fennie is for.