GRAIL · Function papers
What does an AI-augmented quality and sustainability function look like?
By Johan Grönstedt · Last reviewed
The system remembers. The person determines. This is a nine-page position paper, free.
An AI-augmented quality and sustainability function turns procedures, findings, incidents, evidence and lessons into an operating memory that improves every investigation, audit and control decision. The system connects the record and carries learning forward, while accountability for findings, approvals and action stays with the person. The memory becomes institutional.
The operating day
A day in The operating memory as a loop
Most management systems describe the company periodically. They do not help it operate daily. An operating memory forms as each event moves through a connected loop, from the first report to evidence about whether the response worked.
Report
Site events arrive through mobile forms, voice notes and connected systems.
Connect
Structures the record, retrieves similar cases and directs urgent items.
Investigate
A chronology, comparable cases, missing facts and possible causal factors.
Decide
Challenges the suggestions and determines the finding.
Learn
Later evidence shows whether recurrence fell or the control remained weak.
Division of work
What runs, and what stays with the person
The agent layer prepares the record around the decision. It maps controls to evidence, builds chronologies, retrieves related cases, detects conflicts and proposes questions or causal factors. Across the processes, its work is to keep approved information current, connect records that belong together and surface gaps before formal review.
The person remains responsible for judgment. Auditors observe work and determine findings. Process owners determine causes and judge whether an action worked. Document owners approve content and operational change. Safety professionals control incident classification and response, while metric owners approve figures and every external claim.
That split creates continuity without moving accountability. The system can remember across procedures, sites, cases and reporting cycles. The responsible person still tests the evidence, challenges the proposal and makes the decision.
Elsewhere, the same pattern applies. External audit records are assembled and gaps flagged before the management representative confirms formal statements. Supplier records are combined before quality and procurement decide the response. Customer complaints are linked to production failures before quality and engineering determine containment and root cause. Changed procedures identify affected roles before managers determine competence, while regulatory changes are compared with controlled registers before legal and technical owners decide applicability.
| Process | What the agent layer does | What stays with the person |
|---|---|---|
| Management system and internal audits | Maps clauses to controls and evidence, proposes samples and questions, records contradictions and drafts findings | Auditors observe work, test control effectiveness and determine findings |
| Non-conformance and corrective action | Builds a chronology, retrieves similar failures, proposes causal hypotheses and tests whether the action addresses the stated cause | The process owner determines the cause, approves the action and judges whether it worked |
| Document and procedure control | Answers from approved versions, detects conflicts and proposes affected documents when a process changes | Owners approve the content, effective date and operational change |
| Incidents and near misses | Turns mobile or voice reports into structured drafts and flags severity indicators, similar events and missing facts | A safety professional controls classification, investigation and response |
| Sustainability data and questionnaires | Maintains approved claims, metrics, methods and evidence, then drafts cited questionnaire responses | Metric owners approve figures, calculation choices and every external claim |
The position
Six things GRAIL believes
These beliefs put the emphasis on control effectiveness, operating evidence and accountable decisions. Together they describe a function in which the record develops as the work happens and learning remains available to the next investigation, audit or review.
The certificate is the floor. Control effectiveness is the ceiling.
A function can pass an audit while recurring failures remain hidden across sites and systems.
Operating memory is more valuable than document search.
Finding the right procedure is useful.
Continuous assurance changes what auditors do.
When evidence is prepared as work happens, auditors no longer need to spend their attention reconstructing the record.
A proposed cause is not a finding.
The workflow can build a chronology, retrieve similar cases and suggest causal factors.
Sustainability reporting starts in operations.
A separate spreadsheet season is a symptom of disconnected invoices, meters, purchasing records and supplier data.
The function leader has to redesign the rhythm.
Giving people a drafting tool while leaving audit preparation, management review and action chasing unchanged only adds another layer.
These six beliefs do not argue for replacing accountable people. They argue for giving them a complete memory, earlier signals and more time where the work happens.
Get the paper
Read the full position on how operating memory changes the quality and sustainability function.