Review WSP controls, annual testing, exception reporting, business continuity, and compliance-certification topics in Series 26.
This section covers the framework that keeps supervision reliable after the first review is finished. Series 26 expects the principal to understand written supervisory procedures, supervisory controls, annual testing, exception reporting, business continuity planning, system reliability, and related certification obligations. The point is not memorizing a list of internal-control terms. The point is knowing how a firm proves that packaged-products supervision actually works over time.
The exam often uses a recurring error to test whether the candidate can distinguish between correction and control. Correcting one bad breakpoint calculation is not enough if the exception report is weak, the procedure is outdated, or the same error keeps resurfacing. A strong principal response fixes the customer problem and then asks what in the system failed to catch it earlier.
| Control element | What it is designed to catch or confirm | Better supervisory response |
|---|---|---|
| Written supervisory procedures | Whether the firm has a defined process for review, escalation, and documentation. | Update procedures when practice changes instead of relying on informal office custom. |
| Supervisory controls | Whether the review system itself is independently tested and not just assumed to work. | Use control reviews to challenge weak patterns, not just check a box. |
| Exception reports | Whether outliers, missing items, or repeated errors are visible quickly enough to investigate. | Escalate repeated exceptions to root-cause review rather than treating each one as isolated. |
| Annual testing and review | Whether the firm evaluates procedures, technology, and evidence of supervision on a scheduled basis. | Retest the high-risk areas that produce customer harm or recurring errors. |
| Business continuity planning | Whether the firm can continue core supervisory and servicing functions during disruption. | Focus on critical packaged-products workflows, customer access, and record availability. |
| Certification and senior-management oversight | Whether leadership has evidence that required controls exist and are reviewed. | Support certification with documented testing and remediation, not assumptions. |
Series 26 repeatedly rewards the answer that treats the control environment as a living system. If the same issue appears more than once, the principal should think about supervision design, training, and exception visibility.
flowchart TD
A["Recurring exception, processing error, or system breakdown appears"] --> B{"Is this an isolated one-off?"}
B -- "Yes" --> C["Correct the item and document the review"]
B -- "No or unclear" --> D["Escalate to supervisory-control or compliance review"]
D --> E["Identify the root cause in procedure, training, technology, or oversight"]
E --> F["Revise the procedure, report, control, or training path"]
F --> G["Retest the affected process and retain evidence"]
G --> H["Report results to the appropriate supervisory level"]
C --> I{"Does the same issue appear again?"}
I -- "Yes" --> D
I -- "No" --> J["Close the item with documented resolution"]
H --> J
This is the mindset Series 26 wants. One-off correction is acceptable only when the record supports that it really was one-off. Once the same weakness repeats, the question becomes whether the firm’s supervisory design is adequate.
A firm’s breakpoint report has missed the same share-class pricing issue twice in one quarter. Both affected customers were reimbursed, and the representative has been reminded to review the prospectus more carefully. What is the best next step for the principal?
Correct answer: 3.
Series 26 is testing the difference between a customer correction and a control correction. The reimbursement matters, but repeated misses mean the supervisory system itself needs to be reviewed and strengthened.