(Lecture 2.) Week 1 argued that a method is a hypothesis about a molecule and that the discipline is built to revise it when the evidence says so. This week asks three questions that sit underneath everything else in the course: how does an analytical method actually get developed and regulated, what is actually being made, and how much evidence is enough? The third question is risk — assessed explicitly, not by reflex — and it’s the one this week is named for; the first two are the ground it stands on.
A control strategy cannot be designed in the abstract — it is designed against a specific molecule, made by a specific process, measured by a method developed and validated for that purpose, with its own population of things that can go wrong. Before the course can teach how you measure something and how you control it, it has to teach what you are holding and how the method that measures it came to exist — then it can teach how much evidence is enough.
Every technique week for the rest of the term assumes a method already exists. This section is the one-page version of how it got there, so that assumption is never invisible:
| Stage | What happens | Ties to |
|---|---|---|
| Analytical target profile (ATP) | State the requirement — analyte, matrix, range, accuracy/precision — before any column, wavelength, or probe is chosen | Q14 |
| Development | Scout and optimise against the ATP, not against “does it separate” | Taught in full at Separation Methods, the pattern generalises to every technique |
| Validation | Specificity, linearity, range, accuracy, precision, LOD/LOQ | Q2(R2) |
| Transfer | The same answer in every receiving lab | Week 1 · QC |
| Lifecycle | Monitored and revised over its life; what counts as a reportable change is itself a risk decision | Q12, Q14 |
The regulatory expectation — captured in ICH Q14 — is that a method is designed against its validation targets and its analytical target profile from the start, not developed first and validated as an afterthought. Every worked method later in the course (chromatography, mass spec, spectroscopy) follows this same lifecycle; this is the only week that names it explicitly end to end.
Two more questions sit underneath every technique week: what is actually being made, and how much evidence is enough? Both get their own full treatment this week, in their own sections:
Three of the technique weeks later in the term — atomic spectroscopy, molecular spectroscopy, mass spectrometry — carry a risk-assessment assignment: take the method taught that week and build a method FMEA against a stated analytical target profile. The point is repetition: by the third checkpoint, scoring detectability should be a habit.
Nobody hands you the modality landscape or the method-development lifecycle on day one — you infer them from the job posting, the SOPs on the shelf, and the first specification you’re asked to read. And in almost every method FMEA, the analyst is the only person in the room who knows the true detection score. A project manager can estimate severity; a process chemist can estimate occurrence; but whether the current controls would actually catch a failed extraction, a mis-integrated peak, a drifting calibration, or a co-eluting impurity before it reached a release decision is analytical knowledge, and if the analyst rounds it toward “we’d probably catch it,” the whole assessment is quietly wrong.
This is the STEAM “A” again: judgment about what the evidence can and cannot rule out. The refrain for the term — science → evidence → reduced uncertainty → control → regulatory confidence → patient trust — runs through method development above, and through the modality landscape and risk management in the sections that follow.
Source note. Method-development framing follows ICH Q14 and ICH Q2(R2). See the modality landscape and risk management for their own sourcing. (Instructor: this session now absorbs what were two separate lecture weeks — confirm the pacing works in a single 3-hour slot.)
Before any technique week makes sense, the course needs to answer what is actually being made: a small molecule, a large molecule / biologic, and an advanced therapy compared side by side — size, manufacture, what “the molecule” even is, what purity means, and why small molecule dominates entry-level hiring.
ICH Q9(R1) as a loop, not a form: the risk-management toolbox (FMEA, FTA, HACCP, HAZOP, risk ranking and filtering, Ishikawa/PHA), FMEA in action, and how a risk assessment becomes a control strategy — worked through the nitrosamine risk assessments.