Start with one page and four databases

Create a page called "Russian" and add 4 inline databases:

1. Words: every word you learn, with its gender and review date.

2. Cases: one row for each of the 6 grammatical cases.

3. Weekly plan: what you'll do in each session this week.

4. Review log: one line per session, so you can see the streak.

Keep it on one page. If the plan lives in 5 places, you'll stop opening it.

The words database

Russian nouns change their endings, so a plain word list isn't enough. You need the gender of every noun, because the gender decides the endings.

Use these properties:

The Box column runs a simple spaced repetition system. Every word starts in box 1. Get it right and it moves up a box. Get it wrong and it drops back to 1.

The Next review formula spaces the reviews out as the box goes up:

dateAdd(prop("Last reviewed"), pow(2, prop("Box")), "days")

Box 1 comes back in 2 days, box 3 in 8 days, box 5 in about a month. Then add a filtered view called "Due today" (Next review is on or before today) and that's your review list.

One tip: add words in small batches. Ten words a session is plenty. Fifty words on a Sunday turns into a 50-word review pile on Tuesday.

The cases database

This is the part most beginners skip, and it's the part that decides whether you can say a full sentence.

Russian has 6 cases. The ending of a noun tells you its job in the sentence, so книга (kniga, book) becomes книгу (knigu) when you read it and книги (knigi) when you don't have it.

Make one row per case:

Add a Confidence column (1 to 5) and update it every Friday. After a month you'll see which case drags. For most English speakers it's the genitive, because it shows up in so many places: after "no", after numbers, after "a lot of".

If you want the full picture before you fill the table, here's a clear guide to how the six Russian cases work, with the endings for each gender.

The weekly plan

Four short sessions beat one long one. A 25-minute block fits before school, at lunch, or after the kids are in bed.

Use a database with a Day property and a Type select, then duplicate this week as a template:

• Monday: 10 new words, plus the "Due today" view.

• Tuesday: one case. Read the row, write 5 sentences with it.

• Thursday: reviews only, then 10 minutes of listening.

• Saturday: mixed practice. Pick 5 words and put each one in 2 different cases.

Notion's repeating templates can create next week's page for you every Sunday. That's one less decision to make.

The review log

Keep it boring: date, minutes, what you did, one line on what felt hard.

After 6 weeks, read the "what felt hard" column top to bottom. It's usually the same 2 things, and that's your plan for the next month.

Where Notion stops

Notion holds the plan very well. It can't tell you that you wrote книгой where you needed книги.

That feedback is what makes case endings stick, and it's hard to get from a notebook or a database. A teacher gives it. So do some of the apps built for Russian learners, which check each ending you type and show the right form when you miss.

I'd use both: Notion for the plan and the word list, and a drill tool for the 15 minutes a day of endings. The plan tells you what to practice. The drills tell you whether you actually know it.

For teachers using this with a class

Share the page as a template and let each student duplicate it. Keep the Cases database identical for everyone, so you can say "update your genitive row" and the whole class knows where to look.

The Confidence column doubles as a quick check-in. Ask students to screenshot it every 2 weeks, and you'll know which case to reteach before the test shows you.

Ksenia Chekulaeva is the Lead Content Editor at Slova, a Russian learning app that drills case endings and verbs.