Domain 1 (label unverified - scope-mapping method, not content)
Status of this section
The domain assigned here arrived as a placeholder: no syllabus task list, weighting, or concept inventory has been verified for it. Nothing below should be memorised as examinable fact about SAL1 Domain 1. What can be taught honestly is the method for working a domain whose boundaries are not yet confirmed - and that method is itself worth drilling, because scope documents for professional exams are frequently incomplete, outdated, or written at a level of abstraction that forces you to infer the boundaries.
Build a three-column scope map
Open a page with the domain name at the top and three columns: (1) quoted - statements copied verbatim from the official syllabus or blueprint; (2) confirmed - facts you can verify in two independent primary sources (the standard-setter's own text, a regulator's guidance, a statute, a vendor's own documentation); (3) inferred - anything you concluded yourself from the domain's title or from adjacent domains. Only columns 1 and 2 are revision material. Column 3 is a hypothesis list: revisit it, never quote it, never build a flashcard from it.
Named traps
- Treating a plausible-sounding concept list as authoritative because it is well written.
- Over-learning one sub-topic because it is familiar, and therefore assuming it carries the domain's weight.
- Memorising numbers without their units, reporting basis, or effective date.
- Confusing two similarly named frameworks because the abbreviation differs by one letter.
Rule of thumb - the two-source test
Before a fact enters your notes, ask: can I name the primary source, and can a second independent source confirm it? If only one holds, tag it single-sourced and flag it for review. If neither holds, it is a hypothesis - write it in column 3 and move on. This one rule prevents most speculative-content errors.