How we publish
Editorial Standards
These standards describe the principles we use when presenting TestPrepGenius books, parent guidance, and companion resources on this website.
1. Match claims to the specific title
Not every TestPrepGenius book contains the same features. Detailed answer explanations, audio, scoring tools, diagnostics, bonus tests, and other companion resources may be available for some titles and not others. We aim to describe those features only where they apply.
2. Use published test information where available
Test-prep materials are designed around the publicly available structure, skills, question formats, and guidance associated with the assessment being prepared for. Testing programs can change, so families should use the edition and grade that matches their current testing situation.
3. Keep practice materials independent
Our practice questions and companion materials are independently produced. We do not present TestPrepGenius-created practice content as official test questions, official scoring, or official audio unless a page can accurately support that description.
4. Separate practice feedback from official scores
Practice-test percentages, weakness reports, readiness feedback, or similar outputs are study aids. They are not official admissions decisions, percentile scores, school placement decisions, or guarantees of future performance.
5. Correct meaningful errors
If a customer reports a suspected error, broken resource, outdated link, or misleading description, we want to review it and correct the customer-facing material when appropriate. Reports can be sent to [email protected] with the book title, grade, page or question number when relevant, and a short description of the issue.
6. Keep marketing claims supportable
We avoid treating a capability as universal simply because it exists in one series. We also avoid describing independent materials as endorsed by the test owner. Where a claim depends on a particular edition, feature, or product configuration, the individual product page should take priority over general site-wide language.