My 7th-grade son spends 4 agonizing hour
Ask
My 7th-grade son spends 4 agonizing hours every Sunday writing test corrections. His teacher makes them copy out every missed test problem into a notebook, write the entire question word-for-word, and re-solve it. He has 45 missed problems from his pre-algebra tests this month, and he was in tears tonight from hand cramps and exhaustion.
When I looked through his 45 "mistakes", more than 30 of them are actually the exact same two core missteps:
1. Distributing a negative sign across parentheses: he writes -(2x - 7) = -2x - 7 (forgot to flip the minus to plus), which ruined 18 problems on his quiz!
2. Negative base vs parentheses exponents: he writes -4^2 = 16 (treating it as (-4)^2 = 16 instead of -(4^2) = -16), which ruined 14 problems!
I want to stop this useless transcription torture and set up a real mistake notebook:
1. How do we cluster 45 scattered misses into just 2 core cause cards instead of copying 45 separate problems?
2. What are the exact 5 lines for each of these two cards (Prompt, Wrong, ight/epair, Tag, Cause)?
3. How should we set up a spaced review cadence so he actually tests himself instead of just reading answers?
Answer
I'll help you set this up. Let me first check what's already in the notebook and pull the capture guidance, then build the two cards.
Let me check the append script format before building the cards.
Now I'll build both cards in one batch (same-day append):
Both cards are written. Here's how this all fits together for your son.
## 1. Clustering 45 misses into 2 cards
The teacher's notebook treats every missed problem as a separate item, so 45 problems becomes 45 rows. The mistake-notebook treats every missed *move* as one card, so 45 problems cluster into 2 cards (the other 11 are "same as Card 1" or "same as Card 2"). You already found the two causes; the rest is just counting.
The rule, applied to anything new this month: scan the page, label each miss with one cause, same cause → one card. Aim for 6–8 cards across the term, not 45. If a third cause shows up next month, that's a third card — not more copies of these two.
## 2. The exact 5 lines for each card
I wrote both to disk. They look like this:
**Card A — distribute-negative** (the 18 quiz problems)
| Line | Content |
|---|---|
| Prompt | `-(2x - 7)` |
| Wrong | `-2x - 7` |
| ight / epair | `-2x + 7`. Same-type: `-(3x + 5) = ?` |
| Tag | `distribute-negative` |
| Cause | forgot to flip the minus to plus when distributing the negative across parentheses |
**Card B — exponent-sign** (the 14 quiz problems)
| Line | Content |
|---|---|
| Prompt | `-4^2` |
| Wrong | `16` |
| ight / epair | `-16`. Same-type: `-5^2 = ?` |
| Tag | `exponent-sign` |
| Cause | treated `-4^2` as `(-4)^2` instead of `-(4^2)`; only parentheses make the negative part of the base |
Five lines, no rules table on the card. If he wants the *reason* `-4^2 ≠ (-4)^2`, that's a different conversation (handed off to the tutoring side) — the card's job is just to bring the wrong move back on day1, day 3, day 7, day 14, day 30.
## 3. The spaced review cadence
Each new card walks a fixed ladder: **tomorrow → 3 days → 7 days → 14 days → 30 days**. A pass moves it up; a fail drops it back to tomorrow. The card itself doesn't carry the schedule — it's stored in the notebook and `due_today` tells you which ones are up.
The flow each night (this is the "tests himself instead of reading answers" part):
1. un the due list. ead him the **Prompt** only.
2. He tries from memory — book closed, the right side covered.
3. Only after his attempt, reveal the **ight / epair** and the same-type item.
4. Mark `pass` or `fail`. Ladder moves accordingly.
The reason for cover-then-reveal: reading a card top-to-bottom is *re-studying*, which feels productive but doesn't stick. Doing the problem from memory is *retrieval*, which does. The teacher's word-for-word transcription gives him the opposite — every night he reads his own mistakes back to himself, no recall required. That's why his hand cramps aren't buying him anything.
## Two follow-ups before I wire up the daily reminder
- **Timezone** — your family IANA zone (e.g. `America/Chicago`)? I have Asia/Shanghai as the platform default; for a 7pm reminder that lands at the right wall-clock for your son, I need the right one.
- **Teacher conversation** — separate from this notebook. If you want, I can help you write one short note to the teacher explaining why you'll be sending a clustered cause-card set instead of 45 copied problems, so the conversation doesn't go sideways on the first parent email. Just say the word.