Mandarin Sentence Patterns Tracker: My Notion System

I kept hitting the same wall in Mandarin: I could recognize a sentence pattern when I read it, but I couldn't produce it when I spoke. The gap between recognizing a structure and using it is where most intermediate learners stall. The fix wasn't more input. It was a tracker that forces me to produce each pattern repeatedly until it's automatic. Here's the Notion system I built, exactly as I run it.

The problem this solves

Mandarin grammar is largely a set of sentence patterns: 把-sentences, 是…的, comparison with 比, result complements, 连…都. There aren't thousands of them. The issue is that you meet a pattern once, nod, and never deliberately produce it again. So it stays passive. My tracker exists to make production the default action, not an afterthought.

The whole system is built around one rule: a pattern doesn't count as learned until I've written original sentences with it on three separate days.

The database schema

It's a single Notion database, one row per pattern. The properties:

• Pattern (title): the skeleton, e.g. A 比 B + adjective, Subject 把 object verb 了.
• Meaning (text): the function in plain English.
• Source sentence (text): the example where I first met it, with pinyin and translation.
• My sentences (text): original sentences I've produced, dated. This field grows over time.
• Production count (number): how many distinct days I've produced it.
• Status (select): Passive / Active / Automatic.
• Category (multi-select): comparison, aspect, 把, complement, topic-comment, etc.
• Confused with (relation to itself): near-neighbor patterns.

The two fields doing the heavy lifting are My sentences and Production count. Most trackers store what you've seen. This one stores what you've made.

How patterns move through the system

Every pattern has a lifecycle, and Status tracks it:

• Passive — I understand it when I read it, but haven't produced it. New rows start here.
• Active — I've written original sentences with it on at least one day; I can produce it with effort.
• Automatic — produced on three or more separate days, and I now use it without thinking.

The board view grouped by Status is my dashboard. The goal each week is to drag cards rightward. Watching a pattern move Passive to Active to Automatic is far more motivating than an abstract "progress" number, because each move corresponds to something I actually did: I wrote sentences.

The production loop

This is the part that makes it work. Three times a week, fifteen minutes:

1. Open a view filtered to Status is Passive or Active, sorted by Production count ascending. Least-practiced first.
2. Take the top three patterns. For each, write two original sentences about my real life, dated, into My sentences.
3. Increment Production count for each (this is one day of production, regardless of how many sentences).
4. When a pattern hits three production days, promote it to Automatic.

Writing about real life matters. "我比我哥哥高" sticks because it's true; a generic textbook sentence doesn't. Over weeks the My sentences field becomes a personal corpus written entirely in patterns I'm trying to internalize.

Why the Confused-with relation earns its place

Mandarin has clusters of patterns that overlap just enough to trip you up. 比 vs 没有 for comparison, 了 vs 过 for aspect, 在 vs 着 for ongoing states. When I produce a sentence and second-guess which pattern fits, I link the two rows and note the rule in each. A filtered view of everything with a Confused-with link becomes a precise drill of my own grey areas. It's the most valuable view in the system by month two.

Views I actually use

• Production queue (table, Status is not Automatic, sorted by Production count ascending): the daily driver.
• Status board (board grouped by Status): the motivation dashboard.
• By category (board grouped by Category): for focused sessions, e.g. "a week of complements."
• Confusables (table, filtered to rows with a Confused-with link): targeted drilling.

What I deliberately left out

I kept this lean on purpose, because every extra field is friction at capture time:

• No audio attachments. Tempting, but recording each pattern slowed me down enough that I stopped adding patterns at all.
• No difficulty rating. Production count already tells me what's hard — hard patterns sit at the bottom of the queue because I avoid them, which is exactly why the queue surfaces them.
• No grammar explanations longer than a line. If I need a full explanation, I link out; the row is for production, not reference.

Results after a season of use

The concrete change is that my speaking now reaches for patterns I used to only recognize. When I want to say "the more I study, the more I understand," 越…越… comes out without a pause, because I produced it on a dozen dated lines over several weeks. The tracker didn't teach me the patterns; my classes did. What it did was close the gap between knowing a pattern exists and being able to deploy it in real time.

If you build this, start with five patterns you already half-know and run the production loop for two weeks before adding more. The discipline of producing on separate days, tracked by a simple count, is the entire trick. Everything else in the schema just supports it.