Notion Build With Me: A Spaced Repetition Database

TL;DR

Each study session becomes a row in a Notion revision database, with formulas computing “next study date” from an “understanding” level.

Briefing Cornell Notes

Briefing

A spaced-repetition system built directly in Notion can turn existing flashcard-style notes into a self-updating schedule—tracking each study session, grading recall with a “total correct” score, and automatically computing the next review date based on how well the material was understood. The core idea is to store every study session as a row in a revision database, then use formulas to decide whether the next study should happen immediately (same day), the next day, or several days later.

The workflow starts with a “main revision table” where each row represents one study session for a specific deck (e.g., “v1 French revision”). Key fields include the study date, a calculated “next study date,” the total number of flashcards (total toggles), and a “total correct” input that the user fills in after toggling through answers. Each flashcard is implemented as a Notion toggle: the user reveals the answer, marks it correct, and moves on. At the end of the session, the user enters how many toggles were correct; a “revision number” and an understanding score then drive scheduling.

Understanding is handled in two ways. First, a simple template uses a formula that maps low performance to “little to no understanding,” which keeps the next study date on the same day. Higher performance shifts the next review further out: moderate understanding pushes the next date by +1 day, good understanding by +2 days, and great understanding by +4 days. At the top of the table, sorting by revision descending ensures the most recent session appears first, while the calendar view shows upcoming reviews by “next study date,” not the original study date. Each study session retains a snapshot of correct/incorrect outcomes, letting users revisit history.

To scale beyond one deck, the system duplicates the table view and filters by deck name (e.g., “v2 French revision,” “v3 French revision”). A linked database and calendar view then consolidate all scheduled sessions so the user can filter down to what’s due “today.”

The second major step is automation for users already using Notion toggles as flashcards. Instead of manually setting understanding, the template computes it from performance: it checks whether “total correct” is empty (showing a “processing” indicator for aesthetics), then uses percentage thresholds (e.g., ≤30% for little to no understanding, ≤55% for some understanding, ≤70% for moderate understanding, and higher ranges for good/great/no misunderstandings). The computed understanding feeds back into the “next study date” formula, so the schedule updates automatically as soon as “total correct” is entered.

Overall, the build turns Notion into a spaced-repetition engine: study sessions become data, performance becomes a graded signal, and review timing becomes formula-driven—complete with deck templates, nested inline templates for groups of cards, and a calendar-based “what to study next” view.

Cornell Notes

The system builds spaced repetition in Notion by representing each study session as a row in a revision database. After studying a deck’s toggle-based flashcards, the user enters “total correct” and “total cards,” and formulas convert performance into an “understanding” level. That understanding level then determines the “next study date,” ranging from same-day repeats for low recall to multi-day delays for high recall. Decks are separated using filters like “v1 French revision” and “v2 French revision,” while a linked calendar view surfaces what’s due today. For existing Notion toggle users, nested templates and inline card templates automate the grading logic so scheduling updates automatically.

How does the database decide when to schedule the next review after a study session?

Each study session row includes a “next study date” property computed from the session’s “understanding.” The understanding is derived from performance—either via a direct mapping from “total correct” in the simple template, or via an automated percentage calculation in the toggle-based version. Low understanding (e.g., “little to no understanding”) keeps the next study on the same day; moderate understanding adds +1 day; good understanding adds +2 days; great understanding adds +4 days; and “no misunderstandings” adds +7 days. The calendar view then sorts by “next study date,” so upcoming reviews appear in the right order.

What role do Notion toggles play in the spaced repetition workflow?

Toggles act as flashcards. For each deck, the template generates a list of toggles (one per card). The user reveals each answer, marks it correct, and moves down the list. After finishing, the user records how many toggles were correct as “total correct.” That single number (relative to “total cards”) becomes the input for the formulas that compute understanding and schedule the next study date.

How are multiple decks handled without duplicating the entire system?

The revision table supports multiple decks by using a deck-identifying property (like “name contains v1 French revision” or “name contains v2 French revision”). Separate table views filter by that deck name, and sorting by revision descending keeps the latest session at the top. A linked database plus a calendar view then aggregates all decks’ upcoming sessions, while additional filters can narrow to “what to revise today” for a specific deck.

Why does the system keep a snapshot of each study session’s outcomes?

Every row stores the session’s results, including the understanding level and the correct/incorrect record implied by the toggling process. This means the user can look back at prior sessions to see how recall changed over time. The template also keeps the revision history visible through the revision number and sorting, so the schedule’s progression (same-day repeats → next-day → multi-day gaps) is traceable.

How does the automated “understanding” formula work for toggle-based flashcards?

The automation uses nested IF conditions based on the percentage correctness: it first checks whether “total correct” is empty, then shows a “processing” emoji for aesthetics. Otherwise, it computes total correct divided by total cards and compares that ratio to thresholds. For example, ≤0.3 maps to “little to no understanding,” ≤0.55 maps to “some understanding,” ≤0.70 maps to “moderate understanding,” and higher ranges map to “good understanding,” “great understanding,” and finally “no misunderstandings” when the user gets all cards correct.

What’s the purpose of nested templates (database template → group template → flashcard template)?

Nested templates streamline creating new decks and card groups. A database template creates the overall revision session structure. Inside it, a “new group” template lets the user add a group header and specify how many flashcards belong to that group. Then a flashcard template generates the individual toggle entries. This reduces repetitive manual setup and ensures the same grading and scheduling logic applies to every new card group.

Review Questions

If “understanding” is set to moderate understanding, how should the “next study date” change relative to the original study date?
What inputs does the automated understanding logic use, and how is the correctness percentage computed?
How does the system ensure the calendar view shows what’s due next rather than when the material was first studied?

Key Points

1
Each study session becomes a row in a Notion revision database, with formulas computing “next study date” from an “understanding” level.
2
Notion toggles function as flashcards; the user marks correctness during the session and records “total correct” afterward.
3
Low recall triggers same-day re-study, while higher recall pushes reviews forward by fixed day increments (e.g., +1, +2, +4, +7).
4
Decks are separated using a deck-identifying property (e.g., “v1 French revision,” “v2 French revision”) and filtered views.
5
A linked calendar view sorts by “next study date,” making “what to study today” a filterable, centralized queue.
6
Nested templates (session → group → flashcard) automate the creation of new toggle-based card sets and keep the workflow consistent.

Highlights

The schedule is driven by formulas: “understanding” maps to specific day offsets, turning performance into timing without manual date entry.

A calendar view based on “next study date” (not original study date) makes the system behave like a real review queue.

The automation computes understanding from correctness percentage thresholds, so “total correct” alone updates the entire spaced-repetition plan.

Nested templates let users generate decks quickly by creating groups and then individual toggle flashcards inside each group.

Topics

Spaced Repetition
Notion Databases
Flashcard Toggles
Template Automation
Calendar Scheduling

Mentioned

Red Gregory