September arrives with a familiar mix of optimism and chaos. Module handbooks land in your inbox, reading lists appear on the portal, and every lecturer mentions a different deadline. By week three, the paper notes and screenshots start to slip. A Notion setup built in early September stops that drift. It does not need to be elaborate; it needs to match how you actually work.
Begin with a term dashboard
Your dashboard is the first page you open each morning. Keep it to a single screen so it stays useful. Link to the databases you will actually check: assignments, modules, reading, revision. Add a small timetable section and a quick link to your university portal.
What to pin at the top
- A linked view of assignments due in the next 14 days.
- A gallery or list of your current modules.
- Three quick links: timetable, email, library account.
- A single line for the week's main focus.
Resist the urge to add motivational quotes or complex formulas. The dashboard is a launchpad, not a project.
Set up your modules database
Create one database called Modules. Each row becomes a hub for everything related to that module. Useful properties include module name, code, lecturer, semester, credits, and a status field (Active, Archived). Add a colour for each module so you can spot it in calendar and board views.
Inside each module page, add linked views of your assignments and reading lists. Filter them so they only show items related to that module. This means you never have to hunt through a global list to find what you need for Tuesday's seminar.
Views that earn their keep
A table view sorted by module code is fine for admin. A board view grouped by status helps you see which modules need attention. Skip the timeline view unless you have a genuine use for it.
Turn assignments into a single source of truth
One assignments database beats five separate lists. Properties: assignment name, module (relation), due date, status, priority, weighting, and a notes field. The status field matters most. Use clear stages: Not started, Planning, Drafting, Final review, Submitted. A board view grouped by status gives you an instant picture of what is stuck.
Add a calendar view filtered to the current month. When a new deadline appears, add it immediately. Do not wait for a quiet moment. The whole point is to stop relying on memory.
- Open the assignments database.
- Add the assignment name and due date.
- Link it to the correct module.
- Set the status to Not started.
- Add the weighting if you know it.
That takes under a minute. Do it while the information is in front of you.
Capture reading lists without the panic
Reading lists can feel endless. A simple database tames them. Properties: title, author, module (relation), type (Core, Recommended, Background), status (To source, To read, Reading, Notes made), and a page range or chapter. Paste the list in, then tidy the entries over a week.
A reading workflow that survives week five
- Tag only the essential chapters as Core. The rest can wait.
- Open one reading at a time. Not ten tabs.
- Add notes directly to the module page or a linked notes database.
- Mark a reading as Notes made only when you have written something useful.
This stops the list from becoming a monument to good intentions. If a reading is not core, it is fine to leave it in To source for a month.
Build a revision system that starts early
Revision works best when it is a habit, not a panic. Create a revision notes database linked to your modules. Each note covers one topic or lecture. Add a confidence property from 1 to 5 and a next review date. When you review a note, update both. A simple schedule: review after one day, three days, one week, then monthly. You do not need a complicated formula.
Revision is easier when the page already exists. Write the note during the term, not the week before exams.
Link each revision note to its module. Then your module page becomes a complete revision hub: assignments, readings, lecture notes, and confidence checks in one place.
Keep weekly and monthly routines
A system only works if you return to it. Set a 20-minute Sunday reset. Clear your Notion inbox, check due dates, update assignment statuses, and choose three priorities for the week. On the first Sunday of each month, review module progress, archive completed items, and delete any property you have not used.
The Sunday 20-minute reset
- Open the dashboard.
- Check the next 14 days of deadlines.
- Move any stuck assignment to Planning or Drafting.
- Pick three priorities and write them on the dashboard.
- Close Notion.
That last step matters. Organisation is not the work. It is what lets you do the work.
Your first afternoon setup
Set aside 90 minutes this week. Create the dashboard, modules database, assignments database, reading list, and revision notes. Add your first three weeks of deadlines. Link each item to a module. Then stop. You can refine the colours and views later. The goal is a setup you will still use in November, not a perfect system you abandon by October.
Start with the modules. Everything else hangs off them. If you only do one thing, make that database and add your reading list. September is the right time to build the habit.
Photo: Christina Morillo / Pexels
