Final Weak-Domain Remediation Plan

Remediate by Evidence, Not Anxiety

Do not remediate from preference or dread. Use recent practice data to locate weak domains and repeated error types. A candidate who 'knows ethics' but keeps missing confidentiality-in-supervision items does not have a confidence problem - they have a specific E/I decision problem that targeted practice can fix.

The goal of the final phase is not to relearn everything; it is to convert recurring misses into reliable decisions. That means working from the error log built in the previous section, sorted by domain and error tag, and attacking the densest clusters first.

This distinction matters because the two failure modes look different and need different fixes. A knowledge gap (you did not know what a changing-criterion design demonstrates) is fixed by relearning a small concept. A decision gap (you knew the concept but still chose the premature procedure) is fixed only by working scenario items and explaining distractors. Most candidates near test day have far more decision gaps than knowledge gaps, which is why re-reading chapters feels productive but rarely moves the needle.

Prioritize Weak AND High-Impact Domains

Use a simple two-axis priority: blueprint weight times your error rate. Domains that are heavily weighted and frequently missed get attacked first.

Note that C/D (measurement and design) and E/I (ethics and supervision) earn extra attention beyond their raw weights because they appear embedded inside higher-weight assessment and procedure items.

A Tight Remediation Cycle

Run a short, repeatable loop for each weak cluster. Speed matters in the final stretch, so keep each cycle to one sitting.

1. Diagnose - sort missed items by domain, task, and error tag; pick the densest cluster.
2. Relearn - review the smallest rule or concept that explains the misses (one page, not one chapter).
3. Apply - answer 5-10 new scenario items that hinge on that rule.
4. Explain - write one sentence per item on why each distractor fails.
5. Retest - mix the domain into a timed block within 48 hours.
6. Maintain - revisit the rule in a cumulative block later in the week.

The Explain step is the highest-yield part: forcing yourself to articulate why the tempting wrong answer is wrong is exactly the skill integrated items reward.

Replace Shortcuts With Conditions

The most damaging final-week habit is collapsing nuanced decisions into shortcuts: 'always choose reinforcement,' 'never choose functional analysis,' 'pick the least-restrictive option no matter what.' These feel efficient but get punished, because the exam tests conditions.

Convert each shortcut into a conditional rule:

• Not 'always reinforce' but 'choose function-based reinforcement first when it can compete with the maintaining contingency.'
• Not 'never run an FA' but 'run an FA when its information value justifies the risk, with consent, safeguards, and competence.'
• Not 'always least-restrictive' but 'use the least-restrictive procedure that is effective for this function and risk level.'

Conditional rules survive contact with novel vignettes; shortcuts do not.

Build a Conditional Rule Sheet

In the final phase, compress your hardest-won lessons into a one-page sheet of conditional rules - the if/then statements that survive novel vignettes. A few high-yield examples to adapt to your own weak clusters:

• If function is unknown, then the best next step is usually assessment, not a procedure.
• If a plan shows no effect and integrity is unverified, then check integrity and retrain before redesigning.
• If a procedure is restrictive, then require consent, least-restrictive justification, safeguards, training, and review.
• If a baseline is unstable, then extend it or investigate variability before intervening.
• If a stakeholder request conflicts with function or welfare, then the function- and welfare-based option wins.

Reviewing this sheet does more in the last days than re-reading chapters, because it rehearses decisions rather than facts.

Keep the sheet short and behavioral. A page of fifteen or twenty conditional rules, each tied to a concrete cue you can spot in a stem, beats a stack of notes you cannot scan under time. Read it the morning of the exam not to cram new content but to prime the if/then reasoning that the integrated items reward, then trust your formulate-first habit to apply it item by item.

Final-Review Guardrails

Three guardrails keep the last days productive. First, do not chase a raw percentage - the BACB scores pass/fail via a modified-Angoff standard, so a practice percent is a diagnostic, not a prediction. Second, do not introduce brand-new content in the final 48 hours; deepen reliability on what you know. Third, keep ethics and safety inviolate - no shortcut is worth selecting an option that skips consent, integrity, or welfare.

Enter test day with a small set of conditional decision rules, a habit of formulating the case before reading options, and the discipline to choose the least-restrictive, function-based, data-anchored next step. That profile, not memorized trivia, is what the integrated BCBA exam rewards.