Sr Manager, QSE KORE Optimization & Systems Governance

The Senior Manager, QSE KORE Optimization and Systems Governance is accountable for the end‑to‑end KORE optimization, governance, maintenance, change management, and integrity of KORE requirements documentation and mapping within the QSE Quality Management System (QMS). This role ensures that corporate QSE requirements, specifications, and standard methods are current, clear, risk‑based, and fit‑for‑purpose, while remaining aligned to business needs and regulatory expectations.  The role serves as the corporate authority for requirements coherence, ensuring that Operating Unit (OU) requirements and Bottler requirements align to corporate KORE expectations, with clear guardrails, controlled deviations, and consistent application across the system. The role enables “freedom within a framework” while protecting enterprise risk, brand integrity, and license‑to‑operate. 

Scope & Impact 

• Global ownership of corporate QSE requirements within KORE 

• Governance authority over OU requirements alignment to corporate standards 

• Direct impact on Bottler, Co‑packer, and Contract Manufacturer compliance expectations 

• Key contributor to governance effectiveness, audit outcomes, continuous improvement and system simplification 

Key Responsibilities 

1. Corporate KORE Requirements Lifecycle Management 

• Own the revision, maintenance, and optimization of corporate KORE requirements, specifications, and standard methods across Quality, Food Safety, Environment, and Safety domains. Owns Document Change Request system & process. 

• Ensure requirements remain fit‑for‑purpose, risk‑based, and aligned to evolving business models, innovation, and regulatory landscapes. 

• Lead structured periodic reviews to eliminate duplication, retire obsolete requirements, and simplify requirement language and structure. 

• Execute KORE optimization and document mapping to strengthen requirements coherence, traceability, and usability across the QSE QMS. 

2. Governance of Operating Unit (OU) Requirements 

• Serve as the corporate governance point for OU requirements, ensuring alignment to KORE while enabling local applicability. 

• Define and enforce guardrails for OU‑specific requirements, including:  

• What OUs may add vs. what must remain corporate‑controlled 

• Structure, taxonomy, and traceability back to KORE 

• Lead the Document Change Request process for OU Requirement Review of material changes, ensuring transparency, consistency, and risk‑based decision‑making.  

3. Bottler & Contract Manufacturer Requirements Alignment 

• Ensure Bottler, Co‑packer, and Contract Manufacturer requirements remain fully aligned to corporate KORE expectations and are not used to bypass corporate standards. 

• Partner with Legal, Supply Chain, and OU teams to ensure KORE requirements are correctly translated into contractual, authorization, and governance mechanisms. 

• Maintain clarity on non‑negotiable corporate requirements versus OU execution models. 
   

4. Publication, Change Control & Traceability 

• Own the end‑to‑end publication process for KORE requirements, including approvals, version control, effective dates, and structured change communication. 

• Ensure governance content hygiene, versioning discipline, and lifecycle management (creation, review cadence, approval, retirement/archiving) across KORE requirements and related governance artifacts. 

• Lead KORE change management for governance content updates, including stakeholder engagement, release planning, communications, and adoption support. 

• Ensure clear traceability between:  

• Corporate KORE requirements 

• OU requirements 

• Bottler and supplier obligations 

• Support audit readiness by ensuring requirements are accurate, current, and consistently referenced across governance documents.  

5. Stakeholder Engagement & Governance Enablement 

• Act as the primary corporate contact for KORE requirements interpretation and governance. 

• Partner with Governance, Technical Risk, Audit, Digital, and OU leaders to resolve requirement gaps, ambiguities, or overlaps. 

• Support capability building through guidance, FAQs, and structured interpretation materials. 

Digital Skills Required (New‑State Expectations) 

This role is not a digital product owner, but it does require strong digital fluency aligned to modern enterprise QMS operations: 

Required Digital Capabilities 

• Proficient use of enterprise QMS and requirements management platforms (e.g., structured content libraries, metadata, taxonomy). 

• Ability to manage version control, traceability, and structured publishing workflows. 

• Comfort working with data‑enabled insights (usage, adoption, audit trends) to inform requirement optimization. 

• Ability to translate governance and risk intent into digitally consumable, user‑centric content. 

• Own platform analytics, IMCR data integrity, and continuous improvement by monitoring data quality, usage/adoption insights, and governance KPIs to drive targeted optimization actions. 

Not Required 

• Software development, AI model ownership, Product backlog management 

Expected Mindset 

• Digital‑first thinking applied to governance, Strong appreciation for usability, searchability, and system scalability 
   

Qualifications & Experience 

• Bachelor’s degree in Quality, Engineering, Food Science, Environmental Science, Safety, or related discipline. 

• 8+ years of experience in QSE governance, quality systems, standards management, or enterprise management systems. 

• Demonstrated experience working across corporate, regional/OU, and Bottler environments. 

• Strong understanding of ISO‑based management systems and regulatory frameworks. 

• Bold and courageous communication style and competency 

Success Measures 

• KORE requirements are current, coherent, and clearly differentiated from OU and Bottler execution requirements 

• Reduced duplication and inconsistency across corporate and OU requirements 

• Clear traceability and governance of requirement changes 

• Improved audit clarity and reduced findings linked to requirement ambiguity 

• Strong stakeholder confidence in KORE as the single source of truth