The QA head has been with the plant since the first licence. She knows why the cleaning validation for one tablet product uses a different swab point. She remembers which vendor's excipient lot caused a dissolution failure years ago. She has walked every inspector through the site. Her retirement date is eighteen months away, and no successor has been named.
Plants across our drug and supplement manufacturing hub all have someone like her. What follows applies the method of our successor-building service to them.
Which roles carry the site's memory
- QA head: release decisions, deviation history, inspection memory and the reasoning behind SOPs.
- QC lab lead or senior HPLC analyst: method quirks, column history, out-of-specification investigations.
- Block head or production head in an API plant: reaction behaviour, yields by route, safe handling of tricky steps.
- Process or formulation chemist: why a granulation end point or coating spray rate was set where it is.
- Engineering lead for HVAC, purified water and compressed air: how the systems behave across seasons.
- Senior vaidya or formulator in a herbal unit: soaking, drying and boiling practice for each herb.
- Lead compression or encapsulation setter: machine feel that keeps weight and hardness inside limits.
What goes missing when they leave unplanned
SOPs record what to do. They rarely record why, or what happens when things go slightly wrong. When an experienced person retires without a plan, that why goes with them. The next deviation on a familiar product takes longer to investigate. A trend the old analyst would have spotted goes unseen. An inspector's question about a historical change gets an uncertain answer.
There is also a release risk. Some roles carry formal authority, such as approving batches or signing for a section. If no prepared successor holds the right experience and standing, decisions slow down while the plant looks for one.
Why plants leave it late
Talking about retirement can feel awkward, both for the owner and for the senior person. The successor candidates are usually busy officers with no time to shadow. And in a mid-sized unit there may be no obvious internal choice, so the owner postpones the decision until a resignation or a health scare forces it.
A succession plan in seven steps
- 1
List the critical roles
Shortlist the five to ten people without whom a batch, a release or an inspection would stall. Include engineering and lab roles, not only managers.
- 2
Rate each role
Likely exit window, whether a backup exists, and what share of the know-how lives on paper. A simple high, medium or low is enough.
- 3
Talk openly with the senior person
Agree the retirement timeline, what they want their last years to look like, and their part in preparing a successor.
- 4
Pick a successor plus a reserve
For each critical role, a likely successor and a second name. Say whether each is ready now, ready in a year or two, or further off.
- 5
Give the successor real ownership
Lead a validation, own a CAPA, run part of the next customer or regulatory audit, or chair the deviation review. Development happens through work, not only courses.
- 6
Capture the unwritten know-how
Product history files with past deviations, change reasons and troubleshooting notes. Recorded walk-throughs of instruments and systems. Annotated copies of key SOPs.
- 7
Plan the overlap and the handover
A period where both work side by side, then the successor leads with the senior available. Sort out authorisations and named-person records months before the farewell.
Role: ______ Current holder: ______ Expected exit window: ______.
Why it is critical: batch / release / inspection / system knowledge.
Know-how written down: high / medium / low.
Successor: ______ Readiness: now / one to two years / later.
Backup: ______ Readiness: ______.
Ownership given to successor this year: ______.
Knowledge capture items: product history files / walk-throughs / annotated SOPs.
Authorisation or licence changes to discuss: ______ With: ______.
Overlap start: ______ Review date: ______.Smaller and herbal units
In a small plant, the successor may not exist internally. Then the plan is to recruit early, while the senior can still train the newcomer. In herbal units the senior formulator often holds treatment knowledge for every herb in memory; succession for herbal product units treats that case. Before choosing successors, map who can do what; competency mapping in tablet plants shows a format.
Keeping the successor
A successor who is named but not told, or told but not paid differently, may leave before the handover. Tell them plainly what they are being prepared for and when. Adjust title and pay as responsibility moves, not only on the day the senior retires. Review progress every quarter with both people present.
The everyday version of this risk, where process know-how rests with a handful of seniors, has its own post. To map critical roles and successors for your site with us, sketch your blocks and lab on our brief form.



