What are the core components of a food safety management system (FSMS) and how do they relate to the PDCA cycle?

• A. HACCP, training, and audits
• B. Plan-Do-Check-Act to improve
• C. Prerequisites, HACCP, training, records; PDCA cycle: plan, do, check, act to improve
• D. Inventory management and ordering

Answer: (C)

The main idea is that a food safety management system combines foundational operational controls with a structured, ongoing improvement loop. The strongest answer includes prerequisites (the basic conditions that must be in place for safe operation), HACCP (the formal hazard analysis and control plan), training (ensuring people know what to do and why), and records (proof and traceability of what happened). All of these elements work together within a Plan-Do-Check-Act cycle to drive ongoing improvement.

Prerequisites set the stage by establishing clean, well-maintained facilities, proper pest control, supplier approval, sanitation programs, and other basics that prevent hazards from even arising. HACCP provides a systematic method for identifying potential hazards and determining where controls are needed to prevent, eliminate, or reduce risks to acceptable levels. Training ensures staff have the knowledge and skills to carry out the procedures and follow the controls consistently. Records capture what was done, evidence of monitoring, verification, and corrective actions, and they support accountability and continuous improvement.

The PDCA cycle—Plan, Do, Check, Act—slots neatly on top of these components. Plan involves designing the FSMS elements (PRPs, HACCP plans, training plans, and record-keeping practices). Do is the execution of those plans in daily operations. Check means monitoring performance, reviewing records, and verifying that controls are effective. Act is making adjustments based on what the checks reveal, updating procedures, retraining staff, or enhancing preventive measures. This cycle keeps the FSMS dynamic rather than static, ensuring safety practices evolve with new hazards, processes, or regulatory expectations.

Why the other options don’t fit as well: they either miss key FSMS components like prerequisites or records, or they overemphasize the cycle without tying it to the full set of foundational elements. They also don’t explicitly connect the practical components to the continual improvement loop that truly defines how an FSMS operates.