Completeness checks
Questions must include required fields such as answer key, explanation, wrong-choice notes, domain label, concept tags, and review status.
Review policy
How content is checked, updated, and corrected
This policy explains the current internal editorial maintenance and automated quality gates, and what those checks do and do not mean.
Current review checks
Coverage checks
Internal scripts check coverage across domains, task planning nodes, and concept mappings.
Duplicate-risk checks
Question stems and explanations are checked for duplicate risk before release.
Source-boundary checks
Content must not imply official BACB status, copied exam content, pass guarantees, or unsupported professional advice.
What the machine quality gate means
The machine quality gate checks structure, coverage, and consistency, while internal editors maintain the content. It is a quality signal only; it does not certify clinical quality or exam validity. No content has been externally reviewed by a named, credential-verifiable BCBA.
How reports are handled
User reports can lead to clarification, correction, relabeling, retirement from practice, or deeper review. Reports about official exam rules should be checked against current BACB materials.
Update policy
Pages are updated when product behavior changes, a content boundary needs clarification, a source policy changes, a user report identifies a real issue, or a study page needs stronger guidance. Dates should not be changed just to appear fresh.