PEGP Exam common mistakes
PEGP Exam · Understand the traps and how to avoid them.
Treating process validation as a single three-batch exercise that ends with a report, rather than planning a lifecycle approach with Stage 1 process design, Stage 2 qualification, and Stage 3 continued verification.
Older training material and many internal SOPs still frame validation as 'three consecutive batches prove the process,' so candidates reproduce that model and miss lifecycle language, continued process verification, and the role of risk assessment in setting validation scope.
What to do instead
Learn the three-stage lifecycle model as a framework: state what each stage produces (design space and critical parameter knowledge, PPQ with predefined acceptance criteria, ongoing monitoring with statistical trending). For any scenario question, identify which stage the situation describes before choosing an answer.
Confusing validation, qualification, and verification, and applying the wrong term to equipment, methods, and processes in scenario questions.
The terms overlap in everyday engineering speech, and candidates memorize definitions without mapping them to objects: processes are validated, facilities and equipment are qualified (DQ/IQ/OQ/PQ), analytical methods are validated, and verification is the broader confirmation activity.
What to do instead
Build a one-page mapping table pairing each term with its object and its typical deliverables, then practice classifying ten short scenarios. When a question names the object first, the correct term usually follows from that object.
Citing a regulation or guidance document by number or clause without stating what requirement it imposes, and inventing plausible-looking section numbers when unsure.
Candidates memorize document titles and alphanumeric identifiers as isolated facts, so under time pressure they retrieve a number but not its content, and the exam rewards the requirement rather than the citation.
What to do instead
For each key reference, write one sentence in your own words describing the obligation it creates and who it applies to. If you cannot recall a clause number, answer from the obligation itself; never fabricate a citation.
Answering deviation, change control, and CAPA questions by describing the corrective action only, skipping containment, root cause investigation, impact assessment, and effectiveness check.
Engineers gravitate to the technical fix, and exam vignettes are written so the technical fix is present but incomplete; candidates select it because it feels decisive and skip the quality-system steps around it.
What to do instead
Use a fixed sequence for every quality-event question: contain and assess impact on product and batches, investigate root cause with a stated method, define corrective and preventive actions separately, then verify effectiveness and update risk documents. Score each option against all five steps.
Treating GMP as a paperwork obligation and choosing answers that emphasize documentation completeness over product quality, patient safety, and data integrity.
Candidates who work in documentation-heavy roles internalize 'if it is not written it did not happen' as the whole of GMP, and miss that documentation is evidence of control, not the objective itself.
What to do instead
For each GMP question, ask what could harm the patient if the control failed, then pick the option that most directly prevents that harm while remaining traceable. Reframe documentation answers as 'evidence that the control was performed.'
Ignoring data integrity expectations around audit trails, raw data retention, and electronic signatures when answering questions about computerized systems and records.
Candidates focus on the functional purpose of a system (does it record the temperature) and treat audit trails and access control as IT details outside GMP scope.
What to do instead
For any computerized system scenario, explicitly check four things: attributable records, contemporaneous entry, original data preserved, and audit trail review enabled and reviewed. Eliminate options that permit shared logins, disabled audit trails, or overwriting of raw data.
Scaling a process by keeping one parameter constant (often mixing speed or impeller tip speed) without checking which scale-dependent mechanism governs the outcome.
Candidates memorize 'keep tip speed constant' or 'keep Reynolds number constant' as a rule and apply it universally, without considering whether the limiting phenomenon is oxygen transfer, heat removal, shear sensitivity, or blending time.
What to do instead
Before choosing a scaling rule, identify the rate-limiting mechanism and the parameter that controls it. State explicitly which quantities cannot be held constant simultaneously (for example tip speed and mixing time), then justify the chosen trade-off against product quality attributes.
Confusing mass balance with yield and ignoring losses, recycle streams, and accumulation when solving process and unit-operation calculations.
Candidates set up a balance on the main stream only, forget that unreacted material or solvent is recovered and returned, and double-count or omit the recycle, producing an answer that looks arithmetically clean.
What to do instead
Draw and label the flowsheet before calculating, mark every inlet and outlet including recycles, and write the balance around the whole system and around the reactor separately. Check that total mass in equals total mass out before trusting any derived number.
Choosing equipment or operating conditions from a single favorable property (highest throughput, lowest cost) without checking materials of construction, cleanability, and compatibility with the product and cleaning agents.
Design questions reward optimization instincts, and candidates treat cleanability and material compatibility as secondary details rather than hard constraints in pharmaceutical equipment selection.
What to do instead
Screen every equipment option against four gates before optimizing: contact-material compatibility, cleanability and drainability, containment of potent or hazardous materials, and suitability for the required cleaning validation. Only then compare performance.
Treating safety, health, and environmental questions as separate from process design, and answering with generic 'follow the SOP and wear PPE' responses instead of engineered controls.
Candidates compartmentalize EHS as a compliance topic, so they miss that the preferred answer is usually elimination, substitution, or engineering control, with administrative measures and PPE last in the hierarchy.
What to do instead
Apply the hierarchy of controls explicitly to each hazard scenario: can the hazard be eliminated or substituted, then engineered out (closed transfer, local exhaust ventilation, relief devices, interlocks), then administratively controlled, then PPE. Rank the options by position in that hierarchy.