LPLS study materials
LPLS study resources

The Regulator, the Director, and the Twelve Runs Under Load

LPLS · Put your knowledge to work in context.

All case studies

The Regulator, the Director, and the Twelve Runs Under Load

You lead a four-person analysis group. A director asks you to present, in a meeting with an external regulator, the subset of last quarter's results showing the new method performing within tolerance. The full dataset has 60 runs. Forty-eight runs under standard conditions pass, but 12 runs under high-load conditions show a 6 percent deviation against a 4 percent tolerance. High-load is outside the current regulatory scope, but the client has publicly stated an intention to expand into it. A junior analyst has already emailed you, copying two colleagues, saying she is uncomfortable with what is being left out. The director signs your performance review in six weeks.

1. How do you handle the director's request? Specify exactly what you present.

Read the worked answer

Present the full dataset, with the scope boundary stated explicitly rather than used as a reason to omit. The framing that satisfies both obligations is: 48 of 60 runs fall within tolerance; the 12 remaining runs were conducted under high-load conditions, which are outside the current scope of this filing, and they show a 6 percent deviation. That is accurate, complete, and does not misrepresent the method's fitness for the scoped use.

Omitting the 12 runs is not a presentational choice; it is a statement to a regulator that the method was evaluated on 60 runs and performed within tolerance, which is false. The fact that high-load is out of scope affects what the regulator concludes, not what you disclose. Say so in one sentence, in the main body, not in an appendix or a footnote. If the director objects to that wording, offer to add a line the director drafts, provided the 12 runs appear.

2. What do you do about the junior analyst's email, and why does the response matter beyond this meeting?

Read the worked answer

Reply promptly, on the same thread with the same recipients, and answer the substance.

Say that the concern is legitimate, that the high-load results will be presented with the standard-condition results and labelled by condition, and that you will not be omitting them. Say plainly that raising it was the right thing to do. Do not say "let's discuss offline" in a way that reads as suppression; the two copied colleagues are watching how the group handles dissent, and the precedent set here determines whether the next concern arrives in an email or never arrives at all.

Beyond the meeting, the email is now a record. A same-day written response that confirms the data will be presented in full protects the analyst, protects you, and makes any later instruction to omit data visibly improper. Keep the reply factual and free of commentary about the director. Also check whether the analyst was asked directly by anyone to drop it; if so, that changes the escalation route.

3. The director escalates: "High-load is out of scope, not our problem." What is your response and what is your next step?

Read the worked answer

Response: "Out of scope for the filing, agreed. Not out of scope for what we know. If we present 48 runs and say nothing about 12, we have made a statement about the full evaluation that is not true. One sentence fixes it and costs us nothing in the current filing. If the client later expands into high-load using this presentation as support, that sentence is the difference between a limitation and a misrepresentation."

Next step is procedural, not rhetorical. Confirm the instruction in writing, factually and without editorialising: "Understood that you want only standard-condition results presented. I am not able to present them as the complete evaluation. Please confirm in writing how you would like the 12 high-load runs described." A written instruction is a different matter from a verbal one, and the request to confirm often resolves it.

If the instruction stands, present the full data anyway with the scope stated, and inform your own manager or the quality function before the meeting, not after. The performance review is a real pressure and should be named as such only to people who can address it, never as a reason to comply.