ANONYMIZED CASE · CPG
Living quality documents connected to the process
A leading mass consumer goods organization validated Quality Document Management for CPG over the documents of its Quality Management System —SOPs, work instructions, policies, procedures and evidence— connecting them to the plant, the process and the accountable role, without taking the files out of the official repository.
The validation showed that the solution works over the client's operation and the value it delivers: published, current and traceable documents, with evidence ready for audit.
The challenge
In a consumer-packaged-goods manufacturer with several plants, the document-based Quality Management System exists and is usually well organized. The problem is not a lack of documents: it is that the QMS lives in a dedicated space of the official repository, isolated from the rest of the operation.
- The QMS lives separate from the process: an SOP is classified by plant and with a signer, but it does not appear next to the operational process that uses it nor to the control it backs.
- Basic questions are answered manually: which is the current version for this plant today, who approved it and what changed, which evidence backs this control before an audit.
- The plant operation works with local copies: the operator downloads the SOP once and runs with a version that may be expired.
- The audit is reactive: preparing evidence is a project for each audit, not a continuous state.
The QMS is not sustained with documents. It is sustained with documents that are published, current, approved and connected to the process.
The EAFlow solution
Quality Document Management for CPG is a vertical accelerator (CPG) built on the cross-cutting solution Document Governance & Evidence and the common Operational Graph layer of the EAFlow Operational Graph Platform, operating over the client's official repository (SharePoint or Drive) —without migrating files. The validation covered, over the documents of the client's QMS:
- Each document connected to the plant, the process and the accountable role. An SOP, work instruction, policy or piece of evidence stops being an isolated file and becomes associated with the plant or line, the process that uses it and the current status.
- Governed document flow with traceable review, approval, publication and withdrawal, signed by the correct role. Only what is approved gets published; obsolete versions are withdrawn without losing the history.
- Versioning with comparison between versions: what changed, not only when.
- Data Room and Auditor Mode: the external auditor sees the current version, the published evidence and the approval history, without opening the full repository or seeing drafts.
- Plant operation with QR codes always pointing to the current version of the day.
- Document chat with Max over published evidence: it answers in natural language citing the document, the version, the signer and the linked process —never over drafts or withdrawn versions, always with human control.
- Document-risk reporting: expired or about-to-expire documents, critical ones not published, missing evidence, reviewer workload and exposure by plant.
The connection to the official repository is established by scope agreed in discovery (the client's libraries, sites and permissions). The accelerator operates over the official repository, without replacing it or migrating the files.
What was validated
The experience was run over the client's official document repository and the QMS documents. The Quality team went through the full lifecycle: connecting existing documents, classification by plant/type/process, governed review and approval, publication with evidence, plant operation with QR, Data Room and Auditor Mode, version comparison, document chat with Max and three-level reporting —with three concurrent roles (Document Owner, Quality Manager, Auditor) over the same governed repository.
Demonstrated capabilities
- Operational Graph as the common context foundation.
- Traceability document ↔ process ↔ plant ↔ accountable role ↔ version ↔ evidence.
- Document governance with traceable human approval.
- Versioning with comparison between versions.
- Data Room and Auditor Mode for continuous evidence.
- Natural-language queries over published evidence, with citation to source.
- Document-risk reporting by plant and by status.
Observed outcome
The validation made it possible to verify the use of EAFlow to modernize quality document management: the document-based QMS moved from "having the files" to having documents that are published, current, approved and connected to the process. Audit evidence stopped being a project for each audit and became continuously available; the plant operation accesses the current version via QR instead of local copies; and quality questions are answered from published documents with citation to the signer and the process.
The validation confirmed that the accelerator governs quality documentation over the client's official repository, connecting it to the rest of the operation.
Why it matters for other organizations
The pattern repeats in consumer-packaged-goods manufacturers and manufacturing in general: the QMS exists and is well organized, but it lives as an island. Connecting it to the process, the plant and the evidence —without migrating files or replacing the official repository— reduces audit risk and day-to-day risk on the plant floor.
Starting with quality documentation is also a low-risk entry point: the same Operational Graph that sustains the documents later sustains risk, processes and operations.
How it scales — related solutions
The published document evidence is reused on the same Operational Graph:
- Toward processes Process and Architecture Modernization / Process Knowledge
Documents become part of the process corpus; a process change shows which documents get updated.
- Toward risk and control Risk & Control Assurance
A control stops listing "loose documents" and shows the current version, the signer and evidence traceability.
- Toward service operations Operational Graph for Service Operations
When a ticket closes, the evidence backing the closure is a published and traceable document.
- Toward continuity Operational Continuity & Resilience
Plans (BCP, DRP, contingency instructions) are governed with the same discipline.