Setting Up Your Term with Fennie: An Honest Walkthrough
Setting Up Your Term with Fennie: An Honest Walkthrough
It's the Sunday before classes start. You have five syllabi open in five tabs, a notebook with three different to-do lists, and a vague feeling that this semester is going to be the one where you finally stay on top of things.
You won't. Not the way you're trying to.
I've watched a lot of students set up Fennie in week one. The ones who do it well don't try to map out the entire semester in a single sitting. They do less than you'd think — and the system fills in the rest as the term unfolds.
Here's how to actually set up your fall term with Fennie. No checklist with 47 items. No 6 a.m. routine. Just the things that matter, in the order they matter.
The Sunday-night mistake
Most students who churn out of any study app churn in the first 72 hours. Almost always for the same reason: they tried to load every course, build every flashcard deck, and pre-write every study plan in one marathon Sunday session.
By Tuesday they're behind on the system itself, which feels worse than just being behind on classes.
Fennie's whole shape is built around the opposite. You feed it a little. It does some thinking overnight. The next morning you get a small, specific plan — usually three or four items, totaling 30 to 90 minutes. You do those. You skip what you don't want to do. The system notices and adjusts.
The only thing you have to get right in week one is the input. So that's what this walkthrough is about.
Day one: drop in your syllabi
Open Courses. Create one course per class. Drag the syllabus PDF into each.
That's it for day one.
Fennie's syllabus pipeline reads the PDF and pulls out the topic map for the term — week one is intro to limits, week three is derivatives, week six is the chain rule, midterm hits the Friday before fall break. You don't need to type any of this. You don't need to clean it up. Wrong about something? You can edit later.
The reason this matters: every other piece of Fennie reads from this map. The daily plan knows what's coming. The chat tutor knows where you are in the term. The quizzes know what's actually on your professor's list, not a generic "Calc 1" curriculum scraped from the internet.
If your professor hasn't posted a syllabus yet — and some won't, especially for upper-division courses — make a stub course with just the title and the meeting time. Add the syllabus when it shows up. Fennie will catch up.
A small note on the engineering stack
If you're an engineering undergrad with the standard fall load (something like Calc III, Diff Eq, a physics course, a coding course, and a writing requirement), don't try to give all five equal weight. They aren't equal. Calc III and the physics course are the ones that bury people. Add them first. Get the syllabi in. Add the others over the next two days.
For pre-med and MCAT preppers, the asymmetry is bigger: orgo eats the term. Everything else is auxiliary. Set up orgo properly — chapters, exam dates, the lab component if there is one — before you do anything else.
For 1Ls in law school, the trick is that your "syllabus" is half schedule and half casebook reading list. Drop in both if you have them. Fennie will treat the casebook reading as the topic map, which is closer to how you actually study anyway.
Day two: put your calendar in
This is the one most students skip and then complain that the daily plan feels generic. The plan is only as smart as the deadlines you give it.
Open Calendar. Add:
- Every exam date you know about
- Every paper deadline
- Every problem set due date for the next four weeks
- Any travel, work shifts, or commitments that will eat study time
Calendar awareness is the quiet thing that makes Fennie feel different from a chatbot. Drop a Friday midterm in for organic chemistry, and Monday through Wednesday's plans get heavier on orgo. Add a Tuesday paper deadline for your history seminar, and the weekend before turns into reading and outlining time. Push the paper a week because the professor extended? The plan reshuffles overnight.
You don't need to add stuff three months out. The system cares most about the next two weeks. Add what you know. Add the rest as your professors tell you about it.
The 20-minute version
If you only have 20 minutes for setup, do this:
- Drop in syllabi for your two hardest courses
- Add the next exam date for each
- Add anything else due in the next 14 days
Skip the rest. Open Fennie tomorrow morning and see what the daily plan looks like. Adjust from there.
Day three: meet the daily plan
Wake up. Open the app. There's a plan waiting.
It's small. Three or four items. Maybe: 25 minutes of orgo problems on the Monday topics, a short flashcard review on last week's diff eq concepts, draft a thesis paragraph for the history paper, a 10-minute walk-through of where you got stuck in physics last Thursday.
The plan won't be perfect on day one. It's working from very little — basically the syllabus topic map and your calendar. Memory hasn't kicked in yet. Mastery is unknown. The plan is making best guesses.
What matters is what you do next. Open one item. Try it. If it's too easy, mark it. If you skipped a flashcard set because you already know that material cold, that's a signal. If you spent 40 minutes on a 15-minute physics problem, that's a much bigger signal.
By day three or four, the plans start fitting. By week two, they're sharp.
What actually goes into the study tools
People ask whether to use Notes or Chat or Quizzes "first." Wrong question. They feed each other.
Here's a real flow from a pre-med student last fall:
She's reading the orgo chapter on alkene reactions. She takes notes in Fennie — markdown, with a few mechanism sketches written in LaTeX-style notation. When she's done, she clicks "generate quiz." Fennie pulls 10 questions from the note. She gets 6 right. The 4 she misses become flashcards automatically — or with one more click, depending on her setting. Two days later those flashcards show up on her morning plan because spaced repetition decided it was time.
She also pasted a hard reaction problem into chat. Chat didn't give her the product. It asked what she'd tried. She said she'd drawn the carbocation but wasn't sure where the bromide attacked. Chat asked her which carbon was more substituted. She figured it out from there.
That's the loop. Note → Quiz → Flashcard → tomorrow's plan. Chat doesn't give answers; it walks you through. By design.
If you're coming from ChatGPT and expecting "give me the solution to question 3," Fennie's chat will frustrate you for about a week. Then it stops. Because you start solving things instead of typing them.
The mistakes I see most
A few patterns from watching students set up the platform.
Trying to import every old note
You don't need your notes from last semester. The syllabus map is enough. If you have a specific document — last year's exam, a study guide a friend shared — sure, drop it in. But don't spend Saturday converting two years of OneNote into Fennie notes. Nobody reads old notes. They start fresh, and the new notes are the ones that matter.
Building flashcard decks before you have notes
Flashcards in Fennie are downstream of notes. The good ones get generated from material you've already written or read. Pre-built decks are fine in a pinch — there's a stock library — but the cards you'll actually retain are the ones that came out of your own quiz misses.
Ignoring the calendar because "I'll just remember"
You won't. And if you do, the plan won't, which means it'll send you to study probability theory three days before your stats final because it had no other information to go on. Just put the dates in. Two minutes.
Loading premium for week one
You don't need it. The free tier — chat with basic models, basic generation — is plenty for setup. Premium (49.99/year) becomes worth it around week three or four, when you start running into generation limits or want the better models for harder problems. Wait until you actually feel the wall.
A note on Memory
There's an eighth thing in Fennie that doesn't have its own tab: Memory.
It's the part that watches what you skip, what you breeze through, what you bomb on quizzes, what learning style you seem to default to. It feeds tomorrow's plan and the way chat talks to you. You don't manage it directly. You just use the system, and Memory builds itself.
The reason this matters for setup: don't game the early days. If you skip a plan item because you genuinely already know it, mark it as "I know this" rather than just doing it for show. If you got something wrong but you understand why, say so. The more honest the early signals, the faster Memory tunes to you.
Week one schedule, if you want one
Day 1, 15 minutes: drop in syllabi for your hardest two courses.
Day 2, 10 minutes: add the next two weeks of deadlines to Calendar.
Day 3, morning: open the daily plan. Do one item. See how it feels.
Day 4-5: add the rest of your courses and any deadlines you missed.
End of week 1: do a 5-minute pass on what's working and what isn't. Adjust course weights if one feels under- or over-represented.
Don't do this on a Sunday at 11 p.m. when you're already anxious about the week. Do it on a Tuesday afternoon when you're bored. The setup is calmer that way, and the system you build is calmer too.
Why this shape
A study app shaped around you isn't a slogan we picked because it sounded nice. It's the only shape that makes sense once AI can actually do the work. Generic study advice — "make a schedule," "use flashcards," "do practice problems" — has been around for fifty years. It's not wrong. It's just unspecific. And in a 16-week term with five courses and a job and a life, unspecific advice is the same as no advice.
What's new isn't AI tutoring. It's a study system that knows what's coming, knows what you skipped, and writes you a small plan every morning that fits both. The chat, the notes, the quizzes, the flashcards — those are useful. The loop they live inside is what makes them work.
Set up the inputs. Do the morning plans. Let Memory catch up. By midterms you'll have something that actually fits the way you study, instead of the way some product designer thought you should.