AP Calculus BC Mistake Review for a Busy Semester (2026)

Review a BC mistake by locating the first invalid step, classifying it, and re-solving the problem 48 hours later without the answer. Copying a clean solution can create recognition without mathematical control.

Six error types

Code	Failure	Example
CHOICE	Wrong method/model	Used disk method where washers are required
COND	Missing theorem/test condition	Applied Alternating Series Error without decreasing terms tending to zero
ALG	Algebra/trig/arithmetic after correct calculus	Lost a negative in integration by parts
REP	Misread graph/table/context	Confused velocity with speed
CALC	Calculator setup/precision	Graphed wrong window or rounded too early
COMM	Notation, units, or justification	Correct value but no interpretation or unsupported conclusion

Twelve-minute repair

1. Cover the solution and retry from the original prompt.
2. Circle the first step where your work diverges.
3. Assign one primary code.
4. Write a one-line prevention rule.
5. Solve a parallel problem now.
6. Schedule the original for a cold re-solve in two days.

Series example

The student says (\sum (-1)^n/(n+2)) converges “because it alternates.” The first invalid step is COND: alternation alone is insufficient. The repair must show that magnitudes decrease and approach zero. A transfer problem should change the magnitude so one condition fails.

Parametric motion example

A student correctly finds (x'(t)) and (y'(t)) but reports (x'(2)+y'(2)) as speed. The first error is CHOICE, not algebra. Speed is the magnitude (\sqrt{(x'(2))^2+(y'(2))^2}). The prevention rule is “write the requested motion quantity and formula before substituting.” A transfer problem should ask for total distance so the student must integrate speed rather than calculate displacement.

Taylor polynomial example

A student builds the correct polynomial but omits the factorial in one coefficient. Classify the first failure as a formula or execution error based on the written setup. The repair should reconstruct the general Taylor form, match each derivative order to (n!), and test a different center. Do not assign ten random series questions when the issue is one coefficient structure.

Score FRQs by point

Use College Board's released Calculus BC FRQs and scoring information. Mark the exact point lost. If the setup earned credit but arithmetic failed, preserve the valid setup and repair the algebra; do not label the entire unit weak.

For every missed point, write what the scoring guideline required in your own words: a setup, value, condition, justification, unit, or contextual conclusion. Then underline the exact location where the original response stopped satisfying it. This keeps review anchored to student work rather than a polished model.

Do not assume that an equivalent-looking expression earns or loses credit without checking the scoring notes. Mathematical equivalence, required supporting work, and decimal precision can matter differently across parts. Use official scoring samples to understand how reasoning appears in complete responses.

A 30-minute weekly review

• 5 min: group errors by code.
• 10 min: re-solve the two most repeated errors cold.
• 10 min: complete one new problem targeting the same choice/condition.
• 5 min: choose next week's prevention focus.

If CHOICE and COND dominate, slow down method selection. If ALG dominates after correct setup, assign short prerequisite drills. If COMM dominates, practice theorem hypotheses and contextual conclusions.

Fit review into collision weeks

During a busy semester, protect review by attaching it to existing assignments. After a class quiz, spend 12 minutes coding the mistakes before starting new homework. After one FRQ, score it the same day and schedule the cold re-solve. Waiting until Sunday to reconstruct every error increases the chance that the original reasoning is forgotten.

Use three workload versions:

• 10 minutes: code one assignment and write one prevention rule;
• 30 minutes: complete the weekly review above; or
• 50 minutes: add a timed mixed set and transfer problems.

The short version maintains the system but should not become permanent if errors are accumulating. When several deadlines collide, repair the highest-frequency or highest-point failure and archive low-value duplicates.

Build a compact error dashboard

Track date, unit, source, calculator condition, error code, first invalid step, prevention rule, and cold-retest result. Add representation—symbolic, graphical, tabular, or contextual—because a student can know a concept in one form and fail it in another.

After two weeks, count codes rather than rereading every entry. If four errors are labeled COND across series and theorem questions, schedule a conditions set. If REP errors cluster in tables and motion graphs, practice translating axes, units, and signs. If CALC errors appear only under time, reproduce the exact input and add timed calculator-active questions.

Archive entries after successful cold and transfer solves, but keep the category counts. The dashboard should become shorter as control improves; it is not a permanent collection of every mistake.

Use the BC weekly readiness checklist to detect recurring gaps and balance BC with other APs without turning review into a marathon.

Calculator errors need exact reproduction

Record the entered expression, window, mode, and retained precision. “Calculator mistake” is too vague. Re-enter the correct setup and state what the screen result means in the problem.

Distinguish entry from interpretation. Entering the wrong integral bound is CALC execution; clicking the correct intersection but reporting its (y)-coordinate when time was requested is REP or COMM. Both happen on a calculator screen, but the prevention steps differ.

Practice calculator-required work with the permitted device and no-calculator work with the device physically removed. A review system that silently checks every no-calculator answer on a phone can hide fragile algebra.

When to move on

Archive an error after you solve the original cold and a parallel problem correctly. Keep it active if you can explain the answer but cannot independently reproduce the method. After a low practice score, use the more complete BC recovery strategy.

If the same error survives two careful repairs, change the explanation source or ask a teacher to inspect the first invalid step. Repeating the same solution is unlikely to fix a misunderstanding it failed to expose.

Efficient review reduces repeated error types; it does not preserve every missed question forever.